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

AME for transcodes

email adobe! global source settings change in AME, and debayer quality! :)

if you look closely in the AME source settings too there is a "use red rocket" option too, so a rocket CAN accelerate it further, but I think when you have a rocket it takes everything off the cpu. still right now nothing beats the rocket, but once we see some 16 cores, the gap might narrow down more and more, saving you a slot in the tower...
 
If debayer quality could be switched to half... the transcodes would be realtime. This is much better than using RCX without a RED Rocket card. Compared to a RED Rocket the time now is about 2:1. Not bad.. especially that it "seems" AME is doing a full quality debayer.
 
AME: A 30 second R3D clip (2048 x 1152) with 738 frames... takes precisely 60 seconds to transcode to Apple ProRes 4444. The source was on a GRAID 2TB drive connected via FW800 and the destination was an internal 7200 RPM drive. The debayer detail was set to "Medium".

The same clip in REDCine-X took two minutes and six seconds. Debayer values set to 1/2 Good.

12 core Mac Pro - 2.66 GHz.
24GB RAM
Quadro 4000
Adobe Creative Suite 5.5

The same 30 second clip (2048 x 1152) set to "Debayer Values: FULL" in REDCine-X takes two minutes and 39 seconds to transcode to Apple ProRes 4444. Debayer High in AME takes one minute and 12 seconds.

33 second RED clip (4096 x 2304) with 795 frames... takes precisely 59 seconds to transcode to Apple ProRes 4444. The source was on a GRAID 2TB drive connected via FW800 and the destination was an internal 7200 RPM drive. The debayer detail was set to "Medium".

The same clip in REDCine-X took three minutes and fifteen seconds . Debayer values set to 1/2 Good.

12 core Mac Pro - 2.66 GHz.
24GB RAM
Quadro 4000
Adobe Creative Suite 5.5

The same 33 second clip (4096 x 2304) set to "Debayer Values: FULL" in REDCine-X takes seven minutes and 30 seconds to transcode to Apple ProRes 4444. Debayer High in AME takes one minute and one second.
 
Andrae, you are right, right click doesn't work. Select the clips in the project window, go to file menu, then export, or use shortcut.
 
Andrae, you are right, right click doesn't work. Select the clips in the project window, go to file menu, then export, or use shortcut.

That doesn't work either.
 
once the 16 core possibly sandy bridge or ivy bridge comes out, it should be getting super close if not surpassing rocket debayer even at full. pretty neat when it can save a slot on your system. Not selling mine anytime soon though, it will still help with Da Vinci setups :)
 
once the 16 core possibly sandy bridge or ivy bridge comes out, it should be getting super close if not surpassing rocket debayer even at full. pretty neat when it can save a slot on your system. Not selling mine anytime soon though, it will still help with Da Vinci setups :)

I'm looking forward to this. Already got rid of my RED Rocket card. With the fast 2x full debayer transcoding currently in AME... I'm not missing out on much. Wish that I could drop the resolution to 1/2 so that it could be realtime though.
 
Andrea, I have a feeling your bottleneck is the FW800 external drive. My FW800 drive fails to reach 42 MB/s sustained - the bitrate for R3D files. That also explains why the time taken is always roughly 60 seconds irrespective of settings used. Copy the contents on to an internal drive or eSATA drive, and then render out to a different internal drive.

I am sure the upcoming 16-core AMD Opterons releasing in a few days will enable full debayer at 4K or even 5K, real-time. 1/2 res debayer is already easy with the mainstream Core i7 2600.
 
It's a RAID drive that clocks much higher than 60MB/sec... Plus I'm writing to a separate internal drive. Debayer Detail is not equivalent to Debayer Resolution. Switching it from High to Medium is not like going from Full Resolution to 1/2 Resolution.
 
It's a RAID drive that clocks much higher than 60MB/sec... Plus I'm writing to a separate internal drive. Debayer Detail is not equivalent to Debayer Resolution. Switching it from High to Medium is not like going from Full Resolution to 1/2 Resolution.

Aha, if it's a RAID0 Drive it is OK. You might want to check your CPU usage however. If it is dropping below 90% or so, then there is obviously a bottleneck. What does Debayer Detail do exactly?
 
Aha, if it's a RAID0 Drive it is OK. You might want to check your CPU usage however. If it is dropping below 90% or so, then there is obviously a bottleneck. What does Debayer Detail do exactly?

"Debayer Detail has three settings: Leading Lady (e.g., low detail); Medium, or High. These vary the aggressiveness of detail extraction, with Leading Lady being quite soft and naturalistic with High being crisper but on the verge of decoding edges too harshly." --- Got this explanation from Pro Video Coalition
 
"Debayer Detail has three settings: Leading Lady (e.g., low detail); Medium, or High. These vary the aggressiveness of detail extraction, with Leading Lady being quite soft and naturalistic with High being crisper but on the verge of decoding edges too harshly." --- Got this explanation from Pro Video Coalition

I have to say, that reveals nothing. "Low resolution" can be equated with "soft" and "high resolution" can be equated with "crisp" just as well. Also, "Leading Lady" was from CS4 era.
 
I have to say, that reveals nothing. "Low resolution" can be equated with "soft" and "high resolution" can be equated with "crisp" just as well. Also, "Leading Lady" was from CS4 era.

Well it could be equated more akin to blur/sharpness than resolution. I've seen Debayer resolution and Debayer detail on a menu before... So I'm sure they are separate functions. If the debayer resolution is at full then that's a 4k image... So adjusting the detail level would be like sharpening or blurring a 4k image. It's not really lowering the resolution of the image.

clip_image008.png


Debayer Detail is shown as a separate function in CS4 RED Plugin. I'm still trying to get a detailed understanding of it... Hence the questions I've posted on here, adobe forums and creative cow.
 
That makes sense. The playback window lets you choose resolution. As for the final render, I have always just stuck to the best possible quality and haven't looked at much else. Maybe someone from Adobe can comment? Maybe the debayer resolution is selected automatically based on the output resolution? (i.e. Full debayer for 4K, 1/2 debayer for 1080p, etc)
 
Judging by the amount of CPU power being utilized and the correlating render times compared to RCX... I think it's a full debayer. The CPU power being utilized is about 4X to 7X compared to RCX on Full debayer. The render times then correlated to a corresponding increase. AME is also utilizing the GPU for certain functions. On the below example, the CPU utilization difference was 4X but the render times was over 7X.

RCX:
6014635910_82cb4be68f_b.jpg


AME:
6014668038_9af3f13e02_z.jpg


33 second clip done in 47 seconds with AME... not bad for CPU debayering at full resolution. At these speeds I can live without a RED Rocket card.
 
Got an answer from Steve Hoeg at Adobe. The setting below is what controls Full resolution. If it's not checked then AME will automatically control resolution via the output resolution. So 4K to 1080p would be 1/2 Resolution.

6014772306_cfbf89b1c9_o.png


http://forums.adobe.com/message/3845231#3845231

Will do some new benchmark testing as my previous hypotheses was wrong.
 
Thanks a lot Andrae. Very good info. Most of us quit complaining about render times years ago.
 
Back
Top