Skip to main content
Adobe Photoshop Family
DR

7 Messages

 • 

130 Points

Mon, Oct 26, 2020 7:29 PM

Solved

Lightroom Classic: Spot removal removing brush stroke

So I am using the brush tool on some of my photos and after that I decided to use the spot removal tool. Upon doing so it removed more than the spot. It actually ended up removing separate brush strokes I have made. I am not sure how this is possible but please look into this. 

Responses

9 Messages

 • 

140 Points

3 months ago

https://www.dropbox.com/s/c9jf48ry9ytix6k/michelle%20adobe.zip?dl=0

Here is the image I used in the video I created here: 

https://www.youtube.com/watch?v=u1anLY2dn1A&feature=emb_logo

Along with the XML. I notice that the effect is not as pronounced/non-existent if I only apply one brush/one or two spot removals. I have to get to the fourth or fifth spot removal before it acts up. Basically, as the rendering gets more intensive, the problem gets more pronounced (but then goes away for the sixth spot removal)

Mac 10.14.6

iMac (Retina 5K, 27-inch, 2017)

4.2 GHz Intel Core i7

64 GB Ram

Radeon Pro 580 8 GB Graphics Card

Shooting Canon 6D Raw. 

Employee

 • 

81 Messages

 • 

1.6K Points

Thanks @i4detail for sharing the image and other details. Can you confirm if the issue resolves if you disable GPU (in Preferences > Performance > Use Graphics Processor option)?

Regards,

Ganesh

9 Messages

 • 

140 Points

That is indeed the case. 

9 Messages

 • 

140 Points

USe for Display is on. Image processing is off. 

If I turn it on for image processing, the image doesn't change back to normal when I go out of develop. And if I export...I get an "originals missing for some images" error. Hmm. That might be because I tried to do something else yesterday. Hang on. 

No, exports with the edits correct. When I restart, the edits return as correct. 

2 Messages

 • 

72 Points

3 months ago

I have the same issue.  For example, if I use the dehaze brush on a whole sky and then select the spot healing tool to remove a single dust spot on the sky, random chunks of the sky unconnected to the spot that has been removed or the source sky used to heal the spot not only lose the benefit of the dehaze brush effect but actually turn almost white.  Renders a photo unusable.  I am using a brand new iMac with up to date Catalina installed (v10.15.7) and newest (10.0) version of Lightroom Classic.

9 Messages

 • 

140 Points

@richard_wyvill 

Note that, as far as the rest of us have experienced the bug, it is merely a display issue, tied into GPU acceleration. Switch to the library, and your image should look like it should. Yes, it goes back to looking terrible in develop, but the adjustments *should* be there. You could be experiencing something different, so I am using shoulds a lot. 

To get it to display properly in develop, you'll have to restart lightroom. Sorry. 

2 Messages

 • 

72 Points

Thanks for your comment. You are quite correct and the photos do look normal in library view after a second or two of delay.  Until the bug is fixed I will use the spot removal tool as the final step of any editing so that the photo can be assessed properly on screen while performing other edits without the distracting white fuzzy bands running across it.

808 Messages

 • 

9.6K Points

True for DNG but not for raw. Displays the same in Library module AND when exported. The only ways to completely eliminate the problem that I've discovered:

  1. Convert the image to JPEG and do all edits there. 
  2. Adjustment brush as the last step(s) in the develop process. 
  3. Perform all edits except spot removal, export as jpeg, import the jpeg and then perform the spot removals on the imported JPEG .
  4. GPU off and Auto Mask off. 

~~~~~~~~~~~~~~~~~~ 

 

Full results of my testing, reported on a different thread. 

 

Further more extensive tests on my Windows machine. Tests on DNG, JPG and RAF also including some performance impacts. Here are the details, I'll let you draw your own conclusions except for 2 of my observations: 

1. Auto Mask is a performance hit
2. Results are dependent on the image and number of modifications
3. No issue with jpegs


New tests on a DNG:
 
1. GPU off, Mask on or off, the problem doesn't occur. 

2A. GPU on and Auto Mask on, for this photo, it is necessary to remove at least 3 spots before the brush is partially undone. Prior tests with this photo have caused the partial removal of brush strokes with only 1 spot removal. 
 
