FL problem... help?

Audio Plugin Hosts and other audio software applications discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

hi
has anyone managed to find a way to avoid corrup .flp's?
I know it's a problem that many people have, ie: working on a track, and just when it gets really really good, all of a sudden it won't open in FL anymore :mad:
anyway, with all the reports over the years of this happening, i was wondering if anyone had figured out a safe-guard?

here's my process of elimination so far:
-i never save after loading a plugin causes an access violation error
-i never save after trying to preview / load a sample causes an access violation
-i never save if there has been a prolonged (over two seconds) audio glitch, or any other unexplained wierdness - this last one almost never happens anyway, but if it does, i just close without saving, and take the loss in stride. I do the same when the first two happen, wich is really quite often unfortunately, at least with VSTis.

So, am i missing something? Is there anything else that i can do???

I have just lost another one that i was really happy with, and unfortunately the backup is f**ked too; since I have no idea how to predict when this is going to happen, there is usually a good chance that my backup will also be corrupted.

any tips would be much appreciated.
FL is the only host that has ever done this to me since Creator on the Atari; But it is also my most productive music making environment, and they keep adding really f**king great features :mad: otherwise i would have said "f**k it!" a couple of years back.

-g
resistors are futile you will be simulated
Soundcloud
T4M

Post

remember, it's never too late to say 'f**k it'.

I kid, I love FL. :hihi:

You can submit your corrupt FLs to the people at IL, they may analyze and repair it if possible. Other than that, the precautions you are taking are good enough, I guess.
Image
:: FL Studio v9.0.3 :: u-he Zebra2 v2.5 :: u-he MFM v2.0.2b5 :: u-he Uhbik v1.1 :: EnergyXT v1.4.1/v2.0.2 ::

Post

Sorry can't help,I don't get corrupt .flps :shrug:

What plugins are you using?
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe

Post

Save to two different copies and alternate between them when saving

Post

Obviously, save frequently so if it corrupts, you can pull another version out of the FL Trashbin.

Also, when an .flp is corrupted, try removing your vST plugins folder and loading the song; if it loads, you can put the plugins folder back and try manually removing plugins until you find the problem one.

Edit: your techniques are kind of faulty, though. What I'd do is, if I notice the access violation, save it and then check it (so I can open the trashbin file if need be) or save a new version.
Image

Post

hmmmm...good point, toxicator. that could help me save some work.

and what is this trashbin you speak of??? :lol: been using FL since V3.5, and i never heard of it! sheesh, not the most observant of FL users am i?
resistors are futile you will be simulated
Soundcloud
T4M

Post

yea definately move all VST plugs u used in the project to another location temporarily - that might fix it...

Post

Z3R0T0N1N wrote:hi
has anyone managed to find a way to avoid corrup .flp's?
ctrl+N :hihi:

Post

I've been using FL for just about 2 years, including the public beta versions. I have upwards of 600 .flp files on my hard drive.

I have not had a single corrupt .flp file.

what the hell are you people doing?

Post

Z3R0T0N1N wrote:and what is this trashbin you speak of??? :lol: been using FL since V3.5, and i never heard of it! sheesh, not the most observant of FL users am i?
|

Inside the FL folder there's a folder called "trashbin" whenever you save something, it doesn't delete it, it moves the older version here. It will only do one of each filetype (.flp, .fst) but if you realize your save was corrupted you can go here and pull out the "backup.flp" file to retrieve the version you saved over.

Hope this helps,

Tox
Image

Post

My method is, create a Folder structure that looks like this:

C:\FL Projects\Song1\Song1.flp

Then just save the project as many times as I need with the CTRL + N shortcut. That way if anything happens to my project, I can go back to the previos project. Sometimes I end up with 20+ FLP's, but its a really helpful when the infamous corrupt FLP file occurs. Just my 2 cents...

Post

ctrl+n?
cool. i thought that would start a new project... so it makes a new copy of the current one?

thanx for your help, guys.

for those that are saying you have not exerienced this problem, i envy you. i am happy that you haven't, and i hope you never do. But if you have any really excellent tracks that you have not backed up, i would follow some of the suggestions here just in case. This is a problem that has cropped up time and time again for MANY FL users, since at least V3.5. The authors have not been able to find any reason for it, so who knows why it happens.
kode_poet: that is a very good idea you have, and i think i will try doing that from now on. :D
I really love FL studio, so anything that will help me keep using it is a good idea. :D
resistors are futile you will be simulated
Soundcloud
T4M

Post

Yeah, CTRL + N is very useful, instead of overwriting the file, it saves a new copy of it and adds and underscore and a "version" number to it... so if for example, original project is Song.flp, pressing CRTL + N will create Song_1.flp, Song_2.flp and so on.

Post

VladimirDimitrievich wrote:I've been using FL for just about 2 years, including the public beta versions. I have upwards of 600 .flp files on my hard drive.

I have not had a single corrupt .flp file.

what the hell are you people doing?
i reckon - im exactly the same - probably close to 1000 flps on my computer and never had issues (save a couple with some reeeeeeeeeeealllly dodgy free synths, which was fixed by moving the synths)

Post Reply

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”