Realtime debayer

[Jeyendrakumar.G]

Hi,
I am a new to red-workflow, I am trying to achieve real-time debayer of .r3d file into dpx using Red rocket. a 18 second clip takes close to 60 seconds, I am using Mac pro 2.3 ghz (8 core) I have two separate storage, one has the source and the other for destination.
kindly help me by letting me know where I would have missed out. I also want to know if I could see the usage of red rocket hardware Hyper-accelerated.

Thanks
Jeyendran

 

[Deanan]

What resolution are you going to and how fast is your destination storage.

Outputting 2k dpx to a drive that can do 300MB/s, you should be able to get
around 30-32fps.

 

[jimhare]

Keep in mind that the Red Rocket is only doing the debayer and passing the data on.

If you are are transcoding to a CODEC that would take 60 seconds to process 18 seconds of footage anyway, the Rocket isn't going to speed things up.

As it's only dealing with the initial Red footage, your CPU is taking it from there.

Maybe do a couple of tests with an uncompressed file as a source.

 

[Dan Hudgins]

OS/DISK

OS/DISK

I was trying to optimize my systems workflow, and found that the image processing time was only a part of the total time, most of the time was OS and DISK related, try just copying DPX files from the source to result drives and see how many fps you can get that way.

 

[Jeyendrakumar.G]

Thanks for the reply, The source footage is 2k 2048 X 1152 and the output is the same as the source, The storage I am using is a FC storage box, The connectivity between the storage box and the MAC machine is 2 Gbps FC. when I see the activity monitor I see the I/O for the storage is not more than 140 MB/sec.

 

[Deanan]

Thanks for the reply, The source footage is 2k 2048 X 1152 and the output is the same as the source, The storage I am using is a FC storage box, The connectivity between the storage box and the MAC machine is 2 Gbps FC. when I see the activity monitor I see the I/O for the storage is not more than 140 MB/sec.

How many frames are in the 18 sec clip?

At 140MB/s you're going to get about 15 fps assuming the dpx files are coming out at 8.85 MB/fr.

To get realtime speeds (24fps assumed), you'd need to get greater than 212MB/s off your storage.

 

[Lucas Wilson]

Just fyi... the Rocket card is certainly capable of realtime DPX rendering. When set up correctly, Rocket Fuel is easily able to render realtime 2K DPX to disk from 4K R3D. This is not theoretical - I've seen it many times.

A couple of tips for maximum performance:

1) Make sure that system drive, read volume, and write volumes are separate. If the R3D files are on the write volume, you are going to kill write performance.

2) With read and write volumes, for the best performance - they should be separate physical disks. If you are using one dual-channel Fibre card, make sure that the separate channels are not mixing volumes, i.e.: Make sure that Channel1 is physically addressing only the read volume disks, and Channel2 is physically addressing only the write volume disks. Also make sure that the controllers are cleanly addressing the separate volumes as well in the hardware RAID.

3) Make sure you have a true 8x card, not just an electrical 8x. You need at least 8x speeds on one card to properly manage a read/write path for 2K. Although with the low bandwidth of R3D on the read, maybe not... but might as well be safe with it...

Lucas