Community Manager

Question

P: Generative Remove Feedback (Camera Raw)

Forum|Forum|1 year ago
August 13, 2024
81 replies
88955 views

This post applies to Camera Raw.

Lightroom Classic and Lightroom Ecosystem feedback can be found here.

Previous Early Access 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.

As Generative AI analyzes portions of the image that have been cropped out, Camera Raw has the ability to toggle Show Uncropped Image is now available to guide you in your Generative Remove selection.

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:

Show previous replies

A

alexander_9745

New Participant

Update (Aug 2025): The remove and generate with AI is completely "confused". I edited 2 Pictures from a Series a week ago and i could easily remove and generate. You didnt even see that there was a object before. Now he generates random stuff into the raw Image. When a update breaks AI then you know its not a good update.
But basically until July 2025 it was a perfect tool.

DBowker3D

Inspiring

Normally I'd just do the masking and removal myself but thought: Let's try the built in tool!
For one thing the UI is far my clunky than it should be, but even then I made sure to so a very accurate mask of the subject (clearly defined) to be removed. This is almost the perfect situation for this tool except... I think the images speak for themselves...

The yellow line is just the screen capture, not the original mask.

This is what I got... How are the results this bad?

H

Hmmokthen

Inspiring

Hi Rikk,

"With the new release, it is no longer necessary to perform Generative Remove Operations prior to Cropping."

--What about Denoise, is it still recommended that we do that first?

--Does heal still have to be done before AI selections?

thanks

L

Luka22533872

Participating Frequently

No, it does not work. You've made it more complicated—again. It used to work fine, but now it's confusing. I regularly use the spot removal tool to clean dust from the sensor in my images, and you've changed the parameters so it no longer works the way it used to. The functions I relied on are gone. What you don't seem to understand is that people prefer to work routinely, without having to stop and think about technical changes like this. Suddenly, I realize you've altered something that was working perfectly. Why change what already works? This is regression, not progress.

Erik Bloodaxe

Brainiac

Which functions do you think are missing? Can you be a little more specific?

L

Luka22533872

Participating Frequently

Yes, I can be more specific.

Until recently, the functionality for removing unwanted artifacts from images - like dust spots from the sensor - it was simple and efficient. In Adobe Camera RAW, I could select the "Remove" tool from the upper right corner, a circle with a plus sign would appear, I’d click on the dust spot, and it would disappear. It was fast, intuitive, and required no extra thinking, just click and go.

Now, the process has become unnecessarily complicated. I click on the dust spot, but nothing happens right away. Instead, you’ve introduced extra steps like "Use Generative AI," "Detect Object," and then additional options below like "Fill," "Remove," "Opacity." Only after going through all of this does the "Remove" button appear.

Why add all these extra steps?

Please bring back the simplicity - when I click on a spot, it should just vanish. It’s frustrating when something that worked perfectly is suddenly made slower and more complex. This doesn’t feel like progress - it feels like a downgrade.

It honestly seems like someone at Adobe is under pressure to “innovate,” so they introduce unnecessary changes that end up ruining workflows that were smooth and efficient before. At this point, I’m seriously considering asking for a refund.

P

Peegee

New Participant

Removal is apparently very dependent on chance. In one photo I want to remove a wine glass and it works pretty well. In a second picture with the same motif, the wine glass is replaced by various other glasses. Even several attempts do not change this. iMac Sequoia 15.5, in this case Fuji X100F images. However, I have had similar problems with my Canon R5 Mark 2.

A

alan_8562

New Participant

Generative remove often seems to create something entirely new for me. I'm removing a box; it creates a chair. I'm removing a person; it creates and umbrella. It's very odd.

T

TIM DAVID

New Participant

Removing objects does not always remove objects, sometimes just create similar new ones. Drives me crazy.

Robert Ripps

Inspiring

I was working on an image a few weeks ago, using Generative Remove, in ACR, and afterwards the XMP file was 8.8 MB. Today I opened it again into ACR, and applied a blur on top of my previous GR edits, then opened it into Photoshop. Looking back at the XMP file, I expected it to grow a little bit, but instead it shrunk to 1MB for some reason.

Robert Ripps

Inspiring

Looked at another file with some Generative Remove work, opened it into ACR, did one more GR edit and opened into Photoshop- the XMP shrunk on this one as well.

Robert Ripps

Inspiring

I think I was not seeing at the ACR file as well- so for this example, the XMP shrunk, while the ACR grew. Maybe that explains some of the discrepancy.

C

Chapps-LA

Inspiring

HELP.

Not sure if you guys are still monitoring this particular post, but I've been noticing a real bug in reflection removal. This used to happen somewhat infrequently before the latest couple of updates, but for me it's now occurring on every photo. Here's the scenario: if you use denoise before using reflection removal, it completely disables reflection removal's ability to ... well, remove reflections. It might remove a little haze, but that's it.

I do a lot of interior shots in dark museums, and wind up with some significant noise. So I use the denoise tool often, then tweak the results so that I retain as much detail in the shot as possible. Unfortunately, I also have to deal with highly reflective museum glass cases. Now I'm stuck. Three exports are below - original, with no tweaks; reflection removal used, but no denoise; and denoise and reflection removal applied. You'll note that the version where denoise was used is virtually identical to the unmodified original, save the removal of a bit of haze.

Here's a link to the original RAW file: https://drive.google.com/file/d/1ZGuPTHEvfbIVaIqJKMbvnBX9X5AtBM8L/view?usp=sharing

Is anyone else experiencing this? I'm using Canon CR3 RAW files, and previously everything worked great, for the most part. Now I have to decide between denoise or reflection removal - I can't use both. Huge issue for me.