- Posts: 32
- Thank you received: 1
3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
Failed render because of random drop frame
I'm currently using FCP X 10.0.9. On my latest project I tried to render a project but I had a problem.
When I'm rendering from the share - master file in FCP X, it always drops frame at random frame, not during playback.
All my video are .mov files 1920x1080 25 fps. It's proxy media.
I'm using Mac Pro
Processor 2 x 2.4 GHz Quad-Core Intel Xeon,
Memory 6 GB 1066 MHz DDR3 ECC,
Graphics ATI Radeon HD 5770 1024 MB,
OS Maverick
I appreciate your help guys.
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
- Posts: 4455
- Thank you received: 962
- You are editing in Proxy mode in FCPX
- When you play the edit in FCPX you don't get drops during playback
- Then you switch your Playback mode to Original Media and you share the edit to a ProRes 422 Master File
- When you play the exported file in QuickTime player you get drops at random frames
Is that correct?
Please Log in to join the conversation.
1. Yes, when I'm importing all the media, I'm transcoding with proxy media
2. Yes, I don't get drops during playback
3. No, I don't switch my playback mode to original media.
4. It already failed when rendered. Because of the drops.
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
- Posts: 4455
- Thank you received: 962
Or you cannot export (share) the edit? Do you get error messages when exporting?
I think it would be best if you gave us a step-by-step explanation of your workflow.
- Ronny
Please Log in to join the conversation.
You can see my attachment, I attached my screen capture.
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
- Posts: 4455
- Thank you received: 962
Click "Add File" to add your screenshot to the file list
When the screenshot appears in the list, click "Insert" to insert the file in your message
- Ronny
Please Log in to join the conversation.
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
- Posts: 4455
- Thank you received: 962
If you get this kind of export error on multiple frames these are the first things you should do:
1. Disable Mavericks App Nap for FCPX.
Go to your Applications folder, R-click the FCPX application icon and select Show Info.
In the Info window put a checkmark next to "Disable App Nap".
2. Delete ALL your Event and Project render files.
Select your Event and choose File > Delete Event Render Files
Select your project and choose File > Delete Project Render Files (delete ALL render files, not just te unused)
Then try sharing the edit as a Master File without rendering first.
If you still get export errors after this, please post back.
IMPORTANT: Oh yes, one more question: what are your Playback settings in Preferences? Can you post a screenshot of your Playback Preferences?
- Ronny
Please Log in to join the conversation.
0. Create event
1. Import assets ( Video : mov 1920x1080/25fps - create proxy media, audio : mp3 )
2. Create project
3. Rough Cut
4. Adding transition, effect, trimming, etc.
5. Export/Share - master file ProRess 422
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
- Posts: 4455
- Thank you received: 962
See my post above: Can you post a screenshot of your Playback Preferences?
- Ronny
Please Log in to join the conversation.
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
- Posts: 4455
- Thank you received: 962
One thing you should do is disable Background Rendering in your Playback Preferences.
Then do the two things I have mentioned in my reply above (disable App Nap and delete all your render files), then try exporting again. If you stil get the error make a note of the frame where exporting stops and post back.
- Ronny
Please Log in to join the conversation.
Please Log in to join the conversation.
- jjsanderson
-
- Offline
- Elite Member
-
ronny courtens wrote: I was afraid you were exporting in Proxy Mode but that's not the case.
To clarify this: Proxy media is only used if you select Proxy in your playback settings. It's then used everywhere, even for export. Which, yes, is a bit ridiculous, but that's how FCPX currently works.
If you're leaving your playback settings as 'Use original/optimised media', the Proxy media is never touched. You have to manually toggle it to edit in Proxy and export from the originals.
To be honest, I never bother with Proxy. For multi camera work I'll transcode to ProRes ('Optimised media'), but otherwise I just edit the original material.
Try Ronny's advice about deleting render files and disabling background rendering and App Nap. It might also help to know a little more about the system you're editing on - in another thread we seem to have traced problems to a MacBook Pro which had its discrete graphics card disabled in Energy Saver prefs.
Please Log in to join the conversation.
So what is the real problem here, the app nap? OS Maverick? or the background rendering?
Anyway thank you ronny courtens & jjsanderson for your time & help.
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
- Posts: 4455
- Thank you received: 962
I'm glad it works now.
- In your specific case rendering is the most probable cause of the export issue. When you render while you edit sometimes existing render files are overwritten or partially replaced by new ones when you modify and re-render a clip that was already rendered. In some cases this can lead to render files not linking correctly to the media on the timeline, or to corrupt render frames when similar render files overlap. When you export your timeline FCPX detects these corrupt frames and stops exporting to avoid corrupt frames in your exported video.
When you delete all render files and you completely re-render your timeline in one pass before exporting, or when you delete all existing render files and you just export the un-rendered timeline, you will prevent possible corrupt render files or corrupt render frames.
Most render file corruption comes from repeated re-rendering of the same clip or the same part to the timeline. That's why Background Rendering is best turned off. When background rendering is on, FCPX continuously starts rendering whenever it detects inactivity on your timeline. This creates more overlapping render files and more risk for corrupt render frames than if you first finish working on your clips and then do a manual render or just export the un-rendered timeline.
- Disabling App Nap is especially useful for long exports. Apparently Mavericks does not see FCPX exporting as a real "activity", so when you have a very long export there is a chance that Mavericks' App Nap will completely slow down FCPX after a certain time and you will get an export error. That's why at this time it is best to have App Nap disabled for FCPX.
- Mavericks seems to work well for most people running FCPX, but as with every major OS update there are also issues being reported on specific systems and in specific circumstances. If you experience any issues and you don't find readily available solutions on help-forums such as this one, the best (and the only effective) way of letting Apple know about your issue is to use the feedback form.
- Ronny
Please Log in to join the conversation.
- therealamaru
-
- Offline
- New Member
-
Thanks for your wisdom in advance!
Amaru
www.therealamaru.com
www.anniewasaliar.com
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
- Posts: 4455
- Thank you received: 962
- Ronny
Please Log in to join the conversation.
- therealamaru
-
- Offline
- New Member
-
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
- Posts: 4455
- Thank you received: 962
- Ronny
Please Log in to join the conversation.

