Robert Lane
July 20th, 2010, 10:45 PM
If you've used any version of FCP long enough you'll eventually find that at some point, when you launch the application that some or all of your preferences and even recent projects go missing and have to be manually reset/re-located. This occurs to all of us, even those like myself who go the extra mile in keeping things like the OS and the base-code platform clean and maintained.
After living through yet another instance of FCP losing it's mind for no apparent reason I finally decided to ask the FCS-code expert on the matter, who also happens to be the publisher of the FCS Maintenance Pack from Digital Rebellion, and here's his response:
"If you've ever wondered why FCP preferences have to be trashed so frequently, it's because Apple decided to use a volatile proprietary binary format for preferences that no other application uses."
Nice.
While you can't completely prevent this unstable behavior from ever happening you *can* easily store and reset your precious FCP preference file by either;
A) Manually locating the preference file, copying it and saving it somewhere *away* from where the core OS lives (preferably on a separate HDD or even a Flash-drive) or better still:
B) Get a copy of Digital Rebellions FCS Maint Pack which includes a utility to clean, backup and restore your preferences and even deeper FCP core files so that the next time FCP decides to have another brain-fart you don't spend the next hour or so restoring all the user-dedicated data.
Just one more reason D.R.'s Maint pack is a must-have for any FCP editor.
After living through yet another instance of FCP losing it's mind for no apparent reason I finally decided to ask the FCS-code expert on the matter, who also happens to be the publisher of the FCS Maintenance Pack from Digital Rebellion, and here's his response:
"If you've ever wondered why FCP preferences have to be trashed so frequently, it's because Apple decided to use a volatile proprietary binary format for preferences that no other application uses."
Nice.
While you can't completely prevent this unstable behavior from ever happening you *can* easily store and reset your precious FCP preference file by either;
A) Manually locating the preference file, copying it and saving it somewhere *away* from where the core OS lives (preferably on a separate HDD or even a Flash-drive) or better still:
B) Get a copy of Digital Rebellions FCS Maint Pack which includes a utility to clean, backup and restore your preferences and even deeper FCP core files so that the next time FCP decides to have another brain-fart you don't spend the next hour or so restoring all the user-dedicated data.
Just one more reason D.R.'s Maint pack is a must-have for any FCP editor.