Unreliable rendering with nested sequences

[Richard Sanchez]

Are you mixing sample rates? That’s typically the number one cause of having to continually render audio. Also, in your user preferences, you can set your audio playback from the default of 8 tracks to a higher number, which will cause less need to render audio. I’ve also experienced these strange audio issues with audio rendering. Also, as you mentioned, since you can blow away and re-render due to the motion graphics. You can use the render manager to just blow away your audio render files and then rerender just those. Rerendering your audio files shouldn’t take too long.

Richard Sanchez
North Hollywood, CA

“We are the facilitators of our own creative evolution.” – Bill Hicks

[Colin Mcquillan]

[Clint Stringfellow] “I found that I was able to avoid some of the issues by making a splice with the razor in the middle of the sequence and then re-rendering.”

I’ve had this issue as well, and for me, found it occurred occasionally (sometimes very often) when I would render a graphic (motion or still) over a nested sequence. Like yourself I used the razor tool to make a cut, but did on either the first frame after the overlaying GFX or the last frame before the overlay, whichever was needed. Then the video would pop back into sync without having to be re-rendered.

Colin McQuillan
Vancouver, B.C.

[Clint Stringfellow]

Thanks for the responses. One thing I noticed today is that errors happened during export to quicktime movie, even where there was no need for rendering. ~>=| So, certain clips of audio are dropping out and levels are jumping around during the export process. (Yes, I’m using “current settings” and “make movie self contained”).

So, after re-rendering to fix some errors, I get *other* errors during the export to quicktime process. Seriously, this means I have to QC a 30 min piece IN FCP, again after the export, and one more time after making a DVD. ~>=O NOT the best use of my time.

Yes, I did end up mixing data rates in this particular piece b/c, well, long story. I have always avoided doing this, but I was dealing w/ a sequence that someone else had started, and there was too much material and too little time to export all the audio to the same sample rates. I was assuming FCP could handle it…so I went ahead and used what I had. In hindsight it probably would have been worth the time to batch export it all to 48k. I do believe that this contributed to the “export” issue. The render issue has happened in spots where all the sample rates were 48k.

After experiencing all this, I’m just going to avoid nesting unless I absolutely have to. It ended up costing me more time than it saved me. It’s a nifty feature, but it just doesn’t seem reliable, especially when there’s a lot of rendering involved.

[Henry Bradford]

FCP blows on this, I do much nesting using CS3/4, but with my FCP setup the system wants the main timeline with all the nested sequences rendered everytime. This is where adobe has them beat.