• 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: Who's right? I stopped trying to figure out
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Who's right? I stopped trying to figure out


  • Subject: Re: Who's right? I stopped trying to figure out
  • From: Bob Rushing <email@hidden>
  • Date: Sat, 05 Jun 2004 22:14:44 -0400

Wow. That makes sense now. I noticed that when I saved a print job as a PDF in the print dialog and then opened that PDF in PS, it indicated the Generic RGB profile. I didn't know where this was coming from or what was causing it. I bugged me because I was concerned that the Generic RGB gamut was different from or smaller than my working space in PS that I was using and that some of the colors were being changed, clipped or whatever. Humm . . . . so that's why preview behaves the way it does.

Chris Murphy wrote:


On Jun 5, 2004, at 5:00 AM, Bob Rushing wrote:

If I would guess as to what is causing the magenta cast, I would postulate that I know I'm converting my document into the printer space (my particular work flow) in PS, not in the printer driver. So I can only guess that this is why the magenta cast. Next, the magenta cast document gets sent to the printer driver already converted into the printer space. Since no color correction is set in the printer driver , it prints correctly. from what I gather, you can never turn off ColorSync so apparently it's always doing something and it's real easy to ColorSync a document twice.. Huh? It's just my guess. . . . .


Good guess. In the year 2004 you'd think applications, printer drivers and OS's could get along well and talk to each other properly but they don't. OS X is completely ignorant of the fact there are professional applications in the world that prematch data for output.

If things were smart it would be possible for Photoshop to tag the print job with the output profile you selected, and it converted the document with. The OS X could preview the document on-screen correctly. But today, if Adobe did this, OS X would treat this as an excuse to further color manage the job when you print as well, which would then get you less than good quality results. So Adobe doesn't tag the print job. Your image is converted for your 2200 but is tagged with Generic RGB (which is what OS X does to untagged data it receives from applications). Since it's a bogus tag, you get a bogus soft proof.


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.


References: 
 >Who's right? (From: roberto diego torrado <email@hidden>)
 >Re: Who's right? I stopped trying to figure out (From: Bob Rushing <email@hidden>)
 >Re: Who's right? I stopped trying to figure out (From: Chris Murphy <email@hidden>)

  • Prev by Date: Re: colorsync-users digest, Vol 3 #1380 - 11 msgs
  • Next by Date: Re: Who's right? I stopped trying to figure out
  • Previous by thread: Re: Who's right? I stopped trying to figure out
  • Next by thread: Re: Who's right? I stopped trying to figure out
  • Index(es):
    • Date
    • Thread