Whenever I open a specific FLP, it seems to load and open fine but FL Studio is just frozen and unresponsive after. I can't click anything, none of the buttons are highlighted when my cursor goes over them and my only option is to force quit it in task manager. I recently updated FL to the latest build (3517) but when this problem first occurred I downgraded it back to build 3399. I've tried using the tool for recovering an FLP in the diagnostics window but it just created a blank file which can't be read by FL Studio. How can I fix the FLP or FL Studio?
#FL Studio Unresponsive on project open
1 messages · Page 1 of 1 (latest)
someone please help
don't know if it got rid of it when you changed FL to some build but look at the backup folder?
maybe you'll be able to find it there if you haven't done much stuff since that flp
all of the backups do the same thing
This video will show you how to recover/fix a corrupt FLP project in FL Studio. FL Studio projects can sometimes crash or become corrupt. This method can help you fix those currupted FLP projects. You can use this repair and diagnostic tool to repair a project that has become corrupt. A corrupt project will typically cause FL Studio to crash ins...
did you try this?
nah
iwill
ive done the method in this video many times but still nothing works
i even removed all of the plugins and the "recovered" flp has a frozen playhead when I try to play it
When did that specific flp start to act up?
did you add some plugin and that's when it happened?
are u using the 64bit version?
send me that flp as a zip, I'll try to open it
i guess u cant save it as zip since fl freezes
just send the flp then and I'll try to open it
it's works for you?
yeah, I can play it as well
did you try to open what I sent?
np, glad I could help you retrieve some of it
what's your ram and cpu load at
it's low considering the fact that most of the vsts aren't loading
it crashed after trying to undo a change to an audio clip
@11eee#3487
Have you tried using the diagnostic tool to fix it?
Yes, it's already fixed. Thanks.