Re: The need for a substantial upgrade of ColorSync
Re: The need for a substantial upgrade of ColorSync
- Subject: Re: The need for a substantial upgrade of ColorSync
- From: Andrew Rodney <email@hidden>
- Date: Mon, 5 Apr 2010 16:49:28 -0600
On Apr 5, 2010, at 4:36 PM, Matt Beals wrote:
> So for purposes of printing color targets and getting measurment data, printing in general, things are still pretty screwed up and some sort of undesired conversion takes place causing problems.
Yes that’s a good summery but historically (say the last 5-6 years), there have been a number of printing issues that had nothing to do with printing untagged targets, that’s just the latest one and of course a bug that this community would zero in on. And the issues appear to be a combo of application, OS and print drivers. You can for example, find some fairly modern Epson printers that do not exhibit the untagged target issue with the same OS version and same version of Photoshop, while others do exhibit this bug. That would lead you to point a finger at Epson. But using the same combo, you can print the same untagged target out of Preview and it prints correctly so that makes it harder to pin this one bug on the Epson driver. Basically there is so much tiny code fixes here and there, with various companies changing the goal posts in the middle of the game, you never know when either an application, OS or driver gets updated what may break these days. There have been at least 3 or 4 other printing bugs I can think of over the last couple years. One where using the Epson Advanced B&W, you had to set the document to Adobe RGB (1998), one where you’d send a file to the printer and it would just disappear from the queue and never print. There was a bug awhile back where differing applications would print differently when you sent the same data to the same driver (many prints coming out very dark). Its hard to keep track these days.
Placing absolute blame on one company isn’t going to wash either. We need the major players to all sit down and honestly iron out all the details and as importantly, stick with the plan instead of fixing something in one dot release, only to have it break in another when someone else in the chain updates their code. In the old days, we complained about how complicated it was to print (all the stuff you had to set to get the print right). Today its harder because you still have to set all this crap (media type, profile, app vs. printer CMS, driver settings) but worse, doing it all correctly doesn’t guarantee the print will come out correctly thanks to all the bugs and patches and bugs compounding upon themselves.
Now one could say, in the old days, when we had those yummy ColorSync breakfasts, many of the players would get together and at least talk about these issues. I would hope that behind closed doors, this is still happening, but the results for end users doesn’t appear to prove this is so.
Andrew Rodney
http://www.digitaldog.net/ _______________________________________________
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