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: email@hidden
- Date: Wed, 8 Nov 2000 19:23:00 EST
In a message dated 11/8/00 6:02:11 PM, email@hidden writes:
>
I guess I wasn't very clear in my information and question.
Clear enough for Bruce and I to answer in the same vein... but thats
apparently not what you were after...
Yes, QuickDraw
>
hands us the data in RGB, because it's all it knows. But the printer driver
>
also gets handed the profile that goes with the source image. So, coming
>
into the print driver is a nice RGB print job complete with a source
>
profile.
>
>
So, why don't drivers use a CMYK profile to convert directly from source
>
RGB
>
to printer CMYK values, instead of converting from source RGB to printer
>
RGB
>
to printer CMYK?
Does it much matter if there is an extra RGB space in there first? It
simplifies life for the driver developers.
>
>
Actually, I guess what I'm really wanting to know is: Is there a good reason
>
not to do that?
It seems what you are really after is CMYK profile application after
conversion to the ink colors. This problematic, as at this point the
screening or dithering has occured, and the black generation and ink limits
have been set. To run a CMYK to CMYK conversion then would be somewhere
between problematic and catastrophic. If you were writing your own driver,
and could allow profiles to be used for the actual RGB>CMYK conversion at
this point instead of the typical fixed conversion, that would be less
difficult, but the profile used for this would need to be pretty savvy about
all the requirements of the printer.
C. David Tobie
Design Cooperative
email@hidden