Neil Woodall wrote:
Hi,
I’m trying to put together a system the allows a fairly automated way of
characterizing
a display. I put together a script to use spotread to read the display
continuously
while a video sample is playing, but it’s not designed to work at the maximum
speed of
the instrument (I say this by comparing it to how fast display read works on
the same
pattern set).
display
read requires a connection to the device, so if we want to characterize
something that
can’t connect to displayread (eg an iPhone) its not really possible...using
the
webserver doesn’t work because it sees that as an sRGB file for device
characterization
you want to send P3 or rec2020 colorspace.
chartread requires a ti2 file and it’s not
clear how you would use the output to generate a ccss file or whether it’s
compatible
anyway.
What would be useful is the ability to use the scanning type functionality
that is in
chart read, but with a ti1 file instead of ti2 file.
Yes, DisplayCal has this functionality, but they are simply using spotread
and whenever
the i1Pro2 returns any sort of error, it simply stops. It would be better for
it to
continue and for the user to make the pattern slow enough that you can handle
at least
one error response.