icc vs icm

  • Thread starter Thread starter Guillaume Dargaud
  • Start date Start date
G

Guillaume Dargaud

What's the difference between .icc and .icm color profile files ?

Vuescan wants icc files but the software I'm currently experimenting with to
do color calibration produces icm files...

Thanks for any info.
 
What's the difference between .icc and .icm color profile files ?

Vuescan wants icc files but the software I'm currently experimenting with to
do color calibration produces icm files...

Thanks for any info.
Click to expand...


They're the same. I think maybe Mac calls
the ICM, Windoze calls them ICC, or vice-versa.
you should be able to simply change the file
extension without ill effects.


rafe b
www.terrapinphoto.com
 
They're the same. I think maybe Mac calls
the ICM, Windoze calls them ICC, or vice-versa.
you should be able to simply change the file
extension without ill effects.
Click to expand...

Thanks for the clarification.
Now what do I do with them ? For instance I produce an icm file for my
monitor with a Colorvision Spyder2 probe and it is saved automatically in
c:\windows\system32\color and at the same time the ColorVision Profile
Chooser seems to apply it to the entire OS (the screen color is noticeably
different).
Now, I see the [Use custom monitor profile] option in Nikon Scan 4, and a
similar option in ViewScan. But what is the point of selecting them here if
they are already applied to the monitor ? Ain't that redundant ?
 
Guillaume Dargaud said:
They're the same. I think maybe Mac calls
the ICM, Windoze calls them ICC, or vice-versa.
you should be able to simply change the file
extension without ill effects.
Click to expand...

Thanks for the clarification.
Now what do I do with them ? For instance I produce an icm file for my
monitor with a Colorvision Spyder2 probe and it is saved automatically in
c:\windows\system32\color and at the same time the ColorVision Profile
Chooser seems to apply it to the entire OS (the screen color is noticeably
different).
Now, I see the [Use custom monitor profile] option in Nikon Scan 4, and a
similar option in ViewScan. But what is the point of selecting them here
if they are already applied to the monitor ? Ain't that redundant ?
Click to expand...

Hi.

From what I can gather there are 2 parts to Calibrating a Monitor.

The first is varying the Monitor Settings , Brighteness, Contrast etc.
These are always applied to the Monitor, and have an effect on every
program.

The second part is the Profile, which allows C.M. aware programs to change
the RGB numbers so that the colours on screen are accurate. This is why
your scanner Soft Ware asks about the Profile.

If you were scanning through Photoshop, then I am not too sure whether
Photoshop would be controlling the Scanner Display, and Double Profiling
could be happening.

If you are using the scanner "Stand Alone" then obviously it would need to
have its CM working.

Which is why I use both of mine in Stand Alone mode, and they are faster
that way.

Roy G
 
Guillaume said:
Vuescan wants icc files but the software I'm currently experimenting with to
do color calibration produces icm files...
Click to expand...

Actually, the profile can have either a .icc or .icm extension in
Vuescan. At least in the later versions I have been using anyway.
Perhaps this was not the case with earlier versions? Also, if you ever
really needed to you could simply rename your file with a ".icc"
extension and Vuescan would still recognize it. I actually did this
with my monitor profiles before I realized Vuescan would accept either.

As a side note, you may have noticed that the instructions for Vuescan
scanner profiling talk about naming the profile file "scanner.icc" and
the it8 target data file "scanner.it8". These are simply the default
names that Vuescan looks for. In reality you can name them anything
you want. I would recommend using more descriptive names so as to
avoid possible confusion with any other profiles having the default
name.

Jeff
 
From what I can gather there are 2 parts to Calibrating a Monitor.
The first is varying the Monitor Settings , Brighteness, Contrast etc.
These are always applied to the Monitor, and have an effect on every
program.
Click to expand...
That's why the Spyder2 calibration software asks for the monitor settings to
be set on "factory default"
The second part is the Profile, which allows C.M. aware programs to change
the RGB numbers so that the colours on screen are accurate. This is why
your scanner Soft Ware asks about the Profile.
Click to expand...
Here I'm confused: if the profile is applied to the entire screen by the OS
in [Control Panel][Display][Settings][Advanced][Color Management] (and it
makes a noticeable difference), why should I _also_ apply it in Vuescan
[Monitor Profile]. If I do the result sucks (way too colorful)
 
Back
Top