VISTA color management and monitor calibration

Elements 7.0
VISTA Home Premium SP1
Nvidia 8600
Samsung SyncMaster 213T
Canon XSi
Multiple printers
Since getting new system with Vista, I haven't been able to get a print that looks like my screen. I tried Costco today and everything was much darker than I expected, but the reds were much richer. I read a lot about calibrating my monitor, but it is possible that there is more do it than that? Learning to adjust skin tone etc. in Photoshop, only to have the prints look bad is pretty frustrating.
Is the other option to invest in a quality printer, or go to a real lab instead of Costco?
Please use small words, since I'm not a professional.
Regards,
Michael

Michael, color management is certainly a difficult issue to perfect. My monitor is color calibrated but it doesn't guarantee that the prints will match. With the same image, I get different results from different printers and labs. I get the best results from labs in the local camera/photo shops, and the pricing for enlargements is still on par with like Snapfish or Kodak.
Check this setting in PSE: Edit>Color Settings...>Always Optimize for Printing. I would suggest color calibrating your monitor, then try different labs until you find the best results.

Similar Messages

Color Bars and Monitor Calibration

Hy,
Trying to calibrate my monitors using the FCP internal color bars is completely different from using the camera's color bars...!
What is your experience in that?
I absolutely dislike the image I get on my monitors when I try to calibrate it with the internal Bars. Actually I almost can't get the lower right, light gray stripe come visible. I have to push the brightness to the maximum and the image is terrible.
On the other hand, using a recorded camera's bars, it looks nice.
What's up?
I'm using a PAL sequence by the way.

Luis
Are you saying you are using PAL clour bars to adjust your Mac computer displays?
If you are, then that is wrong
You can only calibrate computer monitors using a computer display profiling system using a probe.
such as:
http://www.gretagmacbeth.com/index/products/productscolor-mgmt-spec/products_cm-for-creatives/productseye-one-display.htm
If you are adjusting a PAL monitor, you should use, preferably a test signal generator, or the bars connected direct from the camera to the monitor
Dont use Final Cut Pro or bars recorded to tape as the test signal, you must iliminate any interference to the signal caused by misaligned electronics.
G

Colour management in PS and monitor calibration

I've calibrated my monitors colours with an Eye One Display 2 colorimeter, and for photoshop i've assigned the monitors colour profile it has created to the work area (Edit > Assign Profile).
But for photography i take photos with AdobeRGB colour profile setting on my camera... should i be using this colour profile instead when working on the photos in PS? They look a little washed out. I'm guessing i should keep using my calibrated monitors profile instead?
And when saving photos a jpgs for the web, should i tick the "ICC Profile" box that lists my monitors colour profile when saving? Because i've noticed that now some browsers have started supporting ICC profiles. So in Firefox 4 BETA for instance, if i dont use the ICC Profile setting the colours look washed out on other monitors.
(Note that the ICC Profile setting for jpg is only available in File > Save As... if i go to File > Save for Web & Devices it has Embed Color Profile which is basically the same thing).

