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:

[Alluring_customer15D5]

For example in my attached picture, in the mask panel, it detected 2 people, if there is an option on each person "person 1", "person 2", named maybe "remove with AI", then the people will be removed and generate AI background automatically, it will be much easier for me to use "remove panel" to select the person.

[johnrellis]

@Alluring_customer15D5, got it, makes sense.

[JohnS4557]

I have been using Generative AI to remove people from nighttime and interior displays (Smithstonian Institute); however, a darkish smudge remains after the event. It works well in daylight situations, such as the Arizona desert.

[johnrellis]

@JohnS4557: "a darkish smudge remains"

Are you referring to this?

Please attach a full-resolution JPEG exported from the unmodified original photo.

[JohnS4557]

Yes, even after repeated generations of the area.

[johnrellis]

@JohnS4557: "Yes, even after repeated generations of the area."

Remove did a very good job of removing the black smudge (see below), replacing it with a rope post matching the hanging rope (a great illustration of the fact that all "removes" are really just "replaces").  If you attach a full-resolution JPEG exported from the unmodified original photo, we can see what might be preventing you from removing the person in one go. With nearly every one of the many dozen problem photos posted here, we've been able to show how to quickly remove the desired objects.

[BushEhVee8er]

First of all, I can't say how amazed that I am at how well this works. I use it often and it's amazing. 

Two things I would like to see. 