2B. Same as test 2A except Auto Mask is off. The problem doesn't occur until at least 4 spots are removed. 

3. Problem exists in the Develop module, returning to Library and the photo display correctly. Returning to develop and the problem returns. 
  

New tests on a JPG:
 
1. All tests show no problem. 
 
  
New tests on a RAF (Fuji raw): 
 
1. GPU off, Mask on or off, the problem doesn't occur. 
 
2A. GPU on and Auto Mask on, for this photo, it is necessary to remove at least 8 spots before the brush is partially undone. 

2B. Same as test 2A except Auto Mask is off. The problem doesn't occur even after 51 spots were removed. 
 
3. Problem still exists in Library module. The defect is exported. 


The only ways to completely eliminate the problem that I've discovered: 

  1. Convert the image to JPEG and do all edits there. 
  2. Adjustment brush as the last step(s) in the develop process. 
  3. Perform all edits except spot removal, export as jpeg, import the jpeg and then perform the spot removals on the imported JPEG.
  4. GPU off and Auto Mask off. 


Note 1: Auto Mask slows down painting. 
 
Note 2: Auto Mask slows down spot removal by at least a factor of 4, probably more. 
 
Note 3: my hardware configuration 
 
HP Z440 
Xeon E5-1650 V4 6-core 3.6/4.0 GHz
64GB ECC RAM
Windows 10 Pro 64-bit 
Nvidia Quadro P2200 5GB (default scaling) 
Dell 27" 4K P2715Q 
Benq 32" 4K PD3200Q 
Samsung 950 Pro 512GB - C-drive
Samsung 860 EVO 2TB 
   -dedicated to Lightroom 
   -Samsung Rapid Mode active 
   -on a PCI-E adapter 

Champion

 • 

902 Messages

 • 

14.8K Points

Bill

I can easily make it break on a JPG file (from my iPad) so there are issues with JPG files too.  You just haven't run into them yet.    :  )

macOS 10.15.7.  Imac Retina with GPU turned on.

(edited)

808 Messages

 • 

9.6K Points

  • Fuji X10 jpg
  • started from the unedited image
  • Auto Mask off
  • brushed through about 25% of the image
  • 50 spot removals 
  • no problem 

Repeat test

  • Auto Mask on 
  • now it fails with every spot removal 
  • each click changes the image in a different way
  • return to Library and the problem disappears 
  • return to Develop and it returns 
  • Export from Library, problem not exported
  • Export from Develop, problem not exported

In conclusion, very different results:

  • DNG - GPU needs to be off 
  • JPEG or RAW (at least for Fuji and Olympus RAW) - GPU on or off as long as Auto Mask is off (unchecked). 

We can probably continue to test and come up with many more combinations. For me, I'll just continue with Auto Mask Off for 2 reasons:

  1. solves the problem we're discussing
  2. with V10, Auto Mask On is a huge performance hit. The brush can't keep up with the mouse and each spot removal is 1-4 seconds rather than instantaneous. 

808 Messages

 • 

9.6K Points

3 months ago

On the other thread for this topic, I provided an example where the image, even when exported, was ruined and another when it was not correct after returning to library. . So definitely more than just a display issue. 

Employee

 • 

81 Messages

 • 

1.6K Points

@bill_3305731 can you help us by sharing the image with settings (xmp file) ?

Regards,

Ganesh

808 Messages

 • 

9.6K Points

I won't be at my computer for a few hours so I will send it later. But you can recreate it easy enough. This forum doesn't support sharing raws or xmp files so I don't know how I'm going to do that. How about getting the administrators to add this capability? Should be able to attach a PDF as well. 

  • On windows 
  • Start with a raw picture that has a large area with not a lot of variation, a sky will do. 
  • Overpaint a large area with the adjustment brush setting the ev to - 2. Doesn't have to be that strong just easier to see the effect.
  • Switch to the spot removal too. 
  • While watching the painted area, click different areas of the image. 
  • Sometimes the areas are unpainted with the first click, other times it will take 3 or 4.
  • As you continue to click, the unpainted and painted areas will change.
  • Actually took me longer to enter this info than for you to recreate the problem. 

