Peter Karp wrote:
tools). This would also be useful to allow laboratory instruments (PR-650, CS-2000 and the like) to be used for the calibration of the display. Currently it's not that easy to test if such a device will yield "better" (whatever that means and must be defined before hand) calibration results then a desktop device.
Roger has certainly suggested this too.
A "dummy" demo device just generating some more or less meaningful typical numbers is useful to test the application itself.
It already has this. If you use -dfake, it will either use an internal fake device response, or read the device response from the file "fake.icm"/"fake.icc" if present. [ It's not documented because it's for release testing. ]
I'm not sure if you suggest to enter each color one after the other? If no interative calibration process is used then a list of measurement data will be sufficient.
If you already have a list of measurement data, then you can massage it into .ti3 format and bypass dispread completely :-) Graeme Gill.