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

The "RED" company of NLE

Solomon Nero said:
. I read this article and watched the video in it, and it reminds me of the innovative mindset and attitude that RED has.

http://nofilmschool.com/2011/06/adobe-reveals-video-plan-years-apple-set/
Click to expand...
Mmmmm I'm seriously considering that Premier will be a good option for us.
But whilst the video provides some good info and in love their road it's lacking something massive...... Creativity and inspiration! Very long talking head on a graphic back drop.......kills any enhusiasm.... Definitely not Red like
;)
 
WesG said:
Mmmmm I'm seriously considering that Premier will be a good option for us.
But whilst the video provides some good info and in love their road it's lacking something massive...... Creativity and inspiration! Very long talking head on a graphic back drop.......kills any enhusiasm.... Definitely not Red like
;)
Click to expand...

Lol, I see your point for sure! I think thats why there really isn't another company in this industry like RED. Just hope Adobe is smart and looks at some of the things apple did with file management in fcpx, and maybe adapt something like that...and maaaybbe the magnetic timeline :P
 
Brad Allen said:
Hi Johnny,

Not sure regarding the matrox card but if this were me I wouldn't even bother transcoding to ProRes if you were going straight into Premiere for Editing. I would:

1. Pull R3D's through RedCine-X and do a one light and save that info to the RMD metadata.
2. Close RedCine-X and open Premiere and import all the R3D's. Premiere will read the metadata from the RMD's and apply your one light looks to all of the footage automatically. If you have your RedRocket configured correctly (and RedCine-X is closed), Premiere will then use your RedRocket for debayering your image and will then pass it over to the GPU and CPU for anything else you do to it, levels, curves etc :)

Means you shouldn't have to transcode a single thing until your final export from Premiere.

If your taking it to a grading suite after the edit, I wouldn't even bother doing any effects adjustments in Premiere. Just export your EDL and take your R3D's with you to the grade and you will be grading with your original raw files from the shoot (with your one light adjustments of course :) )
Click to expand...

Thanks for that Brad,
That is what i'm looking for...finally, will i get accelerated transcodes as well when i transcode to prores? Will Premier also utilize the red rocket for transcode speed?
 
Johnny Friday said:
Thanks for that Brad,
That is what i'm looking for...finally, will i get accelerated transcodes as well when i transcode to prores? Will Premier also utilize the red rocket for transcode speed?
Click to expand...

If you encode in process within premiere it will use the rocket. If you encode through AME you just need to make sure rocket usage in AME is turned off and ppro is turned on.

CHeers

Dave
 
David McGavran said:
If you encode in process within premiere it will use the rocket. If you encode through AME you just need to make sure rocket usage in AME is turned off and ppro is turned on.

CHeers

Dave
Click to expand...

Thanks Dave,
so i guess quick answer is yes....meaning. i transcode out of premier. And you'll have to forgive me, but what is AME ?
 
David McGavran said:
If you encode in process within premiere it will use the rocket. If you encode through AME you just need to make sure rocket usage in AME is turned off and ppro is turned on.

CHeers

Dave
Click to expand...
Hey Dave,
I haven't played around with this myself but this seems a little backward? To accelerate encoding in AME with a Red Rocket when coming from Premiere, you need to disable Red Rocket Acceleration in AME?
 
Brad Allen said:
Hey Dave,
I haven't played around with this myself but this seems a little backward? To accelerate encoding in AME with a Red Rocket when coming from Premiere, you need to disable Red Rocket Acceleration in AME?
Click to expand...

Agreed it is a bit anti intuitive... Here is the thing. If you drop an R3D in AME and encode it you want the rocket on. AME is doing the decode in this case so it needs the rocket. However, if you drop a ppro sequence into AME something different happens. A background version of PPro will launch to do the rendering. As of now we can only have 1 app using the rocket. That app in this case is the background ppro. That means the UI version of ppro nor cine x should have the rocket if you want to work this way. The simplest way around this for now is to do the AME encode in ppro but clicking encode instead of queue.

Complicated I know ;)

