4 Replies Latest reply: Sep 29, 2012 7:00 AM by Russ H
dastoelk Level 3 Level 3 (665 points)

I had a lot of effects (across many layers) and, before I stepped away, I clicked "render all." As usual, I noticed the thin orange lines atop the timeline slowly evaporating. the, as expected, the render dial in the HUD slowly dialed up.

 

When I returned, the render display in the HUD read "1.00." Done.

 

But, then I noticed a few stray orange lines. Indeed, a couple of effects were still unrendered. I checked  "background tasks" and nothing was running. So... I rendered again... The remaining lines disappeared. Everything rendered. All was well.

 

Then... It happened again. I had to re-render to get my entire project rendered. (And, again, even after all of my displays said the project WAS rendered.)

 

Has this happened to anyone else? I can always render again and again until all of the orange line disappears, but, I'd rather do it just once.


Final Cut Pro X, OS X Mountain Lion (10.8.1), iMac 27-inch
  • aycas Level 1 Level 1 (0 points)

    It's happened to me too. I keep rendering but the orange lines only disappear temporarily then reappear. I noticed that with each re-render some disk space is used.

  • Russ H Level 6 Level 6 (17,035 points)

    Yes, what you describe sometimes happens to my projects as well. FWIW, unless I can't get reasonable playback, I don't worry about what is or isn't rendered. Exporting unrendered projects has been a fast and reliable workflow.

     

    Russ

  • dastoelk Level 3 Level 3 (665 points)

    Russ, do you mean to say that when exporting, the files are rendered automatically?

  • Russ H Level 6 Level 6 (17,035 points)

    dastoelk wrote:

     

    Russ, do you mean to say that when exporting, the files are rendered automatically?

    Not saying the project gets rendered, but the exported file does. And its appeal is that it's a very fast process.

     

    For example, I just had a 5 minute project (h.264 clips)  with effects/title, and, as you would expect, the orange render bar ran the length of the timeline. Background rendering was off. I exported the unrendered project as an h.264 Quick Time and it completed the task in just about real time. (BTW, this is something I never would have attempted in earlier versions of FCP.)


    So I ended up with a self-contained QT movie file. If I had intended to make several delivery versions (for disk, Web, ATV, etc., I would have exported as Pro Res  and brought that into Compressor.

     

    While the project remains unrendered, it doesn't matter to me. If something comes up that requires me to make changes and create a new version, I can easily do that because of the speed with which it exports. (And I have used up far less storage with this workflow than if had created a whole lot of render files.)

     

    Again, the only time I do any rendering is if playback starts to interfere with edits. And that seldom occurs in my projects. (You might find this iinteresting; note all the unrendered sections of his timeline while he continues to edit on the fly.)

     

    Good luck.

     

    Russ