-
Premiere ignoring rendered Preview files in nested sequences?
I’m having a bitch of a time working with a feature film length project in Premiere CC. I have to create multiple different versions of the film, with different slates, textless versions, etc. So for efficiencies sake, I have the master sequence in a single timeline, which I use as a nested source clip in the ancillary export sequences.
But even though I force render the entire master sequence, when I use that rendered sequence as a nested source in another sequence with the exact same settings as the master sequence, Premiere completely ignores the fact that rendered Previews exist for the items in the nested sequence, and I am forced to re-render the whole damn nest again.
Even more aggravating, even when I do this double-rendering, when I go to export the sequence using Match Sequence and “Use Previews” enabled, Premiere (or AME) appears to have to re-render the damn timeline “on the fly” YET AGAIN, because it’s taking almost 2 hours to export an 82 minute, pre-rendered ProRes sequence to the same output codec.
I’m guessing this is a bug, but if there’s a workaround for this, I’d love to know what it is.
-
1 Reply
-
The work around is render out your master sequence to a file, and then import it in to the different versions, totally side-stepping the need to render nested sequences. Performance should be far better as it should smart render this file on export.
——————–
Angelo LorenzoNeed to encode ProRes on your Windows PC?
Introducing ProRes Helper, an awesome little app that makes it possible
Fallen Empire Digital Production Services – Los Angeles
RED transcoding, on-set DIT, and RED Epic rental services
Fallen Empire – The Blog
A blog dedicated to filmmaking, the RED workflow, and DIT tips and tricks
Can your post production question fit in a tweet? Follow me on Twitter
Reply to this Discussion! Login or Sign Up