[Openicc] Printing targets: App or driver ? Profiling RGB or CMYK
edmundronald at gmail.com
Wed May 18 07:14:43 PDT 2011
my feeling is that whatever calibration there is is stored on the
printer itself, i dont think the driver gets any info back from
downstream. Also, Epson drivers can do AdobeRgb, i think they have
precomputed sRgb and AdobeRgb to DeviceN links, and the printer has
DeviceN calibration burnt in; that's my guess but then what do I know?
On 5/18/11, Robert Krawitz <rlk at alum.mit.edu> wrote:
> On Tue, 17 May 2011 20:24:14 -0600, Chris Murphy wrote:
>> On May 17, 2011, at 8:09 PM, Chris Murphy wrote:
>>> Anyway, I have a 3880 here on the network and can either put it on
>>> the router DMZ if you want; or can take some pointers on what files
>>> to print, and how to configure tcpdump to capture Epson driver vs
>>> 3rd party RIP so you're getting relevant info.
>> Also have multiple 7900's at another location. Using two it would be
>> possible to compare RGB streams going to the two 7900's, compared to
>> the two CMYK(deviceN probably) streams going to those same two
> We need to have the same RGB streams input to each printer. Otherwise
> the comparison is useless.
>> Does Epson's Mac OS/Windows driver itself converts to deviceN on the
>> host computer? Or is it possible the RGB path to the printer is how
>> this calibration data gets used by the native driver, and the
>> deviceN path doesn't?
> I would be very surprised if the RGB path to the printer (which to the
> best of my knowledge is sRGB), if it even exists on this device, is
> used, simply because sRGB is too limiting.
> openicc mailing list
> openicc at lists.freedesktop.org
More information about the openicc