1 Pinned Reply
Update (Dec 2024): With the new release, it is no longer necessary to perform Generative Remove Operations prior to Cropping.
Update (August 2025) With the new release, the Generative Remove Engine has been updated.
See this video for details: https://www.youtube.com/watch?v=YwpUX4b6igY
1367
Replies
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
@Golden Lens Photography: "The removal of undesirable objects has become much worse, now the entire selected removal space is blurred/stained."
This issue isn't new to LR 14 -- lots of similar examples from LR 13. There are two possible causes of this:
1. You've applied Remove on top of an AI mask, e.g. a Sky mask. Do the menu command Settings > Update AI Settings to recompute the mask. In general, Adobe's designed workflow is to apply Remove first, then masking.
2. Sometimes Generative Remove doesn't do a good job of blending the replacement against uniform backgrounds like skies. You can often work around this by making the selection even more ragged or much larger (e.g. to include a much larger part of the sky).
If the issue with this photo is this second reason, please attach a full-resolution JPEG exported from the unmodified original photo, to provide actionable feedback for Adobe.
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
@Dylan Montero: "I have been a member for over two months and this regenerative AI feature has not worked for me."
LR's English translation of that error:
"$$$/Clio/StatusCode/HTTP/Forbidden=We've encountered an issue and can't complete your request at this time. Please try again later."
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.
Hello I am writing to get help on a way to automate this type of image cleaning. It would be amazing that this could come as an auto detection of dust and scratches using the Visualize Spots funtion directly in Lightroom. The first picture shows the original film scanned. It contains some little spots and tiny hairs.
The next picture shows the Remove tool enabled (Q) and the visualize spots also enabled.
Even if we can decide afterwards which white areas of the image we want to retain? This could help not just me, but many others too.
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
@Jasminder Singh_Obero8336: "In the latest update in Lightroom Classic on Generative Remove Tool, it just refuses to remove faces. As alternates it keeps giving new faces"
Your screenshot shows there are two causes, both related to the general principle that you have to select all of the object you want to replace -- if you leave any bits remaining, Remove will try to match the remaining parts:
1. You didn't select all of the person's arm.
2. You have to select all the disconnected pieces of a person. Your screenshot is ambiguous, but it looks like you tried to include the lower body of the person. The screenshot doesn't show if you selected every bit of that person.
There's also a UI design misfeature that Adobe hasn't acknowledged as such. Though Adobe tells you to select all of the disconnected parts of the object, if you make disconnected selections, Remove will treat them separately when it goes to remove, and you're likely to get "replace" instread of "remove". So you need to apply an obscure trick (described in more detail here).
First select all of the bits of the person with a single selection (making sure Detect Objects is unchecked):
Then before clicking Remove, use Subtract to delete the parts of the selection you don't want removed:
Then click Remove:
It's too bad that Remove still has such rough edges. Once you learn about its quirks, it does a very good job, quickly.
If you're still having trouble with this photo, please attach a full-resolution JPEG exported from the unmodified original photo, so we and Adobe can see the issue in detail.
There's also a UI design misfeature that Adobe hasn't acknowledged as such. Though Adobe tells you to select all of the disconnected parts of the object, if you make disconnected selections, Remove will treat them separately when it goes to remove, and you're likely to get "replace" instread of "remove". So you need to apply an obscure trick (described in more detail here).
etc...
By @johnrellis
It is nto a Ui msifire.
The soruce of the problem is the way LrC and CameraRaw handle Remove Refienments.
@Rikk Flohr: Photography
I have now documeted the issue and shared internally...I quoted you there.
.
AdChoices
