• 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: Graeme Gill <email@hidden>
  • Date: Fri, 12 Jun 2009 09:12:02 +1000

Marco Ugolini wrote:
Steve Upton wrote:
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".

Possibly, though that sort of thing is probably quite rare. I have not run into any instances so far in which actual output profiles used in my actual work exhibited this sort of behavior. The anomalies I pointed out earlier were found with profiles that I did *not* have to use for my work.

Hmm. The indications I get are quite the opposite, that most profiles do a noticeably sub-optimal job of perceptual mapping, judging by the difference between using the "dumb" link and using a purpose built gamut mapping.

Graeme Gill.
_______________________________________________
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


  • Follow-Ups:
    • RE: BCP or no BCP to epson without rip
      • From: Roger <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