MAC / CS3 / DVCPRO-HD color shifting

[Martin Jaeger]

Same here… Working on ProRes output from RedAlert and the roundtrip through AE results in gamma and color shifts. This problem is not limited to DVCpro-HD footage. At my wits end for a solution

[Andre Farkatt]

I work with post prduction since 1993 and I’ve seen this colorspace issue only two times… one when we first used digisuite uncompressed and now… ALL other worklflows including recent betacam/digi beta SD editing with FCP + finishing with AE doesn’t show this issue, the quality and integrity of the whole image is pristine and the same from the camera to the final tape… and using AVID meridien (the good old hardware based avid) + back and forth to AE, I NEVER had this issue…

Using an alternate codec as suggested in another answer is not practical, since we use automatic duck and work in AE with the original footage, captured via FCP or AVID… so, if FCP or AVID doesn’t capture straight in a codec that AE is able do open, it’s useless for me… specially if it is a codec who doesn’t have aja kona support…

Andre Farkatt
RTV Producoes

[Dustin Parsons]

What codec did you capture at with the workflow that worked for you (the betacam/digibeta stuff)?

“if FCP or AVID doesn’t capture straight in a codec that AE is able do open, it’s useless for me.

Correct me if I’m wrong but aren’t DVCPRO HD and ProRes codecs supported by AE?

——————————————–
Mac Pro | Leopard 10.5.3
2.66GHz Dual-Core Intel Xeon | 4GB Ram
Final Cut Pro Studio 2 | Avid Media Composer

[David Battistella]

Hey Andre,

You can capture with SHEER CODEC it’s just not RT enabled. If it was it would be a prores killer. Far far superior image quality to Prores for sure.

Why not try a small sequence to see if it gets rid of the problem.

Remember. We are here to help and we do it for FREE.

David

Peace and Love 🙂
Read my Blog
https://blogs.creativecow.net/DavidBattistella

[Andre Farkatt]

Sure David, you’re welcome and all help is welcome. Unfortunately I can’t use anything that is not straightforward as many editors use our facility… it must be as simple and standard as it can…

I’ll try some shoots with sheer, but, even if it solves my personal problem, it will not solve my free-lancers editors…

thanks

Andre Farkatt
RTV Producoes

[Andre Farkatt]

Hi, Dustin… when using beta(component)/digibeta(SDI) I capture using AVID meridien compressed or uncompressed in a media composer mac OR using AJA Kona uncompressed (2vuy). Then after editing I export omf reference or xml to another machine running after effects and automatic duck… thus, opening the original footage captured either by the avid meridien or the FCP with AJA kona… there’s no export/convert/recode in this process…

using this, nothing shifts, the same image seen from the beta/digibeta deck is seen when playing the AE rendered movie back in the avid/fcp… even when it has super white/super black information in the tape…

just replacing the capture process by the p2 import (log and transfer) at the FCP/AJA Kona all the nightmare begins when the footage goes to after and come back rendered… when looking from the fcp timeline, the p2 footage is ok… but when opened by after (again, using automatic duck to open the original footage directly in after) and rendered, the result is what we all see in this topic… gamma shift, luminance crop, superblack gone, superwhite gone… etc…

Andre Farkatt
RTV Producoes

[Dustin Parsons]

Having no export/convert/recode sounds great, I’ve never edited that way. I’ll definitely have to look into it, especially if it fixes this problem.

Thanks for the reply

——————————————–
Mac Pro | Leopard 10.5.3
2.66GHz Dual-Core Intel Xeon | 4GB Ram
Final Cut Pro Studio 2 | Avid Media Composer

[Andre Farkatt]

No, it doesn’t fix… I use the exact same workflow with p2 from fcp to ae and when I play the AE rendered movie, no matter what codec (hd) I use, it does the gamma/luminance crop/washed out result…

It’s not a export problem, but a colorspace interpretation and loss of usable data when getting out of the native yuv usage inside fcp… just in applying a rgb effect we also have some degradation, much less than using AE, but it’s there…

let’s keep talking… I dream with somebody appearing here and showing that we’re all stupid and tell a simple solution ehehehehe 🙂

Andre Farkatt
RTV Producoes

[Matthew Rundell]

I hope to find a solution as well. I seem to have this problem with all Quicktimes, it seems. XDCAM, DVCPROHD, etc, etc. For some reason, CS3 just does not deal with QuickTimes that well– it makes me do most of my important client work in Motion. I hope this issue clears soon, or maybe with CS4.

Matt Rundell

[Francois Driessen]

If you have not found a solution to the problem yet, here you go:

My guess is all of you have an AJA Io or Card, right…? If I did not open a project that rendered fine prior to getting an AJA Io HD I would never have deducted this. But my suite worked fine with round-trip DVCPRO HD & FCP before getting the Io. And checked the same clip on the other suite without Io – and that worked fine too.

Spoke to one of the very helpful guys at AJA and he suggested removing a codec that installs with the A Io control panel. root/ library/ Quicktime/ AJAUncompressed

I don’t need that codec. And uninstalled it. Voila! AE is working fine again with DVCPRO HD. I can live again.

Francois

>- e y e f l a m e .tv –< https://eyeflame.tv