[Openicc] Printing targets: App or driver ? Profiling RGB or CMYK
rlk at alum.mit.edu
Wed May 18 17:49:37 PDT 2011
On Wed, 18 May 2011 18:40:37 -0600, Chris Murphy wrote:
> On May 18, 2011, at 6:18 PM, Robert Krawitz wrote:
>> "DeviceN calibration burnt in" that the driver cannot read back makes
>> no sense *whatsoever*, since the printer isn't receiving data in any
>> kind of color space, but rather a complete specification of what drops
>> are printed.
> Ahhh OK. So then the OEM driver knows how to access this info from
> the printer each time it produces a print.
*IF* it's even stored in the printer, which we don't actually know.
> But in any even ColourBase is UK only, not available in the U.S.
Which makes me suspect that whatever it is isn't stored in the printer
at all, but on the host.
>> * Micro-adjustments to the actual drop size. This is the most
>> intriguing possibility, and would be more difficult to test. I'd
>> probably have to look at the initialization sequences to two
>> printers (in addition to bidirectional communication) to figure this
>> one out.
> But it still seems like such micro-adjustments would be available to
> any ESC/P-2 stream, not just from the OEM driver.
Only if it's stored in non-volatile memory on the printer. If
whatever it is (let's assume for sake of argument that it's
microadjustments to the drop size) is stored on the host and
downloaded to the printer each time, then that wouldn't necessarily be
More information about the openicc