Why do I keep getting a Video rendering error: 10008 when exporting in Final Cut Pro X?

I had this same issue happen to me. At first I overlooked my exported drafts because I knew they were incomplete. After giving them a quick peek, the video stalled exactly where the frame issue presented itself.

Props to Str1cken for the insight into the matter and a successful resolution!

Thank you very much! 😀

I couldn't find the find the export in the project folder but what I did notice is that fcp kept on pulsing rendering, like every second a pulse on, then off, with high cpu load- which is not normal. So if I cut the movie and delete a portion then the rendering stopped- i.e. I was cutting out the bad frame(s) like Striken says. but initially, the cut portion was way too much so I kept splitting the bad part in half to zoom into the trouble spot (undoing after each cut, to restore the full video) until I had zoomed in far enough, basically full zoom, and I could see the missing video frame or maybe two, in the editing window. They were just black, the audio was intact. So I got to delete just that bad frame and now all is good. Took just a couple of minutes to do this...

Can anyone offer any tips on finding / locating a glitchy frames? I did the El Capitan update yesterday and could not render any videos afterwards...I restored previous version via Time Capsule, but I'm still having issues rendering videos and get 10008 error message no matter what I do.

Can anyone offer any tips on finding / locating glitchy frames? I did the El Capitan update yesterday and could not render any videos afterwards...I restored previous version via Time Capsule, but I'm still having issues rendering videos and get 10008 error message no matter what I do.

Also, I've had a chance to test several different projects...I can get some to export / render, but others fail with 10008 error message...so I can't imagine that now all of a sudden I have a bunch of projects with glitchy frames....this is first time I have ever encountered this so I'm somewhat miffed at how a video clips in a project can all of sudden develop some strange issue...but then again...it's data.

You don't even want to think about a bunch of glitch files... this would be crazy to fix one at a time per the methods above... unless the resize solution mentioned by some works- that didn't work for me... this has not been a bad problem for me- only happens to me when I bring in files recorded by an online webinar platform which I do only once/month or so. Finding/correcting the bad section is a pain and if a bunch of files corrupted during captain upgrade would drive you crazy... maybe apple has a fix for you?? But if you have to fix the files yourself I found the easiest is to look at the little percent activity meter in the Background Tasks Window which is in the middle directly above the project timeline window. It's a little circle showing 100% if no background tasks are running. if you have a bad file the thing keeps flicking/running. you can also see this in ActivityMonitor CPU monitoring. Then you don't have keep exporting the segments to see if it fails... you can split the timeline, erase a half, see how the monitor responds, undo to undelete and delete another portion... as described in posts above- you gotta zoom in to the specific bad frames and delete them

Sorry. My deleted reply was redundant to Robert's.

Russ

I did find a video on YT today with someone showing a glitched frame showing up in red, but you need to move play-head directly over the section with segment selected. I have not tried this yet, but think I have found a section I need to look at. I'm hoping Apple comes out with a fix for this. In the mean time, I was able to get a project delivered using Adobe Premiere Pro CC

to solve this problem just select where the render stopped and hit alt-G, and render again

Just had the same error for the first time - I think there may have been 1 dodgy clip in the event viewer, the thumbnail wasn't displaying correctly. I just replaced it, exported an XML then opened it again in FCP and it worked fine.

I've encountered similar problems. In my case the problem could be traced to a glitch buried inside a Compound clip and part of a multicam, thus two sets of timecode pointers.

I found this article from Larry Jordan very helpful:

https://larryjordan.com/articles/fcp-x-export-problems/

I found the bad frames at 00:36:31;25 on the overall Project and at 00:05:43;21 on the MVI file that was inside a MultiCam clip. Once removed, I was back in business.

One of the irritants with this phenomenon is that the user is left to guess where the glitch is. Instead of trying to post to Vimeo as I had done previously, I rendered a master file (command-E), and when the render failed, this message popped, which seems to indicate where the problem element is:

There is a problem with the media file at that frame number in the project. You might have to replace the shot or edit around it.

to Fix “Video rendering error: 10008” when Exporting in Final Cut Pro X or imovie, Follow this Article

http://www.2tech.me/en/videos/computer/how-to-fix-video-rendering-error-10008-wh en-exporting-in-final-cut-pro-x-or-imovi…

or Try this Simple Steps:

1- Getting a final cut pro 10008 error? May mean you have a glitchy frame in your source video

2- between every two videos out together Just before this black frame clicked the video to put down a marker and split the clip (Command+B).

3- Create a new Project then copy the existing project and paste it on the new Project

4- After doing this it was able to export the movie without the error popping up!

Check at what time stamp you are getting the fail notice, by looking where you saved it and that is the clue to which clip is the problem 😀