What happened to the COLOR r3d plug in?

[Cüneyt Kaya]

I saw the adobe sneak preview...awesome

but what about the r3d plug in for COLOR?

are they serious....or does the new iphone 3g get a new update for useless stuff

 

[Alex.Mitchell]

I have a feeling it'll be a while. The .r3d support in the Adobe Suite isn't perfect yet, and I have a feeling that Apple is probably just as far along as they are. The difference, I think, is that Apple won't release their native .r3d workflow until it's a comprehensive solution as opposed to a solution in the making.

Mind you, I could be wrong. Maybe they're more intimate with RED development than we know and a solution is just around the corner. The were the first to support the proxies after all.

 

[Patrick Tresch]

I'm also asking myself why is Adobe showing an jerky internal beta r3d support video to the world? Is this world leader software company communication of the 21rst century?

I see Adobe screaming "we are the first, we are the first..."

Are they affraid to be passed by by Apple????

Future will tell wo is the best quality/workflow/price!

See you

Patrick

 

[Hans von Sonntag]

I guess the main problem is that FCP is QT only and.R3D is obviously no .mov file. Color on the other hand can work with DPX natively. But Color was once FinalTouch, Apple independet and meant for digital Cinema, thus the DPX implementation. I'm pure guessing here but I fear that a lot of FCP has to be rewritten. Adobe once did it with PP and gained a lot.

Adobe PP is not tied up to QT and welcomes 3rd parties. As far as I know, Red does most of the job here. Red cannot do that for Apple unfortunately because FCP is not open to 3rd parties.

Next NAB we'll see wether Apple takes their ProApps serious, or not.

Hans

 

[Cüneyt Kaya]

i think the biggest problem for apple is their 2k limitation.
adobe is resolution independant.
when they can implement a gpu engine for AE or integrate a CC tool in their suite this could be something.

i prefer knowing whats going on, rather then the surprise thing.

 

[Alex.Mitchell]

Yeah, it would be nice if they increased the maximum frame size. That said, at least it'll still support 4K HD res (3840x2160).

I guess the main problem is that FCP is QT only and.R3D is obviously no .mov file.

Really? 'Cause I've always felt that basing their NLE/Pro Apps on the Quicktime framework was kind of nice. From what I understand, all you need to do is develop a plugin/codec for Quicktime and then you've got, at least, partial support for it throughout every app that's Quicktime based. For instance, I just downloaded a video from Youtube that was H.263 inside a .flv wrapper. Because I the Perian plugin installed, all of a sudden I can edit it in Final Cut.

So yeah, I actually like the Quicktime aspect of the FCS. I find it pretty flexible.

 

[Paul Lee]

Let's not rule-out a surprise update to Color only that allows direct .r3d access and render to 2K. That's kind of the buzz one of our guys got at NAB. What with the SDK being released and build 16 going release (remember, all of the RED apps had to be updated to work with b16 footage), the time seems ripe. Edit proxies in FCP, then conform .r3d in Color and render to whatever you want, even if limited to 2K. I'd still take that today with a smile!

 

[Ben Rojas]

Edit proxies in FCP, then conform .r3d in Color and render to whatever you want, even if limited to 2K. I'd still take that today with a smile!

Agreed... I'd be smiling too :biggrin: