REDCINE X vs MEDIA ENCODER CS6 settings

[Roy Rossovich]

So I am used to batching in Media Encoder where I can convert examples wise 300 gb of 5k material in about 2 hours into DNXHD 36.

If I pull the same material into REDCINE X and put the same settings DNXHD 36 and batch it it takes 16 hours.

I notice in my task matanger that media encoder uses aprox. 80% of my CPU and most of my RAM, REDCINE X uses 23% of my CPU and 10% of my RAM, whats up with this? Any way to allocate more power?

Also I am assuming at this point that REDCINE X is not using any cuda cores either or?

Any input much appreciated

 

[Andrew Gentle]

Hey Roy,

I think there's a preference for REDCINE-X which makes it perform more than one job at once. Assuming you have multiple files, this is a good way to increase CPU utilisation in RC-X.

-Andrew

 

[Roy Rossovich]

Hey Andrew,

Yeah I've seen that. They still work slow though on a machine that crunches 5k raw in premiere and media encoder like their is no tomorrow..

just seems strange... I know RCX works fast with a rocket so it basically comes down to buy a rocket to use the software or use media encoder with any set up...

 

[MichaelP]

Are you using Redline within RCX?

Michael

 

[Roy Rossovich]

no, don't know about redline, something i should read up on it seems?

 

[MichaelP]

It's a setting in RCX for the "export" that you set up.

Michael

 

[Angelo Lorenzo]

Load a R3D file into Media Encoder, right click the file in queue and select source settings. Make sure the debayer quality level is the same in both AME and RCPX.

I turned my Red Rocket off (disabled completely in device manager) and got the following results on my quadcore i7 2600K based Windows system:

RED Epic 4K 59.94 to 59.94 220x DNxHD in MOV container

Redcine-X Pro
~33 mins ETA
~35% CPU utilization

Adobe Media Encoder CS6
~5 mins
~80% CPU utilization (seems to launch as many subprocesses as your CPU can handle)

With the Red Rocket I got:

Redcine-X Pro
~2m 25s
~35% CPU utilization

Adobe Media Encoder CS6
~2m 50s
~35% CPU utilization

If you don't have a RED Rocket then it seems like AME multithreads some part of the process Redcine-X does not. Redcine-X outperforms AME with the use of a Red Rocket though. Also, neither program uses CUDA or openCL for decoding the RED footage, as the computations needed aren't part of GPU instruction sets.

*Edit* Make sure AME is keeping metadata like reel name. I know it'll behave well with timecode byt I personally haven't tested the other.

 

[Roy Rossovich]

Thanks Angelo,

Very interesting test.

nice results, seems AME is pretty tight.

 

[Nick Pasquariello]

is AME using the RMD when you do this? All levels and ISO and colorspace and whatnot?

 

[Roy Rossovich]

Yes, settings that are made to the RMD are pushed through to the transcoded file.

is AME using the RMD when you do this? All levels and ISO and colorspace and whatnot?