This content has been marked as final. Show 9 replies
Open up your project settings and check the Preserve Legacy Gamma option. This should solve your problem.
Im sorry but this didn't solve my problem.
Maybe I just don't get this, but this is a general problem amongst filmproducers all over the world.
I have uploaded an image for you to look at, where I have tested and compared different settings in AE. Of course my wish is to get the representation of the video in Quicktime as close to the representation in After Effects, as possible (so that the video image in Quicktime matches color- and general image adjustments in After Effects ...obviously). I have numbered the images in the order I thought was natural to compare the images in. As you can see, match legacy gamma does nothing. The best result is when using HDTV-16-235 with compensate for scene-referred profiles unchecked, and then EXPORTED to h264 from AE. You can see this as the closest image match is between image 10 and 11. Everything is in 8bpc.
The image is located here:
Have you seen this article at Provideocoalition.com?
It has a couple of work arounds. I personally suspect this same (or similar) issue may affect DVC PRO HD.
Mine is fluctuating. Mine worked without having the Match Legacy Gamma Adjustment on and then off then on. I did something which seemed to overwrite a setting and reset something. Not sure.
In project settings, Turn on the Blend Colors Using 1.0 Gamma.
Render something in the render que. My video suddenly got darker and the results were darker than normal.
I went back, checked it off, re-rendered it, and it worked out perfectly.
Thanks for your answer. But I have indeed seen that article before, as well as Andrew Kramers solution.
And it doesn't work.
Firstly provideo coalitions article adresses a slightly different problem where gamma shifts when rendered with QT Pro and appears on Mac and in Safari but not on Windows.
I believe that this is the same problem in the core but that the problem has changed since updates. The problem now appears in Windows and not only when "re-exported" as they say in the article...I have tried the gammastripper from FUELVFX and it can neither find or remove the gamma "tag". (I believe that maybe it did at some point but not anymore).
Regarding x264 I'm very sceptical. Not using the industry standard h264 seems like a dangerous idea. Can our customers use it without complications without themselves having to install a new codec?
(It's like shipping a professionally crafted powerpoint presentation without the fonts that were used in it...or worse).
Even more importantly, can we use it as we always have? Can we rely on the codec-development not to be abandoned? Maybe I'm paranoid but with all technical problems we have to fight with in this business, you can't be too careful. (The reason I haven't really tried it is that I don't want to install unnecessary codecs on my computer that can alter otherwise completely functional stuff.)
And the other solutions mentioned in the article...the bad...are exactly that.
But maybe someone can convince me with some facts that the x264 codec is ultimate?
Thanks for the answer. But did not work for me.
Olle, I share your frustration, and have not found a solution. I have resorted to a adjustment layer called ".9 gamma adjust", not a solution but a work-around.
as far as you work with quicktime, especially with H264 encoding, you'never find an end to this problem. Apple behaves so stupid whenever it comes to these kinda questions because they don't give a damn about pro apps users. anytime they bring out another quicktime release, something else is fixed, and different things are messed up.
By the way, quicktime player is a bad thing for referencing you work.
if you drop a H264 file into firefox browser, the gamma should be then ok.
if you want to have a peace of mind try working with image sequences as PNG, TIFF, TGA or try a much more reliable codec like Sheer Video Codec from Bitjazz.com