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:

[C.Cella]

@johnrellis Opacity slider was available whenever we created a new stroke.

It was removed for the Ui for LrC 14 so now the user must first paint then change Opacity.

This leads a problem.

If one sets an existing Remove to Opacity X then even the next new one will be at Opacity X.

1. So set an existing Remove/Clone/Heal at Opacity 0.

2. Create a new one.

Result: The new one will start at Opacity 0 because we can't set it before painting anymore.

We complained.

[callmedoug]

absolute garbage.  whatever you did makes lightroom impossible to use.  if I use AI to remove say hair from one photo and them remove background components from another photos, and then something from another, every single photo i used Ai on gets Red dot and a message that says "some remove settings need to be updated" and i have to go through every single photo and hit update, and by the time i get to the end and update all my photos they all have the same red dot and message.

it is literally like, the AI wants the same exact edits on every single photo.

Lightroom is no completly unusable and of course becuase it updated my library i can't go back to the old version.

You have literally cost me days of work to have to now do all editing in photoshop or export every single photo out of RAW to JPG as i edit them so that the edits i make don't go away.

FIX THIS NOW.  THIS IS COMPLETELY UNACCEPTABLE

[abuse removed by moderator]

[callmedoug]

so telling you that your update is garbage is abuse?  WOW.  if not for having a backup, you wold have cost me literally tens of thousands of dollars in lost work.  

[Rikk Flohr: Photography]

@callmedoug 

You might have better luck posting in the correct place. 

Please visit this thread for the workaround for the issue you are facing: https://community.adobe.com/t5/lightroom-classic-bugs/p-subject-mask-from-previous-versions-are-requ... 

I have already moved a couple of your posts to this other thread, which contains an easy workaround (takes 10 minutes) and will be updated once a final fix has been released. 

Continuing to post in this thread is probably not the best idea. 

Thank you for your patience. 

[TomBoro]

my lightroom after using the remove option, it's like it forgot that it did it and I have to update each photo after a few minutes, it's a joke. I just finished editing photos for a client and it turned out that after saving the files after editing, the files did not include any remove object, a joke

[callmedoug]

go back to any file you used AI on, i bet they are all screwed as well. 

[Bruce-Wayne]

Hey Adobe, do we need to remind you that we are paying for the software, and you've made no customer support available other than this useless forum? Fix it now!

[Marvin_Landa3055]

WHAT HAPPENED WITH THE ERASE TOOL IN LIGTHROOM, NOW IT IS HORRIBLE, IN ADDITION THE ADJUSTMENT IS DELETED, YOU HAVE TO BE UPDATING THE DELETIONS YOU MAKE, IT ALSO HAPPENS IN THE ADJUSTMENT LAYERS, ANY MODIFICATION YOU MAKE IN LAYERS AS WELL AS THE DELETION ARE LOST, YOU HAVE TO CLICKING ON THE OPTION THAT SAYS UPDATE AND EVEN SO IT IS NOT A GUARANTEE THAT IT WILL BE SAVED, I HAVE BEEN HOURS ON A JOB WHEN NORMALLY IT TOOK ME MINUTES, NOW I HAVE TO SAVE INDIVIDUAL IMAGE BECAUSE OTHERWISE THE SETTINGS ARE LOST AND I HAVE TO START OVER.

[Deremer Studios]

I'm encountering a recurring problem when using Generative Erase in an area that is predominately in an area of sky.  About 50% of the time, I get results that are darker than the surrounding sky.  And if this happens, all the variations are the same way.  Has anyone encountered this?  As a note, there are masks applied - one of which was a smart mask - though I am not sure if there is correlation or causation between the two.  This isn't a matter of needing to refesh the mask, though sometimes that is needed when you remove something throguh generative erase that was modified by a smart mask.     ALC 14.0 - PC - Windows 10. 

[johnrellis]

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

@Deremer Studios: "About 50% of the time, I get results that are darker than the surrounding sky.  ... As a note, there are masks applied - one of which was a smart mask"

