Calibrated Monitor Issues

I was wondering if anyone has encountered this problem.
I bought a Pantone Huey Pro color calibrator for my Macbook Pro and I seem to be having some issues with the way Photoshop is handling it.
I calibrated my monitor and everything looks perfect. Colors look balanced and nice. However I seem to be having some issues with Photoshop. I will open an image in photoshop, edit it a bunch, etc. The image looks perfect on my screen. Colors look great, contrast, etc. Everything just like i want it.
So i save it and post it up on the web. However it has become apparent that what i am seeing is completely different than what my friend sees and so on. He is saying my pictures look weird and overly saturated and warm. Yet on my screen they look great. I don't know what to do. I am a graphic designer and aspiring photographer yet i can't trust my screen.
Here is one image: http://img211.imageshack.us/img211/6484/27038vs047122616locopyua0.jpg
On my screen this looks good. I have no idea what it looks like on others.
Do i have to change photoshop's color settings or export the images a certain way?
Thanks in advance,
Cameron

It appears that this image is sRGB but that you did not embed the profile when you saved for Web.
Your image will only look correct to someone who has a wide-gamut monitor if you convert to sRGB and embed the sRGB Profile when saving for web. But that only works if they are using a color-managed Browser (of which there are only two: Safari and Firefox provided that the User has configured his copy of Firefox to be Color-Managed).

Similar Messages

Trouble with color on Presario, No red tones on display. Not a monitor issue.

Am experiencing trouble with color on Presario, model no. CQ5500F. Purchased a couple of years ago, and trouble was present immediately. Am getting no red tones - red items appear black or sometimes blue. Was told by HP that it was a monitor issue, and let computer slide out of warranty. installed new monitor today and problem still exists. Is this merely a display adjustment of some kind? Or will I have to pay HP their $99 for a one time fix? Any suggestions appreciated.

Hello UncleBob62,
It could be the display driver that is not properly working
1. Click on the start icon
2. Right click on computer and go to properties
3. Select Device Manager
4. Expand display adapters and right click on the video card driver and uninstall
The computer screen will go blank
On the keyboard press the windows key the right arrow key twice and then the letter R.
At this point your computer is going to reboot. After the reboot Windows will install generic drivers for your video card. Do you still see a lack of red tones?
If I have helped you in any way click the Kudos button to say Thanks.
The community works together, click Accept as Solution on the post that solves your issue for other members of the community to benefit from the solution.
- Friendship is magical.

Multiple Monitor Issue

Alright, so I have a 15" Macbook Pro with the dual graphics cards (GeForce 9600M GT and GeForce 9400M GT 256 version). It's the 2.66 intel processor one. Anyway, I've been trying to figure out this dual monitor issue that I've been having for a few days now. When I'm using the 9400M card and I plug into my mini displayport everything works just fine. This includes the VGA cord, the HDMI, as well as a standard Apple monitor. Now, when I switch over to the higher end graphics card, as soon as I plug into the mini displayport my screen goes black. And that's it. I can't do anything. I have to hold the power button down until the computer turns off.
I've been searching for days in order to find an answer to this question or if anyone has ever had a similar problem and no one could help me. I even went to the genius bar and no one could help either. Keep in mind I've tried this in a variety of ways. I've plugged the monitor in after the computer was running, I've had it plugged in while the computer was turning on, and each time after the initial boot up everything goes black.
To make matters worse, I originally came across this issue because I use Windows 7 on bootcamp and I wanted to use dual monitors within Windows. Bootcamp is only set to use the 9600M graphics card which is the one giving me all the heartache and apparently there's no way around it. If anyone has the slightest clue as to what's going on here or why it would be doing such a thing, let me know. Thanks.

Jon: Thanks for answering those questions. Run the Apple Hardware Test that you'll find on one of the DVDs that came with your MBP. If any errors are reported, go back to the Genius Bar with the error codes reported by AHT and ask to have the machine repaired.
If you have extended AppleCare protection, you have a TechTool Deluxe CD/DVD. You can also use that to test your hardware. If it reports any errors, take the exact wording and error codes from that report along with you to the GB, too.
The problem is not with your three external displays or your cables, adapters, or your MBP's mini-Displayport, because they all work fine with the 9400M. The problem isn't some wrong contact that's being made momentarily as you insert the mini-Displayport plug into the port, because it occurs even when the cable is securely connected before starting up the computer. It seems to me the problem must reside either in your 9600M GT or in its connection to the mini-displayport.

