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

Similar Messages

  • 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

  • Lightroom not using the Monitor Profile

    I have recently set up a new computer with a new monitor. When I got PS and Lightroom set up on the new system I noticed that when viewing photos in both applications the colors are VERY different compared to how they look viewed online or in another photo viewer from my desktop (windows 8). I also noticed that when I opened PS I got a message saying that the Monitor Profile is "bad" and I could opt out to ignore the profile. When I did ignore it the color looks fine. Blacks are black, gray's are gray, etc . . . Anyway, I am wondering if there is a way I can have Lightroom ignore the profile as well. I have a monitor calibrator and I will try that, but I am wondering if it will do anything only because other applications look fine. Hope someone can shed some light on this!

    First of all, Photoshop and Lightroom are fully color managed applications that will actually use the monitor profile to display the image.Many other applications (viewers/browsers) are not and will just ignore it. So there's a difference right there.
    That said, when you get that message in Photoshop, it means exactly what it says. That profile is bad and should not be used.
    The real solution is to use a calibrator to make a new custom profile for your monitor. Until you get that up and running, use sRGB IEC61966-22.1 as monitor profile. You set this up in Control Panel > Color Management > Devices:

  • Color Management Confusion-Photoshop and monitors

    Ok, so I am asking this question because I am literally at my wits end with this color management stuff. I have become so confused in the past few days that I can’t even think straight. Anyway, I am hoping you all can help me “understand” how it all work. Let me start with some background information (since I know it will probably be asked)
    am a photographer, I utilize Lightroom 4 and CS3 (I know its old but I am planning on getting CS6 soon).
    put my pictures on the web that I will assume will be viewed on multiple different browsers.
    also will be sending my pictures to print at mpix or whcc. I may decide to print my own but haven’t really made that determination at this point.
    have a mac book pro that I work from.
    Ok, so I need to get a monitor to work with but I am unsure if I should just buy the thunderbolt mac monitor or get a wide gamut monitor. I have heard so many people say that the wide gamut monitors just messed them up. Also, I am bit confused on the nature of monitor profiles and how they work with photoshop and lightroom. I would assume the monitor applies a profile at all times? I also don’t understand the existence of the prophoto and wide gamut profiles for the mac monitors… they clearly are not wide-gamut monitors, so how do these profiles exist for them, and why would they be useful (if you set the profile to prophoto for example, it is all washed out as expected). Are these profiles “assigning” a profile to the color? I am assuming so because if they were converting them to just a standard rgb then you wouldn’t have the faded colors (correct?).
    I just am so nervous that I am going to create something that looks great in Lightroom or Photoshop but that looks awful on the browser, or worse, on a different monitor (standard monitor) and I would have no idea that it looked bad. Or, if I send something to a printer only to get a mess back.
    Also, please let me know if I correct in this. If I am in photoshop and I have an untagged image (send via a friend), and lets just say it is really a prophoto image (although my friend didn’t tell me) and I say to assign the prophoto profile (upon import to photoshop). If that truly is the correct profile, the image should look correct. Now consider two scenarios from there: 1) I embed that profile in the image, if I upload that to the web (I know to be cautious, you should always use srgb for web), if the person has a color managed browser, the image would properly appear, because the browser would recognize the profile (in this case “prophoto”) and convert it to whatever it needed to be. But, if it was not a color managed browser, I run the risk that the web browser will just assign a profile, which will wash the photo out most likely, correct? Ok… and scenario 2) after I get the image from my friend and assign the prophoto profile (since that is the correct profile the image was actually created in, although it was untagged when it was sent to me), the image will look correct… BUT, is photoshop displaying the prophoto profile, or is it converting to RGB for my viewing, or is my monitor converting it to rgb for my viewing? I guess I just don’t understand how the monitor fits into all of this. You HAVE to use your monitor to see your images, and since most monitors (including my current one are standard gamut) it would make sense that you actually can’t see anything in the prophoto profile, and you are truly looking at an srgb profile since that is all your monitor can display.
    Oh ya, and what benefit is the color match rgb? It seems everyone speaks of the srgb, prophoto, and argb.. but never some of the others.. so maybe I am just lost. I would even appreciate a link to some tutorials if you think those would be helpful.
    I am seriously confused.. I would really appreciate the help.

    I am not surprised you are confused about colour management because its a confusing subject. Luckily you own a Mac so you can get to grips with what the problems that colour management solves using the "colorSync Utility" and you will find this in Applications >> Utilities >> colorSync Utility. If you own a windows computer then I am sorry but you will be out of luck here and you should know better when you buy your next computer!! I am not sure why Apple gave us this application but it is really useful and all will help you understand Color Management.
    1. Launch Applications >> Utilities >> ColorSync Utility.
    2. You will see a list of "Installed ColorSync Profiles". Choose Adobe RGB 1998 which I hope you have chosen in you camera preferences.
    3.You will see a 3D representation of the Adobe 1998 Colour space. This represents all the colors this colour space will hold.
    4. Top left hand corner you will see a little arrow pointing down next to "Lab Plot". Click on this and a drop down menu will appear.
        Choose "Hold For Comparison"
    5. Now somewhere in the "Installed ColorSync Profiles" list you will find the profile for you monitor. Choose this.
    6. You will now see a new colour space inside the Adobe 1998 Colour space. If you have a cheap monitor the colour space will be small
    inside the Adobe 1998 profile. This means that you monitor cannot show you all the colors that are missing.
    7. Now choose a printer profile say, if you use them a profile for an Epson paper or any printer profile you have and you will see another profile in the Adobe 1998 box which shows you the only colors that your printer can print. If you like choose your monitor profile then hold for comparison then the printer profile and it will clearly show the mis match between you monitor and printer.
    8. Now choose SRGB and this will show you what colors a person using an average Windows monitor can see, poor people.
    So this is the problem, all devises can reproduce only a certain range of colors. The adobe 1998 profile does not show all the colors our eyes can see " choose Generic Lab" profile, then "hold for comparison" then Adobe 1998 and you will see Adobe 1998 is a small profile but is a good average of our collective colour vision.
    So how to solve all these missing colour problems. Well if you think of each devise, including you camera as speaking a different language from you monitor and printer then it is easy to understand that you need some sort of translator so that they all know exactly what colour is being talked bout pixel by pixel in an image. This is held in the ICC profile, but an ICC profile has o do more than this.
    Say you camera can produce a specific red we will call for demo purposes "001" and your monitor cannot produce it, how do you solve this? Well it is very easy to fool our eyes. Our eyes work by comparison so if the profile maps red "001 to the nearest red that the monitor can show and then proportionally remaps all other reds to fit within the reds the monitor can show us then we actually think we are seeing a full range of reds. The problem comes if we use the wrong profile for this. The red 001 could be re mapped anywhere and could be outside what the monitor can show. Say that happens but the printer can reproduce that red 001. We would see an image on the monitor with not many reds and when we printed it we would be shocked to find reds on the print. Worst, we would see an image on the monitor without reds and would correct for this and end up with a print with heavy reds and would not be able to work out why.
    So to solve this we should:
    1. use the correct camera profile when we are opening "Raw" files.
    2. Make sure you have the correct monitor ICC profile selected in "System Preferences" >> Displays.
    3. In photoshop we should make sure that the " Edit >> colour settings " are set to Adobe 1998 for RGB.
    4. If you are going to print you own photo in Photoshop go to "View >> Proof Setup >> Custom" and a box will
    open. Choose the profile of your printer and paper and choose "Perceptual" for rendering intent and then " OK". If you cannot find
    a profile for you printer and paper go to the printer of paper manufactures web site and download the profiles and instal
    them.
    5. You can now adjust the colors and contrast and photoshop will simulate how the output devise will deal with this. If you
    are using an outside printing house, they will supply you with their ICC profile to download so just follow the same procedure and
    choose their ICC profile and and do you colour correction.
    If you have a cheap monitor you will still not get a 100% result but you will get closer. You really need a monitor that you can  calibrate
    regularly because generic ICC profiles are just that. They are made from the results of many monitors and so are 90% or worse accurate.
    If you want to see a flag ship monitor at work go to http://www.eizo.com/global/support/db/products/software/CG223W#tab02 and go
    to the bottom of the page and download the Eizo Coloredge CG223W monitor profile, instal it on your mac then open then ope
    Launch Applications >> Utilities >> ColorSync Utility choose Adobe 1998 the hold and compare it with the  Eizo Coloredge CG223W
    profile. This is not the top of the range Eizo monitors that we use but you will see that this monitor will show most of the missing colour you monitor does not. This is actually a good tip if you are buying a monitor. Download the monitors profile and see how good it really is.
    The weak link still is printing. The colors you see in RGB on a back lit RGB screen are very hard to reproduce by CYMK inks on paper. Here you really should have a profile made for your printer and chosen paper. If you don't want the expense of buying a calibrator and doing it yourself, there are on line services that will do this for you.
    One final point you must remember. If you are using soft proofing in Photoshop ( "View >> Proof Setup >> Custom" as explained above), when you print you MUST choose in "Colour Handling" "Photoshop Manages Colour" and in the next step when the printing box appears
    you will see a drop down box with "Layout" in it. Click on this and choose "Colour Management and choose "Off No Colour Management". If you do not do this Photoshop will manage the colour then the printer will do it again and the print will be a disaster.
    This is a starting point really. Colour management is difficult but just try to remember that you need a translator between each step in the process to make it work so you have to make sure the correct profiles are being used by you camera, the program you use for opening the Raw photo files (Please don't use jpegs straight from the camera, but thats another subject), the correct monitor profile and output profile. If you don't check these it is like chinese whispers and your picture will be printed in Double Dutch!!.
    Hope that helps. I am on location In Italy for a couple of months so will be unlikely to be able to reply to any questions for a while. Will try to check back and see how you are getting on. Drop me a line at [email protected] if you have any questions. Good luck.
    Paul Williams

  • 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.

  • Color management question on having separate profiles in one document

    I have a document with images in it that have attached printer profiles with different separations, I'd like to print without further conversion of these images since they are profiled to be printed with no color management, how do I go about this?
    Does Indesign see the attached profiles and ignore the document profile? Or Do I have to set a document profile with no UCR/GCR that will maintain CMYK values.
    Thank you

    >I'd like to print without further conversion of these images
    Profiles are only useful if there needs to be additional color conversions at output or exporta conversion to a new CMYK space (new press conditions) or conversion to RGB for monitor display or an RGB proofing device.
    You don't want or need additional CMYK to CMYK conversions so you don't need the embedded profiles. When the profiles are ignored, the ID document profile is assigned to the images (there's no conversion) and as long as you output with the destination as Document CMYK the image values will be output with no change.
    Ignoring the profiles can potentially change the ID preview of images separated with conflicting profiles (CMYK>RGB), but it sounds like you are simply separating for different black generations so you shouldn't see a preview change.

  • Using ICC Monitor Profiles

    Hello,
    I produce ICC RGB monitor profiles for use with Photoshop using an Eye One Photo. Can FCP, or other software, translate those profiles so I know my LCD monitor is displaying color and contrast accurately for editing with FCP? If not, is there a better way to set up a LCD monitor than using Apple's standard calibration?
    Thanks,
    Drew Harty

    It will never have the accuracy that an external video monitor will have. The gammas don't match those that a TV set produces... if you really want accuracy you need an external Video monitor that includes a blue only button on it. Colorists would insist on a CRT.
    Jerry

  • How to design a web based leave management application  using jsf n Spring

    I'm a beginner for spring and jsf technology. I have a requirement to design web based leave management module using jsf and spring. Im confused in the design phase itself and not clearly knowing how to classify the classes. I need to understand clearly on how to do class design, and wanted to use MVC design patterns. As i know jsf itself is MVC but, as i want to use spring, i need to have some kind of model files and bean files.
    I'm clear about the following 3 classes.
    Applicant
    Approver
    Leave
    this will be like applicant will apply for leave and approvar when he logs he will see list of applied leaves and he will approve / reject the same by selecting one or more rows from datatable.
    Please guide me on designing this or gimme some link where i can read about designing java classes for web based applications.
    Thanks for your time and help.

    Please guide me on designing this or gimme some link where i can read about designing java classes for web based applications.Sure:
    http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/

  • Can't use another monitor profile for OD user

    Good day to all! There is a problem: In the network 4 Mac Lion clients with tablets Wacom and Lion Server with OD. Customers get the server security policies that impose some restrictions on them. Limitations are associated mainly with access to the system configuration, control for external drives and flash drives. Currently, restrictions on access to configuration screens available. However, users without administrator privileges can not change the current profile displays all the time is reset to the default profile. It may be necessary to give access to the policy to change the profile to register it manually? Thanks in advance!

    I have to say, I am in exactly the same place ppshr150 is. I have checked both Quicktime and Quicktime Player preferences and the option to choose a default screen for full-screen presentation of movies does not exist.
    I can drag movies over to the second monitor and then press Command F and they will play there but from a presentation perspective, this is rather unprofessional.
    It surprises me that Apple does not have this option. Or is it a bug they haven't/won't fix?

  • Appearance of color in Photoshop after calibration, and outside of Photoshop

    I bought an expensive monitor some time ago which claims to produce the color gamut of Adobe RGB, the NEC PA271W. I also bought an X-rite i1 Display Pro colorimeter, with software, to calibrate my monitor.
    After calibration, the images appear right when displayed in Photoshop, and such images print okay on my professional printer with professional profiles, but such images don't appear okay outside of Photoshop, when displayed on my calibrated monitor. They appear far too saturated and contrasty.
    When I check what profile is listed under the Color Management tab of my monitor, the default profile is the same as that listed among all the other profiles under Windows/system32/spool/drivers/color.
    What's going on, I wonder. Is my video card not compatible with the X-rite calibration process? The video card is the AMD Radeon HD 7700 Series.
    Any help would be appreciated.

    Vincent RJ wrote:
    I think we're either talking at cross purposes, or you are misinterpreting my words. I've always understood that the purpose of calibration is to standardise the appearance of the image on all monitors that are correctly calibrated.
    You are indeed MASSIVELY WRONG there.  Trust me, you're not even close to beginning to understand color management. What you are describing is a simplistic, deficient personal idea of Color Management, not "calibration".
    STEP ONE in Color Management:
    Calibrating and profiling are only a start of the whole Color Management process.  Calibrating and profiling your monitor does nothing, absolutely nothing for the appearance of any image on other monitors.  Trust me:  ZILCH !
    When you leave out the term "profiling" and refer to calibration alone you are talking sheer nonsense.  Get yourself into the habit of thinking of both terms together, though they are part of the one starting point in process.
    STEP TWO:
    Set your saved monitor profile after calibration as your Monitor Profile File only.  Never as your Working Space, never as something you ever embed in a file, never as a print or target profile.
    Once you have set this profile as your Monitor Profile.  You NEVER think of it again, and never mention it again—unless eventually, and for whatever reason, your monitor profile file gets corrupted, damaged or disappears by magic.
    Note that your monitor profile is a strictly device-dependent profile, it applies to nothing else in the entire world, only to your video card and your particular monitor unit.  Not even to an identical model and manufacturing batch.  Each individual monitor has its own performance characteristics (industrial tolerances of components or manufacture and all that, as well as aging of same).
    STEP THREE:
    This entails choosing your WORKING COLOR SPACE.  This will always be a device-independent (repeat: device-independent) standard workspace such as ProPhoto RGB, Adobe RGB, sRGB, etc., in descending degree of gamut width.
    STEP FOUR:
    You make absolutely sure to embed the device-independent Color Profile of your Working Color Space in your document (image file), this is called tagging your file.  This is of such enormous importance that I always say:  "If a moron hands you an untagged file, you're going to have to guess in which color space it was created.  Once you make your best educated guess, remember to go beat that moron who gave you an untagged file mercilessly with a baseball bat or simlar, heavy object!"
    This is just my way of stressing how wrong it is not to embed the color space profile in your finished file. The only worse offense would be to tag it with the wrong profile.  Tagging a file with your monitor profile should be punished by quartering or by burning at the stake.
    Again, just strong imagery to reinforce the concept.
    STEP FIVE:
    This will be using a device-dependent Printing Profile, also called a Target Profile, in the printing dialog of the Photoshop application or the RIP used by a commercial printing outfit.  This will be a device dependent profile prepared exclusively and specifically for your particular combination of ink, paper and printer.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~
    Vincent RJ wrote:
    …I'm not referring to any conversion of numbers or RGB values…
    But of course you are Vincent RJ, you are!!!  Most definitely you are!  Why can't you grasp that basic concept? ?? !!
    With a calibrated and profiled monitor and a properly tagged image file (with the color profile of your working color space properly embedded) Photoshop will use your Monitor Profile that you set in the application as such to CONVERT and CHANGE THE NUMBERS (VALUES) of the RGB colors in your finished image BEFORE sending them to your monitor.  Every single time.  Think of that process as making up for the deficiencies of your monitor and video card combination.
    When other people look at your image, if they're using a color managed application, said application will use whatever they have set as their Monitor Profile in their setup to CHANGE THE NUMBERS of the colors in your finished image BEFORE sending them to THEIR monitors.
    If their monitors are uncalibrated and unprofiled, you don't have a prayer of a chance to control even remotely how your image will look on their screens.  That's 96% of web users, by the way. If their monitors are calibrated and profiled, the image on the screen will be reasonably close to what you see, but the gamut of their monitors (vs. your wide-gamut NEC) will necessarily change the RGB numbers and colors from what your setup does, and the variance will be greater.
    Get rid forever of your silly concept of "standardisation" or standardization, whichever way we want to spell it.  That is simply a pipe dream of yours.  If you have a big stick handy, beat up the moron who got you to believe that.  Use twice the numbers of strikes if that person is a teacher.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Lastly, I'm getting an uneasy feeling because you haven't mentioned printing at all.
    You should be aware that Color Management is defined in terms of the art and science of controlling colors from the digital image to print.  There are different variants of the definition, but they all end with the word PRINT.
    What I'm trying to say is that a person who works with images only to be observed and shown on screens does not need to bother with Color Management at all, because the minute percentage of monitor viewers I mentioned above.  Such a person can just set everything to sRGB (monitor, color space, tags, printer, etc), the lowest common denominator of profiles, and forget about anything else.
    I would hope I got through to you, but I'm not holding my breath.
    I wish you luck in your endeavo(u)rs.

  • Color Management, (Again!)

    I know this has been discussed before, but I still haven't found anything that can help me solve the issue. It's starting to become a serious barrier to professional work, so any thoughts woudl be appreciated.
    I have both the eye1Display2 and a Gretag-Macbeth color checker and regularly calibrate my monitor and camera profiles. I'm working with CS5.  The colors in Photoshop are consistently far off from every other applicaiton outside of it. Even Flickr. I assume this is because of the color management, but I've even turned that off, (which gives me a warning message now every time I bring in an image), and the issue still occurs. Worse, the colors displayed working with RAW images are now different to those in the main interface, and even then, they are NOT the same outside of Photoshop, whereas all the other packages are consistent.  My workaround right now is to save regularly and check in other packages but this is simply not good enough for adjusting curves, HSL, etc.  I do a lot of work with skintones, which are particularly color-critical.
    So my quesions are - how can I turn Photoshop's color management completely off so it's not applying any lookup at all to the color in any module?
    If I WANT it to apply the color profile from the i1Display and the X-Rite Color Checker Passport sofware, how can I know this is being done and carried through from the RAW processing to the rest of the package?
    Many thanks
    Albert Hastings

    ahast42696 wrote:
    I have both the eye1Display2 and a Gretag-Macbeth color checker and regularly calibrate my monitor and camera profiles. I'm working with CS5.  The colors in Photoshop are consistently far off from every other applicaiton outside of it.
    If what you're saying here is that a fully color-managed application, like Photoshop, is delivering color that's different from non-color-managed applications, this is just what you should expect.
    There is no such thing as system-wide color management.  It just doesn't work that way.  Individual applications do (or don't do, or even partially do) color-management.
    This is key:
    Color-managed applications perform transforms on the colors being displayed in pursuit of absolute color accuracy at the expense of consistency with non-color-managed applications.
    Corrollary:
    Some color-managed applications misinterpret some color profiles.  It happens.
    Expanding on what Dag has said in post #1 above, no transform takes place if the document profile matches the display profile.
    So... IF you're working with documents in the sRGB IEC61966-2.1 color space (aka just "sRGB" for the purpose of this discussion) and IF you want the display of these images to match as often as possible between color-managed applciations and non-color-managed applications, this is one possible direction you can take:
    1.  Set your system to associate the system-provided sRGB profile with your monitor(s). This is done via OS configuration dialogs.
    2.  Set your monitor(s) to as closely match the sRGB color space as possible.  Some monitors were manufactured to be close, and others have the ability to be set that way.  Still others can't be directly set that way, but the system response can be tweaked with the basic controls (brightness, contrast, saturation, etc., as well as the curves adjustments in the video card drivers).
    When the above conditions are met, you will see the following results:
    A.  sRGB image documents, which are the majority of those published online and are usually the default output from digital cameras, will appear consistently the same in color-managed (Photoshop) and non-color-managed applications.  Depending on your needs you can configure Photoshop to work in the sRGB color space for creating your own images (this is actually Photoshop's default).
    B.  In Photoshop and other color-managed apps you will get good overall color-management of image documents in other color spaces, though you'll see just the out-of-gamut colors (i.e., those colors from a larger color space that just can't be displayed in the sRGB color space) as fully-saturated and thus somewhat inaccurate.  In practice, most colors in most images fall within the sRGB gamut.
    C. You'll see accurate color management by the partially* color-managed Internet Explorer 9, within the constraints of item B above.
    D.  Since the sRGB color profile that comes with every Windows system is well formed, and is the default, there is a near zero chance that a color-managed application will misinterpret it and produce screwy color.  Such misinterpretation DOES happen with other profiles, a surprising number of times, even sometimes with profiles generated by good quality color measurement and profiling devices.  Color profiles are not trivial, and some software simply can't use some profiles.
    The real (non-trivial) trick in this strategy is actually getting your monitor to closely match the sRGB color space without using a monitor profile.  However, it IS possible to get it close, and for many people "close enough" + "consistent across more apps" is better than "perfectly accurate in Photoshop but mismatching other apps".  It can even be checked with a profiling device to help with the fine tuning.
    -Noel
    *IE9 interprets your document color profile and always transforms it into the sRGB color space, regardless of your monitor profile.  Thus the only way to make the colors come out right is to have the monitor actually BE sRGB.  So far, unfortunately, it appears IE10 in Windows 8 is following this same "half baked" strategy.

  • LR4 color management oversaturated colors on a dull laptop

    I'm starting to use LR4.1 on a Lenovo T500 Win7 laptop with a miserable LCD panel and with an external wide-gamut IPS Dell U3011.
    I used to use Picasa (non-color-managed), and have calibrated both displays with Eye-one display2. Its profile loads upon Win7 startup and corrects laptop colours considerably, while the change on the U3011 is hardly noticeable. I used near-native white point and gamma so that most of the laptop display's limited gamut is used, and I can work on the laptop when necessary with predictable relationship to the U3011 display.
    The color-managment of LR is markedly different; I can see it set in when moving the image more than halfway from one display to the other on the extended desktop. It slightly desaturates the U3011, which is good. And it pumps up the colors on the laptop too much: the pale-colored images do get closer, but any vivid colors are blown on the display. I'm quite positive about this because I see the saturation level in the color channel "staircases" of a sRGB test image that set in just over half-way in the R and B channel, only the G channel is relatively unaffected. In Picasa this does not occur to such extent, and the unsaturted colours are a bit more different due to different white point & gamma.
    Initially I suspected a faulty calibration, but I saw very similar behavior on a similar hw setup with LR4 but without calibration, where Win7 CM was using manufacturer-supplied color profiles for both displays. I would not like to revert to the standard sRGB display profile in Win7 CM because that'd have a bad effect on non-managed programs.
    Is there any way to make color management in LR work like non-color-managed applications? Or to adjust the white point & gamma for the laptop display by LR so that it would become more useful with vivid images (yet less accurate)?

    Remember that "calibration" is actually two procesesses: calibration and profiling. 
    Calibration brings the monitor to a defined state by correction tables to correct white point and tone response curve.  This information is loaded into the display driver at boot-up, and affects the display for virtually all programs (except a few games and such that bypass the driver). 
    Profiling measures (just measures, doesn't adjust) the colour space and other parameters of the monitor, after calibration. Generally colour space can't be altered, only measured.  It is this measurement that goes in the profile.  (Confusingly, the calibration corrections tables are also stored in the profile, despite being nothing to do with the profile!)
    Colour management is really about the profile (the profile measurement, not the calibration info).  Colour managed programs (and only colour managed programs) use the monitor profile (and the image profile) to convert the RGB values in the image from the image colour space (e.g. sRGB) to the monitor's colour space (as measured and information stored in the monitor profile). 
    So the change you see when the calibration is applied at boot-up is just that - the calibration.  Colour management happens when colour-managed programs display images to the screen.
    "The color-managment of LR is markedly different." 
    Or rather, LR is colour managed, Picasa isn't. 
    "I can see it set in when moving the image more than halfway from one display to the other on the extended desktop. It slightly desaturates the U3011, which is good. And it pumps up the colors on the laptop too much: the pale-colored images do get closer, but any vivid colors are blown on the display."
    When you drag an image from one screen to the other, are you using Lightroom (or another colour-managed application)?  In which case you shouldn't see a difference between the two monitors.  If you do, then one or both monitor profiles is probably bad.  If you're using unmanaged applications, then this is what you expect to see. One (or probably both) screens will be displaying incorrect colour.  But each will display different incorrect colour. 
    "Is there any way to make color management in LR work like non-color-managed applications? Or to adjust the white point & gamma for the laptop display by LR so that it would become more useful with vivid images (yet less accurate)?"
    Colour management in LR is always on.  And in truth, it's a bit pointless trying to make something behave "like non-color-managed applications".  Thing is: non colour managed applications will look different on every monitor.  Different unmanaged applications may look the same on your monitor, but they'll look different on someone else's.  There's no single "look" of non-managed applications. 
    The best you can do is export to sRGB for the web.  Most monitors have roughly sRGB colour space, so this is the best guess you can make at the right colour space for unmanaged browsers.  Using an unmanaged colour workflow yourself is simply adding errors in your system to errors in the viewer's unmanaged system.  It's likely to make it worse, not better!

  • IE10 Consumer Preview Still Only Does Half Color-Management

    The Internet Explorer version 10 Consumer Preview does not do full color-management - it ignores the monitor profile.
    This is not a real surprise, as I have had it confirmed to me by someone inside Microsoft, but I thought I'd just pass along that in my Windows 8 CP testing I've verified this to actually be the case.
    IE9 and IE10 do not manage the color of web page elements at all, and both interpret image color profiles in images if they're present, but they only convert the colors to sRGB, no matter what monitor profile you're actually using.  For calibrated and profiled systems, this yields inaccuracy; for example, with wide gamut monitors the colors of images carrying a profile will always be oversaturated.
    Sigh.  Progress marches on EVER so slowly.
    -Noel

    Let me try to help you further:
    1. In Illustrator's Swatch settings pallette, should the Spot Color Mode option be set to use:
    a. CMYK
    b. LAB
    c. Book Color (not sure if this refers to the pantone swatchbook)
    - I would use "c" - Book Color.  This is the file going to the printer which will use Spot Color on press.  For a copy of the file to be output by your Canon, use "a" - CMYK.
    2. In the View menu should Overprint Preview be checked, and why, and would it differ based on the settings for #1.
    - Only if the color was transparent ( which it isn't ) would overprint preview be of any use or you use a tint value of the Spot color and a black, but even then you may not be able to detect any change in the screen view.  I typically do not use any overprint preview and I do not rely on the monitor for any color deisions.  You could be different and that is OK.  Let me know if you are able to detect any deviates using overprint preview.
    I'm sorry for being a little short.  There is a lot of confusion about these issues and Adobe and Pantone are not making things any easier.
    The key is your Canon will not be able to print accurate Spot color without a RIP for the necessary color tables and conversions for that particular printer.  In your case, it will be necessary to build a CMYK file to print a somewhat  approximate representation of that specific Spot color.  Another frustrating part of this matrix is CMYK cannot match all Pantone Spot Colors.

  • 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

  • New Monitor Showing Different Colors - Monitor Profile?

    Hi All, in need of some help. I got a new Acer monitor and I am having three issues. The first is when I open photoshop I ger the following error: "Monitor Profile ACER S232HL appears to be defective. Please return your monitor calibration softwear." Then it gives me two choices, to either "Ignore Profile" or "Use Anyway". I've tried both and they both make the images appear differently. What do I do? Thinking about following directions I found here: http://virtualmcube.com/hardware/how-fix-monitor-profile-appears-be-defective-photoshop-er ror-message
    Number 2 is that when I open the same file in PS, LR, online and in the picture viewier, the colors all look different! HELP!
    Number 3 is that my images in LR seem way over saturated.
    When I first plugged in the monitor I was using HDMI and I was told that would be the best. When I ran into the above trouble it was reccmended to me that I use the DVI. The DVI did help to get richer blacks, but didn't help anything else.
    And just for a control group, I plugged my old monitor back in and everything is fine, but I'd like to use my new one! HELP! Thank you

    Canned monitor profiles are notoriously inaccurate or outright defective. Unless you want to go all the way and calibrate/profile with a third-party package, you're probably much better off just using sRGB, and that's what happens when you click "Ignore Profile".
    It's the same solution in the link you posted, only more convoluted.
    Number 2 is that when I open the same file in PS, LR, online and in the picture viewier, the colors all look different! HELP!
    Number 3 is that my images in LR seem way over saturated.
    Come back if you still see this with sRGB as the profile. In general Ps and Lr are both fully color managed and will use the full monitor profile for display. Most other applications are not, so this is not entirely unexpected in itself.
    When I ran into the above trouble it was reccmended to me that I use the DVI.
    Shouldn't matter. The two are fully compatible and the digital video signal is the same.

Maybe you are looking for

  • How can i review my account

    Hi, I buy new IPhone 4 (It is new for me),I try to download free app(by iTune), but i can't. iTune require me to review account, input Credit card bra bra ..., I don't have credit card(If i had, I wont give it to you, it is confidential), How should

  • Pair Remote ONLY with universal dock

    need some helb guys, i have a macbook pro with the remote of course. now i recently bought a universal dock for my ipod. i heard that you can pair the remote with the dock, by pressing the menu button for a while. but that didn't work, at least not t

  • Address bar too long, some addon icons are not revealed.

    When addons are many, they aggregate to a small menu. This is very inconvenient. See pictures between firefox 30 and firefox 37 I tried to upload a image. In case I failed, see http://img.vim-cn.com/0b/310455fba225df5c97986cf270e6884a1fcde2.jpg

  • Getting the WS Remote Hostname via the PRC?

    Is there any way of programatically determining the portal's WS Server name, as defined in the .properties file used for install/upgrade? I need this when calling IRemoteSession.GetExplicitLoginContext... needed to generate the URI for the first para

  • How can I set time signature for my song?

    I wanted to compose a song in Garageband in a time signature 3/4. I couldn't see any setting which lets me set it. Also I wanted to know what all time signatures do Garage Band support ?E.g. 2/3/, 4/4, 6/8,7/8 ...Would really appriciate if someone ca