Lightroom adjustment brush inconsistent with Camera Raw

I love Lightroom's adjustment brushes, but I find it annoying that I can't use them to take saturation all the way to monochrome, even with the saturation slider turned down all the way. Today, I noticed that in Camera Raw 5.4, the same thing is NOT true - you can remove color completely with an adjustment brush.
Surprised at this difference, I wondered what would happen when I loaded the ACR-adjusted file back into Lightroom. Lo and behold, Lightroom showed the result of the adjustment brush the same way as ACR, with all color removed. Excellent!
But what would happen if I changed that adjustment brush in Lightroom? Would it "forget" what I had done in ACR and revert to its normal behavior? No, it continued to behave just as it had in ACR. But in the same photo, a brush created in Lightroom did not behave the same way. So clearly, it was something to do with which program created the brush.
Then I took a look at my XMP file, and it became (somewhat) clear what's going on. This is one of the XMP attributes for the brush created in ACR:
     <crs:MaskValue>1.000000</crs:MaskValue>
And here's the same attribute for the brush created in Lightroom:
     <crs:MaskValue>0.375000</crs:MaskValue>
The obvious next question is, what happens if you change MaskValue from 0.375000 to 1.000000? Answer: The brush  starts behaving like an ACR brush.
Now, this is kind of cool. I can get the behavior I want in Lightroom, by editing the XMP file by hand. On the other hand, editing XMP files isn't really my favorite thing. Is there some setting in Lightroom that can be used to achieve a MaskValue of 1.000000 for adjustment brushes? I couldn't find one, but hey, there are a lot of settings...

Ian, thank you! It was indeed Density that did the trick. I mistakenly thought Density had nothing to do with it, because you have to set it before you create a new brush stroke. (Each individual stroke of a particular adjustment brush can have a different Density value, along with the other Brush attributes like Size.) So I was changing it for my existing brush strokes, foolishly expecting it to work like the Effect sliders, and seeing no effect.
Jao, my flow was set to 100 all along, so I don't think that was my problem. It really seems to have been Density.

