Richard Kirk
2014-08-27 12:44:34 UTC
Hi.
My company uses a number of devices that are not supported as displays on the windowing system, such as AJA thunderbolt drives, KONA boards; and also devices such as video colour convertors that are capable of putting up a full-screen test patch. We can use ICC profiles as calibrations.
It would be good if we could use the Argyll utilities with some 'dispwin' setting that allowed us to pass the calibration RGB to some other application that talked to the device. For example, if we had...
dispwin -f <file>
...then instead of displaying each colour patch, it would write the RGB values to <file> as a string of floating-point numbers, and then blocked until <file> disappears.
The other application should poll for <file>, read three numbers, and put up a test patch. When the test patch is up, it should delete <file> to signal to 'dispwin' that the patch has been displayed. We could add a 'quit' signal to close the application when Argyll is done.
This may clumsy, but we are not wanting to pass a lot of information, and this would allow us to set up a handshake between Argyll CMS and the display tool using only stdlib calls, which should work on all platforms.
Is this something that other people might want? Can you think of a better way of doing this?
Cheers.
Richard Kirk
---
FilmLight Ltd, Artists House, 14-15 Manette Street, London W1D 4AP
Tel: +44 (0)20 7292 0400 Fax: +44 (0)20 7292 0401
My company uses a number of devices that are not supported as displays on the windowing system, such as AJA thunderbolt drives, KONA boards; and also devices such as video colour convertors that are capable of putting up a full-screen test patch. We can use ICC profiles as calibrations.
It would be good if we could use the Argyll utilities with some 'dispwin' setting that allowed us to pass the calibration RGB to some other application that talked to the device. For example, if we had...
dispwin -f <file>
...then instead of displaying each colour patch, it would write the RGB values to <file> as a string of floating-point numbers, and then blocked until <file> disappears.
The other application should poll for <file>, read three numbers, and put up a test patch. When the test patch is up, it should delete <file> to signal to 'dispwin' that the patch has been displayed. We could add a 'quit' signal to close the application when Argyll is done.
This may clumsy, but we are not wanting to pass a lot of information, and this would allow us to set up a handshake between Argyll CMS and the display tool using only stdlib calls, which should work on all platforms.
Is this something that other people might want? Can you think of a better way of doing this?
Cheers.
Richard Kirk
---
FilmLight Ltd, Artists House, 14-15 Manette Street, London W1D 4AP
Tel: +44 (0)20 7292 0400 Fax: +44 (0)20 7292 0401