Bug in adjustment brush undo

Select Adjustment Brush tool
paint a mask
switch to "Brush: Erase"
paint away some mask
ctrl-z (undo)
tool switches back to "Brush: A" when it should stay on Erase

OS Windows 7 64 bit 8GB
Indeed the same over here.
CTRL-Z does undo the last brush stroke but returns to normal brush and desactivates the pin.
Even without changing of the brush,when CTRL-Z of last brush stroke, the pin is desactivated.
Frans

Similar Messages

  • LR4 adjustment brush undo bug

    Think I have found a bug in the LR4 beta, it's reproducible by me anyway.
    Paint an adjustment of any type onto an image using the adjustment brush.
    Now select the erase brush and erase part of the adjustment you have just made.
    Click undo.
    The undo is made, but the erase brush also changes back to the add brush (Brush B in my case)
    I have found myself finely erasing adjustments, and then accidentally adding them again after clicking an undo.
    Can alone else confirm?
    LR4 beta, Windows 7 64bit.

    The place you should be posting to is the Lightroom 4 Beta Forum...

  • ACR 7.3 Bug on Adjustment Brush tool - changing brush size problem.

    I update photoshop and using ACR 7.3 and now having big problem when I use Adjustment Brush took. Phe problem is when try to change brush size with holding right mouse button and moving the mouse. Behavior completely changed and its impossible to predict if I move mouse right what will happen.
    Please check solution for it. old behaviour was great. I think this is not new feature, its bug.
    Thanks in advance.

    No need.
    Already bugged and acknowledged: http://feedback.photoshop.com/photoshop_family/topics/bug_crash_adjustment_brush.

  • Bug? Vignetting & Adjustment Brush

    Hello.
    This if my first post, so please don't be too harsh if I make any mistakes. I encountered a bug (well, at least I think it is one) while using LR3 on Win7.
    While editing my images I added a post-crop vignetting. After finishing the colour & contrast stuff, I went on to retouching. After "inserting" the first adjustment brush, the vignetting changes, which, I think, shouldn't happen, because I dind't even touch any area near the vignetting. See the screenshots for details. (Sorry for the black areas, I didn't want to show the person I photographed.)
    The difference is not very well visible if the screenshots are placed next to each other. However you can open both images in different tabs and switch between them, then you should definitely see it. Has anyone noticed that behavior before? Or does anybody have a clue what's happening here? I would be even happy for workarounds because I use both tools very often.
    Thank you!
    Luc y Lou

    I'm experiencing this bug as well. In addition to the extra strength post-crop vignette that happens, I'm also getting blotchy tiles where the post-crop vignette is supposed to be when I apply an exposure brush, as seen in the attached screen grab. Takes some fiddling around to make it go away. Usually turning off the "Effects" tab then turning it back on clears it up.
    I'm on LR 3.2 using an iMac i7 quad 2.8ghz, 12gb RAM, ATI 4850 card 512mb V-RAM, plenty of disc space, working on Canon 5DMk2 raw files. Cache has been cleared and catalog optimized.

  • Adjustment brush bug

    Hello - so far my adjustment brush is having issues engaging. I select the brush, the drop down menu appears, I make my adjustment and nothing registers. I open, close, open, close and open again and sometime it works and sometimes it doesn't.
    Suggestions?

    Checked and no. It's not registering when I click on the screen. I use this program everyday and this is definitely a bug.

  • Adjustment Brush edit bug verified by Adobe

    Adjustment brush edits that turn off have been acknowledged as a "bug" by Adobe see http://feedback.photoshop.com/photoshop_family/topics/problem_with_adjustment_brush_tool_i n_adobe_camera_raw Someone on a Mac posted the same problem. From feedback to my post, I had thought it was just a Windows 7 problem.
    Problem is more serious than my post on Oct.16. I have discovered it is more than a Preview issue. An Adjustment Brush edit that is (momentarily) not showing in ACR 7.2 or 7.3 will not be carried over to Photoshop when you update the file into PS CS6 as a Smart Object. So you made multiple Adjustment Brush edits (for example Exposure, Highlight and Clarity) only to discover that not all the edits made it to the Photoshop Smart Object.
    See original Oct. 16 post to see screen shots provided by Noel Carboni that verify bug. http://forums.adobe.com/message/4792575#4792575 Includes specs of my Windows 7 x64 machine.

    Okay, I know I'm just talking to myself here, but I wanted to leave another update. It's not nTune, (at least I don't think that had anything to do with it).
    I've come to find that when I have Firefox (v3.01) open, the problem appears. With FF closed, it's gone. No other program that I've tried causes the same issue. And as far as I can tell, FF doesn't cause problems with any other software.
    This is a strange problem indeed, but I guess if it comes down to having FF closed while I'm working, so be it.
    Anyone have thoughts as to where the conflict is coming from?

  • Adjustment brush bugged? Image areas not brushed over change nevertheless

    Problem:
    I used the adjustment brush to brighten up an area in an image (+0.2 exposure). Doing so, a nearby but not connected area and not touched by the brush brightened up as well, going from almost blown out to blown out as shown by the red warning overlay.
    System:
    Pentium i5 machine, Windows 7 home premium 64 bit, 8 GB RAM
    Lightroom 3.3 64 bit
    Here are some illustrations:
    before applying the brush (note the blue are near the upper edge not yet blown out)
    I am applying the brush here (note area marked in red, not touching the blue almost blown out part near the top edge):
    And this is what happens to the blue area when applying the brush:
    The funny thing is, when I hover the cursor over the brush pin (as in the second picture above), the blue area to the top left is NOT marked blown out (as can be seen in the second picture).
    Something strange is going on here. Either the red 'blown out' overlay is not functioning correctly in this situation, or the adjustment brush is bugged. It should obviously not have any effect on areas that have not been brushed over.
    Any thoughts?
    Christian

    CASpyr wrote:
    Thanks Lee Jay for the quick reply. I did search before posting but apparently have not used the right terms.
    It seems this is known for quite a while. Has Adobe made any statement on a workaround or that this is being fixed?
    I understand this is something occurring in unusual circumstances only but still, it's a bug....
    I think the problem is that they cannot reproduce the issue, hence no fix yet.

  • 2.1 RC - Adjustment Brush Bug Persists

    While the adjustment brush seem a bit more responsive under 2.1, I regret to report that the brush continues to apply adjustments even after I have released the left mouse button. This usually happens when I'm trying to refine the edge created by my initial selection. I've submitted a bug report to this effect.
    As stated in my earlier posts, I'm running LR2.1 on a Vista Home Premium system with adequate processing power for PS CS3, 4 gigs of RAM, and plenty of HD space.
    Adam

    I read the release notes. They specifically said they fixed a couple of problems in the local correction area and went on to say:
    >"We are still working on additional methods to improve the performance of the new Localized Correction features."
    which indicates to me that they attempted to address some issues but as they did not say what issues were addressed or to what degree wouldn't it be prudent for us to keep reporting all problems that we have with LR2.1RC?
    The specific issue reported in this thread may or may not have anything to do with 'performance' but it certainly has to do with the mouse--the mouse up is apparently not acknowledged until about the time the history list is updated so any brush movements between mouse up and the history updating are counted as edits. That is a definite bug and to quote Jeff in another thread about a different bug:
    >Jeff Schewe:"...again you have to understand that MORE bug reports is more better...the more people wh report this as a problem the higher priority it will get. So, vote early, vote often..."
    and since the LR2.1RC web site also said:
    >"If you do experience an issue with this release candidate please report it to the Lightroom User to User forum."
    where the phrase "User to User forum" is a link to this forum I would think the 'voting' should be done on this forum.

  • Bug ACR 7.2 adjustment brush previews

    I realize this is a redundant post - I want to make sure someone at Adobe notices.   Adjustment brush previews are turning off when you hover the cursor over the edit pin, and stay off until off until you hover cursor over another pin.  Neil Carboni took the time to make screen shots that show the problem. See previous post and my Windows 7 x64 specs at http://forums.adobe.com/thread/1083526?tstart=0
    The Adjustment brush previews work as expected so long the Show Mask option is checked AND one of the of the Adjustment Brush pins is selected; so one mask is always showing. 
    For example, when a previously edited image is first re-opened in ACR, no brush pins are selected (Show Mask can be checked). If I hover my cursor over one of the pins (for example I have 6 brush adjustments) the mask flashes on for the associated edit, as expected. When I move the cursor away, the edit preview disappears as if the edit never happened, but the pin remains. I then select one of the pins by clicking on it to make that edit live. Now when I move my cursor over a pin the mask for that pin flashes on, when I move the cursor away from that pin the preview of the edit is showing. Now the preview works for any brush edit.
    Makes working with multiple adjustment brushes extremely difficult - not always sure if the results of a previous edit are showing. Have to constantly move my cursor and hover it over another brush pin to verify that I am seeing results of previous edit. If the preview is not showing, as soon as I put down the brush on that edit, the preview springs to life. I do not see this problem using ACR 7.1 on my Vista x64 machine.
    As my previous post indicates, I have updated the driver on my FirePro V4900, uninstalled and reinstalled Photoshop, etc.  Did not see the problem after I reinstalled Photoshop and briefly used ACR 7.  Problem came back once I updated.

    Well, for one, the current version of ACR is 8.3 by now.
    More information would be needed about your system before troubleshooting steps can be suggested.
    Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers: 
    http://forums.adobe.com/thread/419981?tstart=0
    Thanks!
    Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers: 
    http://forums.adobe.com/thread/419981?tstart=0 Thanks!

  • BUG!  lightroom 3.4.1 Adjustment Brush Doesn't Show It's "Button" Anymore

    Adjustment Brush Doesn't Show It's "Button" Anymore:
    I installed the update for 3.4.1 and warm re-booted my computer.
    The button that you saw after painting (releasing the mouse button), is no longer there.
    There is nothing to hover over to see what area you painted and if you Close the brush, and reopen it, the button does not appear.
    HALP!

    Disregard my second message about not understanding your email reply.
    I thought I had to hit "H" to see a link -on the email- to confirm my registration.
    I didn't realize it was your answer.
    Since I had just installed my 3.4.1 update and the default on my installed version of LR, and since my 'pins' have never been hidden, the 3.4.1 default of hiding the pins was a problem and is likely to fool a lot of users that hadn't read about hiding those pins yet.  Shouldn't the installation of -any- new version, pick up the defaults currently in LR?  That is an issue.
    We're good now.
    Thanks for the response.
    Michael

  • LR4 Adjustment Brushes ... Possible Bug?

    If I proceed to edit a Nikon NEF image in LR4 using the Adjustment Brushes (doesn't matter which one(s)) ... and then proceed to further edit the image in Photoshop CS5 ... the areas in which I've applied brush strokes do not carry over to PS correctly. Basically, anywhere there is a Brush Stroke ... it looks like I've gone crazy with the Dodge tool.
    I do not remember this being an issue in LR3.

    When you edit in Photoshop, you should get the compatibility warning for camera raw.  Do you select "Render in Lightroom" or "Open anyway"?
    If you check the "don't show" option on that warning, you may then lock in use of the incompatible version of camera raw. 
    PS - I've just tried it, and I reckon this might be your problem.  If you edit in CS5 and choose "Open anyway" then adjustment brush work is lost, if you chose "Render in Lightroom" then the adjustments go through to CS5. 
    If you've previously chosen "Open anyway" and checked "don't show again" then try Edit menu, Preferences, General tab and click "Reset all warning dialogs". 

  • New adjustment brush bug

    When setting values for a new adjustment brush, most values are not retained when changing the image being worked on.
    Steps to reproduce:
    - Select more than one image to work on in library, and then enter develop
    - Create a new adjustment brush with non-zero setting for exposure, contrast, highlights, shadows, clarity, and saturation
    - Apply strokes with the brush to the current image
    - Change the image you are working on in develop
    Expected behavior (as in previous versions of Lightroom)
    - All the settings applied to the new brush in the previous image are retained
    Actual behavior
    - Only the modified setting for exposure is retained - all other settings have reverted to zero and must be reentered on each image
    System used: 64 bit Windows 7 running on an IMac under Bootcamp with 12 GB of RAM
    Surely this is not intended behavior. This doubles my work using the adjustment brush in my typical workflow.

    After playing around with effect presets, I now understand what is going on, and I suspect it is intended, but I still don't like it! In Lightroom 3, the default selection in the effects popup is 'Custom', which accepts whatever settings you have entered to a new adjustment brush. When you move on to another image, unless you change it, 'Custom' remains the default selection for the effects pop-up, and the settings you entered for your most recent new adjustment brush 'stick' and appear as the default. In Lightroom 4, the 'Custom' choice in the effects pop-up has gone away, and the first choice that appears in the pop-up list becomes the one that is applied by default to the new adjustment brush, which happens to be the 'Exposure' effect, which has a setting for exposure only, which is why it is the one and only one setting that reappears.
    I expect that when I create a new adjustment brush, without specifically selecting an effect, it will be truely new with all settings at zero! The current behavior is very unintuitive. It should not pick up any defaults, particularly by just picking up the settings from whatever effect happens to be the first one in the effects popup list! I either want the 'Custom' all zeros default back, or at least to have no effect applied by default to the new brush and have settings applied to the brush if and only if an effect is selected from the pop-up.

  • LR 3.2 - Local adjustment brush and heal/clone tool broken

    Hi,
    After installing LR 3.2, the first thing I noticed is that it is much slower than the previous version (using XP Pro + 3GB memory and a speedy processor).
    But the most terrible novelty of this version is that the Adjustment Brush is going berserk after a while:
    It first slows down to a crawl, so slow that it's almost impossible to work with.
    While working with it after a while, it starts to show random rectangular areas that are copies of other areas of the image that have nothing to do with the area I'm working on. This happens after a brush stroke. The Undo command makes these rectangular "patches" disappear.
    From time to time, the whole image is flipped upside down (You can't believe it? Neither could I).
    Eventually, afte a brush stroke, the sandclock mouse cursor is displayed and the program freezes (at this time it can be using over 1 GB of memory although I'm working on a single, standard EOS 5D image). The only way to stop this madness is to kill the process.
    The Heal/Clone tool also shows a similar misbehavior.
    I didn't have these problems with the previous version.

    Ian,
    Ian Lyons wrote:
    Are you looking for help? If so then it would really useful if you provided some information on hardware, OS and what exactly are you doing when the system freezes. Also worth noting that applications very rarely (even badly coded apps) cause the hardware to crash. System crashes are more often than not due to bad device drivers or bad hardware that an application may expose.
    I'm a software professional since PCs exist. I have enough experience to identify software problems when they appear. At least, I'm able to determine whether I have a hardware problem or if the software I'm using (or writing) is buggy. I have read many reports, many threads, many advice about these performance issues. I'm pretty sure that the problem is LR. I repeat: I do not have any performance issue when editing images in Bibble 5, Photoshop or DxO Optics Pro. BB5 is at least an order of magnitude faster than LR when editing images.When I use the Adjustment Brush in Camera Raw, there's absolutely no problem. My hardware is powerful enough and my installation is pretty clean (could it be powerful enough in Camera Raw and not in LR?). My OS is very stable. I have not seen a BSOD since years and all my applications are running flawlessly on this system (which includes image editing applications, software development tools, and many others...).
    Users having various and very powerful systems (PC or Mac) are reporting the very same problems. Like Bruce, I'm convinced that this is not a hardware resource problem. We didn't have these problems with LR2 and LR3 was supposed to enhance performances. Version after version, it has now become unusable for me.
    Drawing the conclusion that since many users don't have any performance issues, the problem must be on the user's side would be erroneous. The bug is in LR and may or may not appear depending on the circumstances. Any developer knows that a bug may or may not hit a given user depending on how she uses the software. I admit that these bugs are hard to fix. But LR has to be fixed, no doubt.
    I profoundly regret that Adobe do not acknowledge this.

  • Wacom Tablet Pen Pressure stops working in Photoshop after using Lightroom Local Adjustment Brush

    Hi all,
    I am experiencing a problem with my Intuos Pro Medium (driver 6.3.9w3 on Windows 8.1)
    I am using Lighroom 5.6 and Photoshop CC 2014.
    I an get the pen pressure to work in Photoshop without any problem. However, if I go into Lightroom and use the Local Adjustment Brush and then transfer the photo into Photoshop (Right Click Edit In => Edit in Adobe Photoshop 2014 CC) then the pen pressure stops working in Photoshop.
    Really frustrating... The only workaround is to close both Photoshop and Lightroom, then reopen Photoshop, then usually the Pen pressure feature starts working again.
    Has anyone experienced this before or has any idea how to fix this?
    Thanks,
    Guillaume

    Your tablet driver isn't reporting pressure correctly.
    The knockoff tablet drivers usually need to be revised for each new version of Photoshop (and we have no idea why).
    Contact your tablet maker to see if they have updated drivers to fix their bugs.

  • Has anyone experienced a problem with the adjustment brush since last update (for Mac) last week?

    Following an update to Lightroom on my Mac Pro work station last Friday: when I apply my adjustment brush to an area in an image, a faint box encompassing a much larger area than the size of my brush appears (extends well beyond the area I've identified with my brush and is clearly a large square shape). When I release my mouse, the adjustment I've made affects my entire image. I had no issues with adjustment brush prior to the update. I've been on the phone with Adobe support (no help). Have uninstalled/reinstalled Lightroom several times (no help). Adobe directed me to Apple (recommend use of Time Machine to date before Lightroom update came through). To ensure it's an isolated bug, I checked my MacBook Pro. Worked fine without update; I let update come through and find the adjustment brush "bug" is intermittent. When it occurs, however, I always see the larger "box" area, and the adjustment brush ultimately affects my entire image.
    Anyone else experiencing this? Adobe support insists it's a Mac issue. Thanks!

    Hi,
    Following an update to Lightroom on my Mac Pro work station last Friday: when I apply my adjustment brush to an area in an image, a faint box encompassing a much larger area than the size of my brush appears (extends well beyond the area I've identified with my brush and is clearly a large square shape).
    Same problem (rectangular areas) + others under Windows. The adjustment brush and the clone / heal tool have been totally broken in LR 3.2. You're not alone. See this thread. I have filed a bug report. No answer until now.

Maybe you are looking for

  • Use api app on free version of reader?

    I am looking at using the SDK to allow me to add a button to the user interface to bring up a new window that will let me assign and write some file attributes to a database as well as determine the path for the saved file, rename it etc. The javascr

  • JAXB unmarshaling: defaultValue not treated correctly

    Hi, Our XML schema defines an int element with default: <xs:element name="reconnect-interval" type="xs:integer" default="3600" /> Running JAXB compiler (xjc) on that schema results in an object-tree which fails to return the pre-set default value whe

  • Search function of tags not working when folders renamed outside of PSE

    hi guys have PSE 9 on MAC. when saving foto files at another place and doing so outside of the program PSE, we all know already that PSE displays them in the organizer with a "?". This fact is not at all comfortable but, thanks to the link PSE makes,

  • I can't set up my Samsung external drive to burn CDs,, I can't set up my Samsung external drive to burn CDs,

    I have a late 2006 MacBook, the cd drive doesn't burn anymore so I bought a Samsung external drive that is compatible for Mac, but I can't figure out how to get it going, I want to burn music CDs to it, help!

  • Fuzzy Logic 4 Accuracy?

    Hi there I've had a look round and couldn't see any posts specific to this porblem so here goes :D When I start up my system the FSB reading in fuzzy logic 4 can vary considerably. Anything from 130MHz to 146MHz! Yet I know it's still set to 133MHz i