Color settings after calibrating monitor with Spyder 4Pro

Hello, Now that I got my new laptop and finally got a perfect calibration with the Spyder 4Pro , I have a question. Do I leave the color space on Photoshop and Lightroom as they are (Abobe 1998) or use the new profile? I also do a lot of my own prints with a great Epson, do I leave that on the setting as is ( let photoshop manage etc) or use the new profile?
Thanks in advance....

The profile saved by your calibration software is your Monitor Profile and absolutely nothing else..
It has absolutely nothing to do with your working color space or your printer (target) profile.
Monitor profiles are absolutely device-dependent, that means it only applies to your particular monitor unit and nothing else, not even an identical monitor of the same brand and model.
Your working space should be a a device-independet color space, such as ProPhoto RGB, Adobe RGB, sRGB, etc.
Your printer profile, also called target profile, is a totally device-dependent profile for your specific combination of paper/ink/printer.
You need to do an awful lot of reading on Color Management, a subject some of us have spent a very long time studying before we grasp it. A good place to start would be here:
COLOR MANAGEMENT PHOTOSHOP CC CS6 Basic ColorManagement Theory ICC Profiles Color Spaces Calibrated Monitor Professional…

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);
}

Images processed in lightroom on calibrated monitor then viewed on non calibrated monitors

I process my images to look good on on my calibrated monitor, then export them to my website for viewing. When I show people my images on their monitors which generally are not calibrated, the images of coarse look washed out and way too light. How do you guys compensate for a situation like that? Of coarse you want your images to look the way you want them too on everyones computer that looks at them. Is it best to darken and over saturate in lightroom to compensate for the difference?
Curt

The histogram represents the numerical values of lightness and color that are stored in the file or in the XMP-data or in the LR Catalog.
Different (uncalibrated) monitors interpret these numerical values differently, so an image from one and the same file would look different on these monitors.
But the (uncalibrated) monitors do not shift the black or white point; they just display the tonal values different. So for instance an image file with correct black and white point would have blown-out highlights on a monitor that is too bright. Or the darks could block-up on a monitor that is too dark.
But the monitor doesn't change your image file and doesn't change the histogram.
The purpose of calibrating the monitor is to give you a standard when you edit your images. If your monitor is not calibrated and - for instance - has a white point of 5000 K instead of the standard of 6500 K, then your images would appear too red (too warm in photographic terms) on your monitor. If you then corrected your image (its numerical values) so that it appears "normal" on your screen, it would have a blue cast (too cold) on a calibrated monitor.
So basically we calibrate our monitors to create a standard (a) between different devices (monitors, printers, etc) and (b) between your own images edited at different points in time. Without calibration your monitor would not only display "wrong" colors but display the same numerical color value differently at different time (monitors "drift" and thus have to be re-calibrated at regular intervals).
But naturally, the color management does not work for uncalibrated monitors. So, even if you have a color-managed workflow, you never know how your images that are posted on the web will look on other people's monitor. And there is no help for that as long as uncalibrated monitors exist.
WW

Graphics card issue or monitor issue?

Hello, i have a MacPro 2.66 w/ an ATI x1900 and a MacBookPro with th nVidia 8600
i recently purchased a 28" Hanns-g Display which i upgraded from my 20" apple cinema display, im curious if this could be a graphic issue or a monitor issue:
When i connect the 28" monitor to my ATI card (port 1) and boot into 10.4.10 (macPro) i noticed diagonal lines that seem to "scroll" (like an overscan line or something) on greyish and lighter backgrounds.
tried it with the second port, same thing, it does it on all resolutions
(it runs @ 1920x1200).
when i boot into XP and try the same sites i did in 10.4.10 it doesnt do it at all, its as it should.
I tried both VGA>DVI and HDMI>DVI to the ATI on OSX but it only does it with the HDMI>DVI connection under OSX, VGA looks fine.
(btw my ati card is clean as a whistle, no dust or anything)
However if i plug it into my MacBookPRo with hdmi>DVI it doesnt do that at all.
so im wondering probably incompatible monitor or what?
im looking to getting a 30" Apple Display but not if its gonna act up like that on my macpro, none of this appeared on my ACD 20".
any suggestions or tips?
thanks!

