Re: iPhoto 5 and Keynote 2 observations, was: ColorSync inconsistency in iPhoto
Re: iPhoto 5 and Keynote 2 observations, was: ColorSync inconsistency in iPhoto
- Subject: Re: iPhoto 5 and Keynote 2 observations, was: ColorSync inconsistency in iPhoto
- From: John Gnaegy <email@hidden>
- Date: Mon, 14 Feb 2005 19:55:04 -0800
On Feb 14, 2005, at 4:09 PM, Chris Murphy wrote:
I've done the following initial tests with iPhoto 5.01
1. Add TIFFs and JPEGs, tagged and untagged, to iPhoto.
a. Duplicates are made and stored in the iPhoto Library
b. The duplicates contain the profiles in the originals. If the
original does not have a profile, the duplicate also has no profile.
No conversions have occurred.
Good, that sounds reasonable.
2. On-screen preview of these images appears to not use the currently
selected Display profile. No matter what profile I choose in
Displays>Color>Display Profile, the on-screen preview remains the
same. Digital Color Meter reports RGB values of variously tagged test
images as having the same RGB values if I convert the test images to
Generic RGB. At this point, it appears there is no display
compensation in iPhoto. [If Pete Carter is calibrating/profiling his
display with a gamma greater than 1.8, such as 2.2, or native display
gamma, this accounts for his experience where the cropped & converted
(sRGB>Generic RGB) copy looks washed out compared to the sRGB
original.]
This depends on a) which of your displays is the default display listed
in ColorSync Utility, and b) whether or not you've used a calibration
app that broke the system profile - default display profile behavior.
I tried this with iPhoto 5 on both Tiger and Panther, setting the
profile of my default display to a BGR profile, added an image to the
iPhoto library, and the image was displayed BGR matched (blue instead
of red) meaning the image data was matched at some point to the display
profile.
3. Using any of the edit functions (e.g. crop or enhance) causes the
copy held in the iPhoto Library to be modified. The RGB values in the
file are consistent with a conversion to Generic RGB. The resulting
file has Generic RGB embedded. However, it is displayed using raw RGB
values in the now converted file, there is no display compensation
(Generic RGB>Display RGB).
I think from this point on the matching results may be misleading due
to what you're seeing in 2. above, if the profile of your default
display isn't being used for matching then that's going to be a
problem. You can determine if this is the case by running this in
Script Editor:
tell application "ColorSyncScripting"
set sp to name of system profile
set i to count displays
repeat with i from 1 to i
set dp to name of display profile of display i
end repeat
end tell
and look at the Event Log, the system profile should be the same as the
profile of one of your displays, if it isn't, you'll have to toss a
pref in Terminal with:
rm ~/Library/Preferences/ByHost/.Global*
Since you're seeing matching indicating Generic RGB Profile is being
used, whiich is symptomatic of the disconnect caused by the profiling
app setting the system profile directly instead of just setting the
display profile, I bet that's what's happening.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden