Maybe this might help someone at some point. Maybe everyone has already figured this out already...but this has helped me now both on the Mac and PC when a plug in preset has become corrupted somehow and prevents the host project from reloading. This has happened to me several times, so I can't imagine I'm the only one.
Try the following if the project just won't load. Remove the offending plug in (or maybe just try different ones by trial and error) from the vst (or au) folder so that it can't load. You'll get an error when you find the correct plug in, but the project will load. You'll have to recreate the patch for that plug in, but that's surely better than losing the whole project.
This just happened to me with Karma FX in Traction, dammit. But at least I can get back the project without Karma FX. Stupid me for not making backups.
Maybe others have discovered other approaches. I hate losing stuff this way...
Ways of retrieving a corrupted project
-
- KVRian
- 1032 posts since 2 Aug, 2004
-
- KVRian
- 1215 posts since 17 Apr, 2004
That is what I do too; I just delete the plug and then load the project. Save the project without the plugin (but with midi data intact). Then I reinstall the plug (this usually solves the prob) and recreate the patch.
:: 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 ::
-
- KVRian
- Topic Starter
- 1032 posts since 2 Aug, 2004
Well - yeah - when it happens you just want to throw the computer out the window ...Jafo wrote:Sound advices indeed. Completely obvious once you think about it for a while, but not while it's happening!
But I had never seen anyone actually mention this technique, so while it may be obvious to some more experienced people, maybe someone will remember it and it will help them in a time of utter despair
-
- KVRAF
- 2285 posts since 20 Dec, 2002 from The Benighted States of Trumpistan
Definitely one for the FAQ. Once we organize enough to write one, that is! 
Last edited by Jafo on Sun May 15, 2005 1:48 pm, edited 1 time in total.
Wait... loot _then_ burn? D'oh!
-
- KVRist
- 157 posts since 15 May, 2005
A shortcut to this (if the plugin that causes the error is not known) is to rename the VSTPlugins folder where the third party plugins are placed. That will give some confindence that the fault is with a plugin.