im not experiencing scan line son my 30" ACD display under OSX or XP with my ATI, could be the monitor you are using, but if its not doing it with your MBP than.....idk
sonds strange, try another gfx card or another macpro if possible.

Calibrating monitor, prints, and CAMERA

I have a canon 5d. I custom white balance for correct color in camera. When I see the photo on the back of the camera dislplay the color looks spot on but when I upload to the computer the colors are almost purple. I use and eye one display calibrator for my monitor.
How can I correct this?

Aimee,
The problem is that your LCD screen on the camera is not color or tonally calibrated and what you see on it is not what you get. That's pretty normal for back of the camera LCDs and there's not anything you can do about it.
Are you shooting RAW or in camera jpegs? If you're shooting in camera jpegs, what color matrix have you chosen? You can basically set them to sRGB or Adobe RGB and, if that's what your'e shooting, they should be pretty close when you open them in Ps. If you're shooting RAW, which I really encourage you to do, the white balance you set in camera is only a guide used as a starting point for the raw image processing application - Canon's DPP, Adobe ACR or Lightroom or PhaseOne's CaptureOne. The white balance, along with the RGB working space can be overridden in the raw software to whatever works best for you.
Obviously a hardware calibrated monitor is a must when evaluating digital files. I assume you've done that, right?
Peter

Playing off the Timeline via firewire( XdCam pal) Monitoring Issues

Hey,
I have just switched to FCP and have found that when recording the from the FCP timeline manually via firewire into a Sony XDCam PDW530 I experience 4:3 flashes in the Camera monitor and viewfinder as the timeline plays down Video Transitions. All effects have been rendered (Blue line above transition)
However the Camera appears to record correctly to disc. I played the recorded material from the camera via an XD deck into a wide screen monitor and all appears fine the 4:3 flashes are not present on transitions. play the disc back in the camera and the 4:3 flashes for the duration of the Video Transitions return????
when playing out of the Camera via SDI and Analogue Composite outputs into a wide screen monitor all appears ok as well.
It's a little odd that you cannot monitor the output correctly on the XDcam. If i change the pull down settings from 2323 to 2332 it monitors the transitions correctly but the video aspect is somewhere between 4:3 and 16:9.
Shoot in 16:9 Capture DV Pal, Edit DV Pal, Playback Output Apple FireWire Pal (720 x 576)
Any ideas????

Thanks Shane,
We have been down the PRINT TO VIDEO road with the same playback issues in the XD Camera's LCD screen. We still see the 4:3 transition on the 16:9 image when playing off the timeline / playing back the recorded media in the camera and viewing on cameras screen .
I guess this is only a monitor issue. If you don't include any video effects it plays down 16:9 perfectly in the cameras monitor
What is recorded onto the disc is fine.
Also my understanding is the what's coming off the timeline is a DV stream so not sure how the GOP format comes into play. Recording onto a XD Cam off the timeline thru other edit programmes has never been an issue. I have come from Avid Pinnacle and the monitoring of transitions was never an issue when streaming back to the xdcam.
Thanks

Help - color management issue, sunburns! (with a calibrated monitor)!

