Premiere CS6's "Export Media" is one lazy bugger.

[Mike P.]

I didn't get a chance to read through this entire thread, but have you set your Optimize Rendering for "Performance" under the memory tab?Whenever it's set to "Memory" I only get about 35% CPU usage... When I set it to Performance it maxes out (98-100%) on all 8 cores and gives me about 2x realtime for renders to 1080p ProRes or 1080p Blu-Ray MPEG2 (assuming max bit depth and max render quality are disabled.)

EDIT:
Premiere>Preferences>Memory>Optimize Rendering for: And choose "Performance."

It hogs a boatload more memory, but you've got 32GB so you should be fine.

[Petri Teittinen]

Mike, I have it set for Performance.

At the moment it looks I've stumbled on a bug where Premiere and RED Rocket refuse to talk to each other when Premiere's trying to process 16x9 footage (for example 4800x2700 and 2880x1620) shot on Epic. I did a test using 5120x2160 content (i.e. 2.37:1 aspect ratio) and Premiere exports were lightning fast. Adobe is now aware of the bug so I guess we can expect a patch soonish.

[Johnny Friday]

Hope you stay with it Petri.....I just find work arounds now since i have so many problems with Premier. The RAW format is why i moved over, but at times it's just so slow and painful that i go back to FCP and prores 4444 transcodes for far faster turnaround times. When and if Premier comes of age....i'll be very happy. but so many 3rd party items for them to work with i sometimes don't even know how they can do it....But, we are left with bugs to report all the time that's one thing for sure.

[Petri Teittinen]

A brief recap for folks who are not following my "Premiere playback smoothness" thread.

Trying to edit and/or export RED footage which has a 16x9 frame aspect ratio (for example 4800x2700 or 2880x1620) on system equipped with a RED Rocket results in very long export times and poor playback performance in Source and Program monitors.
Note: playback performance could be improved by setting playback resolution to Full. I'm not aware of a similar workaround for exporting.

I ran tests on a short clip with a resolution of 5120x2160 (i.e. frame aspect ratio of 2.37:1). Playback in Source and Program monitors is smooth in 1/4 and 1/2 resolutions, and exports are very fast indeed.

Adobe is now aware of this bug.

[Brad Allen]

Nice work on continuing to chase this down Petri rather than just throwing your hands in the air :)

Johnny, I'm fairly certain I could achieve much faster rendering times by using AME. But going that route would defeat the entire point of Premiere's support for native RED format. I don't wish to do that one extra step of exporting from Premiere into something I can feed into AME. To me that feels totally pointless and a waste.

Just wanted to mention that I think Johnny just meant sending it to AME via the queue button when you are exporting? Doesn't really require any extra work on your part, it just renders it out with AME instead. However it's kind of a moot point for a few reasons:

1. The export command should work from within Premiere
2. Exporting out to AME while having Premiere still open will mean that Premiere still has control of your Rocket and AME can't utilize it.
3. AME when rendering Premiere projects actually launches background instances of Premiere to do the rendering as far as I can tell, which means the pipeline between exporting through Premiere directly and AME isn't actually all that different. (But you do at least get a preview window in AME :P)

[Petri Teittinen]

Nice work on continuing to chase this down Petri rather than just throwing your hands in the air :)

Cheers Brad :)

Just wanted to mention that I think Johnny just meant sending it to AME via the queue button when you are exporting? Doesn't really require any extra work on your part, it just renders it out with AME instead.

Whoops! For some reason I automatically assumed he meant a more tortuous solution... Guess I'm one of those "glass half empty" guys :)

[Johnny Friday]

Brad....yes, that's what i meant. You pointed out something i could never verify to work....exporting out of Premier or AME and getting some additional performance from RR card...I NEVER saw a peformance jump---I also submitted (months ago) a feature request to be able to some-how turn on/off RR card from different programs....going from Premier to AME as an export---then choosing something like: "utilize rocket card"...so that it disengages from current program and then utiilized by new program of your choice---same in AE....when exporting to AE....anyway, maybe the terrible performance or no performance issues i experienced were all because i was working with mostly 4k 16:9 footage and transcoding to 16:9....I was getting around 20 to 1 transcode ratio--so 20 or so hours for a one hour doc....and kind of heavy with effects....and a mac 8core i7 32gb ram; quadro 4000 card, red rocket card.....did not seem right AT ALL

[Les C.]

On my mac Pro 2009, I had a big trouble during rendering with CS55. The rendering process began fast, then get slower and slower and only 1 core was left used. I was going crazy with this until i understood that the heat of the cores was the cause : Premiere use all the power of the cores and the temp increase in 5 to 10 minutes (i use a soft to monitor the temperature of the core). When a certain limit has reached, my computer stop using all the core. The problem is that the power don't come back until the next reboot. I changed the fan speed on the core to the maximum when i do rendering. Now, i have not this problem anymore. May be this can help.

Olivier

useful for fan control on MacPro
http://www.macupdate.com/app/mac/23049/smcfancontrol

[Brad Allen]

Brad....yes, that's what i meant. You pointed out something i could never verify to work....exporting out of Premier or AME and getting some additional performance from RR card...I NEVER saw a peformance jump---I also submitted (months ago) a feature request to be able to some-how turn on/off RR card from different programs....going from Premier to AME as an export---then choosing something like: "utilize rocket card"...so that it disengages from current program and then utiilized by new program of your choice---same in AE....when exporting to AE....anyway, maybe the terrible performance or no performance issues i experienced were all because i was working with mostly 4k 16:9 footage and transcoding to 16:9....I was getting around 20 to 1 transcode ratio--so 20 or so hours for a one hour doc....and kind of heavy with effects....and a mac 8core i7 32gb ram; quadro 4000 card, red rocket card.....did not seem right AT ALL

Yeah - they were some crazy render times Johnny. I remember trying to help you with that, though I seem to remember that Wes discovered that you were using 7 instances of Colorista on single clips. Did you manage to change that and did you see the render times change once that was adjusted?

[Johnny Friday]

Yeah - they were some crazy render times Johnny. I remember trying to help you with that, though I seem to remember that Wes discovered that you were using 7 instances of Colorista on single clips. Did you manage to change that and did you see the render times change once that was adjusted?

Brad,
right you are on my effects....heavy on them. BUT, i apply similar in FCP....and don't see crazy render times like this....But in answer to your question, i've not done any tests after that crazy 3weeks of post.....and afraid to do another on CS6....at least any effects/color work that is...I think i'm seeing the light in that i really need to cut one place and color in a pro color app. I really liked and wanted to keep After Effects and Premier inthe pipeline...but just too crazy with delayed effects adjustments and the render times...BUT, my gut tells me that my hardware is just not being used to it's potential....That said, i'll soon be on another project---"home grown" and try again. I'm liking Resolve from what i've seen and if memory serves correct you did some brilliant work in that program for another user...

Thanks Brad,