EDITING 101: Reduce export time in Premiere Pro CC

So if you use like Magic Bullet Looks or any other “heavy & slow” plugins and want to reduce Export-times in Premiere Pro you should set your Sequence to ProResLT or any other good Master codec and work / edit with that Setting.

If you use like MagicBulletLooks and such you had to render while working anyways but you don’t have to re-render everything again with exporting. That happens usually if u don’t have “Use Preview” selected,

So to have this working properly you just select “Match Sequence” and “Use Preview” in the export settings and you are good to go.

Render-Times for this Sequence (GTX760):

with 1080p25 DSLR Seq. Preset = 16min 41sec
with 1080p25 PreResLT Seq. = 14min 42sec

Render-Times for this Sequence (GTX480):

with 1080p25 PreResLT Seq. = 14min 38sec

Render-Times for this Sequence (GTX480):

with 1080p25 PreResLT Seq. = 15min 35sec

Render-Times for this Sequence (GT640+GTX480):

with 1080p25 PreResLT Seq. = 19min 28sec
(it seems it uses the only the GT640 for openGL rendering)

—————————————————————————–

RENDER TIME WITH XFX Radeon HD 7970
(same 2009 MacPro, same sequence, same settings)

with 1080p25 PreResLT Seq. = 26min  37sec

(export time with Match Seq. + Use Preview was basically the same)
 

Rendertime with XFX Radeon HD 7970
in Windows 8.1, Premiere Pro CC, DNX 120 1080p Preset
32min 55sec

—————————————————————————

Export-Time for this Sequence (GTX760):

with 1080p25 DSLR Seq. Preset / no “Use Preview” = 15min 40sec
with 1080p25 PreResLT Seq. + Match Seq. + Use Preview = 01min 51sec

————————————————————————-

The Video-project in this “Tutorial” is actually a “real life” work project:
http://film-sound-color.prosite.com/124476/2094887/work/minidocu-city-leaks

BTW for your reference: I’m on a 2009 MacPro 4,1 with 2x4Cores, 24GB Ram, GTX760 4G GPU, OSX 10.9.1 on a SSD with Adobe Premiere Pro CC 7.2.1. Also have ny Render/Scratch disk on a 2nd SDD and also export to the other SDD.
Oh and here a link to on quick test export with a different project regarding that DNxHD gamma/REC709 issue:

ProRes Export (how it should look)

https://vimeo.com/68263407

DNxHD Export (REC 709 gamma issue)
https://vimeo.com/68239611

Music:
6th Sense – Both Nice
Robbero – Spheres

UPDATE II:

So i did a lil test (just for fun) to see if the HD7970 works better in FCPX, so i used 7toX to get the Project from PPro to FCPX

The Titels showed up as black video but thats ok I replaced that (did not expect to go through anyways) but other than that all good actually ….even though I “cleaned up” the Sequence a bit before … it was just like exporting as FinalCutPro XML opening that file in 7toX … importing that new XML in FCPX…. done! …now of course the MBL values und plugins do not show up but thats OK. One note on that: I had to update to FCPX 10.1.1. and re-installed MBL bcuz before FCPX 10.1 crashed a lot or even the MacPro went black and re-started … now in 10.1.1 all seems to work … render now and see what time i get in FCPX

So now the Rendertime:

FCPX Export-Time for this Sequence: 22min 20sec
(same 2009 MacPro with HD 7970, same sequence, same settings…only DenoiserII missing on the last clips)

PremierePro & Cuda on MacOS 10.8.2 on a MacPro

I now can confirm with the updated drivers for the nvidia card (GT120+GTX480) that PProCS6 works perfectly smooth even with a lot of  MagicBulletLook use (h246 and ProRes clips / 1080p25)

here are some links you might want to check:

QUADRO & GEFORCE MAC OS X DRIVER RELEASE for 10.8.2
http://www.nvidia.com/object/macosx-304.00.05f02-driver.html

current CUDA for 10.8.2:
http://www.nvidia.com/object/cuda-mac-driver.html 

Optimize rendering settings:
http://film-sound-color.tumblr.com/post/31268656116/if-u-have-issues-exporting-or-even-rendering-stuff

GPU for Resolve9 AND PremierePro CS6 in ONE system:
http://liftgammagain.com/forum/index.php?threads/gpu-for-resolve9-and-premierepro-cs6-in-one-system.580/

How To Enable GPU Cuda in Adobe CS6 for Mac:
http://film-sound-color.tumblr.com/post/26071716910/how-to-enable-gpu-cuda-in-adobe-cs6-for-mac-by

Premiere Pro CS5.5 & Blackmagic Design

Well we are testing Premiere Pro CS 5.5 for a few weeks now. Yes, we tried that in the past and it did not work out well. But with the release of the 9.2 Version of the Blackmagic Design drivers (Blackmagic Design Desktop Video 9.2 – a while ago now) for the BMD Video-Cards we use  something changed and now it actually works quite well.

Now, we still use FCP7 for older or “special” projects. But with CS6 in the very near future things are looking good … well bad for FCP and Apple. The whole AVID MC 6 thing did not work that good for the stuff we do… even though it’s a great NLE … it’s just not for how we things rock over here, lets just leave it at that. I will not talk about FCPX … u know how I feel about it … for some work its great …for most stuff not tho’ (a matter of “taste” anyway) … it will take a loooooooong time till that App will be 100% ready … end of story (for FCPX).

Anyway… here are some settings  that worked quite well for us and our “old” MacPro’s with Blackmagic Cards. One note: We are in PAL-Land so we work with 1080p25 or 50i … u might try other frame rates for your footage!

BTW we are on “older” MacPros with 12 GB Ram, MacOS 10.6.8 and BlackMagic Design Decklink HD Extreme 2 cards. (We did not test this in LION  / 10.7.x)

All starts with a “New Project” … select “Blackmagic Capture” … just to be safe. ( at this point I’m not 100% sure if that is Essential or not)… and choose a project name and make sure you did choose a (the right) project folder / location …

You might choose your Video “Settings” … (that is for capture only… if u want to do that)

Now comes the essential part: After you hit OK … You have to choose the Blackmagic Design HD1080 preset (8 bit or 10 bit with the Frame-rate your footage is in) Don’t use the DSLR Preset, that doesn’t work well at all for most Machines (using ProRes footage / with external Playback) One side-note if you use an external Monitor (via HDMI for example) that can not play/show progressive footage (25p in our case) you have to choose an Interlaced Preset (50i in our case) … you will be able to work with progressive  footage (25p in our case) just as good in that Interlaced Timeline it will NOT change it to interlaced or something …. at least in our case.

Now, before you start to work on anything you have to select your playback engine (Player Settings) so that your are able to see anything on your external monitor.

Select “Blackmagic Design Playback” (that is essential!)

After that select your current Timeline / Sequence and go to the “Sequence Settings” ( that only works if you have your Sequence selected … trust me)

Here you might select the codec of your footage. You can “play” with that setting … test out what works better on your system / with your footage.

… and that’s it … all should work well now … if not, let me know … we will keep testing stuff out further on and pretty much look forward to what happens at NAB this year with CS6 🙂 if you have questions, use the commends section below.

On side note … for FCP7 users i highly recommend using the FCP keyboard shortcuts in PPro (even map your own shortcuts to keys).

The only thing we are really missing so far is coping and removing of attributes from clips (that works differently) and moving clips arround in the timeline with the keyboard (up and down) doesn’t work like in FCP7 … and of course other smaller stuff here and there but in the end it kinda is ok coming from FCP7 … if you don’t see it that way … try AVID MC6 and you will see what I mean 😉