Saved image displays differently outside Photoshop

When I save an image I've been working on in Photoshop, then open the saved file outside Photoshop, the image looks quite different than it does inside Photoshop, much drabber and less saturated. I have both Photoshop and the display program set to sRGB.  I figure that I should have consistency within the monitor, whether it's calibrated or not.  I'm sure I'm missing something basic here.  I'd appreciate any help here, because my prints wind up drab, too.  Many thanks!

LBJack wrote:
I overlooked one switch in the Save dialog.  Now the images display correctly.
Can you be more specific, please?
Were you saving images without a color profile before, and some application(s) in your system were displaying them improperly?
Problem is, in that case one wouldn't really expect to see the kind of difference you describe unless your document profile really wasn't sRGB IEC61966-2.1.
Is it possible you're editing your images in the Adobe RGB 1998 color space?  That could happen if you're opening images through Camera Raw, as the color space it's set to deliver is configured separately (via the link at the bottom-center of the Camera Raw dialog) from the Photoshop defaults.
By the way, if you don't already know, you can easily set the status block in the lower-left of the Photoshop window to show you the color space of your current document:
-Noel

Similar Messages

  • PS CS5 Image Display Differs From Used ICC Profile In Win 7

    Hi,
    on my Windows 7 Ultimate x64 machine, I just calibrated my Dell SP2309W monitor using an i1DisplayPro and basICColor 5, creating a ICC v2 profile (I am aware of the problems under Windows with ICC v4 profiles).
    It created the ICC profile and applied it to be used by Windows. I double checked under COLOR MANAGEMENT that the new ICC profile is being used. Although I can see that the new ICC is being used (desktop appearance changes), there are a few issues I am experiencing:
    (1.) Windows Photo Viewer
    The thumbnails in Windpows Explorer look fine (they DO use the new ICC profile), when I double click a jpeg and open the image it DOES NOT use the new ICC profile. When I click the PLAY SLIDESHOW button (starting the slideshow) in the opened image in Windows Photo Viewer, the images DO use the new ICC profile.
    (2.) Internet Browsers
    All current internet browser (Firefox, IE, Safari and Chrome) DO use the new ICC profile and display the image correctly.
    (3.) Photoshop CS 5
    When I open the same image - that Windows Photo Viewer does not correctly displays (according to the new ICC profile) - in Photoshop CS5, I get the same image display that Windows Photo Viewer gives me (when not thumbnail or not in slideshow mode) - it appears to be the sRGB display.
    My color settings in PS CS5 are: North America General Purpose 2 > sRGB IEC 61966-2.1.
    When I go to View > Proof Setup > Monitor RGB I get the image display using the new ICC profile.
    Why does the image look different in PS than my calibrated monitor should output ?
    I was under the impression (please correct me if I am wrong), that the sole purpose for calibrating my monitor was to get a uniform display across (ICC aware) applications. Even when one applies different color spaces to a document in PS, I thought the output on my calibrated screen done by the graphic card should always be according to my calibration and the settings in the ICC profile being used.
    What Am I doing wrong or what am I misunderstanding ?
    Any help or input is appreciated !
    Thanks.
    - M

    Hello,
    A note on monitor calibration: calibrating your monitor will not guarentee that every application will display color correctly, it's more of a step along the pipeline, and for the preview part of a color workflow it's the last step.  Here's how color translation follows for an ICC workflow when previewing to a monitor:
    Image Color Numbers > Document Tag or Workspace Profile > Monitor Profile
    For non-color managed applications, if the original document is or isn't tagged with a color profile it will be translated directly to the monitor profile anyway.  This is the equivalent in Photoshop of selecting "Monitor" in soft proofing.  Selecting monitor in softproofing will bypass the tagged or workspace profile to translate colors directly through the monitor profile.
    For most automatic color managed applications (like Firefox), the image will be translated through the tagged profile and then sent through the monitor profile.  If the image is untagged or the profile is unrecognized, the colors get sent directly to the monitor profile.
    For Photoshop, a tagged document will have its profile respected and then sent to the monitor.  An untagged document will be assigned the workspace profile, which acts like a temporary document profile, and then gets sent to the monitor.  This is often why users will notice Photoshop behaves differently from other applications.  It's usually a case of the workspace coming into play.  By default the workspace profile is set to sRGB.  You can change this in Edit > Color Settings.
    The purpose of the workspace is originally for printing workflows, as a way of keeping consistant color translations when dealing with both tagged and untagged documents.  For web output workflows it can be useful for viewing everything through sRGB, which is typical of the average monitor output (not so with newer wide-gamut monitors, another source of confusion...) combined with the fact that originally most web browsers were not color managed.  Hence viewing everything through sRGB is pretty close to what most monitors see and what untagged/unmanaged docs will look like.
    Monitor calibration is useful only because it brings your monitor output to a "known state".  In traditional workflows the monitor was always a middle-man, a preview device which was useful for getting an idea of what the printed output would look like before you print it.  Since print colorspaces are often smaller than display spaces, it's feasible and useful to narrow down the monitor/display space and calibrate it to a known state, so that even if it doesn't totally match the print, you'll get used to its differences/limitations and they'll be consistent so long as the calibration is maintained.
    For web output, your final output is often another user's computer monitor, which can have any form of behavior (most standard monitors are pretty close to sRGB, or use sRGB as an operating system workspace (default monitor profile).  Wide gamuts behave differently, but I'm not sure if there's a particular ICC space that they closely match, or if different wide-gamuts are even that close to each other in their display color spaces.
    Hope this helps!

  • Bug? Images look different in photoshop

    Hi,
    Am hoping somebody can help me as I must be doing something really stupid here. I'm currently evaluating various workflow products, and really like Lightroom but find that whenever I import an image into LR the tones, particular shadow tones, look way too dark. They look kinda posterised.
    My monitor is color calibrated with a spyder. I am running Windows XP.
    I've attached a link to an image to demonstrate. I took an sRGB JPEG and imported into LR. I then edited a copy in PS (exported as ProPhoto - converted in PS to Adobe 1988 colorspace), another copy is shown exported to Capture NX (also Adobe colorspace).
    http://www.hamiltonconsulting.net/strange%20tones.jpg
    if you look at the shadow tones in the folds of the jacket you can see a minor difference between PS and Capture NX but you can see a clear difference in LR. The shadows are way darker.
    The image opens fine it every other application I have tried, including the free XP viewers. LR is doing something strange to the file but I cant work out what.
    I first noticed the problem occuring in Beta 4.1 and am now getting the same issue in the new Lightroom demo ( I had hoped it was a bug that would have been fixed). I have been installing all sorts of evaluation software of late, so maybe something hasnt been cleaned out of my registry, or something is clashing.
    So far, I've tried lots of different images (all with the same problem). Recreating an image database. Reinstalling LR (countless times).
    Does anyone have any ideas as to what I can try or do I need to reinstall my entire PC

    Yeah dude, that totally makes sense.
    "I notice blocking... that... really is a function of lighting..."
    Is that some sort of new-age yet-unheard-of phenomenon? If so, please elaborate by all means.
    The point is that the image looks like crap displayed in the 'Library' module of LR, but looks fine in any other program. Because no other program is content with sitting around and displaying to you a low quality JPEG preview of your, say, high quality 16-bit uncompressed TIFF image.
    That's why there's no blocking in the image loaded up in Photoshop. Yet it's there in LR because LR doesn't bother to render the image 'on-the-fly' until you step into the 'Develop' module.
    You don't believe me? Then be happy in your ignorance.
    On another note, though, instead of jacking it up to 400% when it's clearly evident at 100%, try calibrating your monitor with a hardware profiler so dark parts of images don't become a muddy mess of blacks. Be forewarned though that it's a double-edged sword: on the one hand, after calibration, you suddenly begin to see details in shadows that you may never before have seen; on the other hand, JPEG artifacts & noise in dark portions of images (inherent to JPEG compression) also become as apparent. Hence, I'll give you the benefit of the doubt and figure you just can't see the blocking due to your monitor.
    Finally, on a LR-unrelated note, why don't you come back to these forums when you're ready to write posts free of cheap ignorant insults?

  • File displaying different from Photoshop to Illustrator

    I have a simple chalkboard background I made in Photoshop and I'm importing into Illustrator. My issue is the file displays completely different from Photoshop to Illustrator. See image below.
    I've had this happen to other files but this one is so incredibly different, I can't understand what's happening and I can't manage the design with it being this different. Any ideas?
    Thanks in advance for your help!
    Rachel

    Thanks again Monika. I can't figure this out. The color management is all synchronized among all my Adobe applications. Yes the file is in layers and when I view the JPG in Photoshop, it looks as it should. It's only when I bring it into Illustrator does it look like that. I opened up a new Illustrator doc and placed the same JPG (as well as dragged the PSD file directly from the Photoshop window into Illustrator) and it looks better and more like it should. My other doc was a new doc too so I'm not sure what happened. At any rate, I can't explain what happened and I'm just hoping it doesn't happen again.
    Thanks for your help!

  • Images displaying differently in Library view to Develop - also affecting Exports

    I've run in to a strange problem since the 4.1 upgrade.
    When displayed in the Library view, images are not appearing correctly.  In my case, there is a huge amount more noise in the Library view compared to the Develop view.  This is also affecting Exports.
    I have been unable to find any answers online, and only found one other case of this reported via a You Tube video.
    Any ideas?!
    Many thanks
    Rick

    I am assuming you have a correctly calibrated monitor calibrated using a hardware calibrator. Lightroom sometimes shows the aforementioned problems with canned monitor profiles on windows machines. Now that out of the way:
    I am also having this problem - the library view is closer to the printer output - very frustrating! In dev mode the image is lighter - sometimes appears to be too hot, but in library and during print it is just right. This was not a problem in 3 - what's the fix?
    Have you tried seeing what happens when you soft proof for the paper profile in the Develop module?
    It seem the fit views do not match up...the confusion comes in that it seems the fill views sometimes do, and sometimes do not match. when the images appear different, I've the sense in dev the images are brighter and hotter.
    This can happen if your image is very noisy or has a lot of high frequency detail. The sharpening preview in fit view that is applied in Develop tends to brighten images with lots of noise or detail. It also happens when you are applying a lot of color noise reduction and have a lot of colored detail. SInce Lightroom cannot really show you the result of this correctly but for when looking at 1:1, this results in the Fit preview showing more color saturation than there really is.

  • Image Displays Differently in PS and Br CS4

    I have a gs tif file that I converted to cmyk. In PS the cmyk version looks virtually identical on screen to the gs version although when you hold the eyedropper over the image, cyan displays as a higher percentage than m or y, with k lowest in both the cmyk conversion and the grayscale original...what do I have set wrong!  In Bridge the cmyk version clearly shows a cyan cast.
    Color settings are synchronized in CS4.
    Can anyone tell me why: 1, the images are displaying differently, and, 2. using Convert To Profile, cymk, Working CMYK US Sheetfed Coated v2, image appears to have a distince cyan cast? And why, for that matter, is the GS image showing uneven cmyk percentages?
    Thanks in advance
    J

    the images are displaying differently
    Have you proofing enabled in both of them? Even if the profiles match otehrwise, that option still has to be toggled.
    image appears to have a distince cyan cast?
    Well, if you print CMYK, you want "rich black", which means that it needs to be underprinted with another color to not look like a dull gray. Only spot black/ text black does not require that. That's not the point here, though. It's really due to the conversion being done wrong. If you really want to retain the blacks as a pure channel, use the method described. Also, if you can, in the future simply start out in CMYK to avoid these issues.
    Mylenium

  • Images displayed differently in Firefox

    I have a Dreamweaver page that displays normally in IE. But when I open it in firefox, one of the elements is displayed differently. Specifically, I have some social media icons that are supposed to be displayed horizontally, and they are in IE. But when I open the same page in Firefox, it displays those same icons vertically. How can I correct that? Thanks.
    http://www.blackexpotourweb.com/hampton.html

    This is what I see
    <style type="text/css">
    html {
        background-color: #000;
        height: 100%
    body {
        width: 1000px;
        margin: auto;
        background: url(http://www.keystonemkg.com/Hampton.gif) no-repeat;
        height: 800px;
        position:relative;
        background-image: url(Hampton.gif);
    .maintext {
        font-family: "Courier New", Courier, monospace;
    #apDiv1 {
        position:absolute;
        width:174px;
        height:305px;
        z-index:1;
        left: 289px;
        top: 329px;
    #apDiv2 {
        position:absolute;
        width:328px;
        height:449px;
        z-index:2;
        left: 138px;
        top: -49px;
    #apDiv3 {
        position:absolute;
        width:137px;
        height:126px;
        z-index:2;
        left: 448px;
        top: 417px;
    .infotext {
        font-family: Georgia, "Times New Roman", Times, serif;
        color: #FFF;
    siteinfo {
        font-family: Georgia, "Times New Roman", Times, serif;
        font-weight: bold;
        color: #000;
    .siteinfo {
        font-family: Georgia, "Times New Roman", Times, serif;
        color: #000;
    #apDiv4 {
        position:absolute;
        width:715px;
        height:22px;
        z-index:3;
        left: 253px;
        top: 804px;
    #apDiv5 {
        position:absolute;
        width:170px;
        height:242px;
        z-index:4;
        left: 46px;
        top: 408px;
        text-align: center;
    dropsha {
        border-top-style: solid;
        border-right-style: solid;
        border-bottom-style: solid;
        border-left-style: solid;
    #apDiv6 {
        position:absolute;
        width:883px;
        height:62px;
        z-index:5;
        left: 71px;
        top: 141px;
        vertical-align: middle;
        text-align: center;
    #apDiv7 {
        position:absolute;
        width:170px;
        height:69px;
        z-index:4;
        left: 51px;
        top: 710px;
        text-align: center;
    #apDiv4 .infotext .siteinfo {
    eventtext {
        font-family: Georgia, "Times New Roman", Times, serif;
    #apDiv8 {
        position:absolute;
        width:181px;
        height:27px;
        z-index:6;
        left: 281px;
        top: 327px;
        font-weight: bold;
    a:link {
        color: #FFF;
    a:hover {
        color: #F00;
    #apDiv9 {
        position:absolute;
        width:200px;
        height:115px;
        z-index:6;
        left: 16px;
        top: 764px;
    .maintext1 {    color: #FFF;
        font-family: Georgia, "Times New Roman", Times, serif;
    #apDiv10 {
        position:absolute;
        width:115px;
        height:36px;
        z-index:6;
        left: 831px;
        top: 716px;
        float: left;
    #rightjust {
        text-align: right;
    #apDiv11 {
        position:absolute;
        width:868px;
        height:53px;
        z-index:7;
        left: 77px;
        top: 214px;
        text-align: center;
    </style>
    What you need to do is add the bold part into this as per
    <style type="text/css">
    html {
        background-color: #000;
        height: 100%
    body {
        width: 1000px;
        margin: auto;
        background: url(http://www.keystonemkg.com/Hampton.gif) no-repeat;
        height: 800px;
        position:relative;
        background-image: url(Hampton.gif);
    .maintext {
        font-family: "Courier New", Courier, monospace;
    #apDiv1 {
        position:absolute;
        width:174px;
        height:305px;
        z-index:1;
        left: 289px;
        top: 329px;
    #apDiv2 {
        position:absolute;
        width:328px;
        height:449px;
        z-index:2;
        left: 138px;
        top: -49px;
    #apDiv3 {
        position:absolute;
        width:137px;
        height:126px;
        z-index:2;
        left: 448px;
        top: 417px;
    .infotext {
        font-family: Georgia, "Times New Roman", Times, serif;
        color: #FFF;
    siteinfo {
        font-family: Georgia, "Times New Roman", Times, serif;
        font-weight: bold;
        color: #000;
    .siteinfo {
        font-family: Georgia, "Times New Roman", Times, serif;
        color: #000;
    #apDiv4 {
        position:absolute;
        width:715px;
        height:22px;
        z-index:3;
        left: 253px;
        top: 804px;
    #apDiv5 {
        position:absolute;
        width:170px;
        height:242px;
        z-index:4;
        left: 46px;
        top: 408px;
        text-align: center;
    dropsha {
        border-top-style: solid;
        border-right-style: solid;
        border-bottom-style: solid;
        border-left-style: solid;
    #apDiv6 {
        position:absolute;
        width:883px;
        height:62px;
        z-index:5;
        left: 71px;
        top: 141px;
        vertical-align: middle;
        text-align: center;
    #apDiv7 {
        position:absolute;
        width:170px;
        height:69px;
        z-index:4;
        left: 51px;
        top: 710px;
        text-align: center;
    #apDiv4 .infotext .siteinfo {
    eventtext {
        font-family: Georgia, "Times New Roman", Times, serif;
    #apDiv8 {
        position:absolute;
        width:181px;
        height:27px;
        z-index:6;
        left: 281px;
        top: 327px;
        font-weight: bold;
    a:link {
        color: #FFF;
    a:hover {
        color: #F00;
    #apDiv9 {
        position:absolute;
        width:200px;
        height:115px;
        z-index:6;
        left: 16px;
        top: 764px;
    .maintext1 {    color: #FFF;
        font-family: Georgia, "Times New Roman", Times, serif;
    #apDiv10 {
        position:absolute;
        width:115px;
        height:36px;
        z-index:6;
        left: 831px;
        top: 716px;
        float: left;
    #apDiv10 img {
        float: left;
    #rightjust {
        text-align: right;
    #apDiv11 {
        position:absolute;
        width:868px;
        height:53px;
        z-index:7;
        left: 77px;
        top: 214px;
        text-align: center;
    </style>
    and remove the float: left that you placed in the meantime under #apDiv10
    Gramps

  • Uploaded image colours different to photoshop

    Hi, I've never had this experience before, however I started using lightroom 3 and photoshop CS4, and the colour calibration from photoshop to uploading is completely different. The only way past it is I've found to screen dump it, then save it as a png, yet the colours are still very distraughted .
    http://photos-c.ak.fbcdn.net/hphotos-ak-snc3/hs177.snc3/20451_1239212413707_1031169870_305 66108_2408780_n.jpg
    image 2 (saved as a high quality jpeg from the TIFF):
    http://photos-h.ak.fbcdn.net/hphotos-ak-snc3/hs197.snc3/20451_1238513876244_1031169870_305 64537_3460636_n.jpg
    image 2 (saved as a screen dump as a png)
    http://photos-d.ak.fbcdn.net/hphotos-ak-snc3/hs197.snc3/20451_1239215293779_1031169870_305 66113_7213148_n.jpg
    Slightly better then the last but the colours are still completely wrong. The colours are fine when I send the picture over by email to someone, the colours are also fine in programs like word, paint and fax viewer (which you would expect to have no colour correction).
    For the first image I showed, I combined it together, then I cropped it, saved it as a jpeg, and it still had the distraughted colours, I had to save it in png. I can't directly save it as a png because the colours are still distraugted :/
    All browsers I've tried have done it, as on my friends computer. We've tried Firefox, chrome, internet explorer and oprah, ff on linux also.
    Photos have been 16 bit modified to 8 bit, however, I've done that plenty of times in the past and its made no difference to the colours. 2nd image is 16 bit png and still weird :/
    I've also tried to upload them to about 5 differnet sites, (facebook, devientart, flickr, imageshack & photo.net gallery). Attachments also do not look fine (however attachments for other sites do :/ *is very stumped*
    Please help. *note, 1st image was edited in lightroom > cs4 > cs3*
    Thank you

    Both images are RGB, I think it might be something to do wiht lightroom, since when I import it into lightroom to CS4 save it and then go into CS3. Colour space is RGB, and both pictures have been converted into 8 bit, however, wihtout the conversion, they still have the desaturated colours.
    Before I was using Adobe CS3 and the in built RAW photo editor, which has been fine. Ever since I've been using lightroom / CS4 combination (I switched both programs at the exact same time), its been a problem. However some images have a greater effect then others (for black and white you hardly notice).
    Would it have something to do with the rendering mode in lightroom? Since I do not have the correct graphics drivers to render in CS4 because my fan doesn't work in my GPU...its holding on till I get a new one, barely...

  • Image display problem in photoshop cs6

    when i open any image in photoshop,its looks like washout but it looks fine in windows image viewer
    here is an example:

    an unprofiled image with the two application using different working spaces?
    that is most likely from where i sit...maybe if the OP included the profile in his screenshot (instead of Doc info) it would be easier to shed light on the problem
    Windows apps likely send untagged/unmanaged RGB straight through to the monitor unaltered (just like they do on the Mac)
    that should be easy to observe displaying one of the extreme colorspaces like ProphotoRGB or WhackedRGB images (or even with a sRGB document if one knows what to look for)
    whereas -- when we don't use the embedded profile or don't color manage the RGB document in Photoshop -- Photoshop Assigns (for all practical purposes) its working RGB, then Converts it to the monitor profile...

  • Why do images appear different in Photoshop after being processed in Adobe Camera Raw?

    I would assume that the screen image would appear the same in each application.

    Probably you are using different color profiles in the two applications, eg: you are using Adobe RGB (1998) in photoshop and sRGB IEC61966-2.1 in Camera Raw, this causes differences in color and in some cases large differences, such as lack of vibrance and saturation.
    check the profiles you are using:
    Camera Raw:
    just check the blue text under the image, to change it just left clik with the mouse, a windows will apear.
    Photoshop:
    In Photoshop just press Alt+Shift+K or follow de above image.
    Sorry, but, my Photoshop language is Portuguese.

  • Image looks different in Photoshop and Lightroom

    I started a forum on flickr and I have some issues with my images.  I have  calibrated monitor but my images look off online even though I saved them as sRGB.  Now my image looks one way in PS and then when I finish editing it and save it, I import it into lightroom and it looks different.
    Same image, but it looks different.
    http://www.flickr.com/groups/photoshopsupport/discuss/72157626443796391/#comment7215762645 5942911

    The image on the left in PS looks the same in Picasa Image
    Viewer (I selected it to be color managed based on the monitor profile), looks the same in Windows Image Viewer, and looks the same in the thumbnail.  The image on the right in LR is how the picture looks when I look at my image in Firefox but in Internet Explorer and in Chrome, the image looks like the image on the left in PS.  The image below shows how the thumbnail looks different from the actual picture when it's double clicked and viewed in Picasa.  The thumbnail (which shows the subjects having green skin) would be how I saw it online while the double clicked version is how I saw it in PS, even though it was sRGB (I checked the image properties to make sure of the color space).
    I have a ATI 5470 GPU on my ASUS 17.3 inch laptop.  Not sure about the drivers.

  • Saved images appear as 72dpi Photoshop CS3 Extended

    Hi
    Suddenly my images which have been saved at 300dpi are coming up as 72dpi when I re-open them in Photoshop CS3 Extended.
    I create a psd file at 300dpi, work on it, save it as a maximum quality jpeg/png etc, but when I open it up in Photoshop again it appears as 72dpi. Even the finished jpeg/png file sizes seem too small. I'm creating business cards and graphics for customers and I must know they are saved at 300dpi.
    Can anyone help? Do you think I may have a bug? Fairly sure it's fully updated.
    Thanks!

    One qualification is that my comments were derived from Photoshop CS4. 
    In that setup a file saved in SFW at 333 ppi and with the All meta data box checked produces a jpeg file, which when opened in Photoshop, shows the resolution (from the Image size dialog box) to be 72 ppi.
    If I then click on File > File Info > camera data it shows the resolution to be 333
    If I look at the so-called Raw data in the SFW file I indeed find the resolutions specified
    Photoshop Version difference ?  Perhaps.  Or, maybe I got one of the platinum editions   . So for CS4 I find that when I ask to have the meta data saved via SFW it seems to happen.
    Paulo

  • Bug? Corrupt Tones / Colours - Image looks different in photoshop

    Hi,
    Am hoping somebody can help me as I must be doing something really stupid here. I'm currently evaluating various workflow products, and really like Lightroom but find that whenever I import an image into LR the tones, particular shadow tones, look way too dark. They look kinda posterised.
    My monitor is color calibrated with a spyder. I am running Windows XP.
    I've attached a link to an image to demonstrate. I took an sRGB JPEG and imported into LR. I then edited a copy in PS (exported as ProPhoto - converted in PS to Adobe 1988 colorspace), another copy is shown exported to Capture NX (also Adobe colorspace).
    http://www.hamiltonconsulting.net/strange%20tones.jpg
    if you look at the shadow tones in the folds of the jacket you can see a minor difference between PS and Capture NX but you can see a clear difference in LR. The shadows are way darker.
    The image opens fine it every other application I have tried, including the free XP viewers. LR is doing something strange to the file but I cant work out what.
    I first noticed the problem occuring in Beta 4.1 and am now getting the same issue in the new Lightroom demo ( I had hoped it was a bug that would have been fixed). I have been installing all sorts of evaluation software of late, so maybe something hasnt been cleaned out of my registry, or something is clashing.
    So far, I've tried lots of different images (all with the same problem). Recreating an image database. Reinstalling LR (countless times).
    Does anyone have any ideas as to what I can try or do I need to reinstall my entire PC :-(

    The image on the left in PS looks the same in Picasa Image
    Viewer (I selected it to be color managed based on the monitor profile), looks the same in Windows Image Viewer, and looks the same in the thumbnail.  The image on the right in LR is how the picture looks when I look at my image in Firefox but in Internet Explorer and in Chrome, the image looks like the image on the left in PS.  The image below shows how the thumbnail looks different from the actual picture when it's double clicked and viewed in Picasa.  The thumbnail (which shows the subjects having green skin) would be how I saw it online while the double clicked version is how I saw it in PS, even though it was sRGB (I checked the image properties to make sure of the color space).
    I have a ATI 5470 GPU on my ASUS 17.3 inch laptop.  Not sure about the drivers.

  • Same image displaying differently in FF and IE6

    This has me beaten
    http://wrfinn.com/map_leros.html
    (login/password fred) - the first image (I know it's out of
    alignment...
    later, later).
    What is displaying in FF is the original image before the
    circle/text was
    added.
    I have deleted it from the server and replaced it
    (desperation as it's fine
    in IE6) checked the scripts are there although I've tested it
    without the
    javascript with no better results. The DOM inspector is
    showing an error on
    the page in FF if this helps -
    [Exception... "'Permission denied to get property
    XULElement.accessKey' when
    calling method: [nsIDOMXULLabelElement::accessKey]" nsresult:
    "0x8057001e
    (NS_ERROR_XPC_JS_THREW_STRING)" location: "JS frame ::
    http://wrfinn.com/map_leros.html
    :: jspw3 :: line 43" data: no]
    <li><a href="#" class="p7PMtrg">About
    Us</a>
    Could somebody possibly throw some light on this?
    Jo

    josie1one wrote:
    > This has me beaten
    >
    >
    http://wrfinn.com/map_leros.html
    > (login/password fred) - the first image (I know it's out
    of alignment...
    > later, later).
    >
    > What is displaying in FF is the original image before
    the circle/text was
    > added.
    >
    > I have deleted it from the server and replaced it
    (desperation as it's fine
    > in IE6) checked the scripts are there although I've
    tested it without the
    > javascript with no better results. The DOM inspector is
    showing an error on
    > the page in FF if this helps -
    >
    > [Exception... "'Permission denied to get property
    XULElement.accessKey' when
    > calling method: [nsIDOMXULLabelElement::accessKey]"
    nsresult: "0x8057001e
    > (NS_ERROR_XPC_JS_THREW_STRING)" location: "JS frame ::
    >
    http://wrfinn.com/map_leros.html
    :: jspw3 :: line 43" data: no]
    > <li><a href="#" class="p7PMtrg">About
    Us</a>
    >
    > Could somebody possibly throw some light on this?
    >
    Hey Jo,
    did you get this resolved? - I don't see the problems that
    you are
    describing nor do I get a dom inspector error.
    The only thing I see is that the image which should reside
    under the
    side nav - you haven't set a path/source for this.
    chin chin
    Sinclair

  • Background image displays differently when published

    I am using Captivate 5. I did a software simulation  and in Captivate the background image is correct (the one on the left) but when i preview it or publish it and view in the browser the colors are off (second image) ..I tried to play around with the brightness/sharpness but it did nothing dramatic...any suggestions?
    Hi,

    Hi there
    Generally speaking, Optimized ofen works well too. I'm unsure of the file size differences (if any) between the two settings. Because the image quality improves it would be logical to assume that the file size will increase.
    Cheers... Rick
    Helpful and Handy Links
    Begin learning Captivate 5 moments from now! $29.95
    Captivate Wish Form/Bug Reporting Form
    Adobe Certified Captivate Training
    SorcererStone Blog
    Captivate eBooks

Maybe you are looking for

  • How do I set ical default values in lion?

    I have just upgraded to Lion and so far, so good.  In the new iCal, how do I set the default values?  In the old version, when you clicked on the calendar, the default value was a 1 hour meeting around the current time of day.  The new version defaul

  • Problem with nesting repetitive groups, using PDF as template

    We are trying to use a pdf file (Acrobat 5.0) as a template for BI Publisher reports. Our report uses as a data source a xml file (facturas.xml) with data from several bills. In each bill, there are areas where multiple lines must be displayed. We us

  • IPhoto doesn't recognise iPhone

    This is contrary to what most are experiencing! I have some photos on my 3G iPhone and cannot get them into iPhoto (08). I have tried turning off the auto-sync with iTunes. I've toggled the auto-import in iPhoto. It worked last week! All I can think

  • Placement of additional fields while enhancing OM infotype

    Hi All,     As per our client requirement we need to create two additional fields in IT1051. We have tried creating the same but the fields we need are to be at the center of the screen as per the client requirement as shown in image1 but its coming

  • Dynamic Mapping concept

    I have a requirement as follows: This is related to data migration from legacy to CRM system. 1.I have a data file from legacy sytem which is mapped to CRM system based on some rule.This is uploaded into program into an internal table. 2.I have a map