Champion

 • 

902 Messages

 • 

14.8K Points

I agree with Bill, it is very easy to recreate.  It is happening on macOS 1015.7 also.

7 Messages

 • 

102 Points

3 months ago

Upgraded to LR Classic v10, and besides the terrible slowdown, the Spot Removal is acting funky:

On each spot removing click, random previous brush strokes of the Adjustment Brush are being deleted and coming back to life with more spot removing clicks, as other brush strokes are being deleted...

iMac 27 2017

4.2 GHz i7

Redeon Pro 580 8GB

Mojave 10.14.6

Note: This comment was created from a merged conversation originally titled LR Classic V10- Spot Removal tool randomly deletes Adjustment Brush strokes

808 Messages

 • 

9.6K Points

Temporary solutions while waiting for the fix, applies to both macOS and Windows:

  1. Don't use Auto Mask with the Adjustment Brush.  - or- 
  2. Use the Adjustment Brush as your last Develop task.

BTW, Auto Mask is also a performance killer if used before any other develop tasks. 

7 Messages

 • 

102 Points

Thank you!
I do keep my Adjustment Brush for last as a result. 

And thanks for the tip on the Auto Mask!

11 Messages

 • 

258 Points

Sometimes when using the spot removal tool I see other immediate, peculiar and very significant changes in the image (highlights and shadows) that I cannot correlate in any develop settings and have therefore not yet determined what particular functions have resulted in the change.  When using the spot removal in other areas the changes are in different areas.  None of these changes are near the spot and they are quite broad. However, when closing out the image and reopening it those odd changes disappear.  So I have an easy workaround, but this is rather annoying. 

I'm using Windows 10.

Note: This comment was created from a merged conversation originally titled Another Lightroom Classic V10 bug?

2 Messages

 • 

70 Points

2 months ago

When I cover a section of an image with a brush tool adjustment, the coverage is even and as expected.

However, if I then use the spot removal tool, even once, the previous brush tool coverage is affected by means of becoming extremely patchy.

This is confirmed when I activate the red overlay. The once uniform and even spread of brushing, is now a mess of random patches.

I couldn't see this being reported yet on the forum.

Note: This comment was created from a merged conversation originally titled Lightroom Classic: Problem / Bug - Brush tool coverage affected by adding spot removal

607 Messages

 • 

12.3K Points

It's reported here Lightroom Classic: Spot removal removing brush stroke | Adobe Photoshop Family and acknowledged(as a bug) by Adobe 

1 Message

 • 

66 Points

2 months ago

Any news on an update fix for this issue?

2 Messages

 • 

70 Points

2 months ago

If I use the "brush adjustment" tool, then use "spot removal" tool, the brush adjustment will move.  If I then move place where the spot removal tool initially selected, then the brush adjustment will move back to where I had it originally.  

Note: This comment was created from a merged conversation originally titled Lightroom Classic brush moving when doing a spot correction

808 Messages

 • 

9.6K Points

2 months ago

From a Windows 10 user. 

 

This is the only bug I experienced with V10, doubly fixed:

  1. the bug is gone
  2. the very slow application of Spot removal after using the Adjustment Brush is also fixed

These were the only bugs I was experiencing. 

 

Performance improvements: the only occasional slowdown I was experiencing was with the Luminance Noise Reduction slider which was much faster with V10 over V9.4 and only occasionally dragged just a little. RAW Fuji X-T3 photos still experience about a 1/2 second delay. It could still be GPU limited (Quadro P2200 5GB) except that the GPU utilization doesn't go over 32%. 4.9GB of the GPU memory is consumed by the slider so the problem could be insufficient memory on the card. My guess is that V10/10.1 are trying to make more used of the card and are limited by the memory limit. I've read on GPU sites that 4K monitors need an 8GB card, for whatever that's worth. 

Note: This comment was created from a merged conversation originally titled V10.1 Adjustment Brush with Auto Mask followed by use of Spot Removal fixed!!!! Thanks.

Adobe Administrator

 • 

9.2K Messages

 • 

128.2K Points

This thread is being merged into an authoritative thread for better tracking and response. 

Adobe Photography Products

Quality Engineering - Customer Advocacy