• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: ColorSync and printing -- Panther (2 of 2)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ColorSync and printing -- Panther (2 of 2)


  • Subject: Re: ColorSync and printing -- Panther (2 of 2)
  • From: Graeme Gill <email@hidden>
  • Date: Sat, 20 Dec 2003 17:34:33 +1100

Chris Murphy wrote:
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?

This is exactly what we've done in the Cyclone RIP ever since we
added profile support (many years ago now). There are two magic
"job ticket" tags. One turns off just the color space conversion,
the other turns off the per channel calibration/linearisation.
They were intended for use in calibrating and characterising the
device, but the same idea could be used to allow upstream color
management. The situation is slightly different to Colorsync,
in that Cyclone effectively uses device link profiles, and it
is entirely possible to create a "characterisation" CMYK->CMYK
null conversion device link profile (which is what gets used
when the magic tags are seen by the RIP, or can be used all the
time for a particular virtual printer.)
[Things are not quite so simple in calibrating or characterising
7 or 8 channel devices in their native space, rather than
CMYK-"pseudo native" space, but that is another story...]

Relying on Colorsync to do a null transform when the source
and destination profiles are the same description strikes me
as clever, but a bit obscure, and rather flaky if it's difficult/impossible
to know what output profile is going to be used.

Graeme Gill.
_______________________________________________
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: 
 >ColorSync and printing -- Panther (2 of 2) (From: John Zimmerer <email@hidden>)
 >Re: ColorSync and printing -- Panther (2 of 2) (From: John Fieber <email@hidden>)
 >Re: ColorSync and printing -- Panther (2 of 2) (From: Chris Murphy <email@hidden>)
 >Re: ColorSync and printing -- Panther (2 of 2) (From: Rolf Gierling <email@hidden>)
 >Re: ColorSync and printing -- Panther (2 of 2) (From: Chris Murphy <email@hidden>)
 >Re: ColorSync and printing -- Panther (2 of 2) (From: bruce fraser <email@hidden>)
 >Re: ColorSync and printing -- Panther (2 of 2) (From: Chris Murphy <email@hidden>)

  • Prev by Date: Re: untagged RGB data
  • Next by Date: Re: DDC control (WAS more printing woes...)
  • Previous by thread: Re: ColorSync and printing -- Panther (2 of 2)
  • Next by thread: Re: ColorSync and printing -- Panther (2 of 2)
  • Index(es):
    • Date
    • Thread