@Mike_Scott28: "Tried this out on a photo with a branch of a bush against a sky background. it did a great job identifying the object and removing it, but, what was left was a lighter color of the background so it looks like a watermark of the branch."   Sounds like you've applied Remove on top of a Sky mask. Do the menu command Settings > Update AI Settings to recompute the Sky mask, and the branch ghost should go away. But if that doesn't help, please attach a full-resolution JPEG exported from the unmodified original photo (not a screenshot), so we and Adobe can see the issue in detail. With nearly every of the several dozen problem photos posted here, we've been able to show how to quickly remove the desired objects. ... View more

@leonard_8252: "lightroom classic mac generative remove failed. we've encountered an issue and can't complete your request at this time."   Sometimes firewalls and anti-malware / anti-virus utilities incorrectly block some network requests from LR. Try these troubleshooting steps:   - Temporarily disable all the firewall / anti-malware on your computer. If that solves the problem, then add a specific exclusion for LR to the firewall's rules.   - Connect to another network, preferably one serviced by a different ISP. E.g. a Wifi connection of a neighbor, a coffee shop, work, or your phone's hotspot. Sometimes the routers in these networks block LR's requests, especially in authoritarian countries like China.   - Try relaunching Finder -- start Finder, click the Finder menu, and do Quit Finder. Someone reported that this solved this problem for him. It's easy to try.   Please let us know which of these work and which don't. ... View more

@angel_omar_8160: "It is not working all the time, sometimes is not make anything, I do not know the reason or proble because I closed and open again."   So after closing and restarting LR, does Remove start working again? ... View more

"You don't even need to be in Library. "   You're right -- I misremembered that Photo > Enhance is one of the many exceptions to the "rule" that commands in Loupe view only apply to the most-selected photos. ... View more

@C.Cella: "do you know any method to select history?   Unfortunately, no. ... View more

@rachelc98485529: "I'm still experiencing this issue"   Please detail the symptoms you're experiencing and attach a full-resolution screenshot (not a phone pic). That could help identify which workarounds for the AMD 5000-series GPUs might work for you.   "Intel UHD Graphics 630, 1536MB"   Did you try disabling this Intel GPU as recommended by Adobe? https://community.adobe.com/t5/lightroom-classic-discussions/gpu-problems-on-lightroom-with-the-new-macos-sonoma-14/m-p/14469192#M358694 ... View more

@Dennis Larson: "The bot thinks I'm working on nudes."   See here for why Remove (and other AI platforms) make so many mistakes in identifying "unsafe" content: https://community.adobe.com/t5/lightroom-classic-discussions/p-generative-remove-feedback-lr-classic-amp-lr-eco/m-p/14959155#M385540 ... View more

There are a couple issues with grain and textures:   1. The replacement patch supplied by Adobe Firefly has a maximum size of 2048 x 2048 pixels. If the selected area in the photo is larger than that, then the replacement patch gets upscaled (and blurry). Your screenshot suggests that you may be replacing an area larger than 2048 x 2048.   2. Even when there's no upscaling of the replacement patch, Remove doesn't always match textures and grain very well.   For grain in particular, see this post for how to ameliorate the problem by adding the grain back: https://community.adobe.com/t5/lightroom-classic-discussions/p-generative-remove-feedback-lr-classic-amp-lr-eco/m-p/14917497#M382464 ... View more

@Carlie26372870bwcy: "not removing light poles in the distance"   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 (not a screenshot), so we and Adobe can see the issue in detail. With nearly every of the several dozen problem photos posted here, we've been able to show how to quickly remove the desired objects. ... View more

@NoemiCoen: "We need the AI ​​removal tool to delete what we select, not replace it with deformed faces, invented objects, and so on."   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 (not a screenshot), so we and Adobe can see the issue in detail. With nearly every of the several dozen problem photos posted here, we've been able to show how to quickly remove the desired objects. ... View more

And what are the results of:   2. With Use Graphics Processor set to Auto, quickly test whether there is an incompatible or corrupted display profile assigned: https://www.lightroomqueen.com/how-do-i-change-my-monitor-profile-to-check-whether-its-corrupted/    If the display profile looks good, then some additional steps:   4. Are you applying a develop preset in the Import window's Apply During Import > Develop Settings?  Take one of the photos into Develop and look at the History panel. If you are, there will be a history step showing it.   5. "AMD Radeon R9 M290X". That graphics processor is ten years old, and AMD stopped supporting it 2.5 years ago: https://www.amd.com/en/support/downloads/drivers.html/graphics/radeon-r9-r7-r5/radeon-r9-200-series/amd-radeon-r9-m290x.html   It's very possible that LR is tripping over bugs in the old graphics driver that are only triggered with HEICs but not JPEGs. ... View more

