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

Should Adobe Media Encoder be using Red Rocket?

P

Paul J Steinberg

Well-known member
Joined
Apr 6, 2011
Messages
575
Reaction score
0
Points
16
Location
Toronto, |+|Canada
Website
www.paulsteinberg.tv
I'm just snooping around through the Adobe suite and found the AME. Wow!! I could really make use of this, but when I did a test of running a 30 sec 4K R3D clip through it the render time was about 17min. Obviously the Red Rocket card on the system isn't being used.

Is there any way to enable it or is the AME just not able to use it?
 
Paul J Steinberg said:
I'm just snooping around through the Adobe suite and found the AME. Wow!! I could really make use of this, but when I did a test of running a 30 sec 4K R3D clip through it the render time was about 17min. Obviously the Red Rocket card on the system isn't being used.

Is there any way to enable it or is the AME just not able to use it?
Click to expand...

Yes you can use it in AME but it is somewhat subtle. If you are just using R3D files in it, go to AME right click on the R3D and select source settings. You can turn on the rocket in there. If you are using ppro sequences with R3D files then turn OFF rocket in AME and on in PPro.

Cheers

Dave
 
David McGavran said:
Yes you can use it in AME but it is somewhat subtle. If you are just using R3D files in it, go to AME right click on the R3D and select source settings. You can turn on the rocket in there. If you are using ppro sequences with R3D files then turn OFF rocket in AME and on in PPro.

Cheers

Dave
Click to expand...

Dave: I'm having difficulty knowing IF AME is actually using my RR card....I've done two tests and all seem to reveal ABOUT same render times.
First: using CS 6.0
Export a MIXED codec sequence from PrPro to AME.....then Close PrPro....and then in AME....begin encoding....That sounds like the intuitive way to do this as you had suggested in previous posts that we need to close down RCX in order to allow PrPro to utilize RR card...so i assumed it is same with AME.....
BUT....i hear different in your post above. So, i need to leave PrPro open and go to source settings in one of the R3d's in my Bins...(not timeline) and select "use RR Card" ? Then begin my encode? All the while NOT shutting down PrPro?? This sounds so oposite of what was recommended with say RCX and PrPro when utilizing RR card.
....with CS 6.0 is this different? Please can you elaborate on this.....I would love to see an easy way to select/deselect rr card on all adobe software that uses it...and if another app is using it, you then get a pop up window that tells you which app is using it and what to do to get control of the app you wish to use it for....this gets a bit tricky the different ways to use the rr card in different adobe software AND there seems to be no way of knowing if AME has control of it...
Thanks,......
 
Johnny Friday said:
Dave: I'm having difficulty knowing IF AME is actually using my RR card....I've done two tests and all seem to reveal ABOUT same render times.
BUT....i hear different in your post above. So, i need to leave PrPro open and go to source settings in one of the R3d's in my Bins...(not timeline) and select "use RR Card" ? Then begin my encode? All the while NOT shutting down PrPro?? This sounds so oposite of what was recommended with say RCX and PrPro when utilizing RR card.
Click to expand...

Hey Johnny,

Here is my take on it (which David can confirm is wrong or not).

If you are wanting to use a RedRocket in Premiere Pro, you need to go into the source settings of one of your R3D's and enable RedRocket acceleration. This setting is then saved in the project. Upon exporting you have two options:

1. Export within Premiere Pro. Going this route has no major issues because Premiere is still retaining control of that RedRocket.
2. Send it to Adobe Media Encoder. If you go this way, AME will attempt to utilize a RedRocket in your system (since that setting has been saved in your project). However, the way AME renders Premiere's Sequences, is by launching a background instance of Premiere Pro. If you still have your original version of Premiere open and running (which has control of that RedRocket), then the background instance of Premiere that AME has launched won't be able to take control of and utilize the Rocket. Because of this, my guess would be that you would need to close your original version of Premiere (which should release the Rocket) and then start AME's rendering process. That way, when AME launches the background instance of Premiere, it will be able to find a free Red Rocket.

