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:

[johnrellis]

@Alan27416038d67j, your screen recording shows you're trying to remove objects from the edge of the photo, and LR is generating some other object as a replacement:

This usually happens when there are pixels beyond the edge that have been cropped out due to Crop, Transform, or Lens Corrections. So undo any of those you've applied and then do the Remove. 

See this article for more details:
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.

[Alan27416038d67j]

@johnrellis 

Thanks for the reply, but the interesting thing is that I didn't crop the photo at all, it's exactly as I took it from the camera, I'll put it here for you to test. Another thing, look, I repeated it again, making sure there was no crop in the photo and look how cool, now it added a mini ball. I did it again and finally he got it right.

Anyway, it worked.

[johnrellis]

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

@Alan27416038d67j: " I didn't crop the photo at all"

You're tripping over a bug that affects many cameras.  When I apply Remove to the JPEG you provide, it does quick work of getting rid of the objects and shadow in the corner:

The metadata indicates you were editing a raw from a Nikon Z fc. That camera's raw sensor is 5600 x 3728 pixels (aspect ratio ~ 1.50215), and the Camera Raw engine in LR automatically crops it to 5568 x 3712 (aspect ratio = 1.5). That cropping is invisible to the user and always occurs. 

The problem is that Remove looks at all the pixels in the photo, including those that get cropped out (16 pixels on each side and 8 pixels top and bottom). But you can't see those pixels, and if you don't select them, Remove generates a replacement that matches them.

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

https://www.lightroomqueen.com/community/threads/more-complications-with-remove-and-cropped-pixels.5...

During the Early Access period, we weren't allowed to submit formal bug reports, so the many reports about this misbehavior got buried in the thousands of replies in the previous version of this thread. Now that it's out of Early Access (beta), it's on my list to submit a formal bug report.

[Alan27416038d67j]

very good, thanks for the information. I didn't know about this detail.

[sarkara1]

After using generative remove to remove a branch, the branch is back later after restarting LR. WTF?
LR Classic 14.

[Jeff30104142ityt]

release 14.0

just upgraded and my first attempt was flawless with LR. I has worked good up to this point but this was a complicated background

 

[jerseyjon]

Hello.

Lightroom Classic 14.0 on Windows 11 

It would seem the app updated to this version in the background in the past 24 hours. Suddenly, the Remove tool, which has worked beautifully as an eraser, is not working - the result ends up moving fragments of the object I'm trying to erase, from one part of the image to another. 
Am I missing something?

[johnrellis]

@jerseyjon: "the result ends up moving fragments of the object I'm trying to erase, from one part of the image to another."

Please attach full-resolution screenshots (not phone pics) of the ENTIRE LR window showing the photo after you've made your selection of the object and then after you've clicked Remove.  We'll then see exactly what's going on and can likely provide an easy solution.

[bergamar]

When applied, the generative remove fx leaves a no-grain patch even if the area is surrounded by pixels with grain; is there a way to match the grain of the rest of the image also on the retouched area?

[C.Cella]

@bergamar to truly match grain in LrC is pretty much impossible.

LrC grain Library is very limited compared to other softwares.

What you can do is apply a Mask with Local Grain over the Gen Remove Area and try to match the image noise/grain.

You can simplyfy the process by creating a Full Image Mask that selects the entire image and apply to all the Image the same Local Grain.

Like this you have a match, in the sense that the grain applied by LrC will be the same everywhere BUT this approach means adding Grain above the one of the RAW. 

DO NOT use Global Grain in the Detail PANEL to match grain

Unfortunately it adds blur we can't control above Grain Size +30.

The Local Grain doesn't add blur so you can keep your orginal sharpness intact, Local Grain is better.

[ch1tone]

I experienced this also. It may be helpful to be able to create a mask directly from the current selection. With this mask one could try to adjust the appearance of the generated area. 

On the positive side, in my case the generated content served as a rough guideline. Using the stamp tool was straightforward from this point on, and i was able to pick up the grainy texture from the surrounding area.