@charlieInNEK: "I just wanted to ask if people have verified that LRC changed the creation date of the file.  This seems clearly wrong, as the file already existed."   When you tell LR to update the metadata in a non-raw file (e.g. a JPEG), either explicitly with Metadata > Save Metadata To File or implicitly, with Catalog Settings > Metadata > Automatically Write Changes Into XMP, LR will sometimes modify the existing file and sometimes create a new file and rename it on top of the existing file (depending on the change and how much space is left in the metadata sections of the file). In the latter case, since a new file is created, the operating system assigns it a file-created date of "now".    There used to a feature request for LR to preserve the original file-created date in that circumstance, but I don't think it got copied from the old feedback forum.  There is is a related feature request for LR to explicitly set the file-created dates of exported photos to their capture dates recorded in photo metadata: https://community.adobe.com/t5/lightroom-classic-ideas/p-retain-date-and-time-during-jpg-export-according-to-exif/idi-p/13469714   Given how old these feature requests are, I think it's unlikely Adobe will implement them. LR does a good job of following industry standards for recording various dates in photo metadata. Since there are so many apps and utilities that make no attempt to preserve file-created dates (including those supplied with Mac and Windows), most LR users don't try to depend on the file-created and file-modified dates, relying on the photo metadata instead.     ... View more

Go to Library Grid view, select all the desired photos, and do Photo > Enhance.   if you try this using the filmstrip in Loupe view (one large photo showing), LR will only enhance the current photo. Many (but far from all) commands only work on the most-selected photo in Loupe view. ... View more

@C.Cella: "In ACR it is possible to see the uncropped image when applying Remove."   That's good. LR 14 disables Lens Blur while Remove is open but not Crop (or Transform or Lens Corrections), even though Crop is used much more often than Lens Blur. There's a feature request for LR to do that: https://community.adobe.com/t5/lightroom-classic-ideas/p-reveal-the-whole-uncropped-image-when-using-remove-tool/idc-p/14970710#M23108   Hopefully LR will soon follow ACR. ... View more

@Soulflare007: "Can spend a bit of time selecting out of focus chain link fencing (in hopes of cleaning up the background in some zoo photos) and Generative Remove replaces it with.... more blurred chain link fencing."   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 (not a screenshot), so we and Adobe can see the issue in detail. With nearly every of the several dozen problem photos posted here, we've been able to show how to quickly remove the desired objects. ... View more

@charlieInNEK: "I have tried the various User Guides, but Adobe's never contain screen shots of what is being discussed; you're supposed to be able to guess from the text description.  So, what's the best resource to learn the filtering system?"   I highly recommend The Missing FAQ by Lightroom Queen Victoria Bampton: https://www.lightroomqueen.com/shop/adobe-lightroom-classic-missing-faq/   I rely it on -- it's the only authoritative reference for Lightroom Classic, while still being easy to understand with lots of screenshots.The PDF is well-indexed and searchable. Adobe's Help is missing lots of details and is sometimes out-of-date.  ... View more