1. A way to remove window glare and reflections while still preserving the underlying image. I sometimes shoot from aircraft in varrying different lighting conditions. Recently we flew across the rockys and I took a bunch of shots out my window. I was trying to remove the larger reflections of inside the cockpit without changing the mountains outside, but as the AI uses surrounding areas and features to generate the fill image (at least I think this is what it's doing) I lose the integrity of the original scenery. As much as I usually like the result, I prefer to maintain the original integrity of the photo because I feel that I'm creating a historical record and want it to be representative of the scene I'm seeing, instead of artificiallly generated details.

2. I'd like to see a historical save of the generations of the AI.. There are times I'm hesitant to click the Generate button after looking at the 3 selections because maybe I've gotten the best one within those three, but don't know it yet.

Thanks! Keep up the great work with this. 

[johnrellis]

@BushEhVee8er: "There are times I'm hesitant to click the Generate button after looking at the 3 selections because maybe I've gotten the best one within those three, but don't know it yet."

Click the + button in the Snapshots panel in the left column to create a snapshot of each promising variant. Then you can quickly review the candidates simply by hovering the mouse over each snapshot in turn.

[johnrellis]

@BushEhVee8er: "A way to remove window glare and reflections while still preserving the underlying image."

Try the "technology preview" of the Reflection Removal tool in Camera Raw:

https://helpx.adobe.com/camera-raw/using/remove-reflections.html

Maybe that will eventually appear in LR.

[ZappaJul]

Gen Remove Feedback, LrC  14.2

MacBook Pro M3 Max, 64GB 1TB SSD, Sequoia 15.3.2. Experience: LrC 18 years / PS 25 years.

I'm finding all the Gen AI tools immensely frustrating in both LrC and PS. Even worse is the loss of functionality we had previosuly, so I can't even just ignore them. I rarely have issues learning new software but this has ruined my workflow and caused massive loss of productivity. The remove/clone/heal tools in LrC were never brilliant, but they did have their uses for isolated areas away from high contrast elements. Now even that basic functionality has vanished and I have to go PS for 99% of heal / remove clone actions.

File 1 (attached): Task: Remove door knob from foreground. Initially tried Generative Remove but it added so many other artefacts I gave up. Returned to file later to try other tools (Remove, Heal). Results:
File 2 (attached): Fill > Remove. Tried 3 x refresh, difference barely visible, so not included here.

File 3 (attached): Fill > Heal (this would have worked OK previously).

File 4: (immediately below) Refresh x 1 (Seriously? Why sample the curtain? It bears no reseenblance to either doorknob or cupboard and is nowhere near either in image).

File 5: Refresh x 2

File 6:  Refresh x 3

File 7: Fill > returned to Generative Remove. This time it worked. Wish I'd kept all the versions with artefacts it added previously, which included adding copies of the cupboard handles in background, completely new cupboard handles it made up, more versions involving the curtains and removal of white line seperating wardrobe doors.

It took a total of ±12-15 attempts before achieving the final result. I don't have time for this.

I wish Adobe had either left the whole AI thing alone or made sure it worked reliably before integrating it it into every element of the software, and left the old tools alone so users could fall back on them when the AI fails - which is provign to be most of the time so far. It works well for very specific tasks which look great when demonstrated at shows / online, but it's failed me utterly in my everyday work).

[johnrellis]

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

@ZappaJul: "Remove door knob from foreground."

Generative Remove eliminated the doorknob from your screenshot on the first try:

Make sure you uncheck Detect Objects -- it doesn't work well, especially with skinny objects and along the edges of photos.

If that doesn't help, please attach a full-resolution JPEG exported from the unmodified original photo (not a screenshot), so we can see what might be going wrong. With nearly every one of the many dozen problem photos posted here, we've been able to show how to quickly remove the desired objects.

[johnrellis]

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

@ZappaJul: "The remove/clone/heal tools in LrC were never brilliant, but they did have their uses for isolated areas away from high contrast elements. Now even that basic functionality has vanished"

The previous tools, now called "modes", are still available:

Clone:

Heal:

Content-Aware Remove:

[ricoyvr]

Lightroom Classic Version 14.2

Macbook Pro M4 48GB

In this sample photo, I selected the "ThinkPad" logo off of a laptop hood using the remove tool with generative AI.

You'll see that it removed the logo, BUT you can clearly see the blotch left behind.

This image was shot at ISO 8,000 so there is some noise in this image, and although LRC removed the logo, it could not properly match the noise levels of the surrounding area to make it 100% invisible.

[johnrellis]

@ricoyvr: "This image was shot at ISO 8,000 so there is some noise in this image, and although LRC removed the logo, it could not properly match the noise levels of the surrounding area to make it 100% invisible."

A fair number have complained about this. A couple of ways to deal with problem:

1. Adobe recommends applying Denoise before Remove. This can reduce the noise, making it more likely the replacement will match.

2. See this post for how to ameliorate the problem by adding the grain back or reducing the grain:
https://community.adobe.com/t5/lightroom-classic-discussions/p-generative-remove-feedback-lr-classic...

[FleurVastgoedsuppo]

Hello, sinds a month or longer, when i use thus tool, after a few seconds i go back to the previous picture. The part that i erased with the erase tool with Generative AI is not erased anymore. Instead it says, the preferences needed to be updated. 

The i click on update everything underneath this tool and then it needs some seconds, sometimes like 20. 

But the problem isn't solved, still needed to update again and again. 

I deleted Lightroom Classic and downloaded again, also made a new lightroom catalog. 

Anybody with the same problem? 

It runs on a macmini 

everything is updated like lightroom classic and other software. 

Gr. Fleur 

[johnrellis]

@FleurVastgoedsuppo: "The part that i erased with the erase tool with Generative AI is not erased anymore. Instead it says, the preferences needed to be updated.  ... still needed to update again and again."

An earlier version of LR 14 fixed a serious bug with these symptoms.  Next steps:

A. Do the menu command Help > System Info. If you're not running LR 14.2 (the current version), do Help > Updates.

B. These symptoms can occur when LR can't write the .lrcat-data file for some reason, either because LR has corrupted it or there is a permissions issue. LR stores computed masks in that file. Try these steps:

1. In LR, do Edit > Catalog Settings > General > Show. That will open Windows File Explorer on the current catalog folder.

2. Exit LR.

3. Move the file <catalog>.lrcat-data to the Desktop.

4. Start LR.

5. In Library Grid view (not Loupe view), select all photos and do Photo > Develop Settings > Update AI Settings. That will recompute all the AI masks, which could take a while. 

C. If steps A and B don't help, do the LR menu command Help > System Info and copy/paste the entire contents here so we can see exactly which versions of hardware and software LR thinks you're running and important LR options that are set.

[DavidH77]

I often run into the generative AI remove tool refusing to do it's job citing 'check community guidlines'. I'm a professional photographer working with dancers and gymnasts. I regularly have this issue. I find it rather annoying that a person wearing a typical dancer outfit or a leotard triggers some kind of guideline issue. I'm usually trying to fix hair falling into the person's face or a wrinkle in the fabric.
I'm including my current version below, but it is really irrelevant as I have been getting these flase guidline fails with every version since generative AI remove has been added to Lightroom Classic.

MacBook Pro M1

15.3.2 (24D81)
Lightroom Classic 14.2

Attached is a screen shot of a typical photos where generative AI refuses to work. It works fine on different photos from this session, same outfit, just a different pose.

[johnrellis]

Lots of people have complained about this in the feedback thread for Generative Remove:

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

Adobe, like the other major AI providers, is scared of the political fallout that might occur if their platforms were used for pornography (especially child p o r n) and other "socially harmful" purposes. So they tune their automatic detection algorithms conservatively, erring on the side of too many false positives.

No one has posted any workarounds.

[johnrellis]

I had to replace with "child p o r n" just now to get around the nanny filter.