Many software programs can become unstable when their preference files become corrupted, which can be triggered by a variety of problems, including sudden computer crashes or shut downs (power loss, etc.). Learn how to resolve issues caused by unusable preference files in Final Cut Pro 4.
When troubleshooting Final Cut Pro, one step you can take is to delete the Final Cut Pro preference files. Doing this restores Final Cut Pro to the default settings and behavior. These files contains user preferences for scratch disk settings, capture settings, window layouts, and so forth.
To delete the Final Cut Pro 4 preferences files, do the following:
- Quit Final Cut Pro 4.
- Click the Finder icon in the Dock.
- From the Go menu, choose Go to Folder.
- Type: ~/Library/Preferences/
- Click Go.
- Drag the file named "com.apple.FinalCutPro.plist" to the Trash
- Double-click the folder named "Final Cut Pro User Data".
- Drag the file named "Final Cut Pro 4.0 Preferences" to the Trash.
- Drag the file named "Final Cut Pro POA Cache" to the Trash.
- Open Final Cut Pro.
Important: Do not delete any of the other files in the Final Cut Pro User Data folder.
Once this process is completed Final Cut Pro reverts to its installed defaults. Reset all of your desired application preferences to match what they were before - in particular your Scratch Disk Preferences, keyboard mappings, and the selected Sequence Settings.
Back up configured preference files
To avoid recreating all your custom settings in the event you have to delete the preference files again, follow these steps to save a clean copy of the file:
- Make a backup copy of the "Final Cut Pro Preferences" and the "com.apple.FinalCutPro.plist" files immediately after it is configured for the first time.
- Put the backup copy of the files in a safe place.
If you have to delete the preference files again, you can simply replace them with the backup copy of the saved, clean files. This preserves your desired preference settings, while eliminating any unwanted behaviors that may have been caused by a faulty Final Cut Pro Preferences file.
