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

NAB13- RED ROCKET-X

Jeff, how big is the improvement in After Effects? AE seems to be so slow in reading files so even without filters I find it's tough to playback in 24fps even with normal 1080p material. With Red material its a lot less fun...

AE is not intended for continuous full-speed playback. The idea is you do a RAM preview to view your footage full-speed.
 
Does the Rocket X speed up Rendering in CS6?

No answer from me, of course, since I don't work for Red.

I have heard, however, that CS7 is going to support all GPUs, from both Nvidia and ATI, and will support multiple cards.

I am super curious about where transcoding R3D's will be with, say 2 GTX 680's vs. 2 GTX 460s vs. a Rocket x.

Of course, in the Adobe Creative Suite world, we just work natively with the R3D's. It would be awesome if we had someone who could do some tests, ;-)
 
I am super curious about where transcoding R3D's will be with, say 2 GTX 680's vs. 2 GTX 460s vs. a Rocket x.
GPU's will not speed up decoding and encoding of R3D-files, which means such a comparison doesn't make much sense. But, what will make sense is putting GPUs and a ROCKET-X together at work. The ROCKET eliminates the bottleneck of decoding R3D-files on CPU, freeing up the CPU for other tasks, the GPU will speed up FX-processing etc and finally the ROCKET will encode back to REDRAW.

And now add in a (fully hypothetical) .RED-encoding-card to that mix... ;)
 
GPU's will not speed up decoding and encoding of R3D-files, which means such a comparison doesn't make much sense. But, what will make sense is putting GPUs and a ROCKET-X together at work. The ROCKET eliminates the bottleneck of decoding R3D-files on CPU, freeing up the CPU for other tasks, the GPU will speed up FX-processing etc and finally the ROCKET will encode back to REDRAW.

And now add in a (fully hypothetical) .RED-encoding-card to that mix... ;)

Yes, but also, lest we forget, the GPU accelerates image scaling - which occurs on every frame of any timeline say set at 1080p, 2K or 4K, but containing 5K or 6K material. SOme of the reDRAW color settings also occur after debayer, and so they too live in GPU land.
 
Can I use one old and one new Rocket in the same MacPro (in a Cubix) to make it run even faster?

/Carl
 
Yes, but also, lest we forget, the GPU accelerates image scaling - which occurs on every frame of any timeline say set at 1080p, 2K or 4K, but containing 5K or 6K material. SOme of the reDRAW color settings also occur after debayer, and so they too live in GPU land.

While scaling on the GPU is common and may come into play in many situations, the wavelet architecture of the R3Ds allows "extractions" like 1/4, 1/8, etc that are not scales per se. I am also not certain that the Rocket (old or new) is absent from the scaling party when required - anyone know for sure?

IAC, the more powerful Rocket-X, with a solid warrantee behind it, will make sense for anyone that deals with a lot of RED footage. Assuming that Thunderbolt enclosures can host it properly, I fully expect to see rentable Rocket-X boxes become popular for per project usage.

The ability of current TB implementations to keep up with both a Rocket-X accelerator card and heavy storage I/O loads remains to be seen, let alone mobile setups where a GPU might be sharing the bus as well...

Cheers - #19
 
The current Rocket does scaling on the card. It always does a full-resolution, full-quality decode of the R3D frame(s) and then scales to the selected output resolution. On faster workstations with enough cores to plow through a few streams of R3D's at lower wavelet extraction levels (1/8, 1/4, etc..), the editing process can often be smoother without using the Rocket. CS6 has done a better job of knowing when to engage the Rocket and when not to. The Rocket is still a handy tool to have -- for processing R3Ds at full quality, you still need a 12-core box at roughly 3GHz to match what the Rocket can do. A monster 16-core Xeon can beat the Rocket at its own game, but it's an expensive beast of a system. A very nice 6-core i7 desktop with Rocket can be had for 40% less than that Z820 box. OTOH, that Z820 provides faster processing for more tasks than just R3D decoding and if you pair it with a Rocket, it's very fast for R3D workflow. So, there is no one truly definitive solution... Even if money is no object, there is still no perfect solution.

Rocket-X will work in a Thunderbolt enclosure, but its I/O will be severely restricted. Not a bad situation to be in really, at least we know the card won't be the bottleneck. And Thunderbolt gets a channel upgrade and speed boost next year as well.
 
@Jeff - I'm going to be building a PC in about month with the idea of dropping a Red Rocket-X in there. I'm going through some interesting storage research at the moment. Curious you have any thoughts about current or upcoming tech on that front.

Looking for a 24-48TB solution. The box itself I'm hoping can be fairly mobile. I'm not doing an external enclosure, Rocket-X will be in there. Something I can pack up and work on location with, not so much as a DIT, but more for editing and color purposes on projects. Hoping to have the ability to work on R3Ds via some sort of portable SAS or "other" connection. Just don't know exactly yet.

There's some new Intel processors coming out in June.

I'm what I would describe as an Adobe Power User and will 99.9% go with nVidia for my GPU. Titan looks interesting. Seeing a lot of driver chaos at the moment. I'll likely want to be able to drive a 4K monitor from this thing at some point.

Lots of fast ram is a given and that works well on my current system here. Kinda want this next system to be a beast though.
 
Back
Top