An error occurred while reading the flp file fl 10

Or is it just something thats impossible and I'm going to have to move on from? Response to Corrupt FLP file!? Want a cool TF2-based and Minecraft gaming forum? Check us out WDZClan. We're the largest pub TF2 community on Steam! Did you try this?

Member since: Oct. Posted March 14, Steve Laboy's Fix: 1 Load up your corrupt FLP file into fruity loops The corruption error will show, fruity loops will be crippled, and your song doesnt show up. Thank Steve! Posted March 30, Tricklozen Posted April 13, Posted April 13, Using the data from the original file in question:.

Mia Posted May 29, Posted May 29, I think our file might be totally hosed. I tried to fix it but didn't get anywhere. Here's the corrupted file: Posted March 22, Legion Posted May 25, Posted May 25, I Dunno LOL! SprinterBot Posted August 4, Posted August 4, Thanks Legion! Posted August 27, I am very grateful. Meteo Xavier Posted August 30, Posted August 30, MonLifeStrolling Posted May 20, Posted May 20, Leno Posted May 19, Posted May 19, I've been working on this song for DAYS and out of no where today I was going to open it to save it as an mp3 and finally be done with the song but I get this message saying: "An error occurred while reading the flp file It maybe corrupted or some plugin caused an error while opening" Idk what to do, I've looked everywhere and I have yet to find anything.

I think I'll die if I have to redo the song over again. Response to Help Corrupt Flp File You might want to check inside of THIS thread. Otherwise, check to see if all the vsts you use in your project are still functional, or if they got moved to another folder. Ars longa, vita brevis. SoundCloud Versilian Studios Facebook. Edit: it turns out those two bytes are a pointer to an address 22 bytes from the end of the file, consistent among all files I looked at.

I believe this is due to the really sloppy way FL handles files With such small files it works, I guess, it's just weird. So what happened in my case was that the pointer to the "end" of the file was really pointing to the very first byte, before the start of data.

I imagine that confused FL. Edit 2: to get the correct pointer address see Edit 1 , look at the end of the file. Look at the last byte of your file. That's byte 1 for our purposes. Let's say the end of your file looks like this:. Starting with the last byte and counting backwards, find byte 22 from the end of the file. In the example, that's the "31" in the first line. This is where you need to point. Now look at the address of that line: ah the "h" stands for Hexadecimal.

The byte "31" occurs in the fifth position of that line counting bytes from the left, like so :. Note that there are 16 bytes per line, and this is in hex, so if the byte you're interested in happens to be the last one on a line, its "number" is F. Add that to the line's address to get a The last four characters representing two bytes are the address we want: A1 I don't remember my assembly programming enough to recall why, but these need to be reversed for pointer purposes EDIT 3: it's because Little-endian systems e.

So now we have the byte string "55 A1". Go back to the top of the file. The second line which is always address h Must begin with "64 74" on the left corresponding to "dt" on the text side. The next two bytes are the address pointer you just got. Overwrite whatever two bytes come after "64 74" to get "64 74 55 A1" as the first four bytes of the second line in the file.

If it still doesn't work, you're fucked. This brought back all of my instruments with intact settings, and all of the patterns I had written. Unfortunately, the Playlist pattern data how you build different patterns together--don't know the right terminology was lost, but all the parts are there and all my pattern labels were still on the playlist. In any event I'm happy it will only take me a few hours to rebuild the playlist data instead of having to start from scratch.

So if you have a corrupt FLP that has data in it i. I don't know if it will work on FL 6. I'll keep comparing FLPs and post anything else I learn about the format, but at this point I'm just happy I got my shit working again.

So I'll probably get lazy. You people are way too brilliant for me. Wow - this is pretty major work you're doing! A lot of people will want to know about this - we have to make sure the word gets out! Thanks for taking the time to sleuth around and not just letting the corruption slide.

Still, I wouldn't rely on this as a method of protecting your FL project files.