By Adobe's design, you should apply Removes before AI masks. If you apply Removes after the masks (a more natural workflow for most people), you often end up with these "holes".  In that case, you can usually fix the issue by doing Settings > Update AI Settings. 

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. In less common cases, Remove sometimes doesn't do a good job of matching sky color.

[Odu Mazza]

The remove tool is much worst in the new version. I don't want to generate anything, just remove small details from my images. The results are getting worse on every new version. I have to edit all my images in Photoshop and use the patch tool.

[richard_1582]

Trying to remove objects in a HDR file, but removal tool is only replacing objects with more problems.

Right now this is terrrible compared to last version. Iv tried all options but same outcome.

[Michael37030880xp0m]

I just got the latest update.  14.0 Release,  Camera Raw 17.0.  Generative Remove does not work.  I uninstalled LrC and installed from scratch again.  Nothing.  I tried the same in both Lr and Ps ( CameraRaw there ) and that worked just fine.

[iBcampion]

It does a nice job of blowing up and crashing Lightroom, 

Is this the expected results?

Is this a beta release? Should I be getting a refund?

 {"app_name":"Adobe Lightroom Classic","timestamp":"2024-10-16 12:30:54.00 -0400","app_version":"14.0","slice_uuid":"632796a1-ef55-3358-af8d-c540b8f900e2","build_version":"14.0","platform":1,"bundleID":"com.adobe.LightroomClassicCC7","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 15.0.1 (24A348)","roots_installed":0,"name":"Adobe Lightroom Classic","incident_id":"8F457B35-81C0-4EDC-B75..........A93"}

[johnrellis]

@iBcampion: "crashing Lightroom"

First, update 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 LR is still crashing, make sure you've submitted a crash report to Adobe and entered the email address associated with your Adobe Id. Then start a new thread with the details of what you were doing when LR crashed, and include a copy of the entire output from the menu command Help > System Info.

[Ángel5CAE]

Hi, I have a problem with the new update, some very strange things have happened to me. I had some files that I had already edited with the previous version, using the remove tool. Well, with the new version it asks me to update each file where I used that tool. I do it, but after a few clicks on other photos, they return to their initial state. That is, I can't get the changes made with the previous version to be fixed with the new version.

[Odu Mazza]

I had this issue, too.

[Drugstore]

Remove tool more worse than ever. Instead of removing it puts new heads in instead. So I still have to go to PS!

[johnrellis]

@Drugstore: "Instead of removing it puts new heads in instead."

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.

[tanay_1863]

Hello,

To be honest the previous version of the AI gen removal was much better, I am struggling to remove objects now that I was very easily able to remove previously, I think the biggest issue I am facing is the object detection feature, now its auto selecting a very large areas and if I try to subtract the area it not letting me do that.

[tanay_1863]

I am sorry but the new Gen AI removal is pretty bad, I would rather go back to the old version while not perfect was 100 times better than what it is now.

[ariel_faith_photography]

I really like this, except that if I make any other edits, I have to update the generative AI again!  

[johnrellis]

@ariel_faith_photography: "I really like this, except that if I make any other edits, I have to update the generative AI again!"

Adobe just released LR 14.0.1 to fix this bug, and after updating, you may have to re-upgrade your LR 13 catalog. See here for details:

https://community.adobe.com/t5/lightroom-classic-bugs/p-subject-mask-from-previous-versions-are-requ...

[Bruce-Wayne]

What about edits made since the catalog upgrade, that would be lost if user went back to the previous catalog?

[johnrellis]

@Bruce-Wayne: "What about edits made since the catalog upgrade, that would be lost if user went back to the previous catalog?"

At the bottom of Adobe employee Rikk Flohr's second post in that thread, he says, "Note: If you did a lot of work in 14.0, it isn't recommended to restore from the 13.x backup." So that suggests that if you've done work in 14.0, then install 14.0.1 and see if the issue goes away. If it doesn't, only then redo the upgrade from LR 13 (losing work you've done in 14.0).