I love Lightroom and its workflow, its unlike anything of its kind. However, lately (since I first started using it) I've seen a problem related to color management on my computer (I believe) and hope someone out there can shed some light.
After importing JPG pictures into Lightroom and making modifications to them, I am getting *completely* different results once I export them (as sRGB, as I'll be sharing them via web). All of the pictures are coming much more saturated (for a lack of a better description).
Here is what I am getting (see brief descriptions below each pic): http://www.bachmannphoto.com/test/couple.html
I'd be very curious as to how they are showing up on your (calibrated/uncalibrated) screen(s), but the 1st and 3rd pics are showing up as 'realistic' on my PC, while the middle (exported from Lightroom) is showing up as too much saturation and even reddish push, as though the couple got hit with sunburns.
Another example of this result here: http://www.bachmannphoto.com/test/dog_chair.html. Though in this case, the picture in the middle actually looks better, it doesn't change the fact that I am getting very different output than what I see in Lightroom (or in photoshop without the embedded profile).
I am thinking this is a problem with color management settings on my PC. First guess would have been "monitor calibration"... but as mentioned in the title, I calibrated my monitors (I have two Dell 1905FPs... not great for accurate color representation, but they do the job) repeatedly, using Spyder2 Pro.
What pushes me to think this is the following (represented here http://www.bachmannphoto.com/test/couple_original.html ):
Before making any modifications to the imported sRGB picture - in other words, importing the picture straight from the camera memory card into Lightroom and then exporting it back (again, without making any modifications to it) - the pictures, both the original and the exported which still look the same and are kept sRGB, look completely different in Lightroom then if I was viewing them in a non-color managed software on my PC, such as the default windows picture viewer.
If my LCD panels are properly calibrated, should I not be more or less seeing the same image colors, whether I'm viewing them through windows, or through Lightroom (or Photoshop along with the embedded sRGB profile)? What gives??
Jesse
PS. I *more* than appreciate anyone taking time to respond to this post. I've been up for nights now trying to understand/fix this.
If it's any help, I have the different version (but original and exported) files here:
original file:
http://www.bachmannphoto.com/test/couple_original.JPG
Original file, imported into Lightroom and then exported back out w/o any modifications (sRGB): http://www.bachmannphoto.com/test/couple_lightroom-nomidification_exported_srgb.jpg
Original file, imported into Lightroom, MODIFIED and then exported back out (sRGB):
http://www.bachmannphoto.com/test/couple_lightroom-modified_exported_srgb.jpg

Exiftool reports the original contains the following EXIF tags:
Interoperability Index : R98 - DCF basic file (sRGB)
Interoperability Version : 0100
The nomidification_exported version does not have those lines, but contains the actual sRGB profile:
Profile CMM Type : Lino
Profile Version : 2.1.0
Profile Class : Display Device Profile
Color Space Data : RGB
Profile Connection Space : XYZ
Profile Date Time : 1998:02:09 06:49:00
Profile File Signature : acsp
Primary Platform : Microsoft Corporation
CMM Flags : Not Embedded, Independent
Device Manufacturer : IEC
Device Model : sRGB
Device Attributes : Reflective, Glossy, Positive, Color
Rendering Intent : Perceptual
Connection Space Illuminant : 0.9642 1 0.82491
Profile Creator : HP
Profile ID : 0
Profile Copyright : Copyright (c) 1998 Hewlett-Packard Company
Profile Description : sRGB IEC61966-2.1
Media White Point : 0.95045 1 1.08905
Media Black Point : 0 0 0
Red Matrix Column : 0.43607 0.22249 0.01392
Green Matrix Column : 0.38515 0.71687 0.09708
Blue Matrix Column : 0.14307 0.06061 0.7141
Device Mfg Desc : IEC http://www.iec.ch
Device Model Desc : IEC 61966-2.1 Default RGB colour space - sRGB
Viewing Cond Desc : Reference Viewing Condition in IEC61966-2.1
Viewing Cond Illuminant : 19.6445 20.3718 16.8089
Viewing Cond Surround : 3.92889 4.07439 3.36179
Viewing Cond Illuminant Type : D50
Luminance : 76.03647 80 87.12462
Measurement Observer : CIE 1931
Measurement Backing : 0 0 0
Measurement Geometry : Unknown (0)
Measurement Flare : 0.999 %
Measurement Illuminant : D65
Technology : Cathode Ray Tube Display
Red Tone Reproduction Curve : (Binary data 2060 bytes, use -b option to extract)
Green Tone Reproduction Curve : (Binary data 2060 bytes, use -b option to extract)
Blue Tone Reproduction Curve : (Binary data 2060 bytes, use -b option to extract)
The modified_exported version likewise does not have the interoperability index tag but contains the actual sRGB profile:
Profile CMM Type : Lino
Profile Version : 2.1.0
Profile Class : Display Device Profile
Color Space Data : RGB
Profile Connection Space : XYZ
Profile Date Time : 1998:02:09 06:49:00
Profile File Signature : acsp
Primary Platform : Microsoft Corporation
CMM Flags : Not Embedded, Independent
Device Manufacturer : IEC
Device Model : sRGB
Device Attributes : Reflective, Glossy, Positive, Color
Rendering Intent : Perceptual
Connection Space Illuminant : 0.9642 1 0.82491
Profile Creator : HP
Profile ID : 0
Profile Copyright : Copyright (c) 1998 Hewlett-Packard Company
Profile Description : sRGB IEC61966-2.1
Media White Point : 0.95045 1 1.08905
Media Black Point : 0 0 0
Red Matrix Column : 0.43607 0.22249 0.01392
Green Matrix Column : 0.38515 0.71687 0.09708
Blue Matrix Column : 0.14307 0.06061 0.7141
Device Mfg Desc : IEC http://www.iec.ch
Device Model Desc : IEC 61966-2.1 Default RGB colour space - sRGB
Viewing Cond Desc : Reference Viewing Condition in IEC61966-2.1
Viewing Cond Illuminant : 19.6445 20.3718 16.8089
Viewing Cond Surround : 3.92889 4.07439 3.36179
Viewing Cond Illuminant Type : D50
Luminance : 76.03647 80 87.12462
Measurement Observer : CIE 1931
Measurement Backing : 0 0 0
Measurement Geometry : Unknown (0)
Measurement Flare : 0.999 %
Measurement Illuminant : D65
Technology : Cathode Ray Tube Display
Red Tone Reproduction Curve : (Binary data 2060 bytes, use -b option to extract)
Green Tone Reproduction Curve : (Binary data 2060 bytes, use -b option to extract)
Blue Tone Reproduction Curve : (Binary data 2060 bytes, use -b option to extract)

IMac monitor issue

Booted my computer iMac today (v 10.6.7) and now monitor it is terribly contrasty and all whites are screaming in everyprogram even web browsing. i.e. had psd file that is an 80% grey white sign with fall off shadows to make 3D looking that now views as a screaming high contrasty white blob image with the bottom red garrishly contrasty as well. Bounced the file to my laptop just make sure and it's fine. No, this is not a brightness issue and have toggled through the calibrations and they made little to know difference. Is this a monitor of software issue? What else can I try? HELP!

You can trying resetting both the SMC and PRAM if there isn't any change post back and there are some other resets that can be done.
SMC RESET
Shut down the computer.
Unplug the computer's power cord and all peripherals.
Press and hold the power button for 5 seconds.
Release the power button.
Attach the computers power cable.
Press the power button to turn on the computer.
PRAM RESET
Shut down the computer.
Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
Turn on the computer.
Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
Hold the keys down until the computer restarts and you hear the startup sound for the second time.
Release the keys.
Roger

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

Calibrated monitor profile 'clips' shadow detail in RAW images

I've been using the Pantone Huey color calibration tool and like it except for one small problem. When viewing RAW images from my Canon 5D in Aperture the shadow areas are 'clipped' and really look crappy. If I do ANY adjustment to the exposure, shadows/highlights, levels, etc. a lot of shadow detail becomes apparent. It's especially noticeable on darker images. This only happens with RAW images from my 5D, and only when I have my Huey profile selected. Aperture and the Huey software are all the most recent versions.
Even if I turn the brightness DOWN shadow detail suddenly pops into life. So the first thing I do when loading in all my photos is to do a batch brightness adjust +.01, or a batch tweak of the levels by .1. See for yourself... Apple, when are you going to fix this odd issue? I've been plagued with it for over a year now and it's getting to be a real pain. Thanks.
Example:
http://www.johnnydanger.net/temp/clipped_blacks.jpg

I'd really like to understand your post because absolute vs. relative black point sound very close.
The terms absolute and relative are used to describe different rendering intents (abs. vs. rel. colorimetric). Black point compensation (BPC) is another option when choosing rendering intents.
The only conversions Aperture does [that are relevant here] are between its internal color space (which is unknown) and the monitor color space and between the internal space and the one it exports into (eg, Adobe RGB in my tests). I have not seen an operating system or application that lets you choose the rendering intent for conversion into the monitor space and Aperture is no exception. Since Aperture uses the preferred intent of a profile for printing it presumably does so as well for displaying (in my case this would be perceptual).
Now since the darkest point of the internal color space is probably lower than that of the display using perceptual, or relative with BPC, or absolute should ensure that all shadow detail is visible. Since Aperture (and other apps) possibly honor the rendering intent of the monitor profile it might be that Aperture is mistakingly using relative without BPC before I check the Levels box and only after that switch on the BPC. Forcing the application to always use BPC or using absolute as the preferred rendering intent might therefore prevent you from encountering the problem.
Does what I just said make sense. No, not really but then I don't really know how these apps work internally. And neither do my printing results with a number of labs [10 10 10] is always indistinguishable from pure black.

Dell Tablet Dock FW Update 0.41.23, A03 with Dell Venue 11 Pro (7130/7139) - monitors issue

Hello,
I have Dell Venue 11 Pro (7130/7139).
I have installed “Dell Tablet Dock FW Update 0.41.23, A03” http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=97N0V (previous version was Version 0.41.19, A02). Installation completed successfully, but my monitors (connected though DP and HDMI) disappeared after installation (system do not see any monitor connected trough Dell Tablet Dock).
I have restarted system, disconnected / reconnected power from “Dell Tablet Dock” – nothing helped.
I tried to revert to previous version 0.41.19, A02, but the installation process requires monitors to be connected to “Dell Tablet Dock”. But they are connected, system simply do not see them!
Could you help me with this issue or with advice, hot to force previous version 0.41.19, A02 installation (to ignore monitor connection check)?
Thanks,
Aleksandrs
Hello,
I have Dell Venue 11 Pro (7130/7139).
I have installed “Dell Tablet Dock FW Update 0.41.23, A03” http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=97N0V (previous version was Version 0.41.19, A02). Installation completed successfully, but my monitors (connected though DP and HDMI) disappeared after installation (system do not see any monitor connected trough Dell Tablet Dock).
I have restarted system, disconnected / reconnected power from “Dell Tablet Dock” – nothing helped.
I tried to revert to previous version 0.41.19, A02, but the installation process requires monitors to be connected to “Dell Tablet Dock”. But they are connected, system simply do not see them!
Could you help me with this issue or with advice, hot to force previous version 0.41.19, A02 installation (to ignore monitor connection check)?
Thanks,
Aleksandrs

Hi,
I had almost the same problem. I used Dell Venue 11 Pro (7130/7139) with Dock and NEC MultiSync LCD 1770 NX through HDMI-DVi cable. There were no probs while tablet was on, however when it was sleeping or off the NEC MultiSync LCD 1770 NX permanently (each 2-3 seconds) showed the sign that there were no input signal. It was not critical for me, however it was one more my disappointment in Dell new products (I have used Dell latitude D620 and dock for 7 years without any problems, thats why I chose Dell Venue 11 Pro, assuming that the Dell quality remains the same... I was wrong, Dell Venue 11 Pro has too much loose ends).
Yesterday I updated Dock firmware to “Dell Tablet Dock FW Update 0.41.23, A03” and Dell lost NEC. I.e. the monitor was connected, but the tablet just did not want to see it or recognise. I connected dock to another monitor Samsung SyncMaster 226CW (took from my friend) through the same HDMI-DVI cable and found that it is working with it. So I decided to downgrade the Dock firmware to 0.41.19, A02 (the only previous version I found at dell support), however it was impossible with my NEC, as tablet didn't see it. I connected again the tablet to Samsung SyncMaster 226CW which was recognised through the dock and successfully downgraded the firmware to 0.41.19, A02. Afterwards connected my old NEC MultiSync LCD 1770 NX and fortunately it was found by my Dell tablet and dock. Now it's working.
Nick

Mid 2013 Macbook Air External Monitor Issues

I am running on 10.8.4 and am using a fully upgraded 2013 macbook air. i7, 8gb of ram, 512 ssd. Recently, I have been having issues connecting my computer to external displays. I have reset the PRAM, and the SMC multiple time with no luck. I have also deleted the windowserver plist files and that did not seem to do anything as well. The issue is as follows: when I plug in my laptop through the thunderbold port to the hdmi on my tv, the screen on my laptop goes blue, as normal, but then nothing shows up on my tv. I have used the same cable with my roomates macbook and it works just fine, on multiple tv's. Mine is not able to connect to any of those tv's. When looking at the display settings in system preferences, I do not see that it ahs detected any external displays. I am not sure what to do at this point.

I think I have fixed it somehow. I reset the PRAM while the tv was plugged in and it worked, but it seems that something may be wrong with my video card, because there was a bunch of fuzziness and weird colors on my computer's monitor for a few seconds before everything went to normal

Calibrated Monitor Issues

Similar Messages

Maybe you are looking for