Camera Raw vs Lightroom Color Spaces

I photographed RAW image of a Gregtag color target with my Nikon D300 and opened it in camera raw in the ProPhoto Color space and adjusted the develop sliders so that the tone squares on the bottom row matched the ProPhoto values, (e.g approx 238,189,144,103,66,37) and ran the Robert Fors calibration script.
So far so good. I have read that all one needs to do is use the same settings in Lightroom. But when I opened the exact same RAW file in Lightroom and use the exact same develop and calibration settings that I used in ACR, it gives different values for the tone squares. And in fact the values are almost exactly the values for Adobe RGB (e.g. approx 242,200,159,121,84,53). And when I open that file in Photoshop from Lightroom using the ProPhoto color space option the value stay at the same Adobe RGB levels within the ProPhoto color space.
What am I missing/doing wrong?

the values in lightroom are not based on prophotoRGB, but on a prophotoRGB-derived space with the same primaries but with a sRGB tone curve. Since adobeRGB has almost the same tonecurve as sRGB, your values came out close. Bottomline is that the values do not correspond to the ppRGB values in ACR.

Similar Messages

  • Camera raw 8.7 color and contrast shifts when file opened in ps 6

    camera raw 8.7 color and contrast shifts when file opened in ps 6

    Thanks ssprengel for the suggestions and running a side by side yourself. I went through all my settings and applied your suggestions and did a side by side each time. I even uninstalled the entire creative suite on my system then reinstalled and updated and I still get the same outcome. It was fine yesterday with the previous version of ACR. It seems like the updated version is not showing the image preview in any color space. When I switch the color space in the workflow options the histogram changes but it doesn't seem to affect the preview window. And yes the preview button was checked on it was just when I was using the screen grab tool in windows it took focus away from the application so that is why the settings appear grayed out. I have attached more screen grabs below illustrating all my settings. Also here is some system info if anyone out there has a similar setup and would be willing to test.
    Adobe Photoshop Version: 13.0.1 (13.0.1.3 20131024.r.34 2013/10/24:21:00:00) x64
    Operating System: Windows 7 64-bit
    Version: 6.1 Service Pack 1

  • How do I install the RC updates to my PS CC, camera raw and Lightroom?

    How do I install the RC updates to my PS CC, camera raw and Lightroom? I have downloaded the correct versions from the Lab site but I still can't open my Nikon D-610 RAW files. The site says follow on screen instructions but I have not found any. Help please.

    Please ensure that for CC you have downloaded ACR 8.3 - CC:
    http://labs.adobe.com/downloads/cameraraw8-3-cc.html
    Please extract the downloaded .zip file to Desktop and then run .exe file.
    After successful installation try opening D610 files, This should work.
    Regards,
    Ashutosh

  • How do I get the latest camera raw for Lightroom 4.2?

    How do I get the latest camera raw for Lightroom 4.2?

    You simply run the updater. if there is a newer version, it will be installed. Other than that 4.2 is the latest release version, 4.3 is currently in the final testing stages and can be downloaded from the Adobe Labs pages.
    Mylenium

  • Are there new updates for camera raw for Lightroom 4, or only for Lightroom 5, as in 5.3 ?

    Are there new updates for camera raw for Lightroom 4, or only for Lightroom 5, as in 5.3 ?

    There will be no further camera support updates for Lightroom 4 beyond what is already listed in this table.
    http://helpx.adobe.com/creative-suite/kb/camera-raw-plug-supported-cameras.html
    Only current versions of Lightroom (currently Lightroom 5.3) will have further camera support added.
    If you need to work with Raw files from new cameras you'll either have to upgrade to Lightroom 5 or join the Photoshop Photography Program (to get PC CC + LR5 + extras) or convert to DNG using Adobe's free DNG converter.

  • Camera Raw shows wrong colors

    since update or pushing button " reset Camera Raw settings"
    Camera raw shows wrong colors and wrong brightness.
    (Adobe RGB, Eizo CG245W)
    Photo has not been converted or anything else.
    Bridge shows correct collors.... opening in Camera Raw the Photo is much
    too magenta and bright....at last opened from Camera Raw in photoshop colors
    look normal like in bridge before...(no modificatio made)

  • Camera RAW: NEF - JPG color dessaster

    Hallo...
    I use PS CS4 on my Mac. Normally I use Camera RAW to convert my D90 NEF-files to JPG-files without using Photoshop.
    In Camera RAW look all colors great. When I convert the 12Bit-Raw-files to 8Bit-JPG's all colors look sad and gray.
    Where is my mistake??
    In the export-dialog it's not important if i set 16-bit export or 8-bit export - the colors look like crap!
    The only workarround i found is to rise the saturation and dynamic for 15-25 points. Is there no better way?

    If you are saving to JPG directly out of Camera RAW and not enhancing further in Photoshop then you should probably save as sRGB, especially if you are putting the JPGs out for people to see on the internet. 
    What could be happening is that you’re saving as ProPhotoRGB or AdobeRGB but the viewer you’re using to verify the colors is not doing color-management properly so it is interpreting the colors as if the JPG was sRGB even though it’s not.
    If you are going to be editing in Photoshop then keep the colorspace in ACR as 16-bit ProPhotoRGB and do the conversion to 8-bits and sRGB in PS just before saving as JPG.

  • Two questions about Camera Raw and Lightroom

    I am now shooting in RAW image format only and cataloging those images into Lightroom.
    My first question is: How do I open an image in Camera Raw from Lightroom? When I right click on an image in Lightroom it gives me a choice to edit in > Photoshop, but does not offer the choice of editing in Camera Raw. In fact, when I go outside of Lightroom and just double-click on one of those RAW images, it opens in Photoshop. What is going on? Before I installed Lightroom, double-clicking on a RAW file would cause it to open in Camera RAW.
    My second question is: Lightroom seems to have all of the same controls over processing a RAW image as the Camera Raw plug-in does. Does that mean I no longer need to open images in Camera Raw? Should I just do all of my adjustments inside of Lightroom? I take it that the sidecar xmp file is the same whether modified in Lightroom or in Camera Raw.
    Pleas set me straight on this.
    Thank You,
    Ken

    Your second question:
    My second question is: Lightroom seems to have all of the same controls over processing a RAW image as the Camera Raw plug-in does.
    Answers your first. Lightroom and ACR share code, so the rendering you get from Lightroom with the same settings is exactly the same as in ACR. What happens is that when you say "edit in Photoshop", ACR gets called by Lightroom and the Develop settings get passed along. ACR then renders the RAW with those settings and opens it in Photoshop. So, because you already have a working interface to the settings, there is no point in showing them to you again.
    Does that mean I no longer need to open images in Camera Raw? Should I just do all of my adjustments inside of Lightroom?
    That depends on your workflow. I no longer open any images in ACR directly as Lightroom provides a more effective interface in my opinion. Other people I'm sure prefer the Bridge/ACR approach.
    I take it that the sidecar xmp file is the same whether modified in Lightroom or in Camera Raw.
    Lightroom does not modify the sidecars by default. All edits are stored in the database. This allows you to have virtual copies with different Develop settings and more tricks like that. You can have Lightroom write out xmp sidecars by choosing "save metadata to file" from the metadata menu in Library or by turning on automatic xmp file generation in preferences. There is usually no real point to doing that however as the "edit in Photoshop" route works just fine. It's only really useful when you have a mixed workflow that still uses Bridge. If you share images with others, you're better off exporting dngs, or exporting subsets of images as catalogs with the images included.

  • Newly supported camera RAW for Lightroom v2.1

    CANON EOS "50D" should be included as newly supported camera RAW as soon as possible. Which has been already on sale since 27th September.

    If you want any reaction, post in the Camera Raw or Lightroom forums.

  • Is the Fujifilm X100T compatible with Camera Raw and Lightroom?

    Is the Fujifilm X100T compatible with Camera Raw and Lightroom?
    I see that the X100 and the X100s are compatible. Nothing about the T model.

    https://forums.adobe.com/search.jspa?q=x100t&place=%2Fplaces%2F1383621&depth=ALL

  • Lightroom VS Camera Raw 5.5 (color correction)

    Hi, does somebody know if discarding the advantage of making layers of Photoshop, is the Adobe Lightroom color correction controls superiors to the CameraRaw PS Interface correction controls ??? I mean for color correction purposes is Adobe Lightroom  better tan PS's  camera raw interface ???? because for me both controls seem to be pretty much the same thing,  does anyone know something about it ??
    Thank you in advance !

    They seem the same because they are the same thing. Lightroom is basically an interface built around the camera raw processing core so you will get exactly the same results. The only thing really that you can do in Camera RAW that you can't in Lightroom is point curves (the interface simply doesn't expose them at the moment), which are almost never needed in raw conversion, except if you do special effects. I almost never use Photoshop anymore as Lightroom basically does all I need.
    P.S. the latest version of camera RAW is 5.6! Lightroom is at 2.6. The last number corresponds not by accident.

  • Lightroom Color Space Problem.

    Hello,
    I am processing my photos in Lightrrom. The histogram in Lightroom looks ok without any clipping, but when i export them to AdobeRGB or sRGB (for web) the photos have clipped shadows or highlights or both. I belive that the problem is that the histogram in lightroom reflect the data of the photo in ProPhoto RGB, and when you export to a narrow color space the clipping happens.
    Is there any way to fix this? I will always have clipping if i export to AdobeRGB or sRGB? What do you do to not have this problem?
    Beside of the clipping problem. The diferece between the histogram in the develop module in Lightroom and the histogram of the exported photo in AdobeRGB or sRGB makes that you don't know what the exported photo will look like, is like working blind. I don't know about you guys, but for me the is a big problem. Well, maybe if you work all in ProPhoto RGB this is a little issue.
    I would appreciate a lot any help or comment that you could give me.
    Thanks, :)
    Marcelo.

    Another thing I sometimes do is to save the development settings (save metadata in metadata menu) to file in LR, and then open the RAW in Camera RAW. In camera RAW the histogram reflects the color space you set, so you can optimize the development settings there. Then I close Camera Raw, which updates the xmp file (or the stuff written into the dng) and in LR do read metadata from file, which will apply the changed settings. This does the trick typically.

  • Camera Raw 4.6 Color Conversion Issues

    I'm using CS3. In the Camera Raw 4.6 import window the color looks great. When I get the image into Photoshop the color looks horrible. I know it's the color profile that Raw is assigning. My question... is there a way to disable the color profile conversion coming from Camera Raw?
    I've always had great results without using profiles and now this alters my color. I've even tried to go in and force the image to use a different color profile but at this point the damage has been done by the camera raw plugin.

    "I've been doing professional color correction for about 15 years and know how to use the programs without the use of color profiles."
    You're always using profiles no matter what, both a source and and destination for everything from your monitor to working RGB, CMYK and Lab to output profiles for proofing and print.
    You need good profiles to define the hardware devices and color spaces. Without them, it's all only a guess.
    "When I say "great color", I mean to say Photoshop doesn't adjust my color with profiles because I have profiles disabled."
    There's not really a way to disable profiles in Photoshop. You can sort of turn them off, but the default profiles in your Color Settings dialog are still in effect no matter what. In fact, you can't even display in image in RGB or CMYK without at least two profile, and more often three.
    Just having profile in the loop doesn't mean that Photoshop will "adjust" your colors. Photoshop will only do what you tell it to do.
    "My monitor is corrected and I have no need to use profiles since I understand UCR & GCR conversion for printing."
    You monitor is corrected? How? Have you calibrated it? After the calibration Photoshop needs, you guessed it, a monitor profile, in order to properly display your images. And how to you get from the RGB of your digital captures to the CMYK you need for offset? Yeah. Profiles. Even if you're using the archaic and outdated Custom CMYK to set your total ink and black generation, you are still in effect, using profiles. You are using the parameters defined there in the same way custom measurement are used in ProfileMaker to generate a custom ICC profile. It's just not as accurate.
    "Also, when I have something printed somewhere I have them disable their profiles to provide true color. And I also force acrobat to use my color maps when building pdfs so my printer has no need for conversion of any kind."
    How you do know you've made the right conversion for that printer. Most printer just ignore embedded profiles anyway, but including proper output profiles can enable them to display the files correctly on their calibrated screens, and for the more advanced printers, that embedded profile can allow them to use Device Link Profiles to convert your files to custom press or proofing profiles.
    "My complaint was that the Camera Raw Plug-in forces me to convert to a profile with 4 possible choices. I was asking if there is a way to disable this?"
    It's actually a choice of four different profiles not a profile with four choices. The choices are based on color gamut and gamma in order of increased gamut. There is no way to disable them. What would you put in their place? There are raw converters that will let you convert the raw data to any color space on output, including CMYK. Maybe that would be more appropriate for you. CaptureOne and Raw Developer are the two that come to mind, but they all use profiles.
    Hell, even in the golden age of the drum scanner, scanners like the Hell 3010 without even being able to see an image on screen, used profiles, only they called them by a different name - lookup tables. Lookup tables for scanner input and characteristic lookup tables for the analog proofing system the house used.
    "I found if I convert using the Adobe 1998 profile the color comes out close, I simply have to increase the saturation to return to the original optical image values. I would however like to bypass this step."
    It sounds to me like you need to spend a few weeks getting up to date with the tools that are available now. Between hardware monitor calibration and custom CMYK output profiles that take into account different ink limits and black generation, you're missing out on a boatload of fun.
    A lot of things have changed in prepress in the last fifteen years not the least of which is that little number called Direct to Plate. Since everone has gone DTP, the one thing that has gone by the wayside are any kind of overall proofing standards. Where you used to be able to send the same file to ten different printers and get back proofs that were extremely close, now they're all over the map. The only way to effectively deal with this is with custom profiles for the high end digital proofers that printers use today.
    Sure, you still need to take into account the specifics of total ink, highlight and shadow values, but you simply can't rely on the positively ancient ink definitions in Custom CMYK to work very well for any of today's output. Unless, of course, you and your clients don't mind going through rounds and rounds of proofs.

  • Can't open photos in Camera Raw from Lightroom

    Hi!
    I used to open my (RAW) photos from Lightroom (2) into Camera Raw - it did it automatically when I clicked "edit in photoshop". Now it doesn't work anymore, and I have no idea why - it opens the pictures directly into Photoshop (CS4).
    However, it works from the finder and from Bridge. Any idea what I should do to get that functionality back? I know some of you will say I should just develop my RAWs into LR, but I prefer Camera Raw and would love to get that option back.
    Any help would be greatly appreciated.
    Thanks!

    1. I'm shouting because you don't seem to be hearing me when I'm speaking normally.
    I (and others) are hearing. And we are offering what we can.  You're
    just not accepting it, in the spirit given, even if it's not what you
    had hoped to hear.
    2. I DO want to open CR. What I'm trying to accomplish is NOT to edit several pictures at once, but to open CR from Lightroom.
    So ... you don't really care about editing multiple pictures; you only
    care about using CR?
    Even if I can edit multiple photos in LR, I will continue to use CR, by opening my pictures from the finder or from Bridge (which
    >I've been doing all week). I'm not trying to be hardheaded, I just like my workflow the way it is, and I made that clear in the
    >question to specifically avoid people coming around and telling me "oh but you can do this from LR". I don't care. I don't WANT to
    >do it from LR. Otherwise my question would have been "how do I do this from LR"!!
    Yes, we all got your preference (repeatedly). What you don't seem to
    get is the fact that - even if you can't get what you want (i.e.,
    using CR), you can still edit multiple pictures. Isn't doing that
    the most important element?  That you get your photos to look how
    want/need them? Or your client wants/needs them, whichever? Or is the
    most important thing to use a specific program?
    Having a fallback plan to accomplish what you need (i.e., editing
    multiple pictures) is key. Any fallback plan will be more unpleasant
    than you first preference.
    Suppose the answer had been "Nope; no way to do that using CR. None at
    all" ... would you then not have edited those photos some other way?
    Or would you simply have abandoned your images, since you couldn't get
    your first preference (CR) to work the way you wanted?
    My question was clearly "how do I open my files from LR into CR". Anybody who's responding anything else than "this is how
    >you open your photos from LR into CR" or "you can't do that anymore" is just here for attention, not to help me. I would
    >understand and appreciate the impulse to show me a new workflow if I hadn't SPECIFICALLY SAID IN MY QUESTION NOT TO
    >DO THAT.
    >
    How can you not understand how frustrating that is?
    I can. I can also understand how you sound, when you didn't get what
    exactly you wanted, which you can't seem to understand.
    Regardless, others have given you insight into how to let you use CR
    (or other areas to explore, anyway), which (according to you) is what
    you care about. So good luck with that, and I hope you find a final
    solution that makes you happy. CR is an amazing program.
    Michael J. Leone, <mailto:[email protected]>
    PGP Fingerprint: 0AA8 DC47 CB63 AE3F C739 6BF9 9AB4 1EF6 5AA5 BCDF
    Photo Gallery: <http://www.flickr.com/photos/mikeleonephotos

  • Bug report: Wrong As Shot White Balance for Nikon D50 NEF in Camera Raw 7, Lightroom 4

    For Nikon D50 cameras Adobe Creative Suite 6 does not read "As Shot" white balance data whether it's specified or not. It defaults to "Automatic". We have the problem only for Nikon D50 and only in Photoshop CS6, Adobe Camera Raw 7.3 and Photoshop Lightroom 4. (Not in CS5. Not for Nikon D5100 or D7000 or Canon S95) .
    There is a more detailed posting at photoshop.com.
    Lightroom 4.2 / ACR 7.2: WB "as shot" does not read the WB of Nikon D50 NEF, defaults to "automatic"
    http://phtshp.us/10utPuk
    phtshp.us/10utPuk

    Moving the discussion to PS Forums

Maybe you are looking for

  • My BB 8320 camera is not working and calls drop after 8 to 10 minutes...

    Hi, Acutally I got this 8320 as a gift 6 months back.  The problem i am facing is that the camera is not starting at all, i have tried troubleshooting it and it is not working still, and sometimes when i am speaking on phone the call drops at the 8th

  • Automatic music upon opening website page

    Hello all. I was wandering if anyone knows how/if you can have music/theme play upon opening your webpage using iweb. I know that you can drap a song into the page where the person clicks on the play button, but can you have it open the page and play

  • IDOC-Process Codes

    Hi Experts, When i'm triggerig the idoc its successfully sending the Idoc from the outbound but getting the status 51 in the inbound as :  The function module IDOC_INPUT_DEBITOR and the application object type KNA1 which were determined are not valid

  • Major problems with mail

    I have been experiencing many issues with mail recently. I've used mail for about 6 years with no problems so these have only occurred since I upgraded to osx leopard a few months ago. In the last 2 weeks it has become worse - mainly I am not receivi

  • How long is dose apple cover the power adapter?

    I got a macbook pro one year and one week ago, and today the power adapter part that can come off the brick, broke, like it just came unglued? so the brick is ok and the part that pulgs in the wall is not .... so does anyone know ?