• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • Stop struggling with Lightroom! There's no need to spend hours hunting for the answers to your Lightroom Classic questions. All the information you need is in Adobe Lightroom Classic - The Missing FAQ!

    To help you get started, there's a series of easy tutorials to guide you through a simple workflow. As you grow in confidence, the book switches to a conversational FAQ format, so you can quickly find answers to advanced questions. And better still, the eBooks are updated for every release, so it's always up to date.
  • 12 December 2024 It's Lightroom update time again! See What’s New in Lightroom Classic 14.1, Mobile & Desktop (December 2024)? for Feature updates, new cameras and lenses, and bug fixes.

Develop module Removing disconnected objects: Select everything, then Subtract

Status
Not open for further replies.

John R Ellis

Senior Member
Lightroom Guru
Premium Classic Member
Premium Cloud Member
Joined
Apr 3, 2012
Messages
3,103
Location
Bay Area, California, USA
Lightroom Experience
Power User
Lightroom Version
Classic
Lightroom Version Number
13.4
Operating System
  1. Windows 11
  2. macOS 14 Sonoma
The guidance provided by Adobe and the Lightroom Queen article on Generative Remove states the need to "Select the entire object/person, including ... any disconnected parts (such as a hand on someone else’s shoulder). " If you don't select the entire object or person, Remove is amazingly clever at generating something that best matches the remaining parts, which we perceive as "replacing" rather than "removing".

But there's a gotcha in the current Lightroom Classic user interface, and selecting an object with disconnected brush strokes makes it more likely Remove will "replace" rather than "remove". To avoid the gotcha, follow this rule:

Select all of the disconnected parts with a single set of connected brush strokes, then refine with Subtract to remove the unwanted parts from the selection.

Gory Details

When you add a refining brush stroke more than a very small distance away from the first stroke, LR Classic (but not LR Desktop) treats it as a separate selection (with its own pin), and the remove algorithm runs on the two selections separately, not as a single unit. This makes it more likely that each generated replacement will be "replacing" rather than "removing".

In this example (motivated by a post in the feedback thread), I want to remove the deck railings, so I select the railings on the left and then on the right, with two different brush strokes:

Screenshot 2024-07-10 at 11.56.57 AM.jpg


After clicking Apply, Remove treats the disconnected brush strokes as two separate selections, each with its own pin:

Screenshot 2024-07-10 at 11.57.45 AM.jpg


Remove has generated a replacement for the two selections separately. When it generates the first replacement, it matches the remaining railing in the second selection, and when it generates the second replacement, it matches the first selection (or its replacement). As a result, it generates new variants of the railing. When you select one of the pins and click Variations, you see variants for just that selection (and all of the variants are railings).

Thus, you need to select the entire railing with one connected brush stroke:

Screenshot 2024-07-10 at 12.13.10 PM.jpg


That successfully "removes" the railing but generates a funky brass door handle:

Screenshot 2024-07-10 at 12.15.29 PM.jpg


So to prevent Remove from modifying the wood divider with a door handle, refine with a Subtract brush to remove the divider from the selection:

Screenshot 2024-07-10 at 12.23.10 PM.jpg


LR still treats this as a single selection, even though it's visually indistinguishable from two separate brush strokes. With this single selection, Remove successfully removes the railing without modifying the wood divider:

Screenshot 2024-07-10 at 12.26.46 PM.jpg


Here's another example, where I want to do a Stalinist airbrushing away of a disfavored family member. If you make three disconnected brush strokes to select the different parts of the person, you end up with another person generated as the replacement:

Screenshot 2024-07-10 at 12.40.09 PM.jpg
Screenshot 2024-07-10 at 12.41.11 PM.jpg


(Note that the lower-right small brush stroke is sufficiently close to the larger brush stroke that LR considers the two to be one selection, whereas the left brush stroke is considered a separate selection/pin.)

But if you select all the parts of the person you want removed with connected brush strokes and then do a refining Subtract to deselect the parts that shouldn't be removed, the results are surprisingly good:

Screenshot 2024-07-10 at 12.43.38 PM.jpg
Screenshot 2024-07-10 at 12.44.15 PM.jpg


