The CS6 version of Adobe Premiere Pro went a long way towards winning me over after Apple stranded the FCP7 community with the release of FCPX. I still have many, many gripes, including stability concerns in the Mac version, but I believe Premiere is close to being a product I can fully recommend. So it is a shame that it is still missing an important feature: background rendering.
Update May 7, 2013
Adobe has announced that the next version of Premiere will be Adobe Premiere Pro CC. The switch to the Creative Cloud subscription model has caused immediate controversy, but personally I think it’s a reasonably good deal IF they keep making significant improvements to their products. I would say that the majority of Adobe’s apps are in desperate need of an overhaul.
Regardless of the Creative Cloud controversy, however, this next version of Premiere Pro looks like a solid upgrade. Adobe has started to put a dent in my Premiere Pro wish list.
HOWEVER, despite all the new features, Adobe Premiere Pro CC still does not offer any form of background rendering!
On the positive side, Adobe did make a very important upgrade to smart rendering in CC. Smart rendering and the “use preview files” export option now work with Apple ProRes. This is huge for those of us who are accustomed to the Final Cut Pro 7 workflow.
Yet, by adding ProRes smart rendering, Adobe is acknowledging that rendering as you work is a legitimate Premiere workflow. Of course it is, because it can save substantial time when exporting. Despite faster hardware (or even because of faster hardware, as I explain below), background rendering is more crucial than ever.
Also, Avid has announced that Media Composer 7 will have background processing. Adobe needs to keep up.
For a detailed look at some major benefits of background rendering, read on…
Adobe ambitiously envisions an NLE into which you can dump any format, edit with real time effects previews, and quickly export directly to your delivery format of choice. It’s a worthy goal.
They have made impressive strides in the first area. Being able to skip transcoding and go right to editing is a wondrous thing.
They have achieved mixed results in the next area. Clips with effects still require rendering to scrub smoothly and sometimes just to play, particularly at full resolution. Multicam is particularly an issue, even with the latest hardware and a supported GPU, and the most common Mac GPUs are not supported at all.
The last part — exporting — is the real problem.
In Final Cut Pro 7 — or with background rendering activated in Final Cut Pro X — exporting to ProRes is extremely fast. This is because FCP does not need to re-encode the video. It takes the previously generated ProRes render files and stitches them together with no generational loss. This is sometimes referred to as smart rendering. In Premiere Pro, it doesn’t matter if you’ve already rendered out the entire sequence to ProRes and are exporting to ProRes. It re-encodes the whole thing every time.
If you need to adjust even a single frame of your sequence, you will then need to re-export the entire sequence, no matter what format you choose. For longform projects, this is a major drawback of Premiere Pro.
You can opt to “Use Preview Files” on export, but this is not what FCP switchers might think it is. Media Encoder still re-encodes every frame even if this is checked in almost all instances. It simply uses the previously encoded render files to assist with the processing. There is a generational loss from those preview files, and the speed improvements are marginal.
“Smart rendering” does already exist in Premiere CS6 for a small number of codecs, such as DV and DVCPro, but not for ProRes (or DNxHD). A smarter system would indicate when the smart rendering capabilities of “Use Preview Files” are enabled (rarely) and when they are not.
Update: As I added above, Adobe has announced that Adobe Premiere Pro CC will support smart rendering of ProRes and DNxHD. That’s awesome! But it’s half the battle. Now that Premiere can use pre-rendered ProRes and DNxHD preview files to speed up the export process, it’s time to allow that rendering process to take place in the background as it does in FCPX and the upcoming Avid Media Composer 7. At the very least, an idle time auto-render setting would be a simple and useful feature.
At a basic level, background rendering would allow many Premiere Pro users to work with fewer interruptions. Maybe that’s the down side! In my experience, adjusting clips that have effects applied to them, even simple color corrections, means that I have to wait…and wait…for preview files to render before I can audition a new cut. In the mean time, I am blocked from doing anything else in the application. (If more Mac GPUs were supported, this might be less frustrating.)
Until I can preview any sequence full-screen at full-res with multiple effects, rendering will be part of my workflow, and therefore background rendering would be beneficial.
I don’t mind dropping the playback to low resolution temporarily as my footage renders, but I shouldn’t have to export a sequence to preview it at full res.
Quality hardware is an important investment, but requiring everyone to work on pimped-out towers at all times is not the answer. Sometimes, the available hardware is not your call, and there are many jobs where being able to cut on a laptop is crucial. I have found this to be the case with large corporate events where work areas are often set up quickly, sometimes in tight corridors, and subject to change. There are many other forms of production where mobility is even more important.
Also, with each bump in processor power comes a new, more demanding codec. 4K is here, and Adobe’s solution for editing raw is to use a proxy format. What? This completely upends their no intermediate codec philosophy.
Smart background rendering
Though performance is an obvious concern, the real potential of background rendering lies in combining it with the export process. Let’s call this “smart background rendering.”
If Premiere Pro allowed you to set the preview file format to the export format of your choice, encode as you go via background rendering, and export using a true “Use Preview Files” option, it would save substantial amount of time in the export process, especially when it comes to re-exporting after making adjustments to the sequence.
As one commenter put it in a Creative Cow thread on smart rendering in Premiere, “Being able to render as you go does save a bunch of time when last minute revisions pop up.” For long sequences, the benefit is enormous.
It should be noted that it is already possible to set the preview file format to Apple ProRes. It requires choosing a “Custom” edit mode while setting up a new sequence. (In any other mode, the preview file format selector is grayed out and locked into the lossy MPEG format.)
When I first floated my thoughts on Premiere Pro and background rendering in the Adobe forums, it was met with some resistance from long-time Adobe Premiere Pro users. (No, I didn’t realize such a thing existed either.) Many of them just seemed concerned that Mac OS users were taking over the ship, but I agreed with one point, which was that it should be possible to turn background rendering off. I would suggest making three different options available in the preferences. Rendering should start: automatically (instantly), only through manual initiation, or during idle periods. It should also be possible to batch render sequences in bins.
Blackmagic Cinema Camera and CinemaDNG
(This section concerning the BMCC is an edit to my original post — 2013/04/03)
The increasing popularity and affordability of RAW workflows has added a new and exciting wrinkle to this discussion. You know what I’m talking about: the Blackmagic Cinema Camera and its use of the CinemaDNG file format.
Adobe discontinued native support for CinemaDNG in Premiere just a few months ago. Ironically, it was Adobe who developed the open-source RAW format in the first place. It seems they weren’t satisfied with the real-time performance in Premiere. I have no doubt that their concerns were legitimate (5 MBs per frame of RAW camera data…geez), but it’s just another argument for more powerful rendering options.
If Premiere supported background rendering, they could offer full native support for CinemaDNG. Systems that don’t have the processing power to handle it, which might be the majority of them at this time, would have a fall-back that doesn’t require a workaround such as converting the footage to lossless using After Effects.
Instead, Adobe is choosing a stubborn, idealogical commitment to native-only editing over compatibility with an important format.
Even for non-RAW workflows, conforming to a high-quality codec via background rendering has the potential to make it easier to get sequences out of Premiere and into third party software such as DaVinci Resolve.
To be fair, Adobe was apparently caught off guard by the sudden emergence of the BMCC and Blackmagic’s choice to rely on CinemaDNG (per Kevin Monahan). This gives me hope that they will reconsider their stance against proxy formats and introduce more advanced rendering options.
At the very least, a built-in proxy format system would be advantageous. If we’re going to be forced to transcode our source footage anyway prior to editing, Adobe’s aversion to intermediate codecs doesn’t really make sense.
Update: Adobe has added native support for CinemaDNG in Premiere Pro CC 7.1! That’s awesome (if you have a new Mac Pro that can handle it). They also added improved capabilities for relinking from proxy media back to full resolution. That’s also awesome, although I would still prefer to work with the original footage and background render preview files for smooth playback. Once again, if you have to transcode, native support doesn’t really mean anything.
Multiple, simultaneous render formats
Simple background rendering would allow Adobe to catch up to FCPX in that regard, but there is an opportunity here for Premiere Pro to leapfrog Final Cut’s background rendering capabilities altogether:
Media Encoder can already encode in the background by creating a temporary copy of your project file. Imagine if it could go to work on active sequences, as you continue to work, and render into multiple file formats. In most cases, I would set it to ProRes for my master and a flavor of H.264 for web delivery, choosing ProRes as the preview format as well. I dream of completing a project in Premiere and then…well…that’s it. It’s already encoded. Just export at the “speed of save.” Then start your uploads and catch up on some much needed sleep.
If this seems like it would be beyond the power of most systems, FCPX handles a single stream of background rendering fairly smoothly even on somewhat older Macs. If your computer can encode one sequence quietly in the background, then it should be able to handle two or more, perhaps prioritizing the preview format.
Higher quality previews, faster exports
Adobe Premiere Pro needs background rendering to allow editors to work more quickly and effortlessly from start to finish, and it’s time for Adobe to bite the bullet and accept that there are benefits to a high-quality intermediate codec that can take advantage of smart rendering. If ProRes or DNxHD present licensing problems, Adobe should develop their own standard.
Adobe, this is your chance! By including smart background rendering (in addition to a mere 88 feature requests), you have the power to make us forget that we ever pined for FCP8. We’re counting on Premiere Pro CS6.5 or CS7 to come through before we’re forced take another serious look at FCPX!
I hear you on smart rendering, I hope everyone makes a request for popular formats to have smart rendering support. I wrote a blog about the currently supported formats: blogs.adobe.com/kevinmonahan/2012/10/11/smart-rendering-in-premiere-pro-cs6-6-0-1-and-later/
Background rendering is a different enchilada and would require a wholly different feature request.
Here is the the link: http://www.adobe.com/go/wish
GingerHDR (don’t get fooled by the name) already provides nice native import and realtime experiance in PP.
Background rendering is a two sided sword.
1. it eats recourses and can ruin your realtime experience.
2. pre rendering is nothing like proxies on the fly – it eats disk space.
3. With a proper build PC I have realtime experience in PP with any format (up to 5k RedRaw). Folks that bitch about the lack of smooth scrubbing and performance, usually come with a knife to a gunfight – i.e. using a sub par laptop (mostly Apple) instead of a proper workstation.
Starting with #3, I agree that investing in quality hardware is critical. However, the reality is that we may need to work on less than perfectly optimized systems for any number of reasons from budget to mobility to the decisions of others. It’s also hard to find a Windows computer on a production set, at least on the US coasts, and laptops often make the most sense on the road. It’s impressive that Premiere works cross-platform as well as it does, but background rendering and better smart rendering would serve to make it more versatile with better performance in many cases.
As an example, last year I worked a large press event in Las Vegas for HP Computer along with another editor and two assistant editors. Somewhat ironically, but not surprisingly, the pieces we created to showcase the new Z1 workstations were all cut in FCP7 on Mac laptops and an older Mac Pro.
I could see convincing the other editors to choose Premiere over FCPX, but nothing would ever convince them to give up their Macs, even after a week of witnessing the impressively powerful Z1 workstations in action. And for this particular shoot, we had to move our production area around a lot while working under very tight deadlines. So laptops were a necessity.
#2 One of the great things about rendering is that you can always delete the files to recover disk space and just re-render if need be.
#1 Absolutely. I don’t see any downside to having it as an option that can be disabled though.
I took a look at GingerHDR and it’s intriguing. Thanks for pointing it out. I will learn more.
I completly agree with you. Even if you have a very good computer, you always need to render every 10s to see what’s going on.
If there was a background rendering, we’ll be able to do another part of the timeline instead of waiting waiting waiting and waiting. Adobe claims Premire Pro have very good performance, but I had a Mac I would really want to try Final Cut ProX because some (a lot) people say it’s crap, but this software have background rendering, it’s slow on a old computer but may be it’s great on a last generation (I didn’t try).
I didn’t find a plugin to allow this, would be great ! What is the best way to increase rendering ? or to avoid them ?
And about the export, it’s just a joke, you already spend hours to render and you have a check box who says use rendering and you need once time again to render and slow down your pc ! So frustrating !
So yes Premiere Pro is nice, but if you apply effect on clips it’s just the worst program because you spend your all time to do rendering !
Hope Adobe will do something but I’m very suprised they didn’t talk about it on the new sneak peak for the next CS generation … So Sad !
I really hope adobe will read this and do something ! Hope Adobe will read your other post with wish list 😉 !
The original article does not account for mxf smart rendering in cc. Additionally even before the cc I could setup custom timeline settings with the codec I knew I would use in the end for the final output, use the highest quality and the bit depth, and use render timeline in to out in the off times ( coffee breaks, in between editing sessions) and then, when rendering the final output I would select the use the previews. That way it would just stitch the preview media as it would do in Fcp. High quality and very fast render.
Proper smart rendering with the “use preview files” option only became available for ProRes with the release of CC. It’s a nice improvement. And I’m glad to hear that smart rendering works for .mxf files as well.
I would still like to see true background rendering, or, at the very least, automatic idle rendering after a set period of time. It’s sounds like you’re good at initiating rendering during breaks, but that’s not something I tend to remember to do when I take a phone call or switch to another app for a bit.
As I mention in my updated list of CC gripes, it would also be nice if there were some indication next to the “use preview files” option to let you know, with certainty, whether or not smart rendering is available for the currently set preview codec.