Welcome to our community

Be a part of something great, join today!

Log in
  • 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 :)

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

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.
 
Last edited:
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.
 
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.
 
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.
 
Nice work on continuing to chase this down Petri rather than just throwing your hands in the air :)

Petri Teittinen said:
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.
Click to expand...

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)
 
Brad Allen said:
Nice work on continuing to chase this down Petri rather than just throwing your hands in the air :)
Click to expand...
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.
Click to expand...
Whoops! For some reason I automatically assumed he meant a more tortuous solution... Guess I'm one of those "glass half empty" guys :)
 
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
 
Olivier Madar said:
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
Click to expand...
useful for fan control on MacPro
http://www.macupdate.com/app/mac/23049/smcfancontrol
 
Johnny Friday said:
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
Click to expand...

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 Allen said:
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?
Click to expand...

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,
 
Hmm wouldn't have been me, I'm only just learning Resolve now - courtesy of the FXPHD course for V9. Loving it so far - super easy to pick up and the new interface is awesome :).

Resolve seems to be pretty solid from what I can tell, and it definitely might be worth investigating it as a grading pathway for your future projects. And it will still allow you to keep a raw workflow through the majority of your pipeline, assuming that you want to of course :P
 
Hey guys, I'm not running a really beefy system: iMac i7 16gb mem and rendering out a 9 minute clip 5K>1080P with MBL and some AE linked projects. Media Encoder taking about 40hours. Normal?

Just seems like ME struggles with the simplest of shots. Example on a 5K clip with just MBL applied and no other effects about 1 frame every 15 seconds. Doesn't sound right to me..
 
Hey Al,

What are the chances that the 5k shots you are referring to with MBL's are After Effects precomps?

If that were to be the case - that might explain it - as when After Effects is Dynamically linked it isn't optimized for multi-threading. Though I should clarify. Premiere/AME itself will still be optimized for multithreading - but my understanding is that the background processes it launches to render out that AE Comp aren't multi threaded. At least, that was the way it worked in CS5.5. Though happy to be corrected if this has changed in CS6.

Also, you didn't mention any of your export settings apart from 1080p. What format are you going to and is Max Render Quality Enabled?

Also do you have a supported GPU? The CUDA acceleration really helping out when scaling footage down - ie 5K > 1080p. If it's an iMac, I'm guessing not unless you have one hooked up externally?
 
Gentlemen,

Not to defend Adobe, but you need to keep a little perspective here. Native support means just that, you don't need to transcode into Prores or anything else, but when getting out of Premiere, you will have to deal with all the processes you've been delaying until now. Such as debayering, a hog on resources. Specially if you are trying to avoid spending $5K on a RR card. Now, you find me any other program that, without a Rocket and without any other custom hardware, can do all that heavy lifting quicker than Premiere. Things that I can tell you:

- when working from R3Ds and applying float point effects to all those clips, specially if you have several tracks and several effects applied to those tracks, and keeping everything at maximum quality, you will get final render times of anywhere from 18 to 45 minutes per minute of footage. You are debayering at the same time you are doing all other processes. The beauty of it, you only go through this burden once, at the end, even if then, it is really cumbersome. To my knowledge, no other application (again, without hardware) moves any faster. Certainly not a Mac, no pun intended.
- Once you've reached the export phase, then you are leaving native territory anyway since NOTHING can export REDCODE, how is this interfering with Premiere's native capabilities? Adobe has put a lot of work into the Media Encoder, why not use it? Just two clicks, ctrl + m, and it launches, how is that cumbersome? ME allows you to customize all your export settings and runs in the background, use it. Direct export from Premiere is more for things like stills or audio sequences.
- If you want to work on proxies, be it ProRes or whatever, I'd dare say Premiere will still move faster than FCP or anything else.
- If you have 2 GPUs, this does not help Adobe in any way, in fact, it can create cross talk and even interfere with the Mercury engine at times, I advice disabling one of them.
- For faster render times with the ME, close Premiere and any other Adobe apps, in fact, close everything except ME. This WILL speed things up.

