[argyllcms] Newbie help?

I've got  a GretagMacbeth Eye-One  Design that I'd  really, really
like to use with Argyll--which is exactly what I've spent the past
few days trying to do.

First, I've read  much of the documentation and  searched the list
archives  for  relevant  stuff. Yes,  I know  that  the  i1  isn't
directly supported  by Argyll and  that there aren't any  plans to
add  such  support  in  the  future. Frankly,  if  it  weren't  so
(relatively) inexpensive  and I not  so poor, I would  have gotten
some other  instrument that /is/ supported  and whose manufacturer
is more generous with documentation. But...I'm poor.

I  learned  the  hard  way   that  MeasureTool  doesn't  like  the
re-ordered  (randomized) ti2  files created  by default,  and that
my  ham-fisted  attempts  at  re-re-ordering  them  simply  didn't
work. Using a  non-randomized chart,  I was able  to read  all the
patches, save the file, use logo2cgats to create the ti3 file, and
then generate  a profile. (I  fed MeasureTool a  ti2 file  with an
appropriate  value  for  ``LGOROWLENGTH''  in  it  but  which  was
otherwise unmodified.) Unfortunately,  the profile wasn't  even in
the ballpark--it looked like somebody scribbled with the pencil in
a  curves  adjustment  in  Photoshop. Granted,  this  was  with  a
smallish chart  (only 64 patches,  one paper white), but  I'm sure
Argyll can't be /that/ bad. It looked just as bad as the 900-patch
chart I did early on with all the patch identifiers scrambled from
my attempts to re-re-re-order them.

I've also tried to use  ColorPort, and quickly discovered that the
output file  needs to be  massaged rather extensively. I  tried to
compile David  Gangola's cpxchg, but  all I  found was the  one he
posted to the list...and that needs a couple #include files that I
didn't  find. ColorPort ``feels''  like the  superior tool  of the
two, but  I'd almost put  up with hand-transcribing  readouts from
Eye-One Share at this point, if that's what it took to get started
on the right path.

I have a very strong  hunch I'm either missing something important
and obvious or trying to re-invent the wheel. Can anybody point me
in the  right direction? I'd  certainly welcome  some hand-holding
about now, but  I should be able to  get by on my own  with just a
couple nudges or so. ``Hack a Perl  script to scale the ti2 values
to 0-255  and then  extract fields such-and-such  from ColorPort's
output'' would even be enough...I'd just rather not chase down too
many more dead ends if I don't have to....

Thanks,

b&

Other related posts: