• 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: BCP or no BCP to epson without rip
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: BCP or no BCP to epson without rip


  • Subject: Re: BCP or no BCP to epson without rip
  • From: Steve Upton <email@hidden>
  • Date: Thu, 11 Jun 2009 04:23:12 -0700

At 10:58 PM -0700 6/10/09, Marco Ugolini wrote:
>In a message dated 6/10/09 5:13 PM, Graeme Gill wrote:
>
>> because the destination profile doesn't know what the source profiles
>> black point is.
>
>I think you're being a bit disingenuous here, Graeme. The Perceptual
>conversion *procedure* first maps source black to PCS black, then PCS black
>to destination black. While strictly speaking the two profiles never "see"
>each other directly, the *procedure* certainly knows how to go about it.

Not to jump in between you two but. I think Graeme's point is that your description is more a matter of convention rather than standard or guarantee.

So many profiles can work together because their creators followed the same convention but there is certainly the possibility that a pair of profiles will "mismatch" and BPC will be required to "fill in the blanks".

Steve

--

 _______________________________________________
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: 
 >Re: BCP or no BCP to epson without rip (From: Marco Ugolini <email@hidden>)

  • Prev by Date: Re: BCP or no BCP to epson without rip
  • Next by Date: Re: BCP or no BCP to epson without rip
  • Previous by thread: Re: BCP or no BCP to epson without rip
  • Next by thread: Re: BCP or no BCP to epson without rip
  • Index(es):
    • Date
    • Thread