Question

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

Forum|Forum|1 year ago
August 13, 2024
652 replies
573375 views

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:

M

Melina5C8D

Inspiring

Hi Adobe team,

I'm experiencing a significant performance regression with Generative Remove on my Intel iMac after updating to Lightroom Classic 15.4.1.

System

Lightroom Classic 15.4.1
macOS 26.5.2
Intel Core i5 iMac
AMD Radeon Pro 5300 (4GB VRAM)
72GB RAM

Generative Remove now takes 4+ minutes to remove a tiny skin blemish. The standard Remove tool works normally.

I've completed extensive troubleshooting, including:

New catalogue
Existing catalogue
Catalogue on internal SSD
RAWs on external HDD
Purged Camera Raw cache
Optimised catalogue
GPU on and off
Restarted Lightroom and the Mac

The key finding is that I installed Lightroom Classic 15.3.1 on the same iMac and repeated the same test using the same RAW file. Generative Remove is significantly faster in 15.3.1 than in 15.4.1.

I have been using Generative Remove since the beta and it worked well on this machine until recently, so this appears to be a regression rather than a hardware limitation.

I'm happy to provide System Info, screen recordings or sample RAW files if they would help.

Participant

Participating Frequently

The latest version is now giving me more Generative remove Use Policy violations than ever before. It has even given it to me numerous times when using the Remove People distractions. It is just removing people, yet giving me a “Use Violation”. It seems to be related to removing reflections in water. I have some screen shots.

J

Johngmcintyre

Participant

can't Remove objects in my Photos Its working , Then it Stopped

M

mangles

Participant

My Generative remove leaves a distorted image . Very frustrating. I cant even remove a blade of grass on a dogs head.

A

AndrosLima

Participant

A remoção esta deixando esverdeado

Z

ZappaJul

Known Participant

LrC Remove unfortunately remains frustrating. I get consistently better results in PS using a combination of Gen Fill, Patch, Clone and masks.

I recognise the cleverness of AI in pattern and style recognition (eg as used in adding edges to sky/ stones / dirt / grass lost to straightening a landscape or architectural image) - but it's unhelpful to have that applied where unnecessary - and filling edges only works in PS anyway, not Lr /LrC).

Removal generally implies simplicity - ie the absence of something, without the addition of new extraneous elements. Obviously removal demands replacement with something, but since Adobe's algorithms do a good job of differentiating between subject and background, can’t this be applied to replacing Removals with backgrounds?

Example attached is an engineering model. The intention is to keep original model (A) unchanged (because it must remain accurate), and to -

Remove unwanted elements (B) from image, replacing them with existing wall and seaside picture...
… without the unnecessary removal of any part of the subject (A) - the components of which should surely be clear from colour /luminance similarity, and colour / lumiance difference between A and elements for removal (B).
… and without the unwelcome addition of cleverly generated new elements (C) to subject (A)

Remove results in LrC using Gen AI and Detect Objects:

Great blending into background area with removal of (B) - BUT it unnecessarily removed part of subject (A). It also replaced stones with grass, which is more understandable in terms of colour/luminous similarity and isn't such a big deal but I'd preferred it to have continued stones).
Again great blending and into background area - BUT it unnecessarily adds a new element (C) to subject (A) and unnecessarily cuts off the corner of subject (A) leaving a peculiar dark element.
Now it gets even more elaborate. Yes, clever that it creates whole new elements (C1-2) in the same style as subject (A) BUT they’re unnecessary and inaccurate.

NB results form LrC with Use Gen AI off and with/without Detect Objects excluded because they’re too ridiculous to even consider!

Desired result achieved in Photoshop with 2 separate selections and Remove / Gen Fill / Clone / Masking.

Mac M3, OS Sequoia 15.7.4, LrC 15.3

johnrellis

Legend

[View this post in your web browser. It contains formatting and images that don't appear in email.]

@ZappaJul, can you attach the full-resolution original image? If the raw is larger than 47 MB, then attach a full-resolution JPEG exported from the unedited image.

With your screenshot, I was able to do a pretty good job with the blue object in the lower-right corner by zooming in and very careful selection of the boundary around the object (I never use Detect Objects -- it’s too random).

When Adobe revised Generative Remove last year, they made it easier for novices to remove objects that included shadows and reflections, but it also significantly impaired the ability to set careful boundaries around objects -- Remove now feels free to change pixels outside those boundaries, making it less useful for careful edits:

A

AnaNana

Participant

No matter how many selections of the background I do and how many times I generate, a blurred band appears on the forehead of the subject (which was obviously not selected).

johnrellis

Legend

@AnaNana, please post a full-resolution screenshot that shows the full Masking panel.

A

AnaNana

Participant

August_The_Dragonfly

Participating Frequently

Generative fill was doing so well now today it starts throwing up random errors. Listen, because seriously. Whatever system “checks” uploaded images is broken and needs to be fixed or just turned off. I’m assuming it’s magically encountered the “this must be porn” error.
https://drive.google.com/file/d/1zPKNLxChHchiyatFaLbZGMcp85D7pX-I/view?usp=drivesdk

also the forums file attachment system is lame 5mb files??? What is this 2005??

johnrellis

Legend

[View this post in your web browser. It contains formatting and images that don't appear in email.]

Adobe's AI is a repressed Victorian and often faints at the slightest hint of skin or small children. In geek speak, it has a high false-positive rate for adult and child porn, making it unsuitable for many kinds of innocuous professional use.

Sometimes if you make minor changes to the photo, e.g. cropping a small amount, or change the brush strokes a little, the erroneous judgment the photo is porn goes away. But often not.

Edward Weston wouldn't have been able to use Generative AI!
https://www.anothermag.com/art-photography/10115/the-edward-weston-nude-that-took-photography-to-new-heights

August_The_Dragonfly

Participating Frequently

Oh yes, I’ve discovered this as well. Which further supports my point. It should just be turned off until working right (or not at all since we’re photographers and we often deal with nudity why can’t “we” edit images that already contain some skin?? I can understand not being able to generate it but if I have a nude image and want to remove a scar or ingrown hair why does that matter??

But yes I cropped in about 2cm on each side and the same image passed just fine.

X

x_hobbes15C2

Participant

The AI Remove tool leaves artifacts at the edge of the selection. It fails to blend the AI generated portion into the surrounding area, leaving a hard transition line. Other tools like Healing Brush and Clone Brush are USELESS now. They barely adjust the image, even when set to full strength. HORRIBLE!

johnrellis

Legend

[View this post in your web browser. It contains formatting and images that don't appear in email.]

@x_hobbes15C2 The AI Remove tool leaves artifacts at the edge of the selection. It fails to blend the AI generated portion into the surrounding area, leaving a hard transition line.

Double-check that Use Generative AI is checked in the Remove panel. There have been a few reports that’s getting unchecked after a recent upgrade.

If that doesn’t help, please post a full resolution screenshot (not a phone pic) showing the full photo and the right column of Develop.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.