Just food for thought,
 
Hi Al,

Without looking at your exact project, My guess is that the slower export times are really compounded by the decode complexity of the R3D files.
If you have a 5k file in AE with FX, then it is using all of your CPUS for the decode, then still needs all your CPUs for effects, etc.
If this is then linked to PR and if you have added other effects (or even slower a 3rd party effect like MBL) then it's going to be slow because of the repeated rendering of very high resolution clips.

Again, I don't know exactly what you're doing in your project, but I'd suggest trying to simplify it where you can. You're pushing things pretty hard.

4k to 1080p shouldn't be much slower than 4k to 4k if you have CUDA card. That's because the CUDA card does the bulk of the heavy lifting for the scaling.

In fact, on systems with a Rocket (where the Rocket covers the decoding - the most render intensive part) and a CUDA card, you can export 4k, 5k to 1080 in faster than realtime while using less than 10% of your CPU.

Yes, 3rd party effects will slow this down. Yes, AE will slow this down.... Some of it is thinking through the render pipeline and devising a good workflow.

LMK if you have more questions.

Wes Howell
Adobe Systems
 
Johnny Friday said:
I can't recall if this was asked, or even if i asked it...BUT here goes:
So you have a red rocket card, NOW you are sending to AME from PP....how do you then get AME to take control of the RR card and disengage from PremierPro?
Click to expand...

Current workflow is to close PR.

If you need more, don't complain unless you've filed a Feature request. :)
 
Wes Howell said:
Current workflow is to close PR.

If you need more, don't complain unless you've filed a Feature request. :)
Click to expand...

Actually i've filed a lot of feature requests....i should have kept track of them. but my primary request was a simple way or solution to turning on/off RR card on each piece of software when jumping from one to the other....And if a notification of sorts could be seen...i don't know a BIG GREEN dot showing an Active RR card or YELLOW/RED that it is not active....Since there is a lot of back and forth: PrPro to AE to AME. So at times i'd lost my place on knowing if the card was active even when i shut down one of the pieces of software...or trusting it was active but not really knowing.

....on that issue of feature requests: in the RAW side of Premier/AE--why can't we get WB to go above 9400 ? In underwater world we are often setting WB to 10500 to 13500. So when i drop a clip that has been adjusted with RMA to 13000 it shows up as only 9400 in Premier.---also requested, but likely i'm a lone voice in this ocean.


***And goes w/out saying Wes---thanks for being on this forum and your support. !
 
Johnny Friday said:
Actually i've filed a lot of feature requests....i should have kept track of them. but my primary request was a simple way or solution to turning on/off RR card on each piece of software when jumping from one to the other....And if a notification of sorts could be seen...i don't know a BIG GREEN dot showing an Active RR card or YELLOW/RED that it is not active....Since there is a lot of back and forth: PrPro to AE to AME. So at times i'd lost my place on knowing if the card was active even when i shut down one of the pieces of software...or trusting it was active but not really knowing.

....on that issue of feature requests: in the RAW side of Premier/AE--why can't we get WB to go above 9400 ? In underwater world we are often setting WB to 10500 to 13500. So when i drop a clip that has been adjusted with RMA to 13000 it shows up as only 9400 in Premier.---also requested, but likely i'm a lone voice in this ocean.


***And goes w/out saying Wes---thanks for being on this forum and your support. !
Click to expand...

Hey Johnny,

I saw your feature request about the white balance stuff! Thanks :) And thanks for all the feature requests. They make a difference. I can understand why you need the higher settings.

I think the functionality you're asking for related to the Rocket is a fabulous request as well. If you find time, please file a request for that too.

Talk to you soon - I'll be around.

Best,
Wes
 
You must log in or register to reply here.
Back
Top