Re: ColorSync and printing -- Panther (2 of 2)
Re: ColorSync and printing -- Panther (2 of 2)
- Subject: Re: ColorSync and printing -- Panther (2 of 2)
- From: Chris Murphy <email@hidden>
- Date: Fri, 19 Dec 2003 13:43:42 -0700
On Dec 19, 2003, at 1:19 PM, bruce fraser wrote:
It's an even bigger pain because many photoinkjets register a single
uber-profile withe ColorSync, then swop in the correct media-specific
profile based on the media settings in the printer driver. In
applications like Photoshop, we use the media-specific profiles. It
would be a royal pain to have to change the paper-specific profile in
ColorSync every time we wanted to print to a different paper.
Yeah it's just too user hostile. It doesn't matter if it makes sense,
or the color geeks can get used to such a thing. It's such a pain in
the ass that most people won't do it and it sets color management
implementation back to a whole new level of abuse.
An explicit null setting would save EVERYONE a world of grief.
I agree, to a point. The problem is that it then turns off ColorSync
color matching when printing from the minor apps that only get managed
through the driver/OS. I think the long term solution needs to be, as
John Fieber describes, applications that do their own color management
need to include in the job ticket a request for a null transform by
ColorSync. That way the ColorSync Utility can be configured correctly,
but those settings are ignored on a case by case basis, from those
applications that can do their own color management - and when set to
do so. This is something that we've needed to see happen as soon as
Photoshop 5 showed up on the scene of things. And yet here we are three
major versions later, and it's been something like 5 years ago this
month hasn't it? Or has it been 6 years?
Either way, there is a requirement for applications to be able to tell
the operating system "don't do anything else" and for that message to
be honored. The idea of relying on source and destination profiles
being identical as the only way to cause null transforms seems like
pretty bad odds to bet on. What would they say about this in Vegas?
"It's a longshot."
But since getting apps to do this is about 18 months away (at least), I
think an explicit null setting might be the only way to go for now.
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.