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

Re: Remote proofing


  • Subject: Re: Remote proofing
  • From: bruce fraser <email@hidden>
  • Date: Thu, 11 Mar 2004 12:45:09 -0800

At 9:17 PM +0100 3/11/04, Henrik Holmegaard wrote:
Leaving aside the strategic level and looking at the tactical level, it is not only the case that the printing industry is opposed to RGB. It is fair to say that the photographic industry is _also_ opposed to RGB.

Now why would that be?

It is desirable to not have CMYK but to RGB in order to achieve the most clean and crisp transparency flattening in the flattening module of a PostScript 3 interpreter.

Therefore, when Photoshop users send content to an InDesign user, they may send their own choice of RGB Working Space tagged content.

They may not send their own choice of CMYK Working Space tagged content but must agree to leave the conversion to a truly late binding solution.

Therefore, only the Perceptual conversion is secure as the ICC has not agreed on a 5th rendering intent for Relative Colorimetric with Black Point Compensation.

This rekindles the objection users of Photoshop 1 to Photoshop 4 have always voiced, and still voice, over Perceptual rendering in the ICC Specification.

No. The fundamental problem with late-binding workflows, and the reason many quality-conscious image creators reject them, is that it simply isn't rational to choose a rendering intent when the output is unknown. Rendering intents are fundamentally just different ways of handling the relationship between in-gamut and out-of-gamut colors. It makes no sense to pick one when the output gamut remains unknown.

Current implementations know nothing of image content, just of the spaces in which they reside, so if I work in ProPhoto RGB, perceptual rendering will always desaturate the image, even if the image contains no colors that are out of gamut for the current output process. If late binding is to become viable for quality work, we're going to need a great deal more intelligence in the CMM instead of trying to handle everything in the profile. At minimum, we'll need adaptive gamut-mapping that actually looks at the colors of the image, rather than simply trying to shoehorn source space A into destination space B.
--
email@hidden
_______________________________________________
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: Remote proofing
      • From: Henrik Holmegaard <email@hidden>
    • Re: Remote proofing
      • From: Doug Walker <email@hidden>
    • Re: Remote proofing
      • From: Henrik Holmegaard <email@hidden>
    • Re: Remote proofing
      • From: Henrik Holmegaard <email@hidden>
References: 
 >Re: Remote proofing (From: Henrik Holmegaard <email@hidden>)

  • Prev by Date: Re: Maximum Chroma vs. Maximum Gamut
  • Next by Date: RE: Maximum Chroma vs. Maximum Gamut
  • Previous by thread: Re: Remote proofing
  • Next by thread: Re: Remote proofing
  • Index(es):
    • Date
    • Thread