ArgyllCMS 875-patch printer profile with i1Pro 2

[roncromberge]

Hello all,

Almost a year later since the last post in this thread.
And i also run into a strange problem with profile making with the i1 pro2 and Argyll.

It seems to relate with the separators?
I can make my own target and print it. (just a test one).

But when i try to read the printed sheet.
Initial starts ok. Calibrating...
The warning message about GretagMacbeth i1 Pro and Xrite i1 Pro2 (It's a efi es 2000)

But what ever i do. I get continue the message about a mismatch of read patches?
When i compare Your ti1 and ti2 files, Despite the diverent no of patches all seems to match?

I have downloaded your 875 targets Both the one with the seperators and the one without them.

Unfortunately, 1 cartridge is total empty now. So tomorrow i can print both an check if i can read the patches now?

One question can and will you the give the used commands and parameters so i can check is they are on the important ones equal or conform the patch divergences.

btw: i use Linux with Turboprint and Argyll version 3.3.0 And the i1 (efi | es-2000) works flawlessly with Argyll Pro 2.0

Found this in my history
targen -v -d2 -G -g16 -f420 i1-01
printtarg -v -i i1 -R1 -T300 -p A4 i1-01
sudo chartread -v -H i1-01
sudo chartread -v -H -T0.4 i1-01


Best Regards,

Newby Ron.

Hello Fixed my problem. i was to quick. I read at some other place that i have to wait 2-3 seconds after push the button. And also wait 2-3 seconds after the line read is finished. And probable even slower moving the reader. even slower than de colormunki.

So now waiting for my printer cartridge and tomorrow test print and the 875 target processing.

 

[Graeme Gill]

The warning message about GretagMacbeth i1 Pro and Xrite i1 Pro2 (It's a efi es 2000)

Exactly what message ?

But what ever i do. I get continue the message about a mismatch of read patches?

Exactly what messages ?

Note that if you don't have a reasonably accurate profile to feed into targen -c, then
expected patch values are much more likely to not be close to the measured patches, and
you are much more likely to get warning messages.

But bottom line is what is the self fit error reported when making a profile ?
This is the best indicator of whether the measured patches are coherent.

 

[roncromberge]

Exactly what message ?

Exactly what messages ?

Note that if you don't have a reasonably accurate profile to feed into targen -c, then
expected patch values are much more likely to not be close to the measured patches, and
you are much more likely to get warning messages.

But bottom line is what is the self fit error reported when making a profile ?
This is the best indicator of whether the measured patches are coherent.

Hello Graeme,

The first one is just the message that the default scanner is the gretag… and it found a i1pro2. Nothing to worry about.

The second one solved itself. I was to hasty and started the measurement to soon and ended to soon. On my Linux machine I don’t get the audible sign. Now I wait at least 2 to 3 seconds to start and end.