-
All replies
-
Helpful answers
-
Feb 28, 2012 4:38 PM in response to CRB_FILMSby xfggfx,You will need to tell us about your OS, hardware and FCPX version etc...
Usuall it is recommended you reinitialise your prefs but I have never had to do that so ...over to someone else.
geoff
-
Feb 29, 2012 5:31 AM in response to xfggfxby CRB_FILMS,Hi there geoff, thanks for your help, sorry forget to list it my OS hardware is the Version 10.7.3 and I have the latest version of Final Cut Pro X (I only purchased it a couple of weeks ago) Cheers
-
Feb 29, 2012 6:07 AM in response to CRB_FILMSby andynick,★HelpfulAs Geoff suggests, try trashing your preferences.
Unexplained faults like this can often be fixed by clearing out FCP X's preferences (for some reason, they get knotted up from time to time).
Download Digital Rebellion's Preference Manager (free, simple to use, and perfectly safe, both to download and use).
http://www.digitalrebellion.com/prefman/
With Preference Manager, you can backup the Prefs when FCP X (or any of the Apple Professional Applications) are working normally. Then when either of the applications are acting strangely, Trash the Preferences, then Restore from your backups (just a mouse-click).
If you trash the prefs and don't restore them, you will need to manually restore all your FCP X settings again, so it's a great idea to backup Preferences from time to time when FCP X is working well, then your backups are up to date.
Doesn't fix every problem, but it fixes a lot.
Andy
-
Feb 29, 2012 6:24 AM in response to andynickby CRB_FILMS,Hi there Andy, thanks very much for your help, I have downloaded the Digitial Rebellions preference software and trashed my FCPX preferences. However FCPX is still crashing when I open it. Any advice on what I should do now? cheers. sorry to be such a hassle!
-
Feb 29, 2012 6:56 AM in response to CRB_FILMSby andynick,Move your project and vent files to new (temporary) folders so that FCP X doesn't find them and try launching again.
If it launches OK, you have a corrupt file somewhere, so introduce the files back to their original positions one at a time to track down the corrupt file.
___________________
This is my pet checklist for questions regarding FCP X performance.
FCP X 10.0.3 runs very well on my 2009 MacPro 2 x 2.26 GHz Quad-Core Intel Xeon with 16 GB RAM and ATI Radeon HD 5870 1024 MB.
First, check that you have at least 20% free space on the Hard Drive that your System and your Media, Projects and Events are on.
Check the spec of your Mac against the system requirements:
http://www.apple.com/finalcutpro/specs/
Check the spec of your graphics card. If it's listed here, it's not suitable:
http://support.apple.com/kb/HT4664
If you are getting crashes, there is some conflict on the OS. Create a new (admin) user account on your system and use FCP X from there - if it runs a lot better, there's a conflict and a clean install would be recommended.
Keep projects to 20 mins or less. If you have a long project, work on 20 min sections then paste these into a final project for export.
Create Optimised media - most camera native files are highly compressed and need a great deal of processor power to play back - particularly if you add titles, filters or effects. ProRes 422 takes up much more hard drive space but is very lightly compressed. It edits and plays back superbly.
If you are short of drive space, use ProRes 422 Proxy - but remember to select High Quality when you export your movie.
Hide Audio Waveforms at all times when you don't need them (both in Browser and Storyline / Timeline). They take up a lot of processor power. (Use the switch icon at the bottom-right of your timeline to select a format without waveforms if you don't need them at the moment, then switch back when you do).
Create folders in the Project and Events libraries and put any projects you are not working on currently, in those folders. This will help a lot.
Move your Projects and Events to an external HD (make sure it's formatted OS Extended - with journaled on or off) and run from there.
The biggest single improvement I saw in performance was when I upgraded the RAM from 8 GB to 16.
Andy