• 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 Architecture
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Colorsync Architecture


  • Subject: Re: Colorsync Architecture
  • From: John Fieber <email@hidden>
  • Date: Sat, 20 Dec 2003 16:48:04 -0500

On Dec 20, 2003, at 10:03 AM, Nick Wheeler wrote:

Printer drivers that ship with the printers might best be designed to not allow for any user intervention other than the typical media and resolution choices. What we have now is a complete fiasco.

I suppose a null setting is a good idea but if a better print driver is desired then there are professional packages out there to do the job: Colorburst, ImagePrint, Best, Pressready (rest in peace) etc come to mind. It's counterintuitive to ask these cheesy print drivers to do professional level work.

Maybe I'm reading this wrong, but it looks like between the idiot and the professional we have a gaping hole. This is where folks like slightly more advanced amateur photographers (eg. me) fit. Not being a "professional" this stuff is a big enough financial black hole as it is without having to fork over a professional sized wad of money to get decent color when I don't really need most of what a high end RIP offers. I just need:

1. A simple way to print a calibration target

2. A simple way to select a profile and rendering intent when printing from any application

3. A simple way for photoshop to take over color management in printing if I want it to

1 and 3 are generally possible now, but the user interface is a disaster that invites confusion errors even for users with a pretty solid grasp of color management. 2 is partly possible now but exceedingly clumsy. And finally, what triggered all this:

4. Web browsers that assume sRGB for untagged color data. (Is the interpretation of RGB values in stylesheets addressed anywhere? )

I've tried a number of third party applications that claim to be colorsync aware and they reliably screw up color when printing (but get screen display right). There are enough of these that there must be confusion among developers, not just users, about how ColorSync works in MacOS X printing. I conclude that it either doesn't really work or that Apple is failing to communicate how it works to developers (and users). Or more likely, some of both.

-john
_______________________________________________
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.

  • Follow-Ups:
    • Re: Colorsync Architecture
      • From: Nick Wheeler <email@hidden>
    • Re: Colorsync Architecture
      • From: Chris Murphy <email@hidden>
References: 
 >Colorsync Architecture (From: Nick Wheeler <email@hidden>)

  • Prev by Date: Re: untagged RGB data
  • Next by Date: Re: untagged RGB data
  • Previous by thread: Re: Colorsync Architecture
  • Next by thread: Re: Colorsync Architecture
  • Index(es):
    • Date
    • Thread