Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Native R3D editing in CS6 and final export to 1080. 720 etc

Hey Johnny,

Otherwise, I'd just use a 1080p Sequence and I'd use "Scale to Frame Size" for the media. The only exception to that is if you need to zoom in on the images or if you have a Pan and Scan workflow.

Like I mentioned before, by my experience, "scale to frame size" or manually zooming in is exactly what kills the render time.

I've noticed that the less you scale, the better it works. Therefore scaling 5K footage to 4K timeline works fine, and doesn't add that much to the render time, but going to 2K or 1080p is murder, and it takes 10-20 times longer to render.

Of course, I am not sure if I am missing out on something in my workflow, except for the RR of course. But since I started editing at native resolution, the render time issue went away.
 
Sami,

The project that we're discussing has 1080p or 720p source in it. You can't export that from a 4k / 5k timeline.

Scale to frame does not cause 20x slowdowns. Especially if the sequence matches the export. I've done it a million times.

Best,
Wes
 
Thought I'd chime in as well with a few gotchas...

First, your Quadro card, and Cuda support, only help on effects added to Premiere clips or sequences, they do not help in the base processing of footage. They will make your fades go faster and clips with color correction will render a bit faster than if you let the CPU do the work, but thats the limit as to where the gains are.

Second, you may have to 'control' your RedRocket card (depending on your project). I have a feature with a lot of linked Ae comps, therefor I have the setting "Use Rocket" saved in the Ae files and "Use None" in Pr. Saves me a few hours of rendering. I often make the mistake of opening Pr while set to use the RR AND while another program already has it (Ae or RedCine). You get a little red error X in the corner of your main window to tell you this, but it's easy to miss. To verify that the RR card is actually being used you should pull up your process list and verify that the app in question is not causing ImporterRedServer processes to use CPU cycles. If it is you have a problem somewhere (driver, firmware, another program has it).

Third, if you are going to do a lot of Adobe editing and special effects, get off the Mac. You are far better off with a single overclocked i7 around 4GHz than a pair of Zeons ~3GHz (I won't bore you as to why). Add to this more PCIe slots for cards, faster memory, more memory, and most importantly bigger and faster RAID arrays (if you are willing to take the time to set it up right). My 4GHz i7 Asus P6T7 WS SuperComputer can run circles around my dual 3.2 GHz Mac Pro, and do 5.1 sound to boot. 550Mb/s read speeds out of a simple 5 disk software RAID5 array of 2TB WD Caviar Blacks. Also has enough PCIe slots for multiple video cards, RR cards, RAID cards, whatever...

Bob
 
Bob - you might consider Western Digital RE4's for your next RAID. They are specifically designed to fail instead of heroically trying to correct a marginal sector - which is exactly the behavior you want in a RAID to minimize latency.
 
Back
Top