It really would be great if there was an easier way to assign who takes control of the Rocket or even if we had a way to know who is currently in possession of it.

EDIT: Didn't see your other thread where David seems to confirm that the above is the way it currently works.
 
Last edited:
Brad:
I've actually NOT heard from David on this issue....i only found some old info where he talked about this issue with i believe CS 5.5....that said, I seem to undertand it differently than what you just stated....This is a good reason for getting a CLEAR answer....I understand it (as David posted some time ago) that you need to leave Pr.Pro ON while sending to AME and launching to the Queue. NOW, that said, i've tried both ways and i pointed out some ERRORS i get or rather just NO RESPONSE when sending from PrPro --or encoding from PrPro....where the progress bar shows No Change, NO % and no preview of the frames being rendered---AS does AME....BUT the strange thing is that i can go to the folder that i setup for the Tiff sequence to be sent and see that Tiffs are being added--which is the one that has control of RR card is a GUESS....since PrPro shows me nothing--no estimated time or anything. So, i'm back in AME with a 24hr render for a 52min doc....that sucks! and i expect does not have control of rr card even when i tried with PrPro closed before beginning AND tried while PrPro is open....

That said, from what i read of David's post it seemed i was to leave PrPro open AND select an R3d and source settings and check UseRR card if Available.
So....I have no idea. Don't find anything to say one way or the other....posted on Adobe forums as well and no answer..so guess it's all a big mystery for now...and yes, there needs to be a way to SEE or ASSIGN rocket control...otherwise what a waste.

Thanks for the response Brad
 
Fair enough - we'll just need to wait to hear from Dave I guess.

Can you just confirm for me a couple of things?

1. You have Red Rocket enabled in your project and see no difference in rendering times between exporting through AME when Premiere is both still open and when it is closed?
2. Could you fill me in on how long you left your Premiere Export running for when generating the TIFF sequences straight out of Premiere? We might be able to create an estimate of how long it would have taken based on the 671 frames it created in that time. This should give us a rough way of comparing export times with your RedRocket vs without.
 
Brad Allen said:
Fair enough - we'll just need to wait to hear from Dave I guess.

Can you just confirm for me a couple of things?

1. You have Red Rocket enabled in your project and see no difference in rendering times between exporting through AME when Premiere is both still open and when it is closed?
2. Could you fill me in on how long you left your Premiere Export running for when generating the TIFF sequences straight out of Premiere? We might be able to create an estimate of how long it would have taken based on the 671 frames it created in that time. This should give us a rough way of comparing export times with your RedRocket vs without.
Click to expand...

Yes, i'd like to hear back from the experts here....i fear however this could be something new. I do know there's a lot of new toys here---NVIDIA card; firmware/cuda updates and 3rd party plugins.....that it's a fragile system...but would hope that these basics could be fixed....i also realize a small % of us are using RR cards in the grand scheme for Adobe....so that may not have been something tested with the utmost of precision.

So:
1. YES....enabled in PrPro project under source settings and tried while PrPro was open and when PrPro was closed...no difference in render time was noticed when sent to the Queue.

2. I was thinking the same thing....but was in a hurry and moved on...BUT, i'll try that when this finishes in July....um, i mean midnight tonight....hard to do this i think since i believe we get an estimation of remaining time based on each clips performance...the best way i think to do that is look at a side by side comparison and time the encode on ONE clip when doing rendering from AME and another from PrPro....and just watch the frame count in the export folder to see when it gets to the target end Tiff number. Sure is a lot of leg work....not sure i'm up to it, but would like to know what's going on. and What is the best method....my sense from watching the PrPro render is that there was no noticeable difference.
 
Maybe it's worth just exporting out a sample of 10 secs from the timeline via the different methods and timing how long it takes? I hear you on the pain of doing this legwork though...

I'm off now for a shoot but will be back on to keep chatting later ;)
 
You must log in or register to reply here.
Back
Top