• Adobe Premiere Pro

  Tips for a faster render on Premiere Pro CC

  Posted by Louis-philippe Denis on August 8, 2014 at 1:09 am

  Hi, I’m writing here asking for advice to get a faster render on Premiere Pro CC. I’m editing a video with a lot of layers, most of them in chroma key with Primatte Keyer.

  So yeah, I know, it’s an hungry plugin. I’m just really disappointed with how long it takes to render stuff on my timeline (not exporting, rendering) … 3-4 seconds can take like 5-10 minutes. Just Primatte and a moving background.

  I have a pretty strong built (except the GPU that I’ll change pretty soon). The videos are in DNXHD, 1080p. They’re from an internal SATA hard drive.

  Windows 8.1
  SABERTOOTH 990FX R2.0
  AMD FX(tm)-9590 Eight-Core Processor 4.7GHZ
  16 GB DDR3 RAM
  ATI Radeon HD 4600
  1000w Power Supply

  Thank you for your help.

  Mike Wood replied 10 years, 9 months ago 4 Members · 7 Replies
• 7 Replies

• 

  Paul Neumann

  August 8, 2014 at 1:47 am

  Build a custom sequence where the preview codec is DNxHD matching your footage exactly. Then try using Ultra for your keying. It’s very good.
• 

  Louis-philippe Denis

  August 8, 2014 at 2:28 am

  Oh my god. Wow. That makes all the difference in the world.

  (the custom sequence) … Should’ve thought about it sooner. Thank you!
• 

  Paul Neumann

  August 8, 2014 at 3:03 am

  Yeah, so when you’re done go ahead and render (shift + r) your timeline and then when you export check the “Use Previews” box and you’ll get super fast output.
• 

  Steve Brame

  August 8, 2014 at 12:36 pm

  Paul, is this because DNxHD is an inherently faster writing codec, or is it just faster to stay within the same codec when encoding previews?

  Asus P6X58D Premium * Core i7 950 * 24GB RAM * nVidia Quadro 4000 * Windows 7 Premium 64bit * System Drive – WD Caviar Black 500GB * 2nd Drive(Pagefile, Previews) – WD Velociraptor 10K drive 600GB * Media Drive – 2TB RAID0 (4 – WD Caviar Black 500GB drive) * Matrox MX02 Mini * Adobe CC
  ——————————————-
  “98% of all computer issues can be solved by simply pressing ‘F1’.”
  Steve Brame
  creative illusions Productions
• 

  Paul Neumann

  August 8, 2014 at 1:36 pm

  Just because the Preview codec matches the source/output. I have presets for DNxHD workflows, P2 workflows and ProRes workflows.
• 

  Steve Brame

  August 8, 2014 at 3:01 pm

  I suppose that in a mixed format sequence, whatever the majority codec is would be the better choice for a preview codec?

  Asus P6X58D Premium * Core i7 950 * 24GB RAM * nVidia Quadro 4000 * Windows 7 Premium 64bit * System Drive – WD Caviar Black 500GB * 2nd Drive(Pagefile, Previews) – WD Velociraptor 10K drive 600GB * Media Drive – 2TB RAID0 (4 – WD Caviar Black 500GB drive) * Matrox MX02 Mini * Adobe CC
  ——————————————-
  “98% of all computer issues can be solved by simply pressing ‘F1’.”
  Steve Brame
  creative illusions Productions
• 

  Mike Wood

  December 9, 2015 at 12:05 pm

  I’m having a similar issue. I just spent a bunch of money on Primatte (along with the whole Keying Suite) and it seems to work much more smoothly in After Effects (CC 2014) than in my Premiere Pro (CC 2015) application. I’m just doing a simple chroma key (albeit, a pretty bad green screen, so I’m trying new keying software), with a video layer (QuickTime H.264 files) and a background still image layer. Just rendering a 10-15 second clip takes appx. 18 minutes in Premiere. Even just adjusting the parameters for the Primatte plug-in in Premiere bogs down the whole system and VERY often gives me the “beach-ball” while it stalls (usually just a few moments, but it’s after ANY click of the mouse on a parameter setting)!

  I’m running these on a brand new (late-2013 model) Mac Pro (trash can) with the following specs:

  Processor
  • 3.7GHz Quad-Core
  – Intel Xeon E5 with 10MB L3 cache and Turbo Boost up to 3.9GHz
  • 3.5GHz 6-Core
  – Intel Xeon E5 with 12MB L3 cache and Turbo Boost up to 3.9GHz

  Memory
  • 3.7GHz Quad-Core
  – 12GB (three 4GB) of 1866MHz DDR3 ECC memory

  • 3.5GHz 6-Core
  – 16GB (four 4GB) of 1866MHz DDR3 ECC memory

  Graphics
  • 3.7GHz Quad-Core
  – Dual AMD FirePro D300 graphics processors with 2GB of GDDR5
  º1280 stream processors
  º256-bit-wide memory bus
  º160GB/s memory bandwidth
  º2 teraflops performance

  • 3.5GHz 6-Core
  – Dual AMD FirePro D500 graphics processors with 3GB of GDDR5 VRAM each
  º1526 stream processors
  º384-bit-wide memory bus
  º240GB/s memory bandwidth
  º2.2 teraflops performance

  Storage
  • 256GB
  • PCIe-based flash storage

  I have my Mercury GPU acceleration clicked “on” but I don’t know that that’s the issue.

  Any help would be greatly appreciated!

Reply to this Discussion! Login or Sign Up