[argyllcms] Re: Newbie help?

Ben Goren wrote: 
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.


The trouble with the Eye1 is that either

        1) the USB interface needs to be reverse engineered so
           that free drivers can be written
or
        2) Gretag needs to make the USB protocol documentation
           available to developers
or
        3) Gretag need to make free (as in LGPL free) drivers
           available for it for all platforms (all flavours of
           Linux/Unix, OSX and MSWindows)
or
        4) A commercial version of Argyll could use the
           commercial (closed source) drivers from Gretag,
           but only on MSWindows or OSX.

I don't have access to an Eye1 to do 1), and don't feel like
spending the money at this time to do so, unless I'm doing 4).

If someone with an Eye1 feels like doing 1) [And decides that
Gretags licensing conditions don't make it impossible, or they
live in a country where the local laws override any such licensing
conditions], then I'm happy to try writing a driver based on the
resulting documentation.

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.


What did profile (or profcheck) report as the fit error ? This is
usually the givaway as to whether the patches got mixed up.

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.


If someone would send me a couple of colorport files, then I'd be
happy to see if logo2cgats can be modified to accept those files
as well. It doesn't sound hard.

Graeme Gill.

Other related posts: