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

RED 4K/RAY workflow?

Claus Mueller

Well-known member
Joined
Jan 5, 2007
Messages
256
Reaction score
0
Points
0
I was just wondering if we can export .RRD (RED 4K/RAY Distribution format) files from a future Redcine build or do we need RED Rocket for that?
 
I was just wondering if we can export .RRD (RED 4K/RAY Distribution format) files from a future Redcine build or do we need RED Rocket™ for that?

The REDCINE-X with the RED Rocket produces exactly the same end product as REDCINE-X does without it. The Rocket just makes it insanely fast.

It shouldn't make a difference whether you have one or not apart from the render times. But it may not be REDCINE-X that produces the RED 4K distribution files - since it's more geared at raw decoding and manipulation, and RED 4K will take RGB files as input. It may be a separate application and/or an encoder plugin for Quicktime or something. But we probably won't know for sure for a while now.
 
If I understood him correctly, I think that Jim said yesterday that one needs an ASIC in order to generate the deliverable files that will go onto the RED-Ray (soon-to-be-renamed). That means that either the Rocket card will be able to generate them (I hope I hope I hope!) or perhaps another PCI-e board will be needed.

Did I get that right?

- Jordan
 
I would also be interested to know if the Rocket will be able (with a firmware update) to play back RRD files.
 
That means that either the Rocket card will be able to generate them (I hope I hope I hope!)

I was hoping so too. But I don't think that will work from what I remember. [Someone from Red answered a question from Mark (Offhollywood)].
 
If I understood him correctly, I think that Jim said yesterday that one needs an ASIC in order to generate the deliverable files that will go onto the RED-Ray (soon-to-be-renamed). That means that either the Rocket card will be able to generate them (I hope I hope I hope!) or perhaps another PCI-e board will be needed.

Did I get that right?

- Jordan

Hmmm.

The final format of any file can be generated as long a the proper math is performed. This could be by specialized hardware (i.e. ASIC), or by CPU/GPU on a regualr computer, or even by pencil and paper (calculator use allowed.)

Now you might WANT dedicated hardware in order to get the file rendered sometime this century, but you technically shouldn't NEED one. Rather like debayering a .r3d... you can do either via your CPU, or the Rocket, ones just a lot zippier than the other.

Speaking of the Rocket, I suspect that it won't encode the Red[Ray|4K] distribution files. It may assist on hte front end with debayering .r3d input files you supply, but I'd bet that's where it stops.

After all... Red has shown their Red[Ray|4K] footage as long as almost a year ago(?), and I sincerely doubt that was rendered on an ASIC-based platform... a beefy machine or 20 is more likely.

-sc
 
Speaking of the Rocket, I suspect that it won't encode the Red[Ray|4K] distribution files. It may assist on hte front end with debayering .r3d input files you supply, but I'd bet that's where it stops.

Yup. This is my understanding too.
 
Back
Top