P: Generative Remove Feedback (Lr Classic & Lr Eco)

Please repost this feature request in the forum's Ideas section, where Adobe and other users are more likely to see it:

https://community.adobe.com/t5/lightroom-classic/ct-p/ct-lightroom-classic?page=1&sort=latest_replies&filter=all&tabid=ideas

[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.

[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.

@Lukasz22018323g86j: "is there a way to set opacity before applying AI Removal to the image? I can't see that option anymore after the update and it allows me to adjust the opacity only after I remove an object with the tool which is very inconvenient."

Agreed. In LR 14, Adobe "simplified" the Remove user interface by hiding the Opacity slider until after you've clicked Remove. Because it uses the hidden previous setting of the slider, there are a number of posts here from people mistakenly thinking that Remove isn't working, merely because the Opacity slider is set less than 100 and LR did its best to hide that from them.

@TheBommel: "I get extreme amounts of posterisation when using generative removal or hdr panoramas"

Since this is occurring with HDR panoramas also, it's not something specific to Remove. As a first troubleshooting step, 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 that doesn't help, start a new thread and include full resolution-screenshots (not phone pics) of what you're seeing and copy/paste the output from the menu command Help > System Info. (Don't reply in this thread.)

@christinag89624499: "Lightroom Classic 14.0.1 - For me the Generative Remove works nicely, except that it constantly needs me to "update remove settings."

LR 14.0 had a serious bug with this, and Adobe very quickly released 14.0.1 to fix it. But getting the fix to work appears to be quite fussy for many people (and Adobe has provided ambiguous direction on that score). See the second reply from Adobe employee Rikk Flohr at the top of the bug report thread:

https://community.adobe.com/t5/lightroom-classic-bugs/p-subject-mask-from-previous-versions-are-requesting-an-update/idi-p/14915210

If that doesn't help, then please post in that thread with details of what's going wrong. You're much more likely to resolve the issue in that thread than in this one.