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:

[C.Cella]

When it comes to Generative Remove usually you will have no other choice then to generate anew.

Check the screenshots:



At this point Gen Remove failed, 3 version 0% usability.

I need to rety.




Ah ah, second attempt, variation 5 overall worked.



6 version but overall only 1 works.
1 in 6 success rate.

Same image in Photoshop BUT with instructions when I type as instructions "Cat Fur"

3 versions 1 works
1 in 3 success rate...no need to iterate though version to see which works unlike LrC since thumbnails help.

All it takes for Camera Raw to be more successful at removing is to add instruction..BUT that would open the door to also generating content on our images.

That option is BTW one click away from you:  Edit in > Adobe Photoshop:

.

[johnrellis]

@pavelk39392526: "I did try making the selection larger but it still left a grey line in 20% of the delection"

There might be an easy-to-remedy cause of this:

- If you've applied Remove on top of an AI mask, do Settings > Update AI Settings. That usually helps, but sometimes people have had to delete the AI mask, do Remove, then redo the AI mask.

- You may have the Opacity slider set less than 100. LR sometimes changes the slider during an upgrade and the new LR 14 Remove UI hides the slider, making it easy to miss that it's not 100.

- If the string of lights extends to the edge of the photo, you might have to disable any cropping commands (Crop, Transform, Lens Correction) so Remove doesn't try to match the cropped-out pixels.

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, 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.

[Jermaine23052171on8g]

I feel like this update made the process worse.

[Tincanpuller]

Removed objects. But when I moved image to Photoshop those areas are now shaded.

[paulao65014850]

"intelligent" -- I don't think so....as someone else said it just leaves a Ghost of the object, does not get rid of it.  Perhaps you released the software too soon.  (Yes - fowllowed the Lightroom Queens suggestions, still no luck.)  As is,it useless. (BTW- it happens every time I tried to use AND yes I am updated with your newest release.)

[johnrellis]

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

@paulao65014850: "it just leaves a Ghost of the object, does not get rid of it. ... it happens every time I tried to use"

Make sure the Opacity slider is set to 100:

You'll have to make at least one brush stroke to see the slider. 

If that doesn't help, please attach a full-resolution JPEG exported from the unmodified original photo, 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.

[Norbert37623792xq2h]

Generative remove in the new version is working less efficient than the previous version. even when only removing unwanted birds or sensor dust in the sky, in 80% of all cases it creates visible edges that can not be removed with LR - not a success.

[johnrellis]

@Norbert37623792xq2h: "even when only removing unwanted birds or sensor dust in the sky, in 80% of all cases it creates visible edges that can not be removed with LR"

There have been a couple other similar complaints here, but no original photos posted showing the problem.  Please attach a full-resolution JPEG exported from the *unmodified* original photo, so we and Adobe can see the issue in detail.

[aaronfoster84]

I am trying to remove a person from my photo and the generative remove tool keeps putting a bear in place of the person I am trying to remove.  I dont want it to do that.

[johnrellis]

@aaronfoster84: "the generative remove tool keeps putting a bear in place of the person I am trying to remove."

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, 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.

[Olivier 64]

Bonjour 

Ok avec le message précédent , le système est devenu trés trés lent .... on ne sais même plus ce qu'on a sélectionné tellement c'est lent et cela provoque des erreurs .

j'espère une amélioration rapide 

Cordialement

[SteveS64]

I tried to remove a parked car in front of a well known building, and I was surprised that the image library you're using didn't have enough info in it to replace the object. It didn't fill the bushes correctly, one option, put a walkway and a door where there were bushes and a window. It's a night shot, so far from perfrect. I'm pretty sure I can fix with photoshop, but still...

Good try, This really wasnt a great shot, and I bet I get better results with people

[Mark340860516rwv]

Absolute rubbish, it can't even remove a small corner of my image that should be the easiest thing for it to compute. See before and after images attached. The object to be removed is a white triangular shaped distraction in the bottom right.

[johnrellis]

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

@Mark340860516rwv "it can't even remove a small corner of my image ... The object to be removed is a white triangular shaped distraction in the bottom right."

