• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
3

P: Spot removal removing brush stroke

Community Beginner ,
Oct 26, 2020 Oct 26, 2020

Copy link to clipboard

Copied

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. 

Bug Fixed
TOPICS
macOS , Windows

Views

1.3K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 2 Correct answers

Adobe Employee , Dec 08, 2020 Dec 08, 2020

Greetings,

Updates to the Adobe Photography Products were released yesterday and include a fix for this issue. Please install the December update, restart your system and verify that you are no longer experiencing the issue.

Thank you for your assistance in reporting, providing additional information and, most of all, for your patience.

Votes

Translate

Translate
LEGEND , Nov 08, 2020 Nov 08, 2020
71 Comments
LEGEND ,
Nov 05, 2020 Nov 05, 2020

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 05, 2020 Nov 05, 2020

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Participant ,
Nov 05, 2020 Nov 05, 2020

Copy link to clipboard

Copied

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 

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 05, 2020 Nov 05, 2020

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Participant ,
Nov 05, 2020 Nov 05, 2020

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 07, 2020 Nov 07, 2020

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Participant ,
Nov 07, 2020 Nov 07, 2020

Copy link to clipboard

Copied

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. 

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 08, 2020 Nov 08, 2020

Copy link to clipboard

Copied

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

And thanks for the tip on the Auto Mask!

Votes

Translate

Translate

Report

Report
Community Beginner ,
Nov 08, 2020 Nov 08, 2020

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 08, 2020 Nov 08, 2020

Copy link to clipboard

Copied

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 08, 2020 Nov 08, 2020

Copy link to clipboard

Copied

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 16, 2020 Nov 16, 2020

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Contributor ,
Nov 16, 2020 Nov 16, 2020

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Community Beginner ,
Nov 23, 2020 Nov 23, 2020

Copy link to clipboard

Copied

Any news on an update fix for this issue?

Votes

Translate

Translate

Report

Report
LEGEND ,
Nov 25, 2020 Nov 25, 2020

Copy link to clipboard

Copied

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.  

Votes

Translate

Translate

Report

Report
Participant ,
Dec 07, 2020 Dec 07, 2020

Copy link to clipboard

Copied

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. 

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Dec 08, 2020 Dec 08, 2020

Copy link to clipboard

Copied

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

Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Dec 08, 2020 Dec 08, 2020

Copy link to clipboard

Copied

Greetings,

Updates to the Adobe Photography Products were released yesterday and include a fix for this issue. Please install the December update, restart your system and verify that you are no longer experiencing the issue.

Thank you for your assistance in reporting, providing additional information and, most of all, for your patience.

Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Community Beginner ,
Feb 06, 2021 Feb 06, 2021

Copy link to clipboard

Copied

Please see this thread with a similar issue I'm having on LR v10.1.1

https://feedback.photoshop.com/conversations/lightroom-classic/brush-work-being-deletedmodified-on-g...

Votes

Translate

Translate

Report

Report
New Here ,
Jul 15, 2021 Jul 15, 2021

Copy link to clipboard

Copied

hi,

i just had experienced this MASSIVE bug and freaked out.
i was noticing some weird behaviors recently but took me a while to connect the dots and finally arrive here to this thread.

what i can add is that it happens to me only with "gpu acceleration" activated, and on Classic V10.

I read that on 10.1.1 the bug is solved.

anybody whom wrote here could confirm this please?

Votes

Translate

Translate

Report

Report
New Here ,
Jul 15, 2021 Jul 15, 2021

Copy link to clipboard

Copied

LATEST

alright i can confirm it myself. problem solved.

Votes

Translate

Translate

Report

Report