Can't share: frame cannot be rendered

FCP 10.5.1 (latest) on a modern iMac.


I'm trying to share my project, which has a bunch of media from various cameras. I did not experience any unusual errors while editing -- playback worked fine.


Now that I'm sharing, partway through the share, I get "The share operation has failed: The operation could not be completed because an error occurred when creating frame xyz (Error 10008)" and then it goes on to give me timecode.


I'm in a hurry, so I went to that timecode, and simply reedited in such a way that didn't require that frame. Then I shared again, and got the same error, but at a later location, so I did the same. Then again, and again.


Now, it's giving me the error, but at an EARLIER timecode than all the other errors. In other words, it's now finding problems during the share/render that WEREN'T there before.


I can't keep deleting frames and re-editing the project. How do I diagnose this and get my project exported, quickly?


iMac Line (2012 and Later)

Posted on Feb 25, 2021 11:30 AM

Reply
Question marked as Top-ranking reply

Posted on Feb 26, 2021 11:58 AM

No. Stay out of the library bundle. Don’t move files around in there. Delete your render files again. Select the library inside FCP and use Delete Generated Library Files. Switch off background rendering. Do not render.


Use the Finder to transcode the file. Select it right click and choose Encode selected file. Use high quality for ProRes. If the file is in the bundle take the converted file out of it. In FCP select the problem clip in the browser and use relink file. Point it to the ProRes file. See if it works without an error message.


Do not render before you export.

Similar questions

8 replies
Question marked as Top-ranking reply

Feb 26, 2021 11:58 AM in response to David Das

No. Stay out of the library bundle. Don’t move files around in there. Delete your render files again. Select the library inside FCP and use Delete Generated Library Files. Switch off background rendering. Do not render.


Use the Finder to transcode the file. Select it right click and choose Encode selected file. Use high quality for ProRes. If the file is in the bundle take the converted file out of it. In FCP select the problem clip in the browser and use relink file. Point it to the ProRes file. See if it works without an error message.


Do not render before you export.

Feb 27, 2021 6:38 PM in response to Tom Wolsky

(OP here.)


I appreciate the help. In the end, I wasn't able to get it to work. I did find Finder > Services > Encode Video Files, so I used that, but it took 24 hours and still didn't finish, and eventually I gave up. (It's a 2-hour file.) It was clearly creating such a massive massive file that I wouldn't even have had the disk space to store it.


I've now worked around it using another method. (Note: quality was not extremely important to me; this was a screen recording of a Zoom capture, so quality was already compromised at the source.) I'll detail it here in case it helps anyone in the future (and I'd welcome input from @Tom or others more knowledgable than me) -- but I was desperate!


  1. I opened the FCP library bundle using Show Package Contents.
  2. I located the problematic file in the Original Media folder, and opt-dragged that file to a different hard drive.
  3. I transcoded that file using Handbrake. I tried to use one of the higher-quality presets. This transcoding took about an hour.
  4. I imported that new Handbrake-produced file back into the FCP library.
  5. I went into my multicam clip, chose Add Angle, then moved the problem clip to the newly created angle, making 100% sure that the start time was the same.
  6. I now imported my Handbrake-produced fixed file into the multicam clip, and put it in the lane of the original angle, again, making 100% sure the start time was the same. I could also verify this visually since the waveforms gave me instant feedback that it was in sync.
  7. Since I had now replaced the source file at the multicam clip level, all the edits at the project level now automatically inherited the replacement file, and I was able to finally render the finished project without error.


Phew.

Feb 26, 2021 11:25 AM in response to Luis Sequeira1

Unfortunately none of that worked.


I started by using the File menu to "delete generated files" and made sure to click ALL render files.


But then, after quitting, I used Show Package Contents and still found a large quantity of render files inside the FCP library. So I manually moved them out. Then I reopened FCP and trashed its prefs (via launching it using opt-cmd). Then I reopened the library, and waited hours for it to do all its re-rendering. Then I tried another export: it got about 80% of the way done, then gave me another similar error, at another random point.


I have no idea what to do now...


Question: it seems like all the errors have to do with that specific file ("2021-01-31 BTTF Episode 2 SF Export.mov"). What if I go to the Finder, find that file, and find some way to resave it (perhaps through a relatively harmless Handbrake transcode, or a QTP re-save), then I reimport that to my library with a different filename, then try and swap it out? I wonder if I can swap it out at the Multicam clip level, thereby preserving all the thousands of edits that I've done at the project level...


This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Can't share: frame cannot be rendered

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