P: Generative Remove Feedback (Lr Classic & Lr Eco)

[Rikk Flohr: Photography]

This post applies to Lightroom Classic and the Lightroom Ecosystem products.

Camera Raw feedback can be found here.

Generative Remove makes it easier to remove unwanted objects and distractions with a simple gesture, even on complex backgrounds. For more accurate results, be sure to include the object's shadow in your selection and/or expand its size. 

Detect Objects uses AI to find the objects underneath a brushed area. The masked areas will now appear larger than the Early Access version of this feature. You can also circle objects for quicker selection now. 

We have also updated the spot selection experience to make it easier to manage variations, switch the fill type, refine the selection area, or re-generate as needed. 

Batch updating is also now supported for Generative Remove spots. 

Try out the latest updates and share your feedback with us here. Please also include the following details in your post: 

• App version
• System details
• Example image(s) if you wish to share

Our team continually monitors this thread to track issues for future improvement. Thanks!

Lisa Ngo: Lightroom Product Manager

Posted by:

[John299771167m8b]

I get a hard line around the selection I removed. It needs its own fethering to get rid of this.

[johnrellis]

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

@John299771167m8b: "I get a hard line around the selection I removed."

Remove often has problems matching the tone of the replacement with the background. See my previous reply for three techniques for ameliorating the problem:

https://community.adobe.com/t5/lightroom-classic-discussions/p-generative-remove-feedback-lr-classic...

Using the second technique, raggedy boundaries for the selection, works well with your screenshot:

[dw24154351]

I've attempted to use the feature to remove people from group shots where people are the primary subject.

The process seems to generate weird looking people. Have tried the Remove and Healing tools.

The process doesn't seem to prioritise substituting the selection area for a part of the background, rather it opts for adding somebody that is potentially part of the group. Definitely not my intention - I don't need to add people.

[dw24154351]

LRC 14.0.1 on Sonoma 14.7.1

[johnrellis]

@dw24154351: "I've attempted to use the feature to remove people from group shots where people are the primary subject. The process seems to generate weird looking people."

Airbrushing out a person from a group photo requires a little extra care. See this short help article for details:

https://www.lightroomqueen.com/generative-remove-replace/

See this post for a detailed example:

https://www.lightroomqueen.com/community/threads/removing-disconnected-objects-select-everything-the...

If this doesn't help, please attach a full-resolution JPEG exported from the unmodified original photo (not a screenshot), so we and Adobe can see the issue in detail. With nearly every one of the several dozen problem photos posted here, we've been able to show how to quickly remove the desired objects.

[Burnone2]

Worked well removing graffiti from cliff face in landscape image.

[juliaanastazja]

Tool overlay and icon gets on the way when visualizing the different variations of the remove tool. Needs a toggle to hide it so you can better see the final results.

[C.Cella]

Tool overlay and icon gets on the way when visualizing the different variations of the remove tool. Needs a toggle to hide it so you can better see the final results.

By @juliaanastazja

It's already doable.
See screenshot



Use "H" to hide or show the overaly...same KBSC also des it for masking.

.

[jillymc926]

I can't get anything to remove.  I'm obviously doing something wrong, but nothing seems to happen regardless of what I do.  Perhaps you could make things more obvious and/or intuitive.

[johnrellis]

1. Uncheck Detect Objects (on by default in LR 14) -- it doesn't always work well, especially with skinny objects and along the edges of photos.

2. After clicking Remove, check that the Opacity slider is 100 -- LR infrequently changes it to something else.

3. See this short article for how to remove objects more reliably:
https://www.lightroomqueen.com/generative-remove-replace/

Most complaints about Remove are addressed in the article. But if it doesn't help, please attach a full-resolution JPEG exported from the unmodified original photo (not a screenshot), so we and Adobe can see the issue in detail. With nearly every one of the several dozen problem photos posted here, we've been able to show how to quickly remove the desired objects.

[jillymc926]

Thank you. The opacity thing solved my issue!
Jill


--
'Work like you don't need the money.
Love like you've never been hurt.
Dance like nobody's watching.'

[johnrellis]

@jillymc926: "The opacity thing solved my issue!"

Good. There have been many reports of the opacity slider getting set to something other than 100 -- either LR is buggily changing it or the UI design is fooling too many people into changing it by accident.

[C.Cella]

Per Desing any new remove uses the last set Opacity in the preferences.

e.g

Set the Opacity for an existing Remove to 0
Crete new one

The new one will have Opacity at 0

The team has decided to remove the Opacity slider upon creation from the UI (the slider was there in LrC 13) so we can't immediately crete a Remove at 100% opacity.

I have been thinking about a plug-in taht notifies users at the Opacity is not at 100% BUT it would suffice to instead return that slider to the Ui as before,

Many users had problems due to this ill fated UI redesign.

The issue has been reported by me "in primis" nearly 6 months ago internally, but also publicly by other users: https://community.adobe.com/t5/lightroom-classic-discussions/p-remove-opacity-slider-has-changed-loc...

.

[johnrellis]

@C.Cella: "Per Design any new remove uses the last set Opacity in the preferences."

That likely accounts for much of the confusion -- some users may have previously set Opacity and then don't notice the previous value is used. But I don't think it accounts for many or most of the reports here. How many people deliberately set Opacity to 0? Given the dozens of reports, I think there's a bug, perhaps in the upgrade process, that is setting Opacity to 0 in the preferences.

