Apple---Reds Partner---integrated R3d files into COLOR?

[Cüneyt Kaya]

ok, apple is reds partner....also Assimiliate
1. Assimiliate developed several products:
PrePost
Scratch Cine...cool, they did something (some like it, some don`t like it :) )
but they did something

they integrated r3d files into their CC Tool


2.What about Apple?
Apple is the other right now/today partner
And they have their own CC Tool---COLOR

Will they do something to integrate R3D files into COLOR ?(for this they have to update COLOR to handle 4k files)

And what about FCS2?
Will something happen?

dont know
maybe redcode 444?
or edit with proxies send to COLOR and COLOR automaticly changes the proxie Files with r3d files?

gamma issue
native support fo dpx files in FCP/Motion
10 bit RGB render engine in all Appl.

i dont know today for what i can use the REDCODE setting in FCP for.
Its ProRes that is workable.

So what is the situation with Apple...
are there any developments for the really near future planned?

I think this is a legitimate question/demand from Apple....
But does RED know something?

For sure they cant force them to be faster.

[Michael Thornton]

Apple won't be @ NAB?

We will find out hopefully in the future.

Sad.....:-(

Tek

[M Most]

ok, apple is reds partner....also Assimiliate
So what is the situation with Apple...
are there any developments for the really near future planned?


The situation with Apple is the same as it's always been. Quicktime is Apple's media handling architecture. Any developments for the really near future all revolve around that. I will be very, very surprised if Final Cut (or anything other than Color in Apple's product line) reads R3d or any other file type other than Quicktime directly.

I could be wrong, but I really don't think I am.

[Dylan Reeve]

I suspect there are a lot of underlying architecture issues with Color that would make it very difficult to support R3D natively. Plus there are probably a fair few more important issues to fix in Color first.

[Chris Kenny]

Well... keep in mind that "QuickTime" isn't a file format, it's a media architecture. And it isn't tied to any specific codec or wrapper format; it already supports quite a few of each. If Apple was sufficiently determined, R3D could just become another format that QuickTime could work with natively.

(I wouldn't consider this too likely, mind you, but it doesn't seem technically impossible.)

[Jason Diamond]

what if they just added a RED 'Room' that you could duck into do what you need and back out into color?
its def possible and you may be surprised what apple is cooking up.

[Fredrik Callinggard]

The highly likely rumors are that Color will be able to take redcode natively.


Fredrik Callinggard

[tylerhawes]

I suspect there are a lot of underlying architecture issues with Color that would make it very difficult to support R3D natively.

I don't think so. Color is an OpenGL/GPU-accelerated application. Iridas has shown that a GPU-based approach for RAW debayering is very efficient, so Color could go down the same path.

Color was developed by Andrew and friends at Silicon Color and was never part of the QuickTime cabal. It already runs much better with DPX than it does with QuickTime media. So there is no QuickTime-entrenched overhead in Color like with FCP to worry about.

So I see no serious issue to prevent them from supporting .R3D, other than pushing 4K pixels will be a much bigger load on the GPU. But again, Iridas is doing realtime 4K RAW with Dalsa footage on a Quadro 5600, so it's obviously possible.

[Dylan Reeve]

I was thinking more about software architecture, rather than hardware restrictions. I believe RAW image handling is quite a long way from what Color is currently doing.

But I'm just speculating really.

[Chris Kenny]

That's where Red's SDK comes in, though. It will presumably contain a library that apps can just instruct to decode frames from R3D files and send over, say, 16-bit RGB image data. So, add a few library calls to appropriate places in your app, maybe add a GUI that lets the user select parameters for the debayer (which simply get passed along when invoking the library), and you've got native R3D support.

[Paris Remillard]

Apple does have system wide support of still camera RAW files. And Aperture is based entirely on the idea of using smaller RAW files as your "negative" and having all of your adjustments as tiny metadata tags, leaving full debayering and processing until output/delivery, keeping storage and processing requirments low(well, until rendering on output). So, they know the game. It's just the matter of whether they can squeeze it into Color. And dealing with a 4K Redcode RAW file would be much less data than a 2K DPX, since it's compressed and unprocessed. I just output a single 2K DPX frame and it was 8MB. A single .R3D would be just over 1MB (I assume since Redcode is 28MB/sec). And it wouldn't need to be "processed" until the final output. So rendering would still be a bitch, but working with the .R3Ds shouldn't be any more taxing than HD. Less really.
I think it would be fantastic. Shit, I'd be happy if I could put .R3Ds into Aperture and batch process. So much more control than the current iteration, at least, of Redcine. Or just add video support and power windows to the Aperture engine. That can't be that hard, right : ) So, fingers crossed.

[Ben Holmes]

Nice prediction at the start of the thread! And lo, it has come to pass...