Regarding this surprising behavior of refining brush strokes, Adobe employee Rikk Flohr says, "Lightroom Desktop and Lightroom Classic behave differently in this regard and that both behaviors are being evaluated while the feature is in Early Access. "
 
Last edited:
Excellent examples John, I’ll update the post to link to this tomorrow
 
The guidance provided by Adobe and the Lightroom Queen article on Generative Remove states the need to "Select the entire object/person, including ... any disconnected parts (such as a hand on someone else’s shoulder). " If you don't select the entire object or person, Remove is amazingly clever at generating something that best matches the remaining parts, which we perceive as "replacing" rather than "removing".

But there's a gotcha in the current Lightroom Classic user interface, and selecting an object with disconnected brush strokes makes it more likely Remove will "replace" rather than "remove". To avoid the gotcha, follow this rule:

Select all of the disconnected parts with a single set of connected brush strokes, then refine with Subtract to remove the unwanted parts from the selection.

Gory Details

When you add a refining brush stroke more than a very small distance away from the first stroke, LR Classic (but not LR Desktop) treats it as a separate selection (with its own pin), and the remove algorithm runs on the two selections separately, not as a single unit. This makes it more likely that each generated replacement will be "replacing" rather than "removing".

In this example (motivated by a post in the feedback thread), I want to remove the deck railings, so I select the railings on the left and then on the right, with two different brush strokes:

View attachment 23742

After clicking Apply, Remove treats the disconnected brush strokes as two separate selections, each with its own pin:

View attachment 23745

Remove has generated a replacement for the two selections separately. When it generates the first replacement, it matches the remaining railing in the second selection, and when it generates the second replacement, it matches the first selection (or its replacement). As a result, it generates new variants of the railing. When you select one of the pins and click Variations, you see variants for just that selection (and all of the variants are railings).

Thus, you need to select the entire railing with one connected brush stroke:

View attachment 23746

That successfully "removes" the railing but generates a funky brass door handle:

View attachment 23747

So to prevent Remove from modifying the wood divider with a door handle, refine with a Subtract brush to remove the divider from the selection:

View attachment 23748

LR still treats this as a single selection, even though it's visually indistinguishable from two separate brush strokes. With this single selection, Remove successfully removes the railing without modifying the wood divider:

View attachment 23749

Here's another example, where I want to do a Stalinist airbrushing away of a disfavored family member. If you make three disconnected brush strokes to select the different parts of the person, you end up with another person generated as the replacement:

View attachment 23750 View attachment 23751

(Note that the lower-right small brush stroke is sufficiently close to the larger brush stroke that LR considers the two to be one selection, whereas the left brush stroke is considered a separate selection/pin.)

But if you select all the parts of the person you want removed with connected brush strokes and then do a refining Subtract to deselect the parts that shouldn't be removed, the results are surprisingly good:

View attachment 23752 View attachment 23753

Regarding this surprising behavior of refining brush strokes, Adobe employee Rikk Flohr says, "Lightroom Desktop and Lightroom Classic behave differently in this regard and that both behaviors are being evaluated while the feature is in Early Access. "
Great info but to Adobe Engineers I would say, "You named it the Remove Tool, if you want to have it do removals and generations add a switch so we can tell it what we want."
 
Great info but to Adobe Engineers I would say, "You named it the Remove Tool, if you want to have it do removals and generations add a switch so we can tell it what we want."
It's called the Remove tool because it is supposed to only remove things, not generate new things based on text like Photoshop can. When it does generate new things, then that's because you left traces of something that need to be matched to something.
 
"You named it the Remove Tool, if you want to have it do removals and generations add a switch so we can tell it what we want."
Good one to put as a Feature Request (link at the top of the page).
 
Unfortunately, Remove selections in LR Classic 14 still behave the same, confusing way. I haven't tested LR Desktop or Camera Raw to see if they've been changed to work like LR Classic.
 
I haven't tested LR Desktop or Camera Raw to see if they've been changed to work like LR Classic.
Desktop, at least, was changed to match Classic's behavior. Apparently, they didn't hear your excellent argument!
 
Status
Not open for further replies.
Back
Top