tony314

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

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

I'm using FCPX 10.2

Yosemite 10.10.3

MacBook Pro (13-inch, Early 2011)

2.7 GHz Intel Core i7

8 GB 1333 MHz DDR3

500GB with 308GB free

MacBook Pro, Mac OS X (10.6.7)

Posted on Apr 21, 2015 2:10 PM

Close

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

  • All replies
  • Helpful answers

Previous Page 2
  • by trinesel,

    trinesel trinesel Jul 31, 2015 3:36 PM in response to Str1cken
    Level 1 (0 points)
    Jul 31, 2015 3:36 PM in response to Str1cken

    Thank you very much!

  • by Robert Schwenkler,

    Robert Schwenkler Robert Schwenkler Sep 19, 2015 10:41 PM in response to Str1cken
    Level 1 (14 points)
    Mac OS X
    Sep 19, 2015 10:41 PM in response to Str1cken

    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...

  • by seopro,

    seopro seopro Oct 29, 2015 8:38 AM in response to tazzunit
    Level 1 (0 points)
    Oct 29, 2015 8:38 AM in response to tazzunit

    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.

  • by seopro,

    seopro seopro Oct 29, 2015 10:02 AM in response to seopro
    Level 1 (0 points)
    Oct 29, 2015 10:02 AM in response to seopro

    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.

  • by Robert Schwenkler,

    Robert Schwenkler Robert Schwenkler Oct 29, 2015 11:41 AM in response to seopro
    Level 1 (14 points)
    Mac OS X
    Oct 29, 2015 11:41 AM in response to seopro

    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

  • by Russ H,

    Russ H Russ H Oct 29, 2015 2:25 PM in response to seopro
    Level 7 (21,770 points)
    Quicktime
    Oct 29, 2015 2:25 PM in response to seopro

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

    Russ

  • by seopro,

    seopro seopro Oct 29, 2015 2:39 PM in response to Robert Schwenkler
    Level 1 (0 points)
    Oct 29, 2015 2:39 PM in response to Robert Schwenkler

    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

  • by Jaw AD,

    Jaw AD Jaw AD Dec 11, 2015 1:25 PM in response to tony314
    Level 1 (0 points)
    Dec 11, 2015 1:25 PM in response to tony314

    to solve this problem just select where the render stopped and hit alt-G, and render again Screen Shot 2015-12-11 at 9.22.23 PM.png

  • by wiseandi,

    wiseandi wiseandi Feb 11, 2016 2:17 AM in response to tony314
    Level 1 (10 points)
    Feb 11, 2016 2:17 AM in response to tony314

    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.

  • by sesweitzer,

    sesweitzer sesweitzer Apr 29, 2016 6:04 AM in response to tony314
    Level 1 (9 points)
    Apple Music
    Apr 29, 2016 6:04 AM in response to tony314

    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/

     

    Final Cut ProScreenSnapz001.jpg

    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.

  • by BurmeseTigerTrap,

    BurmeseTigerTrap BurmeseTigerTrap Aug 26, 2016 7:45 AM in response to tony314
    Level 1 (4 points)
    Aug 26, 2016 7:45 AM in response to tony314

    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:

    Screen Shot 2016-08-26 at 9.42.01 AM.png

  • by Tom Wolsky,

    Tom Wolsky Tom Wolsky Aug 26, 2016 8:06 AM in response to BurmeseTigerTrap
    Level 10 (118,107 points)
    Apple TV
    Aug 26, 2016 8:06 AM in response to BurmeseTigerTrap

    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.

Previous Page 2