Beany3001 wrote:
... after doing this and testing the images on other monitors this does not happen, dont know why it does it on my monitors but as long as the colours are ok on other peoples monitors, and the closest to my displays i can get them, this seems to be the best option.... When opening any sRGB or AdobeRGB images in PS CS5 they always look washed out (like the saturation has been turned down), i can directly open a RAW image taken with my camera that uses AdobeRGB and it will still look washed out.
This only now happens after calibrating my monitor. Before this i could view any sRGB or AdobeRGB and they would look fine, not washed out in any way. I dont know why this happens, but i've seen other people mention this about PS as well after calibrating there monitors with a colorimeter (not sure if it's just with wide gamut displays). Do you have any explanation for this?...
This is not normal and indicates a bad monitor profile. I have a wide gamut monitor too and I had some problems before properly profiling my monitor, after that images look perfect - in fact way better than any sRGB monitors that I've seen. This is especially obvious with sRGB photos from digital cameras because the manufacturers create algorithms that save the captured images with colors using the ideal sRGB color space which can be more accurately displayed on a wider gamut monitor when it is working properly.
Beany3001 wrote.
...I've calibrated my monitors colours with an Eye One Display 2 colorimeter
I'm not an expert with using these devices and I can't tell what could be the reason for generating a wrong color profile - it could be the device itself or wrong settings or probing. When choosing a colorimeter, I searched a lot for feedback and found various links like this one saying that Eye One colorimeters are not very accurate yet with probing wide gamut monitors. But I also read a lot of comments saying that they are fine and some people claim they are better. However only the manufacturer of Spyder 3 claim officially on their web site that it is wide gamut capable, so I got that one and so far it's working fine.
Beany3001 wrote:
... It's why i would have liked to use my monitors profile as it's the only way i can get colours looking properly saturated and not dull...
As I said earlier, by working on an image with a monitor profile, you are in fact turning off the color management and if you don't like the results when the color management is on that indicates that the color management is not set properly and is so wrong that you are better off without it. I think you should start the troubleshooting with properly generating an accurate monitor profile. Unfortunately I'm not a big expert with that as I got my colorimeter only several months ago and also ColorEyes Display Pro which is a profiling software from a different company. I set the calibration and probing settings following the instructions from the tech support of the profiling software and since I liked the results, I never spent time to understand in depth all settings and options.
Beany3001 wrote:....
I've read multiple times that the AdobeRGB colour space can do more colours than sRGB? I thought that only when you save in a limited format like JPG that the amount of colours are the same....
Wider gamut does not necessarily is more colors. When you see those charts plotting gamuts as different 3D volumes or 2D cross sections, this is not the number of colors but saturation. You can have millions of colors on a narrower gamut than, let's say 10 colors with a much wider gamut. Think of the numbers as steps between colors and the gamut as how intensive the saturation can go. The number of colors depends on the bit depth 8 bit, 16 bit integer, 16 bit float, 32 bit float. JPGs are limited to 8 bit but the limit is to the number of colors (shades) not gamut. Check this link - it has jpgs saved with different profiles of various color spaces (gamuts)

'The monitor profile "LCD color management and conversion" PSE6

Does anyone know how to correct this? I can find older posts but they date back too far. Where they say to go and what do has changed since.
The monitor profile LCD color management and conversion appears to be defective. Please rerun your monitor calibration software.
Everything dispalys in a cream color background and nothing prints correct color. I have PSE6.

todls1:
I'm guessing this message appears when you start the PSE6 Editor?
If so, what you should select is Ignore, and check the box to not show the message again. (Alternatively, you can remove the profile. If you wish to do this, tell me what edition of Windows you have and I can provide instructions.)
Essentially, you have a profile installed for your computer's monitor, either installed automatically by Windows Updates, it came with your computer, or it was installed with a driver (or piece of software) for your monitor.
This type of profile is "generic" and does not contain color calibration information.
Elements looks for profiles assigned to your monitor, because if the profile was created as part of a color calibration process, then that profile contains information that will help Elements to ensure that the colors you see on the screen are accurate.
Color is a complicated topic, especially when you introduce computer monitors, but suffice it to say that each monitor has various things that can make it display the same image in a way that's different from every other monitor. These things can include age of the monitor, the specific settings (e.g. contrast, brightness, etc.) of the monitor, and the lighting conditions in the room. When you calibrate a monitor using specialized calibration hardware/software, the calibration software creates a profile that tells programs on your computer (like Elements) about all these factors and how to compensate for them to ensure everything is displayed correctly.
Sorry for what may seem a long-winded explanation, but just understand that using the "generic" profile instead of one created by specialized calibration equipment has caused colors to appear incorrectly in Elements and are likely contributing to the problem when printing. This is why you should select Ignore.

Why "LCD color management and conversion" appears to be defective?

Why? How to fix it?

Apparently "LCD color management and conversion" is the profile that's associated (through the operating system) with your monitor.
The error message is because the color profile named "LCD color management and conversion" likely really is defective. Profiles are complex things and are not always properly crafted. This problem is surprisingly common.
Click Start, then type color management into the search box.
When Color Management comes up, click it.
Click the Devices tab to see or change what profile is associated with your monitor.
How did you end up with that profile associated with your monitor? The windows default is to use sRGB IEC61966-2.1.
Did you profile your display with a color measurement device? Did it get installed with your monitor?
-Noel

OWSM Vs OSB: Security, Management and Monitoring

Has anyone done a comparison of the Security, Management and Monitoring capabilities of OSB 10gR3 and OWSM?
I think both of them have a place in the architecture, but I am looking for pointers on the overlapping capabilities in terms of security and service monitoring. When is one preferred over the other with pros and cons.
Thanks,
-J

In short OSB you configure process by process. OWSM is a layer you can put across your whole enterprise.
Other than that the functionality is very similar.
cheers
James

