Skip to main content
Legend
July 31, 2017
Answered

Render-and-replace entire sequence?

  • July 31, 2017
  • 1 reply
  • 1434 views

A burning question... why doesn't Premiere support a Render-and-Replace for an entire sequence? I manually pre-render to achieve this but I end up having to manage the bits... for example, I create a bin which contains the original sequence side-by-side with the pre-render that I import into the project. It's not the end of the world, but this seems like such a natural thing to have. (I have more to say on this but wanted to ensure I'm not missing something first... I feel this sort of feature might help alleviate the inevitable workarounds we often have to employ through pre-rendering.)

This topic has been closed for replies.
Correct answer Meg The Dog

OK, my confusion was based on your using the term pre-render. In my experience rendering makes a (usually temporary and discardable) preview file, while exporting makes a durable stand alone file, which can either be a master or sub-master file.

I do this all the time to expedite the edit. I don't want to have to repeatedly re-render things for preview when, for example, I am versioning sequences with different graphics or audio mixes. So I export to a high quality file, and use it as a sub-master.

... for example, I create a bin which contains the original sequence side-by-side with the pre-render that I import into the project.

What I've found that works for me is to import the exported sub-master file, and place it back into the originating sequence on a topmost track. Then if I have to modify the edit, it is easy to do as the original edit is sitting in sync right below it.

MtD

1 reply

Inspiring
July 31, 2017

Can you explain what it is you are trying to accomplish?

Why do you need to render and replace the sequence?

Can you give an example work scenario where this is required/is a benefit?

Thanks

MtD

Ashley7Author
Legend
July 31, 2017

https://forums.adobe.com/people/Meg+The+Dog  wrote

Can you explain what it is you are trying to accomplish?

Why do you need to render and replace the sequence?

Can you give an example work scenario where this is required/is a benefit?

Thanks

MtD

It is not uncommon when working around issues in Premiere to use pre-rendering as a way to do so... for example, if you experience intermittent problems, or some quirk, and if you get one good export manually and use that, it just lets you move forward.

For example, currently Open Captions is broken with the latest version of Premiere, meaning it works most of the time, but not all of the time, and when it stops working, no captions appear burned into the video. This issue can arise while in Premiere as well as during export by AME. I can move forward if I babysit an export to pre-render a largely completed sequence so that I can capture what I need... once that's done, the intermittent nature of the Open Caption bug is no longer going to interfere with my primary/main exports. In other words, pre-render can be used as a way of removing the roll-of-the-dice with large exports when there are intermittent software issues/glitches.

I feel pre-render in this manner is not uncommon. Let me elaborate on a broader perspective connected with the specific example just cited...

I have come to realize that these products provide us with a lot of great power, Premiere, AE, Photoshop, others, each one being built up over what is, in some cases, decades of work with successful releases. All of this capability developed over the years seems to inevitably come at the expense of a huge number of variables interacting, complexity that yields software development priorities that will not always fix everything right away... some bugs remain. I'm suggesting that this suite cannot exist without bugs... that such is an impossibility without great expense ultimately to the end-user (i.e., a NASA level of test in prep for a visit to the moon applied to this suite could prevent releases for years and come at great cost... so we cut corners and we all sort of agree this is the way it is... we shoot for the best, but we admit it will not be perfect all of the time).

It seems the CC suite has a largely happy fan base. That fan base, though, isn't without its frustrations at times... I'd say this just goes to say... it seems folks expect issues and part of being good with a suite of this magnitude is developing the chops to pull out the stops, the aces in the pocket, the little tricks to workaround issues. Therefore, it seems like a great value-add to the software (the suite) to perhaps identify the most common techniques for power users/pros to workaround timeline editing and export issues. The ability to allow any old sequence, in its entirety, to be rendered-and-replaced as you can with AE comps, seems like low-hanging fruit here. Let Premiere help me work around issues with pre-render by helping me manage those situations as they will inevitably arise.

I feel Premiere should ensure there are good pre-render (render and replace) workflows for sequences... folks use that option quite often it it seems. If Premiere makes it easy to manage that sort of thing, it can actually make the product easier to use. I'm suggesting that part of what can help a product suite of this immense power and complexity is to include features that make workarounds very easy to employ. Pre-render of a sequence is an obvious one. I'm wondering if there are others... there might be value in identifying common pro/power-user workarounds, and including features in the suite that makes those easy to manage.

In my one real-world case now... Open Captions don't export reliably. I could use titles... painful to switch at this stage. I want my captions. I pre-render and use the CineForm intermediate of the sequence. I have a bin where I manage all sequences with captions... they live side-by-side with the imported Cineform mov pre-render files. It's not the end of the world... relatively easy to manage... just seems like Premiere should support this... it seems a given/natural.

With my workaround I can now reliably export my entire project without having to sit with my hands together praying... instead I can get a cup of coffee. ... really though, this pre-render thing is such a common workaround users shouldn't have to manage it... if they can do it for AE comps should be easy to do it for Sequences... the ux might be: render-and-replace sequence and sequence becomes locked (cannot be edited until Restore unrendered)... use restored unrendered it unlocks the original sequence for direct/normal editing. Low hanging fruit it seems.

Ashley7Author
Legend
August 1, 2017

OK, my confusion was based on your using the term pre-render. In my experience rendering makes a (usually temporary and discardable) preview file, while exporting makes a durable stand alone file, which can either be a master or sub-master file.

I do this all the time to expedite the edit. I don't want to have to repeatedly re-render things for preview when, for example, I am versioning sequences with different graphics or audio mixes. So I export to a high quality file, and use it as a sub-master.

... for example, I create a bin which contains the original sequence side-by-side with the pre-render that I import into the project.

What I've found that works for me is to import the exported sub-master file, and place it back into the originating sequence on a topmost track. Then if I have to modify the edit, it is easy to do as the original edit is sitting in sync right below it.

MtD


From your response I get the feeling exporting to replace a portion of the timeline, either of time savings or to work around an issue, is not uncommon... I also tried, instead of replacing the sequence with the submaster, I placed the submaster on a topmost track in the original sequence... for "safety" I mute/disable the other V/A tracks (and reverse the mute/disable if re-exporting the submaster)... this is really a nice approach thank you again.