[C.Cella]

Given the dozens of reports, I think there's a bug, perhaps in the upgrade process, that is setting Opacity to 0 in the preferences.

By @johnrellis

Very possible:

The preference is this one:

<key>AgDevelop_dustSpotOpacity</key>
  <real>1</real>

The minimum allowed value is 0.01
I suggested to always set it to 1 for any new Remove but even this suggestion never was considered.

.

[MicheleDeeVee!!]

lWhen I used generative fill to remove a person and his shadow, there was still a faint outline on the photo so it seemed to just have lighted it up AND it added a little person.  Very weird.  

[johnrellis]

@MicheleDeeVee!!: "When I used generative fill to remove a person and his shadow, there was still a faint outline on the photo so it seemed to just have lighted it up AND it added a little person."

There could be several causes of these symptoms:

1. After clicking Remove, check that the Opacity slider is 100 -- LR infrequently changes it to something else.

2. If you applied Remove on top of an AI mask (e.g. Sky or Subject mask), do the menu command Settings > Update AI Settings to recompute the mask.

3. See this short article for how to remove objects more reliably:
https://www.lightroomqueen.com/generative-remove-replace/

Most complaints about Remove are addressed in the article. But if it doesn't help, please attach a full-resolution JPEG exported from the unmodified original photo (not a screenshot). With nearly every one of the several dozen problem photos posted here, we've been able to show how to quickly remove the desired objects.

[Rico Myburg]

It would be really convenient if the remove brush tool and Generative AI brush were two seperate brushes.

Even better if they each had their own shortcut button. This would be so much better to help with a quicker workflow.

Example: Removing a simple distraction only requires the remove brush but the AI option is selected and vice versa - removing a complex distraction and Gen AI is not selected.

Hope this makes sense.

[johnrellis]

@Rico Myburg:   "Even better if they each had their own shortcut button."

These are the current shortcuts:

- Q opens the Remove panel, with the last-used mode (Remove, Heal, Clone) selected.

- Option Shift G toggles the setting Use Generative AI.

[Aplanc]

Generative Remove works almost to perfection. I had been using quite a lot, and all the time comes out perfect. The no AI stll haas a lot to be desired and also the construcion of the MASKS. They used to be better than now. 

[MassimoMax]

Subject: Observations on Generative Remove Functionality

The Generative Remove tool is a powerful and highly useful feature. However, there is a specific combination of actions that frequently results in "ghosting" artifacts, which might benefit from optimization.

Scenario:
When attempting to remove an object, such as a lamppost against the sky, the following sequence produces suboptimal results:

1. Create Mask using the Sky selection tool.
2. Apply Dehaze at +20/+30.
3. Use Remove with Generative AI (including Object Detection), targeting the lamppost.

Result:
While the lamppost is removed, a faint white "ghost" of the lamppost often remains visible.

Alternative Workflow:
When the sequence is adjusted as follows, the issue is usually resolved:

1. Use Remove with Generative AI (including Object Detection), targeting the lamppost.
2. Create Mask using the Sky selection tool.
3. Apply Dehaze at +20/+30.

Outcome:
In this order, the removal typically occurs without leaving a white ghost of the lamppost.

Technical Details:
I am currently using Lightroom Release 14.1.1 with Camera Raw 17.1.

Hp Z Book Firefly 14" G9 Mobile Workstation with Windows 11 Pro v 23H2, CPU 12th Gen Intel(R) Core(TM) i7-1265U 1.80 GHz, 32 GB RAM, Intel(R) Iris(R) Xe Graphics, NVIDIA T550 Laptop GPU.

This observation may be helpful in refining the Generative Remove tool's interaction with other features like masking and dehazing.

[johnrellis]

@MassimoMax: "While the lamppost is removed, a faint white "ghost" of the lamppost often remains visible."

Right, Adobe recommends doing Remove first and then masking. But if you do masking first and then Remove, you can easily fix the ghosting by doing the menu command Settings > Update AI Settings, which recomputes the underlying AI mask.

See this article for Adobe's recommended order of applying commands:

https://www.lightroomqueen.com/generative-remove-replace/

[joedibr]

NO MATTER WHAT i DO ALL IT DOES IS REPLACE THE OBJECT THAT I'M TRYING TO REMOVE.  LATEST VERSION OF ALL PRODUCTS. IT'S THE FIRST THING I DO AND IT NEVER WORKS!!  

[johnrellis]

@joedibr: "ALL IT DOES IS REPLACE THE OBJECT THAT I'M TRYING TO REMOVE. "

See this short article for how to remove objects more reliably:
https://www.lightroomqueen.com/generative-remove-replace/

Most complaints about Remove are addressed in the article. But if it doesn't help, please attach a full-resolution JPEG exported from the unmodified original photo (not a screenshot). With nearly every one of the several dozen problem photos posted here, we've been able to show how to quickly remove the desired objects.

[joedibr]

If it takes this much work it's too difficult!  I have trie devery suggestion and every order of operations, and nothing worked.  The way it should work, you highlight the object, extend the highlight a reasonable space beyond the object, then hit remomve.  Under NO circumstanses shoulsd a new object be placed in the photo when the REMOVE is hit. Period.