When most people say "gamma 2.2," they're referring to sRGB... 2.2 just
happens to do a pretty good job of approximating an sRGB curve when you only
have a single parameter to play with.
-Nathan
-----Original Message-----
From: Jep Hill
Sent: Monday, February 06, 2012 9:44 AM
To: [email protected]
Subject: [Nuke-users] Quicktime gamma 1.8
Could be wrong here, but I think Gamma 1.8 was based on the fact that OSX
pre-Snow Leopard (10.6) used default Gamma of 1.8 and, more importantly,
Quicktimes used to be encoded with Gamma 1.8... As Paul suggests, this is
easily over-ridden in defaults.
Gamma 2.2 is the default monitor gamma however, for the past few years, most
Quicktimes are encoded sRGB -- I encourage you to view the movies in
Quicktime and compare them to the same MOV loaded into a read node in Nuke
with Gamma 2.2 and the same clip loaded in at sRGB -- pay special attention
to the blacks. Now, this *is* assuming your not viewing in QuickTime Pro
with "Enable Final Cut Studio color compatibility" checked. In most cases,
you may find that sRGB is actually a better match than Gamma 2.2 -- let me
know if you guys are seeing different results! And then there's the case
where your footage was ingested/encoded by an ad-hoc setup by someone that
may have no interest in correct settings and just wants to get it out of the
way ASAP... but, I'm sure that's never happened to any of you ;)
Bearing in mind that Nuke's defaults are meant to start us off in the right
place for a majority if cases, I agree that the Foundry might consider
changing the default from 1.8, however, I'm not sure that Gamma 2.2 is the
best choice considering the colorspace setting is meant to account for what
the footage was encoded with rather than the viewing device -- sRGB may be a
better choice.
Regardless, no matter -- that's why we have the ability to over-ride the
defaults to fit our color pipeline.
In cases where the Quicktimes are actually Arri Alexa captures or R3D proxy
files, you may not want Gamma 2.2 or sRGB...
By the way, since we're suggesting changes in the Read node's behavior when
loading Quicktimes, we may also want to change the default to "start_at" 0
in order to keep the MOV 1:1 with most Apple apps. (Yes, we over-ride this
in our custom settings too)
Just my $.02...
Cheers,
Jep_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
