1 Pinned Reply
Update (Dec 2024): With the new release, it is no longer necessary to perform Generative Remove Operations prior to Cropping.
715
Replies
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
@motivated_Mercury5F9A: "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 @John R Ellis
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.
.
Doesn't work with a workflow where you synch your setting across hundreds of photos, because you would have to reset all settings.By @Patrick22616748c1sx
What do you mean?
When I sync Gen Remove to other images the the other settings don't need to be reset.
.
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
@Patrick22616748c1sx: "you list 20 things you have to make sure and check"
Another large inaccuracy -- I listed 5 things.
"Doesn't work with a workflow where you sync your setting across hundreds of photos, because you would have to reset all settings."
You haven't replied to C.Cella's inquiry about what you mean by this -- neither of us understands.
"Doesn't work with lenses that automatically have lens correction turned on, once imported. "
No, that's inaccurate, it usually works well. In very infrequent cases, if you're trying to remove an object against the edge of the photo and it replaces rather than removes, it could be that the lens correction is cropping out a small border of pixels that you need to select by brushing wider at the edge. Alternatively, you can just toggle off the lens correction, apply Remove, then toggle it back on:
It would be better if Remove did this automatically, as it does with Lens Blur, but it's a misleading exaggeration to say simply "doesn't work".
"I just see countless other people saying the same thing - Instead of removing, it adds a variation."
With nearly everyone who has provided an example of that here, we've shown how to quickly and easily remove rather than replace the object. There are such examples -- Remove is hardly perfect -- but there have been only a few in this thread and it's predecessor during "early access".
"the workarounds you're describing are just not applicable in most real world situations"
There are lots and lots of posts here to the contrary., and you still haven't posted even a single example to the contrary.
As the article I referenced says, "Like any tool, you need to know how to use it properly to get the best results." You're determined not to attach a full-resolution example where it's hard to get good results, so it's easy to assume you don't want your premature conclusions to be proven wrong.
"I don't care if my feedback carries much weight to you personally."
I don't care either. I do try to help people on this forum provide meaningful, actionable feedback that will be most likely to influence Adobe, by including examples, explaining in detail what's going wrong, and filing bug reports. I've helped a number in this thread and its predecessor identify places where Remove goes wrong. (I'm one of the most persistent critics of LR Classic here and I've filed the most bug reports by far.)
AdChoices
