Re: untagged RGB data
Re: untagged RGB data
- Subject: Re: untagged RGB data
- From: Richard Wagner <email@hidden>
- Date: Sat, 20 Dec 2003 13:30:59 -0700
Andrew,
With respect to digital cameras, I think Eric's got this one nailed.
It's the rendering that's variable. On my Nikon DSLRs, I have a choice
of three output profiles: I: sRGB (optimized for skin tones), II:
AdobeRGB ("wide gamut") and III: sRGB (optimized for "Nature and
Landscapes"). Unfortunately, the manufacturers have confused the
issues of rendering and gamut. In III:, the rendering is optimized to
"punch up" greens and saturate colors for landscapes. Why put this into
sRGB? Got me.... I assume that the "AdobeRGB" is supposed to be
neutral, and sice I obviously want everything in the widest gamut space
possible, that's all I use.
As there are no "device profiles" that can be set for the cameras, each
of the settings is used to provide a different "look" to the output.
Unfortunately, many don't realize that the choice of a particular
setting (sRGB) might start them off in a smaller gamut that they later
can't escape from. It would be nice if the manufacturers set this up
as sRGB/AdobeRGB, with the "look" as a subchoice under either of these.
For those who only shoot for family/friends/web, they could stick to
sRGB. For others, AdobeRGB (or BetaRGB, or..?) obviously would be a
better choice. Nikon could at least keep the sRGB choices together!
Rich
Tucson
Andrew,
Its a really good point and question and one that confuses many users.
Its
easy to forget that sRGB has two parts to it: 1) the encoding, and 2)
the
rendering. [snip]
Its because of this rendering step that we have so many flavors
(different renderings) of sRGB.
_______________________________________________
colorsync-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/colorsync-users
Do not post admin requests to the list. They will be ignored.