Using Before.jpg, my LR easily removed the white triangle in the corner:

When Remove has problems with objects on the edges of the photo, that indicates there are cropped-out pixels beyond the edge that Remove is trying to match (green background, in this case). So you have to undo any cropping commands (Crop, Transform, Lens Correction), apply Remove, then redo those commands.

However, the metadata in Before.jpg indicates that it was exported from a Nikon D750 raw, with none of those cropping commands applied. That camera's raw sensor is 6032 x 4032 pixels, and the Camera Raw engine in LR automatically crops it to 6016 x 4016. That cropping is invisible to the user and always occurs, but Remove looks at those cropped-out pixels nevertheless.

See here for how to select those hidden pixels and ensure Remove doesn't try to match them: 

https://community.adobe.com/t5/camera-raw-discussions/generative-remove-doesn-t-ignore-the-hidden-bo...

Adobe considers this "as-designed" rather than a bug.

[Mark340860516rwv]

That’s very interesting, thanks for the info and explanation. I’ll have a look at this image again and keep at it.

Rgds
Mark G

Sent from my iPhone

[MichaelN0815]

LR 14.0.1

I generate a mask for the sky and increase the brightness.

Then I remove a part (here the top of the hill) which is in the area of this mask with Generative Removing.

The removed part is still visible due it's different brightness.

Bug or Feature?

[johnrellis]

@MichaelN0815: "I generate a mask for the sky and increase the brightness. Then I remove a part (here the top of the hill) which is in the area of this mask with Generative Removing. The removed part is still visible due it's different brightness."

Do Settings > Update AI Settings to have LR recompute the sky mask. In general, Adobe wants you to do Remove first then apply masks.

[MichaelN0815]

THX, I didn't know that. It's possible to Update all affected masks? Or a Solutions to search for it? And, more important, what the reason for the need of update the mask?

[sb2314]

Make sure you are using 100% opacity. Good luck!

[sb2314]

In my experience, I do the generative remove before anything else and keep the outside portion of the round brush well outside the edges. Then do all other editing. If you do a denoise first, it's still OK. Good Luck.

[Weigl2951085693w8]

The new version of the removal has become much worse, whether with or without generative removal. It also generates stripes. very bad version 14. and very slow!!!

[ctcbox]

Oct 19, 2024    Installed LRC V 14.01 yesterday. I have been working on a particular set of 150 photos and LRC asked to Update All in your AI Removal tool for many of my photos ( I didn't look outside my small group of 150.). After accepting my update when I return to some of the photos LRC is asking to Update All again. I have also had to Update All for my masks, although usuall only once. I then went through EACH of the 150 and clicked on Updare All as necessary. Now, a day later, some of the 150 are asking for Update All. One would not accept the Update All and the button remains in the AI Removal box. It appears you have a buggy update. Many others seem to be having problems as well. I tried to go back to 13.75 but you changed the catalog without a backup copy and I am stuck with your problematic 14.01. Please help me do something to my catalog so I can go back to the old version.  Thank you for your help.

[ctcbox]

I just read the post above mine. I have been getting striping as well. They usually show up in in heavily processed images usually in dark blue areas when printed. I have printed on several printers including professional services and the stripes are still there i.e. it's not my printer... They don't show up on my monitor just when printed.

[C.Cella]

@ctcbox the uodate process automatically created a backup copy of your LrC 13.5 catalog

It is in the folder Old Lightroom Catlogs located next to the catalog that was updated.

I suggest to go back to using LrC 13 until Adobe fixes these bugs.

Fwiw nobody needs to Update Ai Settings photo by photo.

Select them all and run the command Update Ai Settings in batch.

In LrC 13 there will be no update to do Btw.

[johnrellis]

@ctcbox: "Installed LRC V 14.01 yesterday. ... a day later, some of the 150 are asking for Update All. One would not accept the Update All and the button remains in the AI Removal box.:"

Please add details of your experience to the bug report about this problem:

https://community.adobe.com/t5/lightroom-classic-bugs/p-subject-mask-from-previous-versions-are-requ...

where it's more likely to have impact than this kitchen-sink thread.  Also, if you follow that thread, you're more likely to see status updates.