Why don't drivers use a CMYK profile?
Why don't drivers use a CMYK profile?
- Subject: Why don't drivers use a CMYK profile?
- From: Dan Caldwell <email@hidden>
- Date: Mon, 13 Nov 2000 13:43:57 -0800
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).
I see what you are saying Chris. If the driver translated using ICC
profiles from Source to a machine language CMYK/CcMmYK then they
could call on ColorSync to do that. The problem with this solution is
the profile would have to be supplied by the printer manufacturer as
we have no way of sending a CMYK profiling target to the printer as
CMYK or 6/color and this would not be much of a step forward over the
current internal transformation.
Dan
--
****************************
http://www.profilecity.com
Dan Caldwell
ProfileCity Manager
ProfileCity.com LLC
E-mail email@hidden
Your Key to Great Color!
****************************