Re: Panther, sRGB, web browsers
Re: Panther, sRGB, web browsers
- Subject: Re: Panther, sRGB, web browsers
- From: Chris Murphy <email@hidden>
- Date: Thu, 18 Dec 2003 14:27:40 -0700
On Dec 18, 2003, at 1:55 PM, John Fieber wrote:
I'm not sure I follow the methodology. I'm not sure how the color
meter works and even less sure of the situations where it even should
match the values stored in the file.
It depends on how it's configured but it basically shows the numeric
values being send to the video card if you have it set to any of the
RGB settings.
But my an independent methodology I've verified that it sure seems to
be the display profile that is used.
Right, that's what I found also. "Monitor RGB" means the currently
selected display profile.
I just took a raster RGB file with some color patches and saved three
versions: tagged with Generic RGB, tagged with the display profile and
untagged. Same RGB numbers in all three. Preview renders the
no-profile case the same as the tagged-with-display profile case.
That's what I'm seeing on Panther as well. On 10.2 the system assumed
Generic RGB for untagged RGB, and now in Panther it appears to be using
the display profile (monitor RGB) for untagged images.
From this sampling of applications I conclude that IF it is true that
untagged data is assumed to be Generic RGB, then the higher level APIs
(Cocoa NSImage, QuickTime, QuickDraw, etc.) must be overriding that by
tagging the data with the display profile by the time it gets to
Quartz rendering.
Yes. But I think it's more likely that the default RGB for untagged
images is now monitor RGB.
In the face of untagged data, you can only guess what to do to bring
it into a color managed universe (and MacOS X claims to be a color
managed universe). The choice of Generic RGB (or sRGB or MyFunkyRGB)
is rather arbitrary, but it really seems a at least somewhat less
arbitrary than the display profile. And since nobody seems to have
found an actually useful function for the "default profile" colorsync
settings, maybe they should just disappear so as to avoid confusing
people?
Yes, if they're not going to get used by even Apple's own applications,
get rid of it. But I'd much prefer to see these settings be used as
actual defaults instead of flapping in the breeze while confusing
users.
For RGB it makes sense for Apple to pick something, and stick to it.
And I don't think it necessarily needs to be user selectable. Just
assume sRGB for untagged objects. But to assume a generic CMYK, and not
have any other option I do not think is a good idea. It needs to be
user selectable. And probably grayscale also.
Chris Murphy
Color Remedies (TM)
www.colorremedies.com/realworldcolor
---------------------------------------------------------
Co-author "Real World Color Management"
Published by PeachPit Press (ISBN 0-201-77340-6)
_______________________________________________
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.
| References: | |
| | >Panther, sRGB, web browsers (From: Chris Murphy <email@hidden>) |
| | >Re: Panther, sRGB, web browsers (From: Steve Upton <email@hidden>) |
| | >Re: Panther, sRGB, web browsers (From: Chris Murphy <email@hidden>) |
| | >Re: Panther, sRGB, web browsers (From: John Gnaegy <email@hidden>) |
| | >Re: Panther, sRGB, web browsers (From: John Fieber <email@hidden>) |
| | >Re: Panther, sRGB, web browsers (From: Chris Murphy <email@hidden>) |
| | >Re: Panther, sRGB, web browsers (From: John Fieber <email@hidden>) |