Re: Goodbye ICC, here come Microsoft !
Re: Goodbye ICC, here come Microsoft !
- Subject: Re: Goodbye ICC, here come Microsoft !
- From: Erik Koldenhof <email@hidden>
- Date: Sat, 17 Sep 2005 21:51:13 +0200
Hey all,
I just had the chance to read the whole doc from MS and more or less
follow this ongoing discussion.
Here are my two cents:
I agree with Jan-Peter on the technical benefits that WCM could bring
us, the endusers.
I won't go in to the marketing talk that is weaved throughout the MS
doc, as it also discusses true issues with current ICC specs as well.
But, let's face it: ICC brought us more then 90% in WYSIWYG, and
Apple clearly did a great job in implementing ICC technology from day
1 on.
I did not see such a OS level of ICC implementation on the other
side. So, in my humble opinion, the credit still goes to the ICC and
Apple for their first 10+ years.
It is not more than logical that a new vision on color engines,
primairly adresses the 'issues' found in it's counterpart.
Just take a look at Adobe's Unique Selling Points for InDesign v1
some years ago (OK, they were right also, but it took some time to
mature)...
The role of ColorSync is (unfortunately) NOT for the real highend
endusers, but more for those who want to have some nice way of
dealing with colors.
The ColorSync implementation might not have been as transparent to us
all, but it does a great job (< 10.4), even in combination with
Adobe's ACE.
Back to the ICC once more: It's my believe that most of the so called
'color errors' that we might find today, are based on implementation
errors by the OS/application software developers on one hand, and
enduser errors in settings on the other. Not the ICC spec itself.
Most endusers who are experiencing flaws in color appeareance will
normally not think about that, and just state that 'ICC
colormanagement is not working' in general.
The MS document discusses transparent workflows with optimum color
results on one side,
and at the same time applauses for nifty stuff like the additional
rendering plugins that developers can add to the workflow (which will
change the color appearance of your image).
If you don't use the same rendering settings (and possible additional
plugins) on two workstations, the result migth be the same when using
two different rendering intents today on those same workstations
working with ICC.
But, let's try to implement it all. Are all apps going to have native
WCM support from day 1?
Will WCM in pratice solve everything it says it does? How about
setting prefs for all those tiny details in WCM at an enduser level?
Will those be 'transparent' and understandable for the normal enduser?
I'm not sure, I would like to see it first...
Is ICC colormanagement really that bad? Did it never enhance our
workflows by hundreds of procents?
Ok, Apple's MacOS 10.4 'Tiger' is one that we would rather forget
(for it's ICC support that is (or isn't)),
but I would like to see MS' WCM in action first...
Erik Koldenhof
_______________________________________________
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