[vincenzo_6388]

Trovo l'ultimo aggiornamento molto peggiorativo rispetto alla versione precedente che reputavo ottima. Rimozione generativa lentissima e a scatti. Ad ogni operazione di rimozione lasci fastidiosissimi aloni chiari. Diventa tutto molto complesso. Urge patch di correzione.

[johnrellis]

@vincenzo_6388: "With each removal operation you leave annoying light halos."

Please attach full-resolution screenshots (not phone pics) of the ENTIRE LR window showing the photo after you've made your selection of the object and then after you've clicked Remove.  We'll then see exactly what's going on and can likely provide an easy solution.

[Kai Marzog]

Generative removal has to be done again for ALL masks in the catalog and this causes errors in already finished images and also means that all newly created masks are deducted from the monthly available credits? WHY?

[nigelr63458360]

Tried to remove a tree trunk but it simply replaced it with a smaller section . I also tried extending the selection quite a way into the background but got a similar result. Went into PS and removed it with the remove tool. 

[sandys19174563]

Hello,

since today i have the problem, that a few minutes after removingan object an exclamation mark appears a few minutes later to indicate that it needs to be updated. The removed object is then back and I can start again from the beginning. What is the problem?

[Kai Marzog]

Next problem: I updated the masks in Lightroom Classic and then Lightroom Mobile tells me on the same image that I need to update the masks AGAIN. Each update reduces the monthly credits...REALLY?

[Floartgraphy]

Please make the remove properties mantained from one picture to others. I have to "update settings" after each use to remove some spots or areas. It's nonsense... if i don't want to use, I don't copy "remove" properties. It's a lot of time wasted.... in previous version it works like a charm this option. Now I have to wait 10-15 sec for every picture even it's not used generative AI. Apart from this inconvenience, generative AI works fine in Lightroom.

[C.Cella]

@Floartgraphy

What do you mean by "Please make the remove properties mantained from one picture to others."

.

[Edwin_Grondinger0084]

Warum muss ich, wenn ich ein unerwünschtes Objekt entfernt habe beim nächsten Öffnen von Lightroom das bereits entfernte Objekt nochmal mit "Aktualisieren" erneut entfernen? Das macht doch - ausse mehr Arbeit - keinen Sinn, oder?

[C.Cella]

To all users having with Remove (i.e Gen Remve doing a poor job OR replacing object with another object) then use the "Report Variation" menu.



You can send the images to Adobe so that eventually can train the Ai.
Unfortunately you must add a description of the problem because there are no checkboxes for "Quality issue" or "Replaced instead of Removed"...the two common case of Generative Content failure that so many of you are experiencing, that we all experience daily.


Adobe will hopefully issue Firefly credits refunds.

.

[armandsbc]

So far the results I got  were much better than with the old tool, but in my case, changing the tool/circle size is extremely slow. There's a huge delay when I turn the mouse wheel or use the square brackets, doesn't matter. Did not have the same issue with the old version.

[Jinx48]

I am using the latest version of Lightroom Classic. When removing objects on a DNG file everything goes well. Later on, when reviewing my photos before exporting them, I realise that the objects I had removed in some of my photos are still visible. Going to the Develop Module I realise there is a red dot under the remove tool and a message saying ''Some Remove settings need to be updated''. I update them and minutes later I have to go over this process another time. It doesn't seem to keep the changes. Am I the only person having this problem? Is it a bug in the software? Am I doing something wrong?

[armandsbc]

I just experienced exatly the same issue. Except that there was no indication of an issue before exporting.  I exported and saw that the removed objects were still visible in the JPEGs. After performing the update all looked good. Still very annoying.

[nathanh78671078]

I have been doing this over and over and over adn over again all day. The only work around i am finding is ediitng and exporting each photo one by one because the moment i move to the next photo the AI edits are gone on the previous. GIGANTIC waste of time! 

if anyone has a fix please  let me know!