P: Spot removal removing brush stroke

Why conversations get merged: https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-auto-import-to-folders-organized-by-date/5f5f44f14b561a3d422ab0ba?commentId=5f5f48984b561a3d422bdf45 

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.

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

And thanks for the tip on the Auto Mask!

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. 

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

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

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.

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 

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.