Similar Messages

  • No Adjustment Brush Tool in Camera Raw 5.2

    Hi, I'm new here. After watching a Gavin Hoey tutorial on HDR editing, I decided to give it a try. My pc came with PSE 7.0 pre-installed (it's version 7.0.1 and the camera raw is version 5.2.0.65) When I drag a RAW image into the edit window of PSE, it opens in a camera raw 5.2 window. On the Hoey tutorial, the window has an adjustment brush in the top toolbar, but on mine, there is no such tool. Is this normal, or can I download an update to fix this? I'm guessing PSE is a "diluted" version of PSand that's why the adjustment brush is missing.

    The tutorial was undoubtedly using Camera Raw hosted by the full version of Photoshop.
    Camera Raw in Photoshop Elements is emasculated by design, even though the Camera Raw plug-in is exactly the same one used by the full version of Photoshop.  There's only a limited subset of the features and tabs offered by Camera Raw when hosted by Elements.
    I don't remember at what stage the Adjustment Tool was added, so you should try updating Camera Raw at least to version 5.7, or higher if your version of Elements supports a higher version.
    In my opinion, Photoshop Elements is overpriced by about $80.
    Wo Tai Lao Le
    我太老了     

  • With the Photoshop and Lightroom bundle, does Bridge and Camera Raw come with it?

    With the Photoshop and Lightroom bundle, does Bridge and Camera Raw come with it?

    Hi,
    Yes, both Camera Raw and Bridge are included. Bridge will need a separate installation, however.
    regards,
    steve

  • When will Lightroom be updated with camera raw 8.7?

    Hi Folks,
    Can anyone tell me when LR will be updated with camera raw 8.7, containing support for the new Nikon D750 camera?
    Many thanks for any feedback

    Until you convert to DNG you wont be able to import the 750 NEFs into Lightroom.
    As I am a Windows user I'm not sure what you mean about Command R but to use the DNG convertor you need to download from the link and install it.
    Then you start up the convertor as a separate application and you will see the following panel:
    Then choose the Images to Convert
    Select a location to save the converted images (defaults to the same location as the input images)
    Rename the images if you so wish (Default is just to creat a file of the same name with DNG extension)
    Then Convert and after the conversion you will be able to import the DNG files into Lightroom 5.6
    Then it doesn't matter if you have Camera RAW 8.7 in CS6 as they will open directly from LR to CS6 as you would normally do.
    I guess it is a little inconvenient because you have an additional step to convert the NEF to DNG but it at least get you there in the meantime while you are waiting for the final LR product.
    Enjoy!

  • 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

  • Pentax K-x calibration with Camera Raw 3.1, and calibration updates

    The Pentax K-x will save its raw files in either DNG (Adobe) format, or PEF (Pentax) format. Until Camera Raw 3.1 was released, I had my K-x writing DNG files, since there was no support in Apperture for PEF files. With Camera Raw 3.1, the K-x is now explicitly included, so that I could switch to PEF format.
    My initial sense after doing that was that the PEF files were coming in darker than the DNG files had. But when I switched back to DNG, those were darker than I thought they should be, too. Since I had DNG files that had been processed with Camera Raw 3.0, I went back and made new versions, processing those with Camera Raw 3.1. Those, too, were much darker than the same files processed with the earlier raw developer. For examples, this picture is from a K-x DNG master processed with Camera Raw 3.0, while this picture is from the same master, reprocessed with Camera Raw 3.1. I've embedded the histograms shown in the inspector in each. Each of those has no adjustments applied. The JPEG image produced in camera (I shoot Raw+JPEG) is much closer to the brighter 3.0 image than the darker 3.1 image.
    I've seen one other report of similar behaviour with K-x images in here, but that took the approach that the solution was to revert to Camera Raw 3.0, for now, at least. I hate to move backward, particularly if it locks me out of any future updates. So, does Apple have a history of recalibrating cameras that they've already released Raw support for? Might this change in a future Camera Raw update, or is this likely to be what they alway render for the K-x?
    I can get the new style images looking okay (in fact, they seem to have better noise characteristics) with a good deal of adjustment, but not if I confine my adjustments to the Raw Processing brick. There, Boost and Hue Boost are both maxxed out by default, already. If I add adjustments in the exposure brick, and maybe a few others, I can probably get a general set of adjustments that will work as a default for this camera, but how common is it to have to do that?

    Aperture 3 mostly seems to work fine for me, at the moment. There were some issues with importing my iPhoto Library that I've mostly worked out, and some quirks that were fixed by the 3.0.1 update. I'm not saying it's all better, but it's not the doom that one might imagine reading some of the threads here, either.
    I only had the trial version of Aperture 2, though. I only got the K-x in late December, and before that, I had no need for raw processing. The software Pentax supplies is UGLY, though, and iPhoto wasn't cutting it, so I tried the Aperture 2 trial and the Lightroom 3 beta. I concluded that I much preferred Aperture to Lightroom, but I wasn't going to buy Aperture 2 when all the speculation was that Aperture 3 was right around the corner, or not coming at all. Since my Aperture 2 trial had run out, it wasn't a hard choice to buy Aperture 3 as soon as it came out. I do find I use the editing brushes more than I imagined I would, and I'm very happy that it now directly supports my camera - I've switched to shooting PEF raw instead of DNG raw.

  • If I'm in Lightroom 5, and try to Edit in Photoshop CS6, I always get the following message: "This version of Lightroom may require the Photoshop Camera Raw plug-in version 8.6 for full compatibility." But I have updated to 8.6 and have no remaining updat

    If I'm in LIghtroom 5, and try to Edit in Photoshop CS6, I always get the following message: "This version of Lightroom may require the Photoshop Camera Raw plug-in version 8.6 for full compatibility." But I have updated to 8.6 and have no remaining updates. How can I fix this?
    If I click "Open Anyway" or "Render using Lightroom", I get the following message:
    "Adobe Photoshop CS6 cannot be opened because of a problem.
    Check with the developer to make sure Adobe Photoshop CS6 works with this version of OS X. You may need to reinstall the application. Be sure to install any available updates for the application and OS X."
    Please tell me what to do so I can edit from Lightroom to Photoshop.

    In Photoshop, if you choose Help - About Plug-in... - Camera Raw, does it say 8.6?
    Seems to me there was some hiccup they found in the update process, which prompted this:
    Camera Raw updates cannot be applied
    I honestly don't know if the problem could apply to 8.6 as well, which is why I asked you to check to make very sure you really got it.
    -Noel

  • Problem opening photos with camera raw 7.1 with Photoshop CS6

    I am using Windows 7 32 bit system with 4GB ram and graphics accelerator.
    I have Photoshop CS5.1 installed in the same system at it works perfectly.
    What happens is when I use the B+W function, I get an error message saying that I have not enough ram.
    After that, when I open the next photo with Camera Raw, the raw image will not open.
    I have already maximised the Ram that Photoshop can use to 1.7GB and there is more than enough space in my scratch disk.
    Anyone can tell me what the problem is?

    Hi Noel,
    Thanks for your reply.
    Just to clarify.
    I applied B+W layer adjustment on my photos.  It is part of an automated set of actions which I apply to all my photos.  I adjust the B&W layer to 50% overlay.  When I click on the B&W adjustment layer, there is an error message that tells me I have not enough ram. Once that happens, when I open the next photo in raw, I don't see the new photo but only the frame of the camera raw though which I see my photoshop desktop.  
    It doesn't occur with the first few photos.  But by the 3rd or 4th it happens.
    I will adjust it to 50% and see what happens.
    Leslie

  • Possible GPU Issues With Camera Raw 6.6

    Over the past day on my Windows 7 x64 workstation I've done some updates.  Specifically:
    The Adobe updater brought in Camera Raw 6.6, replacing 6.5.
    I updated the to the ATI Catalyst 11.12 display driver version from previous version 11.11.
    I allowed Windows Update to apply the dozen or so changes that were pending.
    I was just doing some OpenGL testing with Photoshop CS5 12.0.4 x64 and I noticed that under some conditions I saw Photoshop drop out of OpenGL acceleration.  Specifically, when I opened a Canon 5D Mark II image through Camera Raw I saw subsequent operations stop using OpenGL acceleration even though the checkmark remained in the [  ] Enable OpenGL Drawing box in Edit - Preferences - Performance.
    What I did to determine whether OpenGL acceleration was enabled was this:  Select the Zoom Tool, then click and hold the left mouse button on the image.  When OpenGL is enabled, I see a smooth increase in zoom.  When it goes disabled, I see only a jump in zoom level after letting up the mouse button.  Also, the [  ] Scrubby Zoom box gets grayed out.  As I mentioned, even in this condition, a check of Edit - Preferences - Performance still shows OpenGL enabled.
    Just as a control, I saved the converted file as a PSD, and every time I opened THAT file (with a fresh copy of PS CS5 running) and did the same operations I could not reproduce the failure.  The difference being I did not run Camera Raw.
    Since I wasn't specifically looking for issues with Camera Raw, I am not sure that the problem occurred every time I did run Camera Raw.  I do know that when I open images from my own camera (40D; I do not own a 5D Mark II) that the problem doesn't seem to occur.  Notably I always open my image from Camera Raw to the largest possible pixel size - 6144 x 4096, as I did with the 5D Mark II image, so it's not an obvious size difference that's leading to the issue.  Given other comments of late, I'm wondering if it could be a specific issue with conversions of files from 5D Mark II.
    Nor am I sure whether any of the above updates caused it - it might done this before; I don't regularly convert 5D Mark II images.  I DO think I would have noticed Photoshop reverting to GDI operation before, since I just noticed it pretty easily, but I'm not completely sure of that either.  I do use OpenGL-specific features (such as right-click brush sizing) pretty often.
    I'm trying now to find a set of steps with which to reliably reproduce the problem now, and will advise.
    -Noel

    Figures.  Now I can't reproduce the problem at all, even after an hour of testing.  It probably had nothing to do with Camera Raw.
    I wonder if there are latent GPU status indicators and config values stored by Photoshop based on its specific environment that might not be right for the first run (or first few runs) after a display driver update.  Hm....
    -Noel

  • PSE 9 does not come with Camera Raw 6.2?

    Photosho Elements 9 does not come with camera raw 6.2
    , I downloaded the trial version which came with an outdated 6.1... the only version of 6.2 is for PSE8 and does not work with PSE9 how is this possible? How can they release a product with an outdated ACR????Now we have to wait for an update to a new product???Come on people!!!

    Cheap shot, Phil. Up to now, Mac users got no Organizer but a special bonus: full Bridge, full access to full featured ACR. With this version, both platforms get the same stuff -- it's less than full Photoshop/Bridge CS5, at a small fraction of the price.
    I admit, as a Mac user who shoots RAW, I liked the old trade-off...but I can understand the desire to make the two products consistent. If that makes PSE "inferior" for you than you should stick with Bridge CS4/Raw 5.7, or move up to the full-featured siblings, or switch to Lightroom.

  • Installed Lightroom 5.7 Update and Camera RAW 8.7 But still will not recognise my Canon 7D MkK ll even though this is now on the list

    Installed Lightroom 5.7 Update and Camera RAW 8.7 But still will not recognise my Canon 7D MkK ll even though this is now on the list- what can I do?
    Operating System OSx Yosemite IMac.

    What exactly does "not recognise" mean, Kathy?
    You're on Mac (thanks for providing that detail): are you getting a "could not be read" message? If you are, it's a write permissions issue with the destination. Change the permission, and all should be well.

  • Can a Lightroom adjustment brush draw a straight line by clicking the start and stop points?

    Can a Lightroom adjustment brush draw a straight line by clicking the start and stop points?

    studioMac wrote:
    I'm trying to selectively adust areas of an image in Lighroom. eg: a window frame in an architectural photo, and so being able to make straight lines with the adjustment brush would be very useful.
    I agree it would be useful. It's something that's been asked for. The best thing is to keep requesting at the Lightroom feature request forum

  • I've just installed CS6 creative suite mainly for photoshop CS6. It comes with camera raw 7.0.something, but need something newer to use my canon 6d. When I download camera raw 8.5 and install the raw converter doesnt work anymore, wont even open or isnt

    I've just installed CS6 creative suite mainly for photoshop CS6. It comes with camera raw 7.0.something, but need something newer to use my canon 6d. When I download camera raw 8.5 and install the raw converter doesnt work anymore, wont even open or isnt available anymore in the plugin list. Tried to reinstall everything for a few times, but nothing helps.

    When I search for updates the raw converter doesnt get update automaticly. Frustrating, is costing me the whole morning.

  • Bridge 5.0.2.4 with camera RAW 8.4.0.199 ON a MAC 10.10.1. Trying to update to camera RAW 8.7 to get my canon 7dMK2 raw files to work. But the updater say I have the latest update! Witch I clearly don't have . And my Photoshop have to different camera RAW

    Bridge 5.0.2.4 with camera RAW 8.4.0.199 ON a MAC 10.10.1. Trying to update to camera RAW 8.7 to get my canon 7dMK2 raw files to work. But the updater say I have the latest update! Witch I clearly don't have . And my Photoshop have to different camera RAW plug-ins. The old 8.4 and the new 8.7. But it doesn't work. Have removed and reinstalled several times. What is going on? Why can't I update bridge to the latest version 8.7 or read my raw files from the Canon 7dmk2?

    Try this:
    http://blogs.adobe.com/crawlspace/2011/03/keeping-photoshop-up-to-date.html#notconnected

  • RAW images in Lightroom aren't opening in camera raw in Photoshop.  Instead, I have to open the image in Finder before it will open in Camera Raw in Photoshop.  How can I correct that?

    RAW images in Lightroom aren't opening in camera raw in Photoshop.  Instead, I have to open the image in Finder before it will open in Camera Raw in Photoshop.  How can I correct that?

    Your question is a little unclear. In a "normal" Lightroom/Photoshop workflow the raw images do not open from Lightroom into Camera Raw. Lightroom has all of the Camera Raw functionality in the develop module. When you choose to open an image in Photoshop, and Lightroom and Photoshop are synchronized (i.e. referencing the same version of Camera Raw) then Camera Raw is simply used to interpret the Lightroom adjustments as the image is transferred to Photoshop. If Camera Raw is an older version then Lightroom offers you the choice to open the image or create a PSD or TIF file that includes all of the Lightroom adjustments. But in either case, opening in Camera Raw is not part of the workflow. It is possible to open the image as a smart object or convert the image to the smart object in Photoshop and then open it in Camera Raw. That is done from within Photoshop or is one of the open options in Lightroom. If you choose to go the smart object route the image first has to be opened in Photoshop and then from there you can open it in Camera Raw.

Maybe you are looking for

  • Tried to open Private browsing and get message "the url is not valid and cannot be loaded"

    up graded Firefox directly from older version to latest version and problem cropped up. Latest version on my laptop which is out of service and in shop works fine and on my net book works fine. Should I have done it in steps?

  • Can't Export to Compressor due to a

    Message that i'm getting that Reads. one or more jobs do not have a source media file assigned. anyone know how to fix this.

  • How can I gift specific music, not a generic gift card?

    I would like to share my new album with family and friends- I want to give it to them for free. If I give gift vouchers, they might just go and buy something else! How can I gift specific music, ie my album to other people?? Thanks

  • Bug in iOS Contact

    This looks like a bug with the latest iOS update. I can't seem to go to a specific field in Contacts, the cursor jumps to the next field. The only way to update that field then is to go to the previous field. But that leaves me with the problem of fi

  • Getting rid of music redundancies

    When I imported all music files from various external drives into my new macbook pro, the result (due, I'm afraid, to a complete lack of organization on my part), was that almost every song has at least one copy, many have several. Is there a simple