Re: [Openicc] [Gimp-print-devel] [Printing-architecture] Colour
Re: [Openicc] [Gimp-print-devel] [Printing-architecture] Colour
- Subject: Re: [Openicc] [Gimp-print-devel] [Printing-architecture] Colour
- From: Doyle Yoder <email@hidden>
- Date: Sun, 15 Nov 2009 14:28:45 -0500
On Nov 15, 2009, at 10:11 AM, Paul Foerts wrote:
> All this is an extremely simplified idea of how future systems could be
> designed:
> Auto (one button) for the less sophisticated user and manual modes which are
> generally simple to understand and use but can extend to custom CMYK and
> profile editing...
As I see it this is exactly why we are in the trouble we are in right now. Instead of using the workflow idea of Apple's old printing path where one had complete control of all printer driver settings, the new printing path tries to make things default in the driver. As it is now implemented (in the new path) when application manages color is selected if the driver behaves correctly it should turn off colormanagement. But when something is wrong in the whole printflow it defaults to ColorSync. Witness LR3 Beta compared to LR2. Somebody screwed up there. But release LR3 with that behavior and watch the blame game heat up again.
As for me, give me all the control back and quit trying to idiot proof this. If people want to get correct prints let them learn how to do it. As it is now we are all chasing a moving target and with every new release it needs tested on none main work partitions to see if some new screw up has been implemented. I don't believe that a lot of software designers really understand CM and that also contributes to this problem. For example a canned profile if linked to the media setting in colorsync may print just fine when chosen in the application even though it is double profiling, but of course print correcly because it is doing it with the same profile. But just try that with a custom profile. If people don't realize what is going on they start chasing all kinds of ideas which is what these forums are mostly filed with.
Bottom line is if one little thing in this forced workflow is not talking properly with the other then double profiling occurs. A perfect example of this is the LR3 Beta release compared with LR 2 and PSCS4. Blame who you want but in this scenario only Abode changed things.
Doyle
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden