Why did this happen?!?

[SessileNomad]

ive been working on a song for a while, like a month now, which is kinda long for me

anyways i go to my computer and open the file, and ALL of the patterns are gone, all of the effects are gone, and the .flp locks up after about 2 minutes of trying to figure out what the hell is going on

the only thing i still have in it is are the instruments

why the hell did it have to be the one .flp ive been working on for so long now, all other .flps are working fine...

has this happened to anyone b4 or know why it happened so i can possibly avoid it?

i had a rendered mp3 of most of the song, but i cant write up the intro or outro now, cuz all of the EQing, compressing, and all of the effects i used in dBlue Glitch are all gone, so ill probly jsut end up submiting it and stop in fl for a while, get back into the grove of a regular instrument

[Rig]

Did you download anything suspicious?

[SessileNomad]

At 10/21/09 08:43 PM, Rig wrote: Did you download anything suspicious?

nope, ive been using the same setup for months now

[Box-Killa]

Did you delete any samples?
Delete any vst's?
Install any new vst's?
Move any files in fl?
Save over the file?
virus scanner delete?
someone else used the computer?
check your recycle bin?

always back up your song at least twice, especially if you have been working on it for a long time :D

[nal1200]

Not sure what happened, but it would be wise of you to no longer rewrite the same .flp file every time you save.

Simply "save as new version" each time you make drastic changes to the project file. You'll be glad you did.

[sorohanro]

Also I had this problem in FL and in Mu.Lab, quite weird because those programs are different. I figured out that the error was because of a broken VST, I removed it and problem disappeared from both programs.

[SessileNomad]

At 10/21/09 11:40 PM, nal1200 wrote: Not sure what happened, but it would be wise of you to no longer rewrite the same .flp file every time you save.

Simply "save as new version" each time you make drastic changes to the project file. You'll be glad you did.

sorry for bumping the old thread but i figure i should reply since i started the damn thing

yes i will def. start doing this on a regular basis, cuz i honestly dont want to quit FL out of rage if it happens again

Did you delete any samples?

nope

Delete any vst's?

nope

Install any new vst's?

nope

Move any files in fl?

nope

Save over the file?

well yeah, but with the actualy file, if you mean with a different file..no

virus scanner delete?

no i dont run a virus scanner, my FL pc isnt connected to the internet so im pretty safe from viruses

someone else used the computer?

nope

check your recycle bin?

i guess ill check it but i doubt the uncorrupted file is in there

Also I had this problem in FL and in Mu.Lab, quite weird because those programs are different. I figured out that the error was because of a broken VST, I removed it and problem disappeared from both programs.

i have had this happen a very long time ago, but ive been using the same vst's forever now and they all still work fine

thanks everyone, ill be sure to make backups from now on

[joshhunsaker]

Sadly - sometimes FL Studio (and really any DAW I've used except Reason) is on very rare occasion (not so rare with FL) prone to corrupting the original source file so that the file is either irreparable, unopenable, unrecognizable or significantly altered. It can happen with really any activity - usually involves however adding certain vsts/dx plugs or even trying to delete them in a certain fashion.

The only thing you can do is save multiple copies (think "songname1", "songname2", "songname3", etc.) simultaneously (save at least 2 identical copies by renaming) so that it would unlikely that both could become corrupted at the same time. This is really the only workaround. Sometimes data on the computer can just become corrupted for no good reason. It happens, electronics fail and can be very odd at times - just the nature of the beast.

I started this practice a number of years ago after having a number of such occurances on my own computer (they happen still from time to time but I'm very good about backing stuff up now).

[Meonly70]

Upgrade to the Newest FL. FL 9 is out now.

[iceblueglow]

its probably an good idea to look if the audio driver is messing up. my driver did that so many times. the best thing to do is to use fls own drivers if possible. otherwise, it happens alot at my laptop. best thing to do is make multiple copies like joshhunsaker said.

[kelwynshade]

At 10/21/09 11:40 PM, nal1200 wrote: Not sure what happened, but it would be wise of you to no longer rewrite the same .flp file every time you save.

Simply "save as new version" each time you make drastic changes to the project file. You'll be glad you did.

This is pretty much the truth if you're getting pretty serious into a track. In all honesty, which I need to be better about myself, you should create entirely new folders for each track and get used to saving as new versions inside each individual song folder. This really helps incase you want to go back to an earlier version or if an instance like this happens and your file takes a knife to its own throat.