Question

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

Forum|Forum|1 year ago
August 13, 2024
601 replies
558973 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:

Show previous replies

J

jacobsquires

Participant

This latest version in demonstrably worse than before. I'm trying to "REMOVE" a person and Generative AI keeps filling it in with another person. You REALLY NEED a button to say fill with surrounding background and a checkbox no People, or Pets.

C.Cella

Inspiring

Lots of users are saying the older version was better.

I have checked and unelss I am mistakenly Gen Remove in LrC 13 and LrC 14 is using the same ModelVersion(s)

.

johnrellis

Legend

@C.Cella: "unelss I am mistakenly Gen Remove in LrC 13 and LrC 14 is using the same ModelVersion(s)"

Running Any Filter on my LR 13 and LR 14 catalogs shows that the Generative AI Model Version did change between LR 13 and 14:

- Almost all photos in my LR 13 catalog use version 1.0.5-beta.1-1.2_1.2-8c2cea4-0.1.27.1r16.2.

- Older photos in my LR 14 catalog use version 1.0.5-beta.1-1.2_1.2-8c2cea4-0.1.27.1r16.2, while photos edited recently use 1.0.5-beta.1-1.2_1.2-8c2cea4-a6.

Interestingly, there are a few photos in the LR 13 catalog using the newer model on 10/2/2024 and the older model on 10/10/2024. Since the model version actually used may be determined by the Firely servers and not the LR app, perhapst Firefly jumped the gun and used the newer model for a bit around 10/2 and then backed up to the older model until the LR 14 release on 10/14.

* * *

In addition to the model changing, Detect Objects changed as well, using a larger border around the detected objects.

However, without seeing actual examples, it is premature to conclude that the change in model or Detect Objects is the cause of the complaints. So far, only one person has uploaded a full-resolution JPEG exported from the unmodified original showing bad behavior, and that turned out to be an errant Opacity slider.

So until more people experiencing issues upload full-resolution JPEG exported from the unmodified originals, I don't think Adobe will likely pay much attention.

MichaelN0815

Known Participant

LRc 14.0.1 ; WIndows 11 23H2

scrolling through pictures with AI masks increases GPU VRAM use very fast. Reaching 100% slows down LR. Only restart of LR helps for short time.

johnrellis

Legend

@MichaelN0815: "scrolling through pictures with AI masks increases GPU VRAM use very fast."

Most problems with LR's AI commands are caused by older, buggy graphics drivers. Try updating your graphics driver by going directly to the manufacturer's web site:
https://helpx.adobe.com/lightroom-classic/kb/troubleshoot-gpu.html#solution-4

If that doesn't help, please copy/paste here the entire contents of the LR menu command Help > System Info -- that will let us see exactly which versions of hardware and software LR thinks you're running.

SADDLE-UP

Participating Frequently

Sometimes amazing, sometimes crap.
I wax and wane between love it and hate it.
AI is human, it can be seriously dumb 😞

J

jguo114

Participant

Please bring back the old Lighroom Classic. This new update with the generative AI is terrible. As others have said, the remove tool's Detect objects feature auto-extends the selection way too much. It then takes painstaking work to try to reduce the selection. The generative AI feature is not even as good as it had been in the previous version before this update as it either replaces the object with unwanted background or introduces new fringing that was not previously an issue.

Overall, this update has substantially slowed my workflow, and I am now spending 5x the time I used to editing my photos... and the results aren't even as good!

K

krakozavr@gmail.com

Participating Frequently

Generative remove tool:
usually it works well. But sometimes, it continuously suggests different versions of objects I'm trying to remove, even with multiple attempts of regeneration. For example, it may again and again draw a different person in the background, instead of removing the original one (and in many cases, the new "person" looks more defined and recognizable than the original). Or just now, when I tried to remove some metal frame from the forest setting, it redrawn it many times into something different but still a metal frame 🙂 Modifications of the existing selection don't help.

The only way to make it do right job is to completely remove the selection and start over.
LR 14.0.1 - Camera Raw 17.0 (Windows 10 with all recent updates)

OS Name Microsoft Windows 10 Pro
Version 10.0.19045 Build 19045
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name KRAKOZAVR
System Manufacturer To Be Filled By O.E.M.
System Model To Be Filled By O.E.M.
System Type x64-based PC
System SKU To Be Filled By O.E.M.
Processor Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4001 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. P7.30, 1/23/2018
SMBIOS Version 2.8
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer ASRock
BaseBoard Product Z170 Gaming K4/D3
BaseBoard Version
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "10.0.19041.3636"
User Name KRAKOZAVR\AlexArtPhoto
Time Zone Eastern Daylight Time
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 31.9 GB
Available Physical Memory 10.3 GB
Total Virtual Memory 114 GB
Available Virtual Memory 76.5 GB
Page File Space 82.1 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

johnrellis

Legend

@krakozavr@gmail.com: "sometimes, it continuously suggests different versions of objects I'm trying to remove, even with multiple attempts of regeneration."

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.

K

krakozavr@gmail.com

Participating Frequently

Thank you for the link, I found it already and read it. I figured these tricks on my own already, but sometimes (I can admit, on rare occasions) it doesn't help and modifications of the existing selection don't help, too. In these cases, if I delete the original selection completely and start over, it works properly even if I recreate the original selection in details.

M

Meteor_Freak

Participant

Removed object, but left a circle,that appeared like a dust spot.

johnrellis

Legend

@Meteor_Freak: "Removed object, but left a circle,that appeared like a dust spot."

Are you applying Remove on top of an AI mask (e.g. Sky mask)? If so, do Settings > Update AI Settings.

If that doesn't help, thensee 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.

C

ctcbox

Participant

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.

C

ctcbox

Participant

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.

W

Weigl2951085693w8

Participant

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!!!

MichaelN0815

Known Participant

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

Legend

@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

Known Participant

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?

M

Mark340860516rwv

Participant

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

Legend

[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-border-pixels-automatically-cropped-by-camera-raw/m-p/14925572

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

M

Mark340860516rwv

Participant

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

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.

Scanning file for viruses.

This file cannot be downloaded