• 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: using embedded vs converting to profile at final output
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: using embedded vs converting to profile at final output


  • Subject: RE: using embedded vs converting to profile at final output
  • From: "Eric Adloff" <email@hidden>
  • Date: Thu, 21 Oct 2004 19:29:21 -0400
  • Thread-topic: Colorsync-users Digest, Vol 1, Issue 44

Recently, I had to figure out how to more closely match a customer's Epson for color critical jobs with a profile for a device that doesn't exist any more in either workflow; however, the customer is still using it in their proofing sys. I may have misunderstood, but I thought any incoming files should be converted to our press profile prior to ripping, but I obtained much better results by ripping it with their profile.

My question is, should the press profile only be used in a prepress environment only for soft proofing, or should it be used to convert all files prior to ripping and plating?



<<winmail.dat>>

 _______________________________________________
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: using embedded vs converting to profile at final output
      • From: Henk Gianotten <email@hidden>
    • Re: using embedded vs converting to profile at final output
      • From: Roger Breton <email@hidden>
  • Prev by Date: Further color education & books
  • Next by Date: Re: Kodak is back in the ICC game?
  • Previous by thread: Re: Further color education & books
  • Next by thread: Re: using embedded vs converting to profile at final output
  • Index(es):
    • Date
    • Thread