"On my Mac, and all past systems on which I have run LRC (maybe 3 or 4), hovering the pointer over an icon such as the "filter on edit status" one, brings up an explanatory pop-up phrase about 1 time in 1,000 tries."   Yeah, the tooltips have been very fussy in Mac LR (though not Windows LR) since the earliest versions. Adobe has never prioritized a fix. ... View more

  @igi333: "Instead of removing objects, it changes them to AI variants of the same stuff, or random crap."   Your screenshots immediately showed the issue -- you need to select both the reflections and shadows cast on the floor and the wall by the objects you want to remove. Otherwise, Remove will try to generate replacements that cast the remaining reflections and shadows.  (This hasn't changed in LR 14.)    See this short article for more details about this and other techniques required to use Remove effectively: https://www.lightroomqueen.com/generative-remove-replace/     ... View more

Those two pics import correctly in my LR 14.0.1 / Mac OS 14.6.1 / Macboook Pro M2 Max. Do all three troubleshooting steps:   1. Remove them from the catalog, Set Preferences > Performance > Use Graphics Processor to Off, and re-import them.  Still turn green?   2. With Use Graphics Processor set to Auto, quickly test whether there is an incompatible or corrupted display profile assigned: https://www.lightroomqueen.com/how-do-i-change-my-monitor-profile-to-check-whether-its-corrupted/    3. Do the LR menu command Help > System Info and copy/paste the entire contents here so we can see exactly which versions of hardware and software LR thinks you're running and important LR options that are set. ... View more

@AlexJz: "you pretty much have to do this as the very first step in the process."   That's how Adobe designed it, though it doesn't match many people's natural workflow. Often, you don't know which objects you should bother removing until you've cropped and applied basic editing.  Adobe's recommended order of operations, along with more details about shadows and reflections, are detailed in this article: https://www.lightroomqueen.com/generative-remove-replace/ ... View more

@igi333: " Instead of removing objects, it changes them to AI variants of the same stuff, or random crap. "   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 (not a screenshot), 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. ... View more

And if C.Cella's suggestions don't help, see this previous reply: https://community.adobe.com/t5/lightroom-classic-discussions/p-generative-remove-feedback-lr-classic-amp-lr-eco/m-p/14988891#M387288 ... View more

Thanks for the update.  Given that you can duplicate an AI mask component within a photo and you can copy an AI mask component between photos using Copy/Paste Settings, Sync, and Auto Sync, the lack of copy/paste sure looks like an oversight. ... View more

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   "I change a slider (I picked Shadows), and image disappears, replaced by message  "No photo selected". "   That's because you've set the filter to show unedited photos only:   As soon as you make an edit to the photo, it no longer matches the filter and disappears from the selection.  Turn off the filter and this won't happen.     This behavior has confused many people over the years.   ... View more

@Ric G: "I discovered that this not only occurrs when trying to create a virtual copy in a Smart Collection, it happens when you try it in a Collection Set. It interesdting to note that Lightroom will happily undo the creation of this nonexistent virtual copy and report that it has done so."   When you make a virtual copy, it always appears in the same folder as the original.   When you have a smart collection selected as the current source, select a photo in that smart collection, and create a virtual copy, the virtual copy also appears in the smart collection, since it will have all the same metadata and attributes as the original. The one exception is if the smart-collection rules specifically exclude virtual copies.   When you have a collection set selected as the current source, select a photo, and make a virtual copy, the copy will appear in the folder only, not any of the collections contained in the collection set. This is because in general, LR doesn't know in which contained collection it should place the virtual copy (if the photo is in more than one collection).   If you're not observing this, then please post details about exactly what you're doing, including full-resolution screenshots (not phone pics) of the entire LR window. ... View more

@lizannec24357135, see my reply to your other post: https://community.adobe.com/t5/lightroom-classic-discussions/p-generative-remove-feedback-lr-classic-amp-lr-eco/m-p/14988891#M387288 ... View more

@lizannec24357135: "I am not sure if it is since i updated to latest version but sometimes it does nothing, other times it just makes it a more opaque version of what was there and they are not hard removals to do so i dont understand why it is struggling" @daneg47269868: "Yes!!! It was working great for about an hour or two and now all of a sudden the removals aren't opaque and are essentially useless."   1. Uncheck Detetct Objects (on by default in LR 14) -- it doesn't work well, especially with skinny objects and along the edges of photos. 2. After clicking Remove, check that the Opacity slider is 100 -- LR infrequently changes it to something else. 3. 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 (not a screenshot), 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. ... View more

@AlexJz, "Once I included this reflection in the selection, remove worked perfectly!"   Yeah, Generative Remove is very clever at matching shadows and reflections. ... View more

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]   @JeffP3456: "LRC removes the object but leaves a light shadow which it will not get rid of."   I was able to quickly remove the branch from your screenshot:   You've likely applied Remove on top of an AI mask (e.g. Background). Do Settings > Update AI Settings to recompute the mask. ... View more

@hughlPhugh: "When I use the Generative AI Remove I can't see what its done in cases of small areas because you need to 'remove' the symbols superimposed on the image by the app. "   In the Remove panel, set Tool Overlay to Auto and move the mouse out of the image.  Alternatively, set Tool Overlay to Never.  Use the keyboard shortcut H to cycle overlay modes. ... View more