Strange Behavior of the Remove Tool in Lightroom Classic 14.0.1 – Has Anyone Experienced This Issue?

[Słowik inspiruje]

Hi,

I've encountered strange behavior in Lightroom Classic. When I make adjustments to one part of the sky using the Remove tool, another part of the sky—where I haven’t made any changes—becomes brighter on its own! This is very odd behavior from the software and often makes it difficult for me to work with the Remove tool.

Check out the video I recorded demonstrating this strange behavior of the Remove tool in Lightroom Classic 14.0.1.

https://youtu.be/8AS5ikTluFQ

I’m curious if any of you have experienced the same issue?

Have a great day,
Paweł Słowik
www.slowik.eu

[Słowik inspiruje]

My system info:

Wersja Lightroom Classic: 14.0.1 [ 202410161356-30922cfc ]
Licencja: Creative Cloud
Ustawienie języka: pl
System operacyjny: Mac OS 15
Wersja: 15.1.0 [24B83]
Architektura aplikacji: arm64
Liczba procesorów logicznych: 10
Szybkość procesora: NA
Wersja SqLite: 3.36.0
Źródło zasilania: Podłączony, 100%
Wbudowana pamięć: 16 384,0 MB
Dedykowana pamięć GPU używana przez Lightroom: 947,5MB / 10 922,6MB (8%)
Pamięć rzeczywista dostępna dla Lightroom: 16 384,0 MB
Pamięć rzeczywista używana przez Lightroom: 2023,3 MB (12,3%)
Pamięć wirtualna używana przez Lightroom: 414 762,3 MB
Rozmiar pamięci podręcznej pamięci: 72,7MB
Wewnętrzna wersja wtyczki Camera Raw: 17.0 [ 2043 ]
Maksymalna liczba wątków używanych przez Camera Raw: 5
Optymalizacja SIMD Camera Raw: SSE2
Pamięć wirtualna programu Camera Raw: 85MB / 8191MB (1%)
Pamięć rzeczywista programu Camera Raw: 316MB / 16384MB (1%)

Cache1:
Final1- RAM:89,0MB, VRAM:270,0MB, 80D2944B-D2D7-415F-B2BE-9B7A4E31307D.dng
NT- RAM:89,0MB, VRAM:270,0MB, Combined:359,0MB

Cache2:
m:72,7MB, n:35,3MB

U-main: 115,0MB

Rozmiar podglądu standardowego: 3024 piksele(i)
Wyświetlacze: 1) 3024x1964

Procesor graficzny – informacje:
Metal: Apple M1 Pro
Stan inicjalizacji: Użycie procesora graficznego do eksportu jest domyślnie obsługiwane
Preferencje użytkownika: Automatyczne
Włącz tryb HDR w bibliotece: WYŁ.

Folder aplikacji: /Applications/Adobe Lightroom Classic
Ścieżka biblioteki: /Users/pawelslowik/Pictures/#LIGHTROOM-CATALOG/Lightroom2021-v13-3.lrcat
Folder ustawień: /Users/pawelslowik/Library/Application Support/Adobe/Lightroom

Zainstalowane wtyczki:
1) DxO PureRAW 3
2) DxO PureRAW 3 Importer
3) Flickr
4) LensTagger Exif Tool

Flagi Config.lua:

[JohanElzenga]

What you probably see here is that you applied Dehaze. Dehaze is a complicated calculation, based on the entire image. So if you remove a bright part of the image, it is possible that this affects the Dehaze result on the rest of the image.

[Słowik inspiruje]

Hi Johan,

Thank you for your response! I understand how adjustments like Dehaze or Clarity could influence other parts of the image due to their nature, but in this case, neither Dehaze nor Clarity were used. This odd behavior occurs even on a clean RAW file with no added adjustments right after opening it in Lightroom. It seems that the Remove tool itself might be causing unintended changes to the brightness in untouched areas of the sky.

If anyone else has encountered this issue or has insights on why this might be happening, I’d love to hear your thoughts!

Best regards,
Paweł Słowik

[JohanElzenga]

I don't think that the remove tool itself can possibly change parts of the image that it didn't select. This must be some effect that is based on the entire image, and the fact that this image has changed. Maybe the profile has something to do with it. You could try to select another profile and see if that changes this behavior. Also double check your camera defaults, because some edits (like dehaze) could be part of a custom profile that is applied in a camera defaults preset.

[JohanElzenga]

BTW, have you tried resetting the preferences? A lot of strange things can happen if there is corruption of the preferences: 

https://www.lightroomqueen.com/how-do-i-reset-lightrooms-preferences/

[Słowik inspiruje]

Hi,

I appreciate your input! I’ve been using Lightroom for seventeen years, so I’m quite familiar with how it typically behaves. The file is a clean RAW image with no edits applied, and this issue happens regardless of the profile I choose—be it Adobe Color, Adobe Neutral, or Adobe Standard.

Here’s the RAW file if you’d like to check it out yourself: https://1drv.ms/i/s!AsZHYrT1GG17reNdnW7QbKFlxsuLww?e=dgkXfY

I’ve done some additional testing and found that this effect doesn’t happen with every file. However, it has occurred on multiple recent images, which is why I posted about it—it’s not an isolated incident. Any further ideas would be much appreciated!

Thanks,
Paweł Słowik

[JohanElzenga]

Thanks, I will try to test it later today if I can (using my iPad right now). Did you try resetting the preferences already? This tool is many years old. So even if this only occurs with some images, it is very unlikely that this would never have been seen and reported by anyone else if it is some bug.

[JohanElzenga]

I just downloaded your photo and tried the same Healing tool action with the exact same tool settings (I did have to darken the image about one stop, or else the sky was way too bright to see anything), but I cannot reproduce what you show in the video. The bright part on the right is removed, but nothing else is affected in any way, no matter how carefully I look at it.

However, if I add some Clarity or some Dehaze, then I do see the same thing as you see. With Clarity 30 it is not very pronounced but still visable, with Dehaze 30 it is quite clear. Do reset the preferences if you did not set any clarity or dehaze, because that is almost certainly what causes it.

[GoldingD]

I notice the down arrow in the thumbnail indicating a metadata conflict (changed in LrC not in image??) I have no idea why that world effect an develop edit. I suspect that the cause of the conflict might, maybe, perhaps, relate????