"monitor calibration software" "LCD color management and conversion" is defective.

My photoshop is not working and A message pops up saying to rerun monitor calibration software. How do I do this?

Which calibration tool are you using? With my Spyder4Elite it's just about running a recalibration with its software...

Color management problem with calibrated monitor

I'm using a Samsung Syncmaster T220 LCD profiled and calibrated with a Spyder2Express. PC runs Vista 32 SP2, Photoshop CS4. Using Adobe RGB for workspace profile. System profile is set to the Spyder2Express profile.
Open up photo in Photoshop. Colors fine.
Resize for web, convert to sRGB, then check preview in "Save for web..."
Under preview, I preview the following:
-Monitor Color
-Windows (no color management)
-Macintosh (no color management)
-Document Profile
The Preview of Windows, Document Profile settings look exactly right, whereas the Monitor Color setting looks badly darkened. I preview with Firefox, save and view image using IrfanView and Firefox. It's badly darkened. I'm stumped. I don't know what I'm doing wrong. This is similar to another recent posting here, except that I am using a calibrated display with profile.
Anyone know what I'm missing?
Thanks, Luke

I'm a little confused. Previewing through "Monitor Color" and "Windows (no color management)" are both technically not color managed. Perhaps we should distinguish further between "colorspace aware" and "device profile aware". So I can understand when you say that Irfanview will do some color management, but does not use the monitor device profile. But I would have thought that Firefox in non managed-color config would still use the monitor device profile.
I would have thought (and I might turn out to be wrong) that previewing using "Windows (not color managed)" would be the standard for previewing images for stock browser configurations. What photoshop shows me is correct rendering of the image based on what I edited in this mode. But the browser shows me a version that looks like it is not device aware, counter to photoshop's prediction. What is going wrong here? Do none of these major window apps use device profiles? Why does photoshop think that they will?
Another thing that has been suggested is that my monitor is calibrated so far from the stock configuration that sRGB photos displayed on it without the benefit of device profiling will come out far off the mark. But I profiled the monitor in stock hardware configuration and made no adjustments, and don't think that the hardware config of the monitor has changed.
If this turns out to be just a practical issue, then it leaves a major question. What did I accomplish by calibration if my calibration doesn't look like anything I actually display with? I can guess that prepress work will be more accurate in most respects, or I hope so anyway. But how should I manage workflow for developing images for web content if I am unable to match up what I'm editing with what the end user will see?
Or maybe I'm just doing something wrong...or maybe photoshop is...or I don't know what. Where do I go from here? Is WCS implicated in this somewhere?
Luke

Fully Color Managed Application (using calibrated monitor profiles)

Hi,
I'm new to JAVA 2D so I may be missing something obvious - apologies if I am, but I've been trawling the API and web to try and solve this for many hours - so any help would be much appreciated!
I'm trying to write an application to open a JPEG with an embedded colour profile (in this case AdobeRGB) and display it with correct colour on my monitor, for which I have an accurate custom hardware calibrated profile. In my efforts to do this several problems / queries have arisen.
So, JAVA aside, the concept is simple:
a) Open the image
b) Transform the pixels from AdobeRGB->Monitor Profile (via a PCS such as CIEXYZ).
c) Blit it out to the window.
(a) is fine. I've used the following code snip, and can query the resulting BufferedImage and see it has correctly extracted the AdobeRGB profile. I can even display it (non-color corrected) using the Graphics2D.drawImage() function in my components paint() method.
BufferedImage img = ImageIO.read(new File("my-adobe-rgb.jpg"));(b) Also seems OK (well at least no exceptions)...
ICC_Profile monitorProfile = ICC_Profile.getInstance("Monitor_Calibrated.icm");
    ColorConvertOp convert = new ColorConvertOp(new ICC_ColorSpace(monitorProfile ),null);
    BufferedImage imgColorAdjusted = convert.filter(img,null);[I was feeling hopeful at this point!]
