1 Pinned Reply
Update (Dec 2024): With the new release, it is no longer necessary to perform Generative Remove Operations prior to Cropping.
821
Replies
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.)
The Lightroom Queen article is a good reference and Victoria and Paul are keeping it updated:
https://www.lightroomqueen.com/generative-remove-replace/
By @johnrellis
Yes but it's not widely known.
Personally I think that it should be Adobe to provide the info, available offline in LrC.
But thats just me probably.
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
@DhandaNot: "Generative Remove does not work well LR CLassic 14.0.1 I tried to use Heal and Clone. But that too leaves a trace of what I am trying to remove."
Your screenshot shows two issues:
1. You've applied Remove on top of masking (as C.Cella pointed out). Do Settings > Update AI settings to recompute the masks after applying Remove, or do as Adobe recommends, appy Remove before masking (which doesn't match many people's workflow).
2. You've applied Remove to a cropped photo, and if the selection extends to the edge of the crop, Remove is trying to match the cropped out pixels. Apply Remove before cropping. See here for more details:
https://www.lightroomqueen.com/generative-remove-replace/
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.
Wow, remove and replaced worked pretty good until today's update. Now I get ghosting or a complete replace with a similar object. Almost useless at this point.
AdChoices
