• 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: Why not double profile?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why not double profile?


  • Subject: Re: Why not double profile?
  • From: Henrik Holmegaard <email@hidden>
  • Date: Wed, 14 Mar 2001 08:52:32 +0100

Roberto wrote:

As for editing, more than once I've found profile editing programs ruin
the black generation or the ink limits. So my personal favorite method
for editing is editing the instrument values before building the profile.
The visual way to do this, very unorthodox, has been to make a TIFF image
of the Lab readings of the original chart (via Logo ColorLab). Then open
it in Photoshop, and place some Lab photos at the side. Then edit in
Photoshop, slightly, to get desired visual appearance (calibrated monitor
needed). Then crop the edited testchart, downsample it so that each patch
is only one pixel, and save as RAW. A linux shell line converts that raw
into tab delimited ascii values, which go to excel, and are saved into a
testchart ascii file.
That one is imported into PrintOpen, and the profile made. That way I
have a first-generation profile, concordant with PrintOpen's internal
model, but in fact edited.

They really do take their coffee strong and black in Peru -:).

--
------------------------------------------
Henrik Holmegaard, TechWrite
Stationay +45 3880 0721 - +45 3881 0721
Mobile +45 2178 3959
Toelloesevej 69, 2700 Broenshoej, Denmark
------------------------------------------


  • Prev by Date: Re: CMYK to Lab bug (part 1)
  • Next by Date: AW:colorsync-users digest, Vol 2 #216 - 18 msgs
  • Previous by thread: Re: Why not double profile?
  • Next by thread: Profile Mismatch Between PS 6 and PS 5.5 (Using Same ColorSpace)
  • Index(es):
    • Date
    • Thread