Re: Am I getting closer to understanding color management?




"Loren Amelang" <loren@xxxxxxxxxxx> wrote in message
news:79ma835vs02jm7g3os44ou4f4h4n1arieb@xxxxxxxxxx
On Fri, 29 Jun 2007 01:29:29 GMT, "Roy G"
<roy.gibson1@xxxxxxxxxxxxxxxx> wrote:


"Loren Amelang" <loren@xxxxxxxxxxx> wrote in message
news:4fi8839tbpmqcgdn8r7blbvt2eovt0m4cc@xxxxxxxxxx
Just used a "Spyder2" on my monitor. At the end of the guided process,
it shows the "PDI Test Image" and lets you toggle between "color
managed" and "not color managed". In "color managed" some yellows and
.Snip

Hi.

You seem to be getting confused between the different Gamuts of sRGB /
Adobe
RGB,

My confusion started with the Spyder app showing me a color managed
view of an AdobeRGB file compared to a non-managed view, and me
thinking the change was supposed to be due to profiling.

and the purpose of Monitor profiling.

The purpose of Monitor Calibration, (which is the first part of the
process
when you adjust the Monitor Controls) and of Monitor Profiling, (which is
automagically done by the Spyder), is to get your monitor to show the
Image
Colours as they would be shown on any other Calibrated and Profiled
Monitor.
That is its SOLE purpose.

If you were very lucky, you could have a Monitor which showed no
difference
after Calibration and Profiling. It just naturally was correct, or had
been
accurately calibrated and profiled at the factory. Until you used a
Spyder,
you would not know that.

Seems to be the case here.

The Calibration part will affect all applications, simply because your
Monitor Controls are now permanently set that way.

The Spyder Monitor Profile, and even the Generic Profile, will only be
used
by C.M. aware applications.

I disagree. The monitor profile contains a color Look-Up-Table that
gets loaded into the graphics card at startup, when the Spyder logo
appears on the screen for a moment. Similar to how Adobe Gamma can
load a LUT at startup. On a good monitor, you don't see much change,
but on my notebook (which I also Spydered) the change in the Windows
display is quite obvious.

When you set Soft proof in PS to "Monitor RGB" you are effectively setting
it to "No C.M.".(This is not an exact answer, which is why I said
effectively)

Agreed. I was getting caught up in the various ways that is not
exact...

Soft Proof is for seeing how your Prints should look after Printing using
a
Printer Profile.

PS will use your Spyder Monitor Profile only to adjust the colours shown
on
the screen, and will only do so if that Profile is set as Default in
Display
Properties.

But I can also select that profile, along with many others, as an
option in proof setup. I guess what I'm trying to understand are the
interactions involved in "proofing" for using various monitors as the
target output device.

I guess accurate color on the web is a lost cause, but being able to
see how far off you will be on a typical properly configured Mac or PC
seems useful.

Loren

Hi again.

I suspect that you are correct about the Spyder Profile always being used by
the Graphic Card, but I am not a Computer Techie, so I am not sure.

The reason that the Spyder showed an Adobe RGB Image, is because most home
printers using Inkjets opt to use adobe RGB as their Working Space Profile.

Accurate colour on the Web is not a lost cause, if the Web users are using
Calibrated and Profiled Monitors. If their Monitors are not Calibrated then
the colours might well be very far off, just as much off as their own image
colours will be, but that is their problem.

The fact that sRGB is used for Web Images does not mean that the colours
will be off, it just means that the Gamut will be limited.

Proof is not for anticipating how colours will appear on different Monitors.

If those Monitors have been Calibrated and Profiled then the colours will be
exactly the same as on your own Calibrated and Profiled Monitor. That is why
Calibration and Profiling is used, to eliminate variations between Monitors.

Your Spyder Monitor Profile is specific to your own Monitor, and is designed
to rectify any incorrect rendition on your particular Monitor.

If you are using a fairly new Mac Display, then according to the Mac Fans,
it should not have needed Calibration and Profiling, because that was done
at the Factory. However as it gets older, its colours will slip and it will
then need re-doing.

The only reason for using Monitor RGB in Proof, is so that you can estimate
how your image MIGHT look for the Non Calibrated and Profiled Web users.
BUT you can not know how far off their colours will be, so it is anything
but accurate. The majority of them will not even be working at 6500K.

Just have a look at the working monitors on show in any big Computer store,
and notice the Colour variations between them.

The real reason for Proof is, as I have already said, for anticipating how
your Image will look when Printed.

You set Proof to use your Printer and Paper Profile, or your Printing House
Profile, and you can then see how much it changes from the On-Screen
Display. It is a bit like comparing a projected Slide with a Print made from
that Slide, they will look entirely different.

I hope this helps a bit more.

Roy G


.



Relevant Pages