(1) That "device" in the color space name means that the image is likely
to look different on different machines.
(2) If I took the image and fed it to CGImageCreateCopyWithColorSpace
along with the generic RGB color space, it would do color matching to
convert to generic RGB (as opposed to pretending that the image was
generic RGB all along), and the resulting image would still be
device-dependent.
--
James W. Walker, Innoventive Software LLC
<http://www.frameforge3d.com/>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartz-dev mailing list (Quart...@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/quartz-dev/quartz-dev-garchive-50095%40googlegroups.com
This email sent to quartz-dev-g...@googlegroups.com
In practice, I would assume an sRGB gamma 2.2 space and go from there. Your mileage may vary.
> https://lists.apple.com/mailman/options/quartz-dev/wave%40pixar.com
>
> This email sent to wa...@pixar.com
--> Michael B. Johnson, PhD
--> http://homepage.mac.com/drwave (personal)
--> http://xenia.media.mit.edu/~wave (alum)
--> MPG Lead
--> Pixar Animation Studios
(2) If I took the image and fed it to CGImageCreateCopyWithColorSpace along with the generic RGB color space, it would do color matching to convert to generic RGB (as opposed to pretending that the image was generic RGB all along), and the resulting image would still be device-dependent.
Thanks, that helps.