• 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: Default and factory profiles in OSX Colorsync Utility
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Default and factory profiles in OSX Colorsync Utility


  • Subject: Re: Default and factory profiles in OSX Colorsync Utility
  • From: Chris Murphy <email@hidden>
  • Date: Mon, 27 Dec 2004 12:50:29 -0700


On Dec 22, 2004, at 12:47 AM, colorcanuck wrote:


I would be very interested in any information that allows one (me) to change the Factory Profile to a more realistic default.

That's up to the driver, I believe. So you'd probably have to learn how to hack a driver. It might be as simple as going through the PM and finding a plist of some sort, it might be in there as just plain text.


Has anyone else out there had devices register no information under the ColorSync Utility? Similar situations?

Yes and they don't always get used. There are so many drivers out there that do the wrong thing that without considerable testing, I wouldn't trust such a workflow with a 10 foot pole. Much of ColorSync is untrustworthy because somehow either the driver developers are reading Apple's documentation wrong and building crappy drivers, or Apple's documentation is the problem. Which it is, or how much of a combination of the two possibilities, I don't know. But the end result is we have faith based color management on Mac OS.



I'm innocently printing away under OSX 2.8 (with no rip) and I can't help but notice that everything going out the CUPs printing pipeline ends up in Generic RGB, so I have to convert everything to Generic before sending it down the pipe.

Do I really have to convert everything to Generic RGB to get it through the CUPS print pipeline?

I'm a Rip/postscript guy so please excuse my ignorance, but wasn't this issue raised a while back. Can't seem to find it in the Archives.

RGB data going to a PostScript device remains RGB, but CSA's are included in the PostScript stream. The CSA's are based on the source profiles for objects in the document. There could be numerous sources, a single source, or none. If there is no source profile defined by the application, then the OS assumes Generic RGB. If you don't want to convert everything to Generic RGB, your application needs to be capable of informing the OS of something else to use.


In OS 10.2 there is no other option. In OS 10.3, you can choose to do OS level color management instead of in-printer color management (PostScript color management). The option is found in the ColorSync portion of all print dialogs.


Chris Murphy Color Remedies (TM) www.colorremedies.com/realworldcolor ------------------------------------------------------------- Co-author "Real World Color Management, 2nd Edition" Published by PeachPit Press (ISBN 0-321-26722-2)

_______________________________________________
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


References: 
 >Default and factory profiles in OSX Colorsync Utility (From: colorcanuck <email@hidden>)

  • Prev by Date: Re: Printing ECI2002 target from InDesign
  • Next by Date: Re: ICC V4 Profiles Needed
  • Previous by thread: Default and factory profiles in OSX Colorsync Utility
  • Next by thread: nuts and bolts fixed! Darren wins the troubleshooting session!
  • Index(es):
    • Date
    • Thread