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

@X1Jogi: "Takes too long compared to stamping, e.g. to stamp away sensor spots (pollen, dust, ...). "

Adobe recommends you use the other Remove modes (Content-Aware, Heal, Clone) for correcting small spots.

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

You've cropped the photo. Remove looks at all the pixels in a photo, included those that are cropped out, and it's generating replacements that match those unselected cropped-out pixels. 

Adobe wants you to remove first, then crop (which doesn't match many people's natural workflow).  So undo the crop, do Remove, then crop again. 

See this 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 everyone who has posted a problem photo, we've been able to show how to quickly remove the desired objects.

@evalsky: "Generative remove was unable to remove flash reflection in a window, and when someone's ear was in the vicinity, it made us look like elves."

It sounds like you may have had checked the Detect Objects selection, which often makes the selection too big. Uncheck it and then select just the flash with a smaller border around the flash that doesn't include human parts.

If that doesn't help,see this 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 everyone who has posted a problem photo, we've been able to show how to quickly remove the desired objects.

@eXecutiveHippie Adobe censorship is kicking in.

Whenever there is some skin showing in the image (e.g. woman in bikini) then Adobe Ai thinks we want to generate p*** or nudity content.

Both legal in many countries especially the latter.

I want to make an example.

Female model wearing lingerie (lingerie job)

I try to remove a scratch ON THE BACKGROUND so not the model's body NOR what she is wearing.

Violation of guidelines!

It's nonsense and the same happens in Photoshop BUT in Photoshop it can be done with a simple workaround.

There is a way to bypass this nonsensee in LrC but you need to use a Plug-in (not because it allows illecit content OR hijacks the system) but becausee it allows to work properly with Remove.

.

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

@Blue Baron II: "I want to remove one of the generative replacements that I did. but it will not go away.  I right click on the idon and chose remove, but nothing happens."

That right-click menu is confusing. Select Delete, not Remove, to get rid of the chosen instance of Remove.

Adobe made some very confusing choices for the names of the command and its various modes (precision naming hasn't been their forte). The overall tool is called "Remove", and it's various modes are called "Remove" (the old content-aware), "Generative Remove" (aka Generative AI Remove), "Heal", and "Clone".   The first four menu items in that right-click context menu let you change the mode of the existing Remove tool selection, e.g. from Generative Remove to content-aware non-generative Remove.

@kenneth_4368: "This update doesn't remove any objects even small ones."

After clicking Remove, check that the Opacity Slider is at 100:

For some people, the update sets it to something less than 100.

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

With your screenshot, Remove immediately removed the tire:

Things to check:

1. If you had previously cropped the photo, then undo the crop, do Remove, then crop again. Remove looks at all the pixels in a photo, including those that are cropped out, and it's generating replacements that match those unselected cropped-out pixels. Adobe wants you to remove first, then crop (which doesn't match many people's natural workflow). 

2. You might have to select more of the shadow cast by the tire. Otherwise, Generative AI can create replacements that also cast the shadow.

See this 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. 

@lalocurapura: "I am trying to remove a child from the corner of a picture I took of my two kids, but the generative remove always puts me another child there, in all versions"

1. Is the photo cropped?  If so, uncrop it, do the Remove, and then re-apply the Crop.  Remove tries to match the cropped-out pixels.

2. Make sure you select all bits of the child, even small ones that might be disconnected from the main part of the child (e.g. a hand around the shoulder).  And select any shadows cast by the child.

See this 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 everyone who has posted a problem photo, we've been able to show how to quickly remove the desired objects.