Welcome to our community

Be a part of something great, join today!

Log in
  • 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 :)

4k And Digital Fusion 5???

sure would be great! We use it all the time around here, far more then AfterEffects
 
Native support for .r3d clips in compositing apps sounds great on the surface but at this point I think it's totally implausible.

The challenge here will surely manifest itself as an issue of maintaining "user interactivity" in the toolset.

The key to an efficient compositing pipeline has alot to do with maximizing the speed at which the artist can tweak and coax the multiple layers of footage required for their comp.

Knowing how much computational power (either GPU or CPU) is required for processing r3d clips in realtime, i cannot imagine a day anytime soon that a computer (any computer) would be able to provide enough processing power to allow working with multiple, simultaneous layers of r3d clips.

Maybe CINEFORM will be a valid option here, but I don't think native RED camera clips ever will be.

my $.02

Adam
BOXXlabs
 
BOXXLabs said:
Native support for .r3d clips in compositing apps sounds great on the surface but at this point I think it's totally implausible.
Click to expand...

I completely disagree. Compositing apps don't work in realtime. unless you are on a monster like an Inferno or something, but most of us using AE, Shake, Fusion, etc, have to render to see everything. So native .R3D in compositing apps should happen before anything else. The editing apps are where realtime is needed.

Don't get me wrong, I would love to have realtime R3D compositing in Fusion, but I don't see it happening any day soon and I will live with native support and having to render like I already have to do anyway.


Mahalo,
Dusty
 
Dustin Cross said:
I completely disagree. Compositing apps don't work in realtime. unless you are on a monster like an Inferno or something, but most of us using AE, Shake, Fusion, etc, have to render to see everything. So native .R3D in compositing apps should happen before anything else. The editing apps are where realtime is needed.

Don't get me wrong, I would love to have realtime R3D compositing in Fusion, but I don't see it happening any day soon and I will live with native support and having to render like I already have to do anyway.


Mahalo,
Dusty
Click to expand...

I think you misunderstood my post. Nobody is talking about "real time compositing"... Even inferno isn't really "realtime" in the traditional sense. You still must cache out sequences if you want to see them at full frame rate and you still must render-out the sequence when you're finished.

I am saying that for "normal" multilayer compositing, the artist needs to have some level of interactivity.

It's not uncommon for composites to get 30, 40, 50 layers deep - with many of these layers being actual full-resolution motion clips (and not just "graphics" layers)

I think that the computational overhead for working with dozens of layers of R3D clips -not to mention the additional strain of calculating the effect of various filters, keys, masks, etc. is not going to be possible with current CPU/GPU performance.




The other (and possibly more challenging) issue I see here is that r3d is NOT a true CODEC - you can't mix two layers of RED footage (or a layer of Red footage and anything else) and then create (render) a new r3d clip such as you might do with DPX or QT clips - or compressed media using true file CODECs.

It is exactly this limitation that explains why editing r3d (and proxy clips) in FCP (and soon to be Premier Pro) is strictly a "cuts-only" affair. -no dissolves, no transparancies/subtractives/additives, titles, etc.

If anybody can explain how software developers might engineer a solution to this problem then I would LOVE to hear it...I'm certainly not smart enough to figure it out...

;)
 
I agree with Adam. Transcode to openEXR or other supermacho:angry2: file format if latitude loss is a concern in the comps. The idea of de-bayering on top of processing the other hundreds of image ins & operations in a typical comp... ouch.

If you're talking about using Fusion as a color tool then I guess I can see it... but having graded a few long form projects in combos of Shake, Nuke, Combustion, and AE, I'd rather break my own knuckles than do that again.

Ok, maybe not break... maybe just crack them really hard.


cheers,


John T.
 
You must log in or register to reply here.
Back
Top