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

Similar Messages

  • 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

  • Indesign image display is very slow and jerky

    good morning
    I contacted Adobe Customer Service in Italy because I have big problems with the Creative Suite CS 5.5, in particular with Indesign and in general with the display of images of AI and Acrobat.
    As I work with Indesign image display is very slow and jerky. Even with AI and Acrobat work experience is not good, the images are jerky and there are hesitations in the fluidity of view.
    The software is installed on windows 7 64bit Utlimate, the workstation is very powerful: Supermicro motherboard, dual Xeon E5620 2.4ghz, 16gb ram, SSD OCZ vertex4, PNY Nvidia Quadro 4000.
    The customer service has sent me several tips for email, I have followed all the instructions but I did not get results. In conclusion, when I pointed out that reading on the forums I was not the only one who showed this problem and after discussing about my hardware configuration, they told me that the problem is probably due to the fact that I have two Xeon processors!
    In efects had observed that CS 5.5 on my notebook works better, but I never thought about having problems because the PC is powerful. I checked the CPU and GPU when using Indesign and I could see that uses a single CPU, and most "only 1 core"! But of CPUs in the system there are two for a total of 8 cores. Indesign seems to use only 1/8 of the available computing power ... In addition, practically does not use the GPU (only 10-15%).
    From the customer service was suggested to disable or remove a processor from the system. All this seems to me incredible. I use the workstation for applications that can take advantage of the power of the machine, should I remove the processor whenever I have to use CS 5.5? If things are this way I'm thinking of asking if Adobe buy me a PC with a single processor only for use with CS 5.5 ...
    Thank you.

    Interesting idea, I'll investigate in this direction, I should try to make a mirror of the ssd on a traditional hard drive, exchange them and see if the situation changes. It must, however, be a further factor in the eventual bad combination hardware ... on my laptop I have: windows 7 x64, intel core i7 processor, 16gb of ram, nvidia quadro 3000m, and .... a ssd ocz agility 3, but indesign is more responsive.
    But why indesign should be influenced by the hard-drive? With 16gb of ram and working files on NAS because in design interacts with the hard drive?

  • Why do my (raw) pictures display differently in LR2 and CS4 ???

    Hello,
    When I "Open with CS4" from LR2 the pictures seem to be opened as "raw" unprocessed pictures. LR2 did not ask for any options (which it does once I have modified the image in LR2). The raw develop screen from CS4 does not open...
    any Ideas?
    cu,
    Michael

    Indeed the Monitors (3 of them) are calibrated. I use a Spyder3Elite for calibrating. All three monitors show the same effect in any combination of LR2 and PS-CS4 displayed on the same or different monitors. To my knowledge I've never touched any settings within any adobe product that involves monitor adjustment and never had any problems with PS-CS3 using the same constellation.
    Do you have any suggestions of where to look, or which settings to check?
    Thanks,
    Michael

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

  • 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

  • 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 size different in debug and publish

    My project is purely actionscript based movie. I am trying to
    display an image file (jpg) that is received from the movie server.
    The image file displays with corect zoom dimensions when in
    development environment but after the movie is published...the
    image displays full size (612x494). It gets more
    wierd...occassionally it works correctly (displays image with
    correct zoom) after several tries of publishing the movie.
    Any ideas what might be the cause of this? Please help!!!
    regards,
    staylor
    >>>>>>>>>More
    Info:>>>>>>>>>
    the following code is executed to size up the image after
    image load is complete.
    viewPort_width_ = 450;
    viewPort_height_= 350;
    var zoom : Number = 1;
    var scale : Number = 100 * zoom;
    image_.scrollRect = new Rectangle(0 / zoom,0 /
    zoom,viewPort_width_ / zoom,viewPort_height_ / zoom);
    image_._xscale = image_._yscale = scale;

    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.

  • Image size different in debug and in publish

    My project is purely actionscript based movie. I am trying to
    display an image file (jpg) that is received from the movie server.
    The image file displays with corect zoom dimensions when in
    development environment but after the movie is published...the
    image displays full size (612x494). It gets more
    wierd...occassionally it works correctly (displays image with
    correct zoom) after several tries of publishing the movie.
    Any ideas what might be the cause of this? Please help!!!
    regards,
    staylor
    >>>>>>>>>More
    Info:>>>>>>>>>
    the following code is executed to size up the image after
    image load is complete.
    viewPort_width_ = 450;
    viewPort_height_= 350;
    var zoom : Number = 1;
    var scale : Number = 100 * zoom;
    image_.scrollRect = new Rectangle(0 / zoom,0 /
    zoom,viewPort_width_ / zoom,viewPort_height_ / zoom);
    image_._xscale = image_._yscale = scale;

    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.

  • 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

  • Same colors display differently between Illustrator and Photoshop

    Hi there,
    I would love to know why the same colors display differently between my Photoshop and Illustrator apps (CS3). For example, a logo will display much darker or more vividly in Illustrator than in Photoshop, same file, same colour values. My color settings are synchronized from Adobe Bridge to North American Pre Press 2. I've opened the logo file in RGB color mode, in both apps. It would be so helpful if both apps displayed the colours consistently.
    Any suggestions on how to do this would be wonderful!
    Thanks!
    Bobbie

    Hello Bobbie,
    I am using CS3 too and let me tell you that this Illustrator version is the worst ever. You best bet is to take the "Eye Drop" tool and select the Photoshop element to match the color.
    CS4 also have problems when handle placed items. Sadly I can tell you that CS2 is more reliable than CS3 and CS4.
    Not even if you use Pantone colors will match, Illustrator will change the colors making it impossible to match. "Adobe Quality"

  • Embedded fonts display differently in mx and spark

    Hi there,
    My apologies if this is an known issue but I have not been able to find any posts describing this problem. As the title of the discussion describes the problem I see is that when embedding the same font for spark and mx components they display differently to the point of making the application look sloppy. I created a small app to illustrate the problem:
    <?xml version="1.0" encoding="utf-8"?>
    <s:Application
        minWidth="955" minHeight="600"
        xmlns:fx="http://ns.adobe.com/mxml/2009"
        xmlns:s="library://ns.adobe.com/flex/spark"
        xmlns:mx="library://ns.adobe.com/flex/mx">
        <fx:Declarations>
            <!-- Place non-visual elements (e.g., services, value objects) here -->
        </fx:Declarations>
        <fx:Style>
    @namespace s "library://ns.adobe.com/flex/spark";
    @namespace mx "library://ns.adobe.com/flex/mx";
    @font-face
    src:url("arial.ttf");
    fontFamily: arialCFF;
    embedAsCFF: true;
    @font-face {
    src:url("arial.ttf");
    fontFamily: arialNoCFF;
    embedAsCFF: false;
    advancedAntiAliasing: false;
    s|Label
    fontFamily: arialCFF;
    fontSize: 20px;
    mx|Label
    fontFamily: arialNoCFF;
    fontSize: 20px;
    </fx:Style>
        <s:layout>
            <s:VerticalLayout
                paddingLeft="10"
                paddingTop="10"/>
        </s:layout>
        <s:Label text="This is a label that uses spark"/>
        <mx:Label text="This is a label that uses mx"/>
    </s:Application>
    I used the Arial.ttf font I found in my mac, though I have also tried with courier new and even the myriad web pro provided with an example in the SDK. Also I have tried with SDKs 4.1, 4.5 and 4.5.1. I have played with the value of advancedAniAliasing as well. Regardless of the combination I will still see differences such as this:
    Is this a known issue? Any solutions at hand?
    Thanks in advance for the help!!

    Hi there,
    Thanks for the quick reply. I was able to make fonts display correctly after hacking the display of some components (mx.controls.FormItem for example) however I did notice a whole buch of runtime warnings that showed up as a result of the workaround such as:
    warning: incompatible embedded font 'arialCFFFont' specified for mx.core::UITextFormat. This component requires that the embedded font be declared with embedAsCFF=false.
    TextFieldAutomationHelper:captureSelection() - 'selectionBeginIndex' is not implemented in FTETextField.
    And in some cases for components I do not even use:
    warning: incompatible embedded font 'arialCFFFont' specified for mx.controls::TextInput (TextInput1967) . This component requires that the embedded font be declared with embedAsCFF=false.
    Any ideas on how to avoid this noise or do we have to live with this?

  • In Lightroom CC images look different in Library and Develop modules. After output, images do not appear as they do in Develop.

    As above.

    Mac OS X 10.9.5 has a color management bug that can lead to colors appearing different in Develop and Library: Jao's photo blog: Serious color management bug in Mac OS 10.9 "Mavericks" . See also: Jao's photo blog: Further quantification of the Mavericks color management problem and Jao's photo blog: Color management in Safari is broken in Mavericks too. Sorry for all the links to my blog, but this bug really annoys me and it bugs me that it hasn't been fixed all these months that Mavericks has been out. This can lead to color shifts especially in the deep tones. You can sometimes work around it by turning on soft proofing and proofing to adobeRGB or sRGB. Adobe could fix this but they haven't so far. Apple could fix it too, but they haven't until now. They fixed some code that lead to Aperture working correctly but Lightroom still has the problem.

  • HT2946 Why is the contrast of my images totally different when processed and then opened in CS4?  Does anybody else have this issue?

    Why does the contrast in my images processed in Aperture look markedly different when opened in CS4?  The images look fab on the screen in Aperture - even if these are then opened in CS4 from Aperture they look different  - much flatter.  This is a new issue.  I am a wedding photographer and an album processed in Aperture has been sent back by my wedding album printer saying the images all lack contrast!  Can anybody shed any light on this!  I have checked colour spacing etc! 

    I Also have this problem!!
    In my situation, the screen simply started exhibiting the same symptoms a few weeks ago (early February) for no apparent reason.  At first I thought the screen was dead, but discovered the heat solution by accident.  Now I turn it on and keep it from going to sleep until I go to bed.  Thank goodness the battery is still awesome on this thing.
    I bought it new and still has the original screen, I keep it at home (never below 62 degrees).  Coincidentally, this happened a day or two after the expiration of the warranty!!  Any help figuring this one out would be eternally appreciated.
    iPad mini retina Wi-Fi, iOS 8.1.3

  • Images Appear Different When Viewed in Photoshop CS4 vs. LR 2.7

    Hello, I hope someone on this forum can help.
    I have a series of high quality images that are catalogued using Lightroom 2.7.  Many were edited using Photoshop while others were edited in the "Develop" module of Lightroom.  All of the images look exceptional in both Lightroom and Brdige.  However, when I open some of the images in PS, either directly from Bridge or by using the "Edit in" command from Lightroom, they appear washed out and dull -- very different and much worse.  I always use the setting, "Edit a Copy with Lightroom Adjustments."  The problem pertains to all images regardless of file format (JPEG, DNG, NEF, etc.) and regardless of whether they are opened from LR, Bridge or directly from the image using the "Open with" command in Windows.
    This happens on two completely different set of monitors.  At work I have a Dell 2208 WFPt UltraSharp monitor, and at home a dual monitor setup with an Asus VE278Q and an LG flat screen (all are flat screen, high quality monitors).  I have a Lenovo X201s with 8gb of RAM and a high-speed i7 processor running Windows 7, 64-bit.  All of my Adobe products are up-to-date.  Windows Color Management shows all displays as "Generic PnP Monitor - Intel HD Graphics," and the Advanced mode of Intel's HD Graphics correctly identifies each monitor being used.  The problem is identical regardless of which monitor is being used and it does not seem to make any difference as to which color profile is associated with the monitor (I have two profiles added -- Adobe RGB (1998) (the default) and sRGB IEC61966-2.1).
    Specifically, if I double-click on a particular TIF image in Bridge (where the preview looks great), it then triggers Camera Raw 5.7 - TIF, where again the image looks terrific.  The settings applied by Camera Raw are "ProPhotoRGB; 16 bit; 3607 by 2420 (8.7MP); 300 ppi" (although changing these settings makes no difference whatever when the image is subsequently opened in Photoshop).  When the image is opened in Photoshop it looks terrible -- dull and washed out.  I encounter the exact same problem when using my dual monitor setup at home, so I don't think monitor calibrations are the cause.
    Strangely, I don't think this problem existed a couple of months ago.  I've been busy on a project and haven't used Photoshop since the end of this past July (of 2011).  As I recall, this problem did not exist then, so I'm wondering if a setting in Photoshop inadvertently got altered since then.
    I have the following key settings in Photoshop's "Color Settings":
    Working Spaces: RGB -- ProPhoto RGB
    Color Management Policies -- Preserve Embedded Profiles
    Conversion Options -- Adobe (ACE)
    I have the following key settings in Lightroom's "Preferences / External Editing":
    Edit in Adobe Photoshop CS4
    File Format -- PSD; Color Space ProPhoto RGB, 16-bits, 300 dpi
    File Format -- TIFF; Color Space ProPhoto RGB, 16-bits, 300 dpi
    I have tried and tried to figure this out, to no avail.  Any help would be greatly appreciated!
    Bob Woods
    St. Paul, Minnesota

    Thanks, I think you're right.
    Any suggestions for a cheap and easy way to calibrate my monitors?

Maybe you are looking for