Javier Bonafont

Q: fcpx continually re-renders some clips

This problem has arisen recently.  I will be working on a project, and some part of it will start rendering because of a change.  But it will NEVER stop.  It will BG render all the way to 100% and then start over.  For ever.  I've come back after an hour and found it still cycling through the render.  Closing and re-opening the project has no effect.  The only thing that works is making a duplicate project.  The duplicate will be fine, renders will stop immediately.  To be clear, the progress gauge on the timeline zips up from 0 to 100%, but the orange render lines do NOT shrink or change like they normally do when this is happening.  It is very bizarre, since the renders happen fine by just duplicating the project.  What gives?  Any insight?  Also, I can't tell whether its an audio or video render happening, as it often happens across a range of video clips.  Thanks for any advice.

Mac Pro (Early 2009), OS X Yosemite (10.10.3)

Posted on May 11, 2016 3:31 PM

Close

Q: fcpx continually re-renders some clips

  • All replies
  • Helpful answers

  • by Russ H,

    Russ H Russ H May 11, 2016 3:48 PM in response to Javier Bonafont
    Level 7 (21,820 points)
    Quicktime
    May 11, 2016 3:48 PM in response to Javier Bonafont

    Have you ever turned off BG Rendering? If not try that and turn it back on.

     

    If it still re-renders, delete the project's render files.

     

    Good luck.

     

    Russ

     

    PS: Many users leave background rendering off and manually render if they encounter playback that's problematic enough to interfere with editing decisions. Nor is it necessary to render prior to exporting.

  • by Javier Bonafont,

    Javier Bonafont Javier Bonafont May 11, 2016 3:58 PM in response to Russ H
    Level 1 (6 points)
    Mac OS X
    May 11, 2016 3:58 PM in response to Russ H

    Yes, well, I could do this, but it doesn't really address the problem that something is wrong.  It defeats the entire purpose of BG rendering if it has to be off, and having to continually purge render files and have it all re-render is a huge time suck.  Obviously there is something weird happening.  Manually rendering the area still does not erase the orange line on these projects.  Except for these bizarre little areas on the timeline, BG rendering works perfectly.

  • by Russ H,

    Russ H Russ H May 11, 2016 4:07 PM in response to Javier Bonafont
    Level 7 (21,820 points)
    Quicktime
    May 11, 2016 4:07 PM in response to Javier Bonafont

    Javier Bonafont wrote:

     

    Yes, well, I could do this,

    Do what? Switch BG Rendering on and off? Delete the Render Files? Or what I wrote in my PS?

  • by James Cude,

    James Cude James Cude May 11, 2016 4:28 PM in response to Javier Bonafont
    Level 4 (1,424 points)
    May 11, 2016 4:28 PM in response to Javier Bonafont

    Are you using Final Cut Pro X 10.2.3? If so, are these clips with Optical Flow?

  • by Javier Bonafont,

    Javier Bonafont Javier Bonafont May 11, 2016 4:36 PM in response to Russ H
    Level 1 (6 points)
    Mac OS X
    May 11, 2016 4:36 PM in response to Russ H

    Sorry, what I mean is that none of these solutions help me diagnose whatever the root problem is.

  • by Russ H,

    Russ H Russ H May 11, 2016 4:44 PM in response to Javier Bonafont
    Level 7 (21,820 points)
    Quicktime
    May 11, 2016 4:44 PM in response to Javier Bonafont

    If you have a corrupted render file?

     

    Russ

  • by Javier Bonafont,

    Javier Bonafont Javier Bonafont May 11, 2016 4:57 PM in response to James Cude
    Level 1 (6 points)
    Mac OS X
    May 11, 2016 4:57 PM in response to James Cude

    Optical flow... well some of them maybe, but not all of them.  I haven't noticed an obvious pattern yet.

  • by Javier Bonafont,

    Javier Bonafont Javier Bonafont May 11, 2016 5:15 PM in response to Russ H
    Level 1 (6 points)
    Mac OS X
    May 11, 2016 5:15 PM in response to Russ H

    So why/how would a render file get corrupted?  I don't understand how if it re-renders that does not replace the corrupted file?  Is it writing the file to the wrong place somehow? (how do we know where they are going? IDK at all).  In any event, this wasn't happening before, so I'm either doing something I wasn't doing before, or have inadvertently changed something to cause these random corruptions.  And why would duplicating the project file immediately cause the issue to vanish? 

  • by Russ H,

    Russ H Russ H May 11, 2016 5:32 PM in response to Javier Bonafont
    Level 7 (21,820 points)
    Quicktime
    May 11, 2016 5:32 PM in response to Javier Bonafont

    Javier Bonafont wrote:

    I don't understand how if it re-renders that does not replace the corrupted file?

    Nope. It adds another render to the existing files.

     

    Russ

  • by Javier Bonafont,

    Javier Bonafont Javier Bonafont May 11, 2016 5:52 PM in response to Russ H
    Level 1 (6 points)
    Mac OS X
    May 11, 2016 5:52 PM in response to Russ H

    Right.  But why is that not happening?  It goes through the motions, but nothing happens, and it starts again.  It will do this dozens or hundreds of times until stopped.

  • by Alchroma,Helpful

    Alchroma Alchroma May 12, 2016 8:19 AM in response to Javier Bonafont
    Level 6 (19,006 points)
    Video
    May 12, 2016 8:19 AM in response to Javier Bonafont

    Turn off BG rendering and then export as a Master File.

    If you are lucky the export will throw an error message like "frame 12345 is dogey".

    If it does then you change the Timecode display to frames and then you can find the section of problematic video.

    Screen Shot 2016-05-12 at 1.12.41 PM.png

     

    Al

  • by Javier Bonafont,

    Javier Bonafont Javier Bonafont May 12, 2016 8:27 AM in response to Javier Bonafont
    Level 1 (6 points)
    Mac OS X
    May 12, 2016 8:27 AM in response to Javier Bonafont

    Okay folks, so after some repeated back and forth, it seems that whatever was causing the render issue was a compound clip of audio tracks.  I still do not know WHY, but that was what culprit.  I expanded the compound clip and the issue vanished.  I created a new compound clip, exactly the same, and the issue did not recur.  Whatever.  Now, this compound clip had a Limiter audio filter on it, which is what I'm guessing was rendering over and over?  Its the only effect or anything that existed, but its bizarre because normally the limiter effect does not create an orange render line (or at least never had before or since).  The new version has the same filter and settings and works fine.   In any case I know to check for this again in the future, but still do not know what the root issue is when this happens.  Thanks for all your advice.