Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Events that go missing in Final Cut Prox

I was working on a project when I recorded a voice over and got the beach ball. I force quited FCPX and when re-open the program and projects shows the event as missing even thought it exist


any tips?

Final Cut Pro X, Mac OS X (10.7.3)

Posted on Sep 11, 2012 8:14 AM

Reply
Question marked as Best reply

Posted on Sep 11, 2012 9:35 AM

When you say FCP X shows the Event as missing, what do you mean?

Is the EVENT there, but the clips are offline - or is the Event not there at all?


Are any other events there?


If the Event fails to show in FCP X, it's likely that it was corrupted when you Force Quit.


Wuit FCP X and use finder to create a new folder within the Event (call it Temp or something like that) and move the CurrentVersion.fcpevent file into it.


Then go into the Backups folder and drag the CurrentVersion.fcpevent from there, into the Event Folder (where the original file was before you moved it).


Re-start FCP X and all should be well.

_____________________


Regarding that beachball . . .


This is my pet checklist for questions regarding FCP X performance - you may have already addressed some of the items but it's worth checking.


Make sure you're using the latest version of the application - FCP X 10.0.5 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. I run it with Lion 10.7.5.


First, check that you have at least 20% free space on your system drive.


For smooth playback without dropping frames, make sure 'Better Performance' is selected in the FCP X Preferences - Playback Tab.


If you have not already done so, move your Projects and Events to a fast (Firewire 800 or faster) external HD. Make sure the drive's formatted OS Extended (journalling's not required for video). You should always keep at least 20% free space on the Hard Drives that 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.


If you ever experience dropped frames, I strongly recommend you use ProRes 422 Proxy - it edits and plays back like silk because the files are small but lightly compressed (not much packing and unpacking to do) - but remember to select 'Original or Optimised Media' (FCP X Preferences > Playback) just before you export your movie, otherwise it will be exported at low resolution.


If you have plenty of processor power, for the ultimate editing experience, 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.


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. There's a great application for this, called Event Manager X - for the tiny cost it's an invaluable application.

http://assistedediting.intelligentassistance.com/EventManagerX/


Unless you cannot edit and playback without it, turn off Background Rendering in Preferences (under Playback) - this will help general performance and you can always render when you need to by selecting the clip (or clips) and pressing Ctrl+R.


The biggest single improvement I saw in performance was when I upgraded the RAM from 8 GB to 16.

Andy

4 replies
Question marked as Best reply

Sep 11, 2012 9:35 AM in response to ChicVoyage

When you say FCP X shows the Event as missing, what do you mean?

Is the EVENT there, but the clips are offline - or is the Event not there at all?


Are any other events there?


If the Event fails to show in FCP X, it's likely that it was corrupted when you Force Quit.


Wuit FCP X and use finder to create a new folder within the Event (call it Temp or something like that) and move the CurrentVersion.fcpevent file into it.


Then go into the Backups folder and drag the CurrentVersion.fcpevent from there, into the Event Folder (where the original file was before you moved it).


Re-start FCP X and all should be well.

_____________________


Regarding that beachball . . .


This is my pet checklist for questions regarding FCP X performance - you may have already addressed some of the items but it's worth checking.


Make sure you're using the latest version of the application - FCP X 10.0.5 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. I run it with Lion 10.7.5.


First, check that you have at least 20% free space on your system drive.


For smooth playback without dropping frames, make sure 'Better Performance' is selected in the FCP X Preferences - Playback Tab.


If you have not already done so, move your Projects and Events to a fast (Firewire 800 or faster) external HD. Make sure the drive's formatted OS Extended (journalling's not required for video). You should always keep at least 20% free space on the Hard Drives that 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.


If you ever experience dropped frames, I strongly recommend you use ProRes 422 Proxy - it edits and plays back like silk because the files are small but lightly compressed (not much packing and unpacking to do) - but remember to select 'Original or Optimised Media' (FCP X Preferences > Playback) just before you export your movie, otherwise it will be exported at low resolution.


If you have plenty of processor power, for the ultimate editing experience, 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.


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. There's a great application for this, called Event Manager X - for the tiny cost it's an invaluable application.

http://assistedediting.intelligentassistance.com/EventManagerX/


Unless you cannot edit and playback without it, turn off Background Rendering in Preferences (under Playback) - this will help general performance and you can always render when you need to by selecting the clip (or clips) and pressing Ctrl+R.


The biggest single improvement I saw in performance was when I upgraded the RAM from 8 GB to 16.

Andy

Sep 11, 2012 7:20 PM in response to andynick

Thank you very much. Your advice on the event solved my issue. THe last step was to relink the event files.


As for the performance tips I have most of those covered with exception of trying out another admin account and hiding the wave forms. I'll try that. I upgraded to 16gb as well on my imac and it did rock for a while.


I'm running a lacie 2gb firewire drive, but it does hang sometimes. I'm jealous of your macbook pro setup I would like to edit on the go. Which screen size are you using?

Events that go missing in Final Cut Prox

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.