Cheers

Dave
 
David McGavran said:
Agreed it is a bit anti intuitive... Here is the thing. If you drop an R3D in AME and encode it you want the rocket on. AME is doing the decode in this case so it needs the rocket. However, if you drop a ppro sequence into AME something different happens. A background version of PPro will launch to do the rendering. As of now we can only have 1 app using the rocket. That app in this case is the background ppro. That means the UI version of ppro nor cine x should have the rocket if you want to work this way. The simplest way around this for now is to do the AME encode in ppro but clicking encode instead of queue.

Complicated I know ;)

Cheers

Dave
Click to expand...

Figured that something like this must have been going on. However - it seems that it shouldn't be too hard for future releases to instruct applications to give up the right to the RedRocket when sending an r3d to another program (ie, a background instance of PPro?). Maybe there would be a way to give users an option for this (ie," use Red Rocket for media encoding" when exporting etc)

I dunno, just another idea among the many I'm sure you guys have :D
 
David,

As always the Adobe apps are the best, hands down... The fact that you guys are here on the forum speaks volumes...

I still do not understand your answer, however I was able to get AME to use the Rocket. My film was going to take 24 hours to render in AME so I stopped it and exited all apps that use the Rocket (Pr and AME), re-started AME, duplicated the job and removed the original. The current render is showing me 6 hours but it should be less as the film is front heavy with Ae comps.

Just walk me through what's going on. I understand that only one app can use the Rocket, but at what point do the various Adobe apps actually latch onto the Rocket? Does the switch in Pr cause a 'Use RedRocket' flag to be inserted into the XML that goes to AME? If so would closing the app that currently is using the Rocket during the 2 minute pause period allow AME to latch onto it, or does AME just try to latch onto it when it starts?

Thanks,

Bob
 
Again my apologies as I helped decide on this craziness. Basically we wanted to get Rocket support out in 5.0.3 and this was our only way to do it in that time period. We haven't had a chance to go back and fix it.

PPro, AME an AE all have a pref to enable Rocket. Import a red file and go to source settings. If you enable it for each app then the app that is launched first grabs the rocket and doesn't let go. Same with Cine X.

That is step one.

The more interesting bit is our background renderers. So when you put a ppro sequence in AME a background version of ppro launches (in activity monitor it is called PProHeadless) That is the app that debaters the RED and where you want the rocket to kick in. AME only does the compression in this case. So for things to work the way you want.

1. Go into ppro and turn rocket on
2. Go into ame and turn rocket off
3. Finish your edit in ppro and quit
4. Go to âme and add you sequence (file->Adobe Premiere Pro)
5. Export, rocket will be used because PPro headless will launch and get the rocket

Cheers

Dave
 
Thanks for this explanation, Dave, and have a great holiday! Don't dare to show up here while you relax ;-)

This attitude of openness regarding the inner works of your package is very helpful for us pro's. Apple never gave us any info of that level!
 
Hey Dave,
Thanks for the info. I get the concept of how only one app at a time can use the RR.
However, I am confused as to how to "turn off" or "turn on" The red rocket for PPro or AME? Is it a preference or settings option?
Is there a way to tell if the app is using the Red Rocket or not?
Also I still can't figure out how to use the RR to be used for the Ppro monitor window so I can view it at higher resolution.
Thanks!
 
Josiah Spencer said:
Hey Dave,
Thanks for the info. I get the concept of how only one app at a time can use the RR.
However, I am confused as to how to "turn off" or "turn on" The red rocket for PPro or AME? Is it a preference or settings option?
Is there a way to tell if the app is using the Red Rocket or not?
Also I still can't figure out how to use the RR to be used for the Ppro monitor window so I can view it at higher resolution.
Thanks!
Click to expand...

We don't have the best ui to tell you that you wanted the rocket but you can't have it... You turn it on and off in the source settings for any red clip. Right click on a clip in ame/ppro and you get the settings. There you can turn rocket on/off globally.

Cheers

Dave
 
You must log in or register to reply here.
Back
Top