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 :)

Tutorials for Newcomers to Premiere Pro

No Prob regarding the thread Troy :)

Unfortunately though I have no experience with using external monitoring solutions in AE. I'm assuming you have already tried adjusting your settings under: Edit > Preferences > Video Preview ?

Thanks for the response brad, we figured it out, there was a control panel for matrox that needed some tinkering, all good now.

Btw are you running external monitoring from premiere yourself, or do you just view on your computer screens.
 
I'm just using my 24" screens here for monitoring. Would love to say I have a better monitoring setup, but financial constraints and other priorities make it an impossibility for the moment!
 
Hi Guys, sorry to dig this thread up from the dead.

Just updated the first post with an overview tutorial on exporting with CS6 and going through all the various options there. Hopefully these tuts are still of use to some of you guys :)

I also attached a resolution cheat sheet with the post that gives a read out of various resolutions for aspect ratio's and frame sizes that I thought some of you may find handy. If you spot and problems with it, be sure to let me know and I'll get it updated :)
 
Yeah thanks for all these Brad, great stuff.

I am currently trying to get Pr CS6 and AME CS6 to render using my Red Rocket but am having no luck.
It is working to playback footage in Pr but when I go to export a 5 minute timeline of 5k material it says its going to take over an hour in Pr and AME.
I have tried sending to AME and then quitting everything and reopening AME by itself. No Go. I also tried bringing an r3d into AME directly and changed source settings to RR enabled and it still doesn't' seem to be using it...

If you have any tips that would be amazing!
 
Any chance you could post a screen grab for me of your timeline and then another of your export settings within Premiere, Tehben?

If it's sensitive content (ie, can't be seen on a public website), feel free to shoot me a PM :)
 
Any chance you could post a screen grab for me of your timeline and then another of your export settings within Premiere, Tehben?

If it's sensitive content (ie, can't be seen on a public website), feel free to shoot me a PM :)

I will do that later tonight or tomorrow :)
 
Here you go.
screenshot20121214at115.png


screenshot20121214at115.png
 
Thanks Tebhen,

What are the specs of your system, and what effects are you running on the clips in your timeline?

macosx 10.8.2, Pr 6.0.2, 15" rMBP 2.7GHz 16GB ram. Magma box with RR, OWC Thunderbolt box with Atto R680.

I don't think there are any affects. Maybe a couple punched in shots. It's possible there was some alchemy settings applied to the clips in RCX but I don't think those carry through to Pr do they? and they rendered out of RCX fine with the RR.
 
Hmm ok,

I'm just wondering why your timeline is showing red - thought it may have been effects that you had applied on to clips (My timeline with default RED material is yellow). Are your Video Rendering setting (Project>Project Settings>General) setup for GPU acceleration or software?

Basically I'm trying to work out if it's possible that your RRocket is doing it's job but the downscaling from 5k > 1080p is where you are seeing the performance hit (as that downscaling operation is done by the CPU or GPU depending on your preferences)
 
If I select software acceleration my timeline turns yellow but still takes over 10 minutes to export a 1 minute sequence.
I just created a new project. 5kFF and dropped 5kFF clips straight on and still no go.

Do you have any sharpening applied in either the RMD or source settings (OLPF Compensation)??????
 
If I select software acceleration my timeline turns yellow but still takes over 10 minutes to export a 1 minute sequence.
I just created a new project. 5kFF and dropped 5kFF clips straight on and still no go.

Yeah - definitely hardware acceleration is the way to go. The thought in the back of my mind was that it might have been on software when it should have been hardware.

What are the chances that I would be able to grab a small clip of one of your R3D's to have a look at? Would love to see how it goes on my end. (I'm not running a RRocket here, but it would be still useful to have a look at how the file performs on the timeline)
 
Do you have any sharpening applied in either the RMD or source settings (OLPF Compensation)??????

Same thing whether I have Alchemy or not... My computers fans speed way up and it takes way over 1 to 2 minutes to export a 1 minute clip.

Question. Does maximum render quality force the render onto the processor or still use the RR? Because when I turn that off it speeds WAY up...
 
Max Render Quality will force Premiere to go into the R3D and downscale and debayer the complete 5k image to 1080p. Having it unchecked means you will just be doing a 1080p debayer and thus avoiding downscaling - From what I can tell in my testing anyhow.

Thus, huge performance gains can be had when not using Max Render quality since it's not debayering your entire image. (at the expense of actual measured resolution in the file)
 
Last edited:
Random thought: Being that the Macbook Pro Retina's use the Intel HD4000 when doing standard operations GPU operations, I wonder if it's possible that Premiere is seeing the HD4000 and ignoring the 650M in the system, thus disabling CUDA acceleration from working.

Having the GPU not in use for the downscaling operation when having Max Render Quality selected will cause this to fall back on the CPU which could cause the performance penalty we are seeing.

I wonder if there is a way for you to disable the HD4000 altogether so that OSX can only hand over the 650M for Premiere to use? I'm a Windows guy, so am probably not much help there...
 
Another thought - In order to test whether the performance penalty is caused by the downscaling operation or the debayering, it might be worth exporting out at full 5k resolution. That way no downscaling operation will be needed and the bottleneck should be how fast the RRocket can debayer those 5k frames.

It seems the latest version of ProRes can export at 5K (http://images.apple.com/finalcutpro/docs/Apple_ProRes_White_Paper_October_2012.pdf)
It would be worth seeing if Premiere allows you to export at full 5k res to ProRes. Make sure you export it to a fast drive through a fast interface to ensure that your not making a bottleneck somewhere else :P. Perhaps the internal SSD just for testing purposes?
 
It seems like if the RR is actually working it HAS to debayer at full resolution so regardless of the Max Render setting it should be using the entire image. However I don't know if Pr would switch off the RR when that setting is checked.

Just tested export to 5k without Max Render Quality and it's taking about 5 minutes to do a 1 minute clip and using about %60 of the CPU. That's with CPU acceleration.
Setting the CUDA it doesn't seem any different.
Also checking Max Render Q at 5k doesn't seem to effect it noticeably.


OK, that's weird. After trying that I put it back to 1080 and with the Max Render Q selected its taking about 3 minutes... Did I just trick it into using the RR???
 
It seems like if the RR is actually working it HAS to debayer at full resolution so regardless of the Max Render setting it should be using the entire image. However I don't know if Pr would switch off the RR when that setting is checked.
Hmm, not sure on this. I was under the impression that the RRocket would assist debayering at any resolution. It's just that below 4k it will accelerate it faster than real time (whereas 4k is about realtime and 5k is almost realtime from memory)

EDIT: I was wrong on this point. Seems Red Rocket will always do a full debayer of your source footage.
Just tested export to 5k without Max Render Quality and it's taking about 5 minutes to do a 1 minute clip and using about ` of the CPU. That's with CPU acceleration.
Setting the CUDA it doesn't seem any different.
Also checking Max Render Q at 5k doesn't seem to effect it noticeably.
This all makes sense. If you are rendering output files at 5K then since no downscaling operation is happening, leaving max render quality checked or unchecked shouldn't make much difference to the export time (and also since you don't have any effects or downscaling offloaded to the GPU, CUDA won't make a difference to performance)

OK, that's weird. After trying that I put it back to 1080 and with the Max Render Q selected its taking about 3 minutes... Did I just trick it into using the RR???
Perhaps you did? Those are the sorts of render times you would be hoping to see :)
 
Last edited:
Back
Top