Re: Why don't drivers use a CMYK profile?
Re: Why don't drivers use a CMYK profile?
- Subject: Re: Why don't drivers use a CMYK profile?
- From: Chris Murphy <email@hidden>
- Date: Mon, 13 Nov 2000 12:14:37 -0700
>
No Chris, the reason is if the driver called ColorSync to make the
>
conversion the resulting file could not be sent to the printer as
>
QuickDraw can only send RGB (or three channel) data from the OS.
Dan you're missing where the point of conversion would be taking place.
Once the RGB data in QuickDraw is given to the printer driver, the
printer driver converts that data from RGB to CMYK (or CcMmYK depending
on the printer) using a built in table and screening algorithm. Then CMYK
or CcMmYK data is sent in printer specific language to the printer.
The original poster is wondering why the RGB to CMYK conversion IN THE
DRIVER can't be done by ColorSync. And I suspect the reason has to do
with the proprietary nature of screening algorithms being tied to
whatever RGB to CMYK/CcMmYK conversion is needed.
The location of conversion I'm referring to has nothing to do with
QuickDraw because it comes at the QuickDraw RIP stage by the driver. I
know that QuickDraw only supports three channel color spaces (and most
applications only support creating RGB QuickDraw streams).
Chris Murphy