Tag Archives: Premiere Pro

Audio101 – Quicktip – Audio in Premiere

20 May

These are some quick tips for more precise audio work in Premiere Pro …
Setting up your workspace and switching your sequence to Audiounits so you can line up audio clips better in your sequence.

THIS IS THE VIDEO I WAS WORKING ON IN THAT PROJECT: vimeo.com/66087839

blog: film-sound-color.tumblr.com

music (via VIMEO MUSIC STORE):
6th Sense

Voice-Over was recorded with the SAMSON G-TRACK …. test & review will be online soon

Premiere Pro CS6 render & export times

2 Jul

UPDATE JAN. 2014:

Reduce export time in Premiere Pro CC
“Use Preview” now works pretty good
in Premiere Pro CC 7.2.1

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

A lot of numbers flying around in the interwebs regarding the power of CUDA in Premiere Pro. Mostly they are about how much layers of blur or how many “tracks” of HD video can be played in realtime without dropped frames without rendering and stuff like that. All that is very nice and indeed the combination CUDA & Premiere Pro  is very powerful. In Fact its the most impressive native codec / footage performance I have seen and experienced so far – if you have a powerful machine.

On a 2006 MacPro you will not have the same experience at all.

Anyway – i wanted to see how that “translates” to a real life / real work project. Especially with things like MagicBulletLooks.

After seeing a post from Juan Salvo about what Nvidia Card might be the best in terms of CUDA power I was curious how a GTX285 and GTX480 will perform in a real work test.

So for this test i used a rather typical 4min 20sec project. Mostly h264 files from a DSLR, some ProRes files, some HDV files, a few AfterEffects titles (via Dynamic Link) … just a Stereomix-Track from ProTools (wave file). A usual edit –  we do all the time – for a Corporate film clip. Color Grading was done via MagicBulletLooks on every clip (like we do all the time) The MagicBullet effects i created look like that:

So in the end a “Everyday-Project / Edit” for us.

I used the DSLR 1080p25 project preset in Premiere Pro. No other effects were used. Nothing fancy

All that on a 2009 MacPro 4,1,  8 Core 2.26 GHz, 32 GB Ram, 7200 rpm Hard drives, on MacOS X 10.7.3.  CUDA Driver 4.2.7, GPU Driver 1.3.4.0 (270.00.00f01)

I used different combinations of Nvidia Graphics Cards. GT120 (standard card of the MacPro 4,1 ) + GTX285 (Mac Card) GT120+GTX480 (Window card that works with MacOS Lion with the Nvidia driver …. with out boot screen though) and GTX285 and GTX480 the GT120. The GT120 was used to connect the screens and GTX card for CUDA processing only ( at least that is what was recommended by many sites and ppl)

I also tested the single GTX cards – so I connected the screens to those for these tests. (I always used DELL 17” + DELL 22”)

Here is the edit I used for that test … just so you have a better idea what i’m talking about.

Since I did not get any realtime playback even with 1/4 resolution with all that MagicBulletLooks on the clips I had to render to see any “moving pictures” with the final grade … with all the cards and combinations)

here are the numbers:

So even though the combination of GT120 + GTX card might work good for CUDA processing only it actually it’s very bad for stuff like MagicBulletLooks or Colorista 2 that uses OpenGL for GPU processing and so the GT120 slows everything down quit a bit. Also the GTX285 that actually is a Mac Card is quite unstable in terms of crashes and freezing the app during render or export ( = PPro crashes )  … so in the end the GTX480 is the better salutation (here is how I did get the card to work.

One side-note though: Sadly Premiere Pro doesn’t seem to use the rendered preview data for exports. So even if you activated the option “use preview” that really doesn’t change that much export times. So for long projects with a lot of 3rd party effects on clips export times are getting quite long. That is a big issue.
Conclusion: 

- The Combination of GT120+GTX card did not work that good especially if things like MagicBullet Looks are used.

- GTX 480 works best

- Encoding via Adobe MediaEncoder is slower especially if you count the time it takes to “send” the project to the MediaEncoder

- The option “use previews” for export doesn’t  really work

I will test an edit with transcoded ProRes footage soon just so i can see if that changes anything. I still have not found the best Workflow for Premiere Pro – so hang in there and stay tuned.

UPDATE JULY/02/2011:

so i did the whole ProRes Sequence Preset settings for better “use previews” and therefore faster export times thing:

… but did not really change a thing:

Render time was 20:36 (so around 2 min longer than native) … export time was 17:04  so not really faster than the 16:46 export time i got with native or the 17:09 export time native to ProResLT)

UPDATE JULY/11/2012:

So I still testing stuff to find the “best” workflow and settings for Premiere Pro. I’m still on a “voyage” to figure out the “use Preview” issue … I tried all kind of stuff – deactivation of CUDA – transcoding footage to ProResLT and working with that in a ProResLT sequence – using Blackmagic uncompressed Sequence settings ….

… everything I could come up with … still no real change basically export time = render time even if I rendered everything before. My guess: Its a OpenGL/MagicBullerLooks thing, because some people actually seem to benefit from the “use preview”  … just not with MBL stuff . See: Biscardi Creative Blog – Continuing Tales of an FCP Switcher – CS6 workflow, for now

So anyway I also did compare Premiere Pro vs. FCPX vs. AVID MC6 vs. FCP7 with the same project (new – a bit different form the initial test). still around 4:16, same footage (Transcoded to ProResLT), same edit, same MagicBulletLooks settings/preset.

Here are the results of that Test:

So apparently even FCP7 smokes FCPX in terms of render time of MagicBulletLooks stuff. Also FCPX crashed like every 5-10 minutes while rendering. AVID MC6 did a good job but since it was linked AMA ProRes Footage “overall performance” did not feel as solid as PPro or even FCP7.  The old school FCP7 worked actually quite OK – not surprisingly so due to ProRes transcoded footage. So at the end of the day PremierePro is “solid average” – quite usable though I guess … for now … I still will have an eye on all that and let you know as soon as I find out new stuff or solutions.

Premiere Pro CS5.5 & Blackmagic Design

27 Mar

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 ;)
Follow

Get every new post delivered to your Inbox.

Join 3,516 other followers