QUESTION 1: Does this conversion go through the CIEXYZ (I hope) rather than sRGB, there seems to be no way to specify and the docs are not clear on this?
(c) Here is the major problem...
When I pass imgColorAdjusted to the Graphic2D.drawImage() in my components paint() method the JVM just hangs and consumes 100% CPU.
QUESTION 2: Any ideas why it hangs?
Pausing in the debugger I found the API was busy transforming by image to sRGB this leads to my third question...
QUESTION 3: If I pass an image with a color model to drawImage() does drawImage do any color conversion, e.g will it transform my adobe image to sRGB (not what I want in this case!)?
And if answer to Q3 is yes, which I suspect it is, then the next question is how to make the J2D understand that I have a calibrated monitor, and to tell it the profile, so that the Graphics2D it provides in paint() has the correct color model. Looking in the API I thought this was provided to J2D through the GraphicsEnviroment->GraphicsDevice->GraphicsConfiguration.getColorModel(). I tried looking at what these configurations were (code below). Result - 10 configurations, all with the JAVA 2D sRGB default, despite my monitor colour management (through the windows display properties dialog) being set to the calibrated profile.
QUESTION 4: Am I just off track here - does Java 2D support monitor profiles other than sRGB? Is what I am trying possible?
GraphicsConfiguration[] cfg = GraphicsEnvironment.getLocalGraphicsEnvironment().getDefaultScreenDevice().getConfigurations();
    System.out.println(cfg.length);
    byte[] d;
    for (int j=0; j<cfg.length; j++) {
      System.out.println("CFG:"+j+cfg[j]);
      d = ((ICC_ColorSpace)cfg[j].getColorModel().getColorSpace()).getProfile().getData();
      for (int i=0; i<d.length && i<256; i++){
        if (d[i] != 10 && d[i] != 13){
          System.out.print((char)d);
System.out.println();
Any help much appreciated.
Thanks.

I have had some sucess with this, but it wasn't easy or obvious. The trick is converting the color to the monitor profile and then changing the color model to be sRGB without changing the pixel data. JAI's Format operation does this easily although I'm sure there are other ways to do it. The RGB data is then displayed without being converted to sRGB so that the monitor calibration is maintained. I will answer your questions since I had similar ones.
Q1. Yes the conversion is done using XYZ as it should be.
Q2. I believe paint is just very slow, not hanging. Any color model other than XYZ or sRGB requires conversion before it can be displayed (as sRGB). This is both slow and incorrect for a calibrated monitor.
Q3. Yes that is what I have found, a conversion to sRGB will always happen, unless it appears to be already done as when the color model is sRGB (even though the pixel data is not!).
Q4. It is possible but apparently only with this somewhat strange work around. If there is a way to change the Java display profile to be other than sRGB, I could not find it either. However, calibrated RGB display can be achieved.
Since I have seen many other posts asking for an example of color management, here is some code. This JAI conversion works for many pairs of source and destination profiles including CMYK to RGB. It does require using ICC profiles in external files rather than embedded in the image.
package calibratedrgb;
import com.sun.media.jai.widget.DisplayJAI;
import java.awt.*;
import java.awt.color.*;
import java.awt.image.*;
import java.io.IOException;
import javax.media.jai.*;
import javax.swing.*;
* @author keitht
public class Main {
    public static void main(String[] args) throws IOException {
        String filename = args[0];
        PlanarImage pi = JAI.create("fileload", filename);
        // create a source color model from the image ICC profile
        ICC_Profile sourceProfile = ICC_Profile.getInstance("AdobeRGB1998.icc");
        ICC_ColorSpace sourceCS = new ICC_ColorSpace(sourceProfile);
        ColorModel sourceCM = RasterFactory.createComponentColorModel(
                pi.getSampleModel().getDataType(), sourceCS, false, false,Transparency.OPAQUE);
        ImageLayout sourceIL = new ImageLayout();
        sourceIL.setColorModel(sourceCM);
        // tag the image with the source profile using format
        RenderingHints sourceHints = new RenderingHints(JAI.KEY_IMAGE_LAYOUT, sourceIL);
        ParameterBlockJAI ipb = new ParameterBlockJAI("format");
        ipb.addSource(pi);
        ipb.setParameter("datatype", pi.getSampleModel().getDataType());
        pi = JAI.create("format", ipb, sourceHints);
        // create a destination color model from the monitor ICC profile
        ICC_Profile destinationProfile = ICC_Profile.getInstance("Monitor Profile.icm");
        ICC_ColorSpace destinationCS = new ICC_ColorSpace(destinationProfile);
        ColorModel destinationCM = RasterFactory.createComponentColorModel(
                pi.getSampleModel().getDataType(), destinationCS, false, false, Transparency.OPAQUE);
        ImageLayout destinationIL = new ImageLayout();
        destinationIL.setColorModel(destinationCM);
        // convert from source to destination profile
        RenderingHints destinationHints = new RenderingHints(JAI.KEY_IMAGE_LAYOUT, destinationIL);
        ParameterBlockJAI cpb = new ParameterBlockJAI("colorconvert");
        cpb.addSource(pi);
        cpb.setParameter("colormodel", destinationCM);
        pi = JAI.create("colorconvert", cpb, destinationHints);
        // image is now the calibrated monitor RGB data ready to display, but
        // an unwanted conversion to sRGB will occur without the following...
        // first, create an sRGB color model
        ColorSpace sRGB = ColorSpace.getInstance(ColorSpace.CS_sRGB);
        ColorModel sRGBcm = RasterFactory.createComponentColorModel(
                pi.getSampleModel().getDataType(), sRGB, false, false, Transparency.OPAQUE);
        ImageLayout sRGBil = new ImageLayout();
        sRGBil.setColorModel(sRGBcm);
        // then avoid the incorrect conversion to sRGB on the way to the display
        // by using format to tag the image as sRGB without changing the data
        RenderingHints sRGBhints = new RenderingHints(JAI.KEY_IMAGE_LAYOUT, sRGBil);
        ParameterBlockJAI sRGBpb = new ParameterBlockJAI("format");
        sRGBpb.addSource(pi);
        sRGBpb.setParameter("datatype", pi.getSampleModel().getDataType());
        pi = JAI.create("format", sRGBpb, sRGBhints); // replace color model with sRGB
        // RGB numbers are unaffected and can now be sent without conversion to the display
        // disguised as sRGB data. The platform monitor calibration profile is bypassed
        // by the JRE because sRGB is the default graphics configuration color model profile
        JFrame frame = new JFrame();
        Container contentPane = frame.getContentPane();
        contentPane.setLayout(new BorderLayout());
        DisplayJAI d = new DisplayJAI(pi); // Graphics2D could be used here
        contentPane.add(new JScrollPane(d),BorderLayout.CENTER);
        frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
        frame.setSize(600,600);
        frame.setVisible(true);
}

Vista color management & CS3

Two weeks ago I wrongly faulted my new Dell 2707WFP monitor for its high contrast and saturation after many failed profiling attempts using the Spyder2Pro with the updated Vista software. I'm still at a loss as to why images are dark and overly saturated in Photoshop, Bridge and Lightroom. They were all fine on an older Dell system running XP home and CS2. I've gone so far as to purposely inflict various gamma curve settings in Spyder to bump up the low end luminance but resulting profiles still show images clipped in the low end and overall saturated even as the desktop and the PS interface turn a sickly pale.
I'm new to CS3 and Lightroom and so I'm not sure if the following is normal. When I view a NEW batch of images that were not previously viewed in Bridge, they are normal looking, however when I click on a thumbnail, it then reverts to the same garish contrasty version that I see full size in the above adobe software when opened. The same thing happens in the WINDOWS PHOTO GALLERY viewer but NOT in WINDOWS EXPLORER. In Explorer the thumbs are as they should be...normal, and if I open them in Microsoft OFFICE PICTURE MANAGER or in Quicktime PICTUREVIEWER, they open as normal images.
All this sounds like a profile issue of some kind, but as far as I know, everything appears to be set correctly in both PS and the profiling software. However, Im not sure about the system settings regarding profiles. In the Windows COLOR folder all the profiles are where they should be and I can select which one to load using the Spyder Profile Chooser. And again, I do restart PS when I change a profile. Could this be some kind of Vista bug??
Other notes:
If I do a screen shot and paste it back into PS, it turns DARKER than the original file.
When I do additional calibrations I restart PS to load the latest profile.
All files tagged sRGB and in sRGB workspace. PS shows this correct space and likewise the correct monitor profile in COLOR SETTINGS
ATI CATALYST CONTROL CENTER fails to run on bootup so windows shuts it down. No fix that I can find for this.
Running Vista Home Premium on a Dell Inspiron 530 E6550, 4GB memory, Radeon HD2600XT
Thanks again for your help!

Found this on the DATACOLOR site in their SUPPORT CENTER:
Incorrect Color outside Photoshop on Wide Gamut Display
Solution >>I just purchased a Dell 2407 HC display, considered wide gamut and the spyder 3 elite. I've used the spyder 3 to calibrate the monitor. In photoshop whenever I "Save for Web" or "Save as" in the sRGB color space, I wind up with over saturated oranges and reds. I'm needing to save in the sRGB for web work. My working color space is set to sRGB which looks fine when editting in photoshop, but as soon as I save it out of photoshop the reds and oranges are over saturated. I purchased the spyder 3 because of the wide gamut support, is there something I'm missing in calibration?
The display profile is not at fault here. The ICC profile for the display tells any application that uses color management what the color values for the display are. Thus Photoshop, which is using the profile, corrects for the colors on screen, giving correct results. A non-color managed application (such as Internet Explorer for Windows) would not use the profile and thus the colors would be oversaturated on your wide gamut screen. This is not the fault of the profile (that would make the color look wrong in Photoshop, where the profile is being used), but the lack of a profile (which makes the color look wrong in non-color managed applications).
This is the problem with using a Wide Gamut display for viewing in non-color managed applications. A typical gamut display is not color correct in such applications, but is at least approximately correct; a wide gamut display is noticably oversatured in some colors. On the Mac many applications, including web browsers and OS utilities, are color managed, so it is less of an issue than on Windows.
Article Details
Article ID: 723
Created On: 10 Jan 2008 07:31 PM
So if the color is off outside PS, then its not the fault of the profile. My problem is the image is off INSIDE PS, and by the same reasoning, then the profile is at fault. If the profile is to blame, is this a Spyder issue or Vista issue? So far noone seems to know anything including Adobe tech support and Dell. Been waiting 2 wks to hear from the Spyder people.
Would really appreciate some input on this. thanks.

Color Managment and CS3 Confusion - new LCD

Please help, I'm just learning about how Ps handles color and this is driving me nuts.
I'm using Ps CS3 in Vista 32-bit. Just got a new Dell 2408wfp LCD monitor. I'm using the default color profile it installed with monitor (specific to the monitor, not a "generic monitor" profile). Picture colors look great in Ps workspace. When go to "save for web" the images look way oversaturated (more orangish). In the save for web options, it's currently set to "uncompensated". If I change it to "Use document profile" or "standard windows color", it looks correct in "Save for web" preview. However, if I save it with either of these 2 settings and open it in IE, it looks bad again. In Ps, under "edit", my "color setting" is set to "North American General Purpose 2" with the workspace set to sRGV IEC61966-2.1. If I got to view -> proof setup -> and select "monitor RGB", the Ps workspace looks just like the "save for web" preview. My "Color Management" in the Vista Control Panel has the following settings:
Devices tab, ICC profile = Dell 240WFT color profile, D6500 default.
Advanced tab, device profile = system default (sRGB IEC61966-2.1)
Advanced tab, viewing conditions profile = WCS profile for sRGB viewing conditions.
What is going on here? From the forums it seems like either Ps is wrong or my monitor is. Which version is truly in the image? What I see in Ps workspace or in the "save for web" preview? In this scenario what version would my website visitors see (bad or good image color)? Could Ps be "correct" and saving without a color profile when "save for web" and then IE is using my monitor profile and therefore looking bad? How can I fix?
Thanks in advance!

"What was confusing to me is ON MY MONITOR it looks good in Ps. "
What's confusing about this. Of course it looks good on your screen. Ps is using your monitor profile in conjunction with the workspace profile to display correctly. As soon as you view that sRGB image in Monitor RGB, which is what your other apps are doing, the on screen view goes to hell.
"If I then follow that logic, I should just ignore the SFW and final visualized output on my monitor in my workflow and hope my end users visiting my website don't have wide gamut monitors with goofy color profiles?"
Yes, that's about the best you can do. Actually embedding the profile and pushing for profile aware applications like Safari to become more widespread.
"Seems like this approach doesn't correct the problem for me or visitors to my website with a similar monitors. And if the issue is just my monitors color profile, why don't all images on the web also look color shifted on my monitor?"
How far off images look depends a lot on the image in question. Some types of images don't shift very much at all while others look hugely different. Also, if you're looking at images other than your own, you have no idea under what conditions (viewing and calibration) those images were adjusted. There are so many people, even professionals, who don't yet understand color spaces and calibration that you can't take anything for granted unless you do it yourself. For instance, I work with a lot of stock images from agencies like Getty and even though most of the files have embedded profiles, almost all of them were corrected by people who had no idea of how to properly do color and tonal correction, yet, somehow, you have to assume they thought the images looked great on their systems.

Color Management and files for web

I'm doing a layout for a web page in AiCS(11). What are the correct color management policies I should use so the colors will display in Illustrator as they will on the web.
So far I cannot find a combination that works. Even if I (i think) have color management off.
Christo.

Here's the more complete, accurate approach to this.
In System preferences > Displays > Color run the calibration routine and set the gamma for your display profile to 2.2
That has nothing to do with Illustrator or Photoshop color settings but everything to do with how well your display is prepared to show you how your images will look on Windows displays.
In Illustrator, choose sRGB for your working RGB space.
For profile mismatch policies, for RGB, "Convert to Working Space" is often a good choice for beginners who only do Web work. After you have studied up and practiced some, or if you do more general art prep in Illustrator, you may want to instead use "Preserve Embedded Profiles."
I do a lot of Web and print work for a number of purposes. All in all, if you are preparing artwork for the Web, you will have best results if you profile your display with a colorimeter and work in sRGB. The only reason to preview in Monitor RGB is to preview how the image will look when the profile is stripped, or when it is displayed in an application ON YOUR CURRENT MONITOR ONLY that isn't color managed.

Photoshop 7 color management or monitor settings?

For financial reasons, I'm still on Photoshop 7. I'm using Windows XP Pro with all the updates. Here's my problem. When I take an outdoor picture (for example) with my nifty new digital Nikon, all the colors look normal on the camera's LCD. As you would expect. When I move the photo file to my hard drive, the colors also look normal in thumbnail view. If I open the photo in Photoshop, it's yellow green. I've read several articles recommended on this Adobe site and set Photoshop color management to sRGB IEC61966-2.1, but that didn't make any difference. If I go to File > Save for Web, the image returns to normal color in the preview window. One more layer to this mystery: If I e-mail one of the photo files to myself, they are also yellow green inside Mozilla Thunderbird. Someone tell me what I'm doing wrong. PS, My monitor is a 1024x768 NEC MultiSync LCD 1550V. I've also experimented with the QuickGamma utility to see if that would have any effect, but no. Thanks in advance.

Your display profile is bad - replace it.
This is a common problem when people install the first color managed application (most applications don't use the display profile, so it can be bad and you won't notice).
(and there is no "true RGB" - every display's RGB is different)

Color management and Adobe Reader

Will Adobe Reader ever be color managed with regard to monitor profile ?
(I've searched forum but didn't find "color management" . Nobody's interested ? Wrong colors all the time ? )

There is no question that some designers seriously abuse transparency. Just because there are 16 different available blend modes, for example, doesn't mean a designer has to try to use all 16 such blend modes on a single page. This is akin to how some designers in a previous generation designed pages on which all 35 base fonts in early Adobe PostScript-based printers are used on a single page! However, it really isn't the role of the layout and design software to act like a nanny, trying to analyze whether a designer is using too much or otherwise abusing the transparency feature.
With reference to spot colors and transparency, spot colors are permitted to participate in transparency blending. The problem is generally that spot colors often have very unusual attributes in terms of physical opacity that transcend what we can show on a screen. The user can get into real problems if spot colors and transparency are improperly or imprudently used together. Often the problem is that the designer uses spot colors in their design, even though printing will be done completely with process colors that only approximate the typically out-of-gamut spot color, simply as a means of accessing "pleasing color" which is of course out of gamut for printing.
The bottom line is the need for training and education of users and proper preflighting of the content by both the designers and the prepress personnel. Nanny modes are typically useless and counterproductive since they often yield too many false positives, resulting in users turning off such modes.
- Dov

Color management and ICC V4 support in Firefox 4?

Could you give us an update on how color management has changed in Firefox 4 (if at all) and if V4 ICC profiles are supported again?
There are still very few browsers that really support color management correctly and this it's a pretty big deal for photography buffs and users of wide-gamut monitors.
Tried looking at FF4 FAQs and support and also Googled and Binged but I could not find any info on this related to FF4.
Thanks.

Hello Dennis,
this is the old (known since 2009-04) "qcms doesn't support ICC version 4" bug.
Have a look at:
https://bugzilla.mozilla.org/show_bug.cgi?id=488800
It's a shame that ICC v4 support has not been implemented yet again.
For all others, who don't know what we are talking about, you can test the Firefox colormanagement behavior here:
http://www.color.org/version4html.xalter
Regards, Lilien

VISTA color management and monitor calibration

Similar Messages

Maybe you are looking for