ArgyllCMS V1.6.2 has been released.

[Graeme Gill]

ArgyllCMS V1.6.2 is primarily a bug fix release, although one feature has been added.

Some of the changes are:

Added "dark region emphasis" -V parameter to targen and colprof, in an
attempt to improve the accuracy of display profiles intended for use with
video. This should improve the subsequent black point accuracy of the profile.
See <http://www.argyllcms.com/doc/targen.html#V>

Fixed bug and tweaked dispcal black point optimisation to err on the black side.

Changed i1d3 driver to be more forgiving of EEProm checksum calculation, so
that it works with the latest release "A-02" rev. i1 display pro & colormunki
display instruments.

Fixed a race condition bug in OS X HID driver, curing the problems in
communicating with the ColorHug on OS X. The ColorHug is now fully supported
in ArgyllCMS.

Fixed major bug in illumread - result was being corrupted.

Fix bug in -H flag in ccxxmake, chartread, dispcal, dispread, illumread
& spotread so that it works once again.

Graeme Gill.

[Pascal de Bruijn]

Post by Graeme Gill
ArgyllCMS V1.6.2 is primarily a bug fix release, although one feature has been added.
Added "dark region emphasis" -V parameter to targen and colprof, in an
attempt to improve the accuracy of display profiles intended for use with
video. This should improve the subsequent black point accuracy of the profile.
See <http://www.argyllcms.com/doc/targen.html#V>
Fixed bug and tweaked dispcal black point optimisation to err on the black side.
Changed i1d3 driver to be more forgiving of EEProm checksum calculation, so
that it works with the latest release "A-02" rev. i1 display pro & colormunki
display instruments.
Fixed a race condition bug in OS X HID driver, curing the problems in
communicating with the ColorHug on OS X. The ColorHug is now fully supported
in ArgyllCMS.
Fixed major bug in illumread - result was being corrupted.
Fix bug in -H flag in ccxxmake, chartread, dispcal, dispread, illumread
& spotread so that it works once again.

I did some experimental package builds for Ubuntu users here:

https://launchpad.net/~pmjdebruijn/+archive/argyll-testing

These packages are built using Argyll's own unmodified build system without
any patches.

Regards,
Pascal de Bruijn

[BC Rider]

I understand, generally speaking, a slower scan of the strip is better. But does Chartread have a MINIMUM speed requirement? Any restrictions? When does "slower" become "too slow"? Designing my automated strip scanning jig! (For Colormunki) Thanks.

[Graeme Gill]

Post by BC Rider
I understand, generally speaking, a slower scan of the strip is better. But does
Chartread have a MINIMUM speed requirement? Any restrictions? When does "slower"
become "too slow"? Designing my automated strip scanning jig! (For Colormunki)

Hi,
the only restriction (I think) is that there is a maximum buffer size/time
of 20 seconds set in i1pro/munki_imp.c. This is intended to allow for longer
than A4 strips, and should be pretty generous. It's possible that too slow a scan
of a short strip may cause the patch transitions to be too gradual and not be detected.

In practice you should be able to simply try it and see how slow you can go before
it starts to become unreliable at detecting the patches, while remaining within
the 20 seconds.

Graeme Gill.