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:

[johnrellis]

@ziggee123: "Instead it will replace the bench with some other weird or whacky bench intead.  I have also had to when I wanted to remove a destracting child from the background.  Intead of cleaning it up, it replaces the child with a random AI generated 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 everyone who has posted a problem photo, we've been able to show how to quickly remove the desired objects.

[ziggee123]

Thank you. I well try that. I’ll do some testing
Sent from my Vic 20

[Carlos De Carvalho]

apos a nova atualização..piorou muito. 

[lex_9408]

Rikk, something changed this week. I updated the AI removal option, but now any removal with or without object removal selection replaces the subject (wife and dog) with a unwanted substitute (repetiveley) Last week removal worked perfect without object selection. I tried to attached the original nikon .dng (Z8) file but that format is somehow not supported. I have therefore convert and attached a jpeg 

Thanks for your support

Best regards Lex 

[willy_9983]

I am having the same problem. I wanted to remove an unwanted part of a person but AI keeps on replacing other unwanted parts instead of removing it. Last week everything worked just fine.

[willy_9983]

Sorry, dat staat er onduidelijk. Ik bedoel dat AI er telkens iets anders voor in de plaats zet in plaats van het te verwijderen.

[johnrellis]

@willy_9983: "I wanted to remove an unwanted part of a person but AI keeps on replacing other unwanted parts instead of removing it."

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 everyone who has posted a problem photo, including many who thought something had changed recently, we've been able to show how to quickly remove the desired objects. But perhaps something has indeed changed, so seeing an example photo is crucial.

[willy_9983]

Het gaat om het restant van een persoon rechts onderdaan in het beeld. Dat krijg ik niet weg.

[johnrellis]

@willy_9983: "It's about the remainder of a person on the bottom right of the image. I can't get rid of that."

With your attached .jpg, Remove immediately removed the remainder of the person from the bottom-right corner:

The image's metadata indicates that you cropped the image along all four sides. So when you applied Remove to the bottom-right corner, Remove was trying to match the unselected, cropped-out pixels.  Adobe wants you to remove first, then crop (which doesn't match many people's natural workflow).

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

[willy_9983]

Bedankt voor je reactie, nu begrijp ik waarom het telkens niet lukte. Het is wat onhandig op deze manier want nu moet ik vooraf inschatten wat ik moet verwijderen. Ik ga het uitproberen. Nogmaals bedankt. Vriendelijke groet, Willy

[johnrellis]

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

@lex_9408: "any removal with or without object removal selection replaces the subject (wife and dog) with a unwanted substitute (repetiveley)"

Be sure to select the shadow cast the by the woman and dog. If you don't select it, then Remove will try very hard to replace them with an object that also casts that shadow:

But when you add the shadow to the selection, it easily removes the woman and dog:

It's too bad that Detect Objects hasn't been trained to include shadows and reflections -- that would help users avoid this common problem.

[C.Cella]

@johnrellis If the Ui had a small "help text" saying "Tip: include shadow and connected parts to Remove in the selection" soooo many users would not have problems

@Rikk Flohr: Photography 

A small help text can surely be added to the Ui in little time by the team.

That small Ui change would help users tremendously with Gen Remove.

.

[lex_9408]

John,

Thanks, I should have known this 

best regards 

Lex 

[stanislavat34109225]

Hello, i dont understand why when i use generative ai and i draw the area i want to fix, why it doesnt hold the area i draw but it draw new one and i have to fix it?

[C.Cella]

@stanislavat34109225 From your description it looks like you are using Detect Objects that makes a new selection, based on the painted area.

Disable it and the paint using Generative Remove normal mode.

[stanislavat34109225]

Hello, how should i do it, please?

[C.Cella]

Uncheck the Detect Objects option, i.e the second checkbox (see screenshot)

[stanislavat34109225]

thank you very much

[C.Cella]

Glad to have helped.

[C.Cella]

FWIW I myself am unable to remove a window despite painting a very large area.

I tried to refresh more times and never I was able to get a result

In Photoshop by instructing the Ai and typing "Wall empty" I got 2 usable results.

So IMO  without instruction Generative Remove is failing too much in LrC.

.

.

[johnrellis]

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

Interesting, that's the first example of several dozen posted here where the object didn't remove easily. After about 5 minutes of experimenting, I was able to remove the window by selecting the discoloration underneath it -- it looks like Remove is treating that discolored area like a shadow and trying to generate something to cast the shadow. I agree that allowing the user to provide prompts as in Photoshop would make this example easier.

Here's my result, along with the same selection with Opacity = 1 to show the original image:

[C.Cella]

@johnrellis 

I think that if I try multiple times eventually I can get the window removed.

But it's a waste of time and credits IMO when in Phothsop is few seconds with instructions.

Now even when Remove succeeds in (LrC or PS) if I zoom I can see the removed area is sub-res/blurred AND the hard edges.

So all looks fine but if one looks carefully the Remove it's evident...it's worse when the area generated is big.

One needs to apply grain on all the image to kinda "hide" the sub res...or the pseudo high res in Phothsop.

.And if one doesn't want to aplly grain then simoly is better to use Clone or Heal that reuse the photo's pixels and have feather.

Reducing Opacity kinda helps with Gen Remove as well but in certain conditions only.

I have sice day one Generative Content in Camera Raw asked to have feathering to at least solve the problem of hard edges...it probably will nver be done.

[johnrellis]

"it's worse when the area generated is big."

That's caused by the maximum size of a replacement patch returned by Firefly, 2048 x 2048 pixels. If the removed area is larger than that, it is upscaled, resulting in loss of detail.

[C.Cella]

@johnrellis 
If one look carefully even very small "holes" have blur



Yes it is hard to spot but the blur is there so it's not only for upscaled patches.

It is sufficient to paint a stroke and the blur, the different color, the hard edges become very evident.

Grain helps to blend the patch and neutralise the blur (or add mroe if one does global Grain) BUT doens't solve the hard edge and the different colors.

I don't know which setting is responsible for the colors (pm_gamma_type or pm_black_level).

[Damian25720529zyod]

Generative AI deleting should have it's own mode - 4th in the remove panel. Or at least, remove tool should reset to deafult after using, because now it saves feature tha was used before, which is often waste of time to change it manually by unchecking 'generative ai' or both 'detect object' and 'generative ai'.