Copy link to clipboard
Copied
The recommended order for applying edits is:
Copy link to clipboard
Copied
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
Google translation: "when it wants to detect an electric cable, it detects something else totally unrelated to what it was marking." Error message: "Remove. No object has been detected."
You've brushed over the horizontal cable but the white outline of the brush marks are vertical. There have been a couple of other similar reports that the brush strokes on a portrait photo don't correspond to what LR actually indicates as the brush strokes. There's clearly a problem with Remove interpreting the orientation correctly. Unfortunately, I'm not able to reproduce the problem.
To help get an actionable bug report, please upload the original photo (not an export or screenshot) to Dropbox, Google Drive, or similar and post the sharing link here. Unless Adobe is able to reproduce the problem, or unless many people report the symptoms, they generally won't pay much attention.
Using your low-resolution screenshot, Remove did a very good job of removing the cable:
As a workaround, if you export the photo as a TIFF and then reimport it into LR, Remove should work properly.
Copy link to clipboard
Copied
Any tips on removing bubbles from an underwater scene?, I've not had much success although I think the way it can remove "objects" is great!
Here's an example image I've just been working on
Copy link to clipboard
Copied
actually - forget what i just said... I just installed 13.4 and tried again. This time it nailed it!!
it might not stand up to close scrutiny but I suspect I could get it perfect with more effort.
What an excellent tool this is!
Copy link to clipboard
Copied
Tengo 2 preguntas:
1. Si aplico la herramienta IA generativa (en Lightroom Classic) sobre una previsualización inteligente, esta se aplica sobre la imagen al 100% o al tamaño de la previsualización? Cuando desactivo la previsualización no queda bien a tamaño 1:1, queda borroso.
2. Si aplico esta herramienta IA Generativa desde Lightroom o Lightroom Deskop a una foto de una colección sincronizada desde Lightroom Classic se aplica en la previsualización o en la foto original?
Me está pasando que el trabajo realizado se ha aplicado a las previsualizaciones, y no a las fotos tamaño 1:1. Quedando difuminadas las zonas que he tratado con la herramienta !quitar"
Copy link to clipboard
Copied
I've used it on some small things and its done great. It has however left some bright spots over the object I have removed but, ive been able to fix it so far.
Copy link to clipboard
Copied
MY AREAS UNDER 'REMOVE' LOOK NOTHING LIKE THE ONE I JUST SAW ON PHLEARN...NOTHING REMOTELY LIKD WHAT HE WAS WORKING WITH...MY 13.4 IS 'EARLY ACCESS'....BUT AGAIN HAS NO APPEARANCE LIKE THE ONE HE WAS USING AS AN EXAMPLE...I WATCHED HIS VIDEO SEVERAL TIMES, THE SCREEN IN MY 'REMOVE' IS NOTHING LIKE THE ONE HE SHOWED....SHOULD I REINSTALL 13.4? PHLEARNS DID NOT SHOW 'EARLY ACCESS' IN THE BOX....ANY IDEAS???????
Copy link to clipboard
Copied
@Frankie36, please post a full-resolution screenshot (no a phone pic) of the entire LR window, so we can see what you're seeing and get the issue straightened out.
Copy link to clipboard
Copied
EU ESTOU AMANDO, ERA O QUE FALTAVA NO LR
Copy link to clipboard
Copied
a clear yellow line not removed
other pictures the same with clear objects
Copy link to clipboard
Copied
@Gerard38305403cjab: "a clear yellow line not removed, other pictures the same with clear objects"
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 the original photo here (not an export) so we and Adobe can see the issue in detail. If the forum won't let you attach it, upload it to Dropbox, Google Drive, or similar and post the sharing link here.
Copy link to clipboard
Copied
I find the generative remove in Lightroom Classic very helpful, but the replacement resolution is much too low and the replacements, at 100%, often reveal a vicious halo around the edges. Sometimes there is stippling or what may be a grid patter in the repair area also. I am confident in time these issues will be resolved........
Copy link to clipboard
Copied
@corneliusr7095, please attach here full-resolution JPEG exports of the original photos and the results of applying Remove showing these different issues. That will provide Adobe with actual examples of what's going wrong.
Copy link to clipboard
Copied
This is dissappointing - not nearly as good or effective as the AI tools in Photoshop. Still better to Edit in Photoshop (edit a copy) to remove distractions, generate extra space etc first, then go back into LR and do all your other edits etc there. You keep a copy of the original as well, in case it all goes wrong!
Copy link to clipboard
Copied
@Top Cat2000: "This is dissappointing - not nearly as good or effective as the AI tools in Photoshop."
Could you please post an example or two of the original photo and the results of LR Remove and Photoshop Remove? Most of the reports here of Photoshop doing better are addressed in this article:
https://www.lightroomqueen.com/generative-remove-replace/
It would be helpful to know in detail which issues you're facing with LR Remove.
Copy link to clipboard
Copied
A difficult image to edit, so ignore the underexposed ship. In the LR edit, there is a ghost image where the wind turbine has been removed - this took about 4 attempts to get a reasonable result. The cars were fairly well removed in LR (2 attempts), and the figure by the bollard was more successfully removed, (1st attempt) as was the smaller mast in the distance. I then used the Generative fill in PS to compare, and the replacements were all better than the LR ones.
Copy link to clipboard
Copied
@Top Cat2000, the ghost outline of the wind turbine is caused by doing Remove (any kind of remove) on top of the an AI mask (e.g. Sky). The original mask didn't include the turbine, so when you removed it, its pixels were replaced by the original unedited sky. You can either do Settings > Update AI Settings to recompute the mask, or apply Remove first then the mask (which is what Adobe recommends, though that doesn't match the natural workflow of many people).
As for removing the person next to the bollard, I didn't see any qualitative difference between LR and PS.
The cars, however were tedious for me to get an acceptable replacement with both LR Remove and PS Generative Fill. Lots of just-OK variations but nothing very good. Here is the best I did with LR after many tries (PS was different but no better):
Copy link to clipboard
Copied
Thanks johnrellis. Yes , I have had that ghosting issue before, I should have done things in the proper order! (As you say, not always the most intuitive way of working). I sort of assumed the AI was intelligent enough to see through this, as it is amazing how it does recreate scenes. You certainly got the car park flat, which I didn't achieve!
PS always offers 3 alternatives which is handy as the first is not always the best, but LR does not appear to do this. It all goes to show theres nothing like the craft of making a good image in the first place like we used to in the days of film!
Copy link to clipboard
Copied
@Top Cat2000: "PS always offers 3 alternatives"
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
LR Remove also offers 3 variations each time you click Refresh, though you have to click the left- and right-arrow buttons to see them in turn:
I like that PS shows you all three at the same time, and as you click Generate to see more, it shows all the variations you've generated:
With LR, I find myself making a Snapshot for each variation that looks promising, and then hovering the mouse over the list of snapshots to quickly compare the best variations. It's clumsier but gets the job done.
Copy link to clipboard
Copied
AMAZING!!!!! I love what it has done for some of my images... it can be funny though! I'm adding 3 images... the first original with a '360° camera' in the shot, the second (unrefined) capture to remove it and the third, a much better defined selection to remove but still an unsubmittable image. The AI did very well in my opinion, and I hope your further development of it will be even more pleasing. Bravo!
Copy link to clipboard
Copied
It replaced my reflection in a mirror with the reflection of some weird guy with red face...scary and weird!
Copy link to clipboard
Copied
@AlexMastellone: "It replaced my reflection in a mirror with the reflection of some weird guy with red face"
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 the original photo here (not an export) so we and Adobe can see the issue in detail. If the forum won't let you attach it, upload it to Dropbox, Google Drive, or similar and post the sharing link here.
Copy link to clipboard
Copied
So far so good
Copy link to clipboard
Copied
I'm running into some issues with LrC's Develop module not always displaying/rendering changes to Gen AI Remove settings, e.g. opacity. This seems to only crop up when modifying some overlapping gen AI remove areas. The changes are properly reflected in LrC Library previews after a few moments, and everywhere in Cloud products (LrD/LrM/LrW) once synced. The changes are also properly reflected in exports of the image from LrC.
The only semi-fix I have found is quitting and reopening LrC—that will get Develop to properly display opacity as defined. However, it also requests a reupdate of AI settings at that point, which recomputes/alters some of the Gen AI in the image. You can then choose the previous history step before "update AI settings." That gets you back to the Gen AI versions you had, at the opacity you actually specified, without any AI errors. But, you're then back to the same original issue, as further opacity changes will again not render in Develop.
I realize overlapping Gen AI Remove areas is probably not an intended usage. I'm using the overlaps because I'm getting some interesting abstract artistic results. Which I realize also isn't an intended usage. But stiill: LrC Develop should render settings properly, as everything else does—and as LrC will export.
In LrC, I have tried saving metadata to file, and tweaking other develop settings. Nothing other than quitting and re-opening seems to force LrC to reevaluate the opacity on some of these areas in Develop.
Unfortunately for troubleshooting, the issue is inconsistent on different areas in different snapshots of the same image. If relevant, most/all of the removal areas were probably applied in LrD or LrM. I've created various snapshots in LrC from versions synced down from the cloud; some of them have issues, some of them don't.
Broadly, my fix has been to just work with any artsy overlapping Gen AI Removal in LrD or LrM. If I create snapshots in LrC, I'm safe editing things other than the Gen AI Remove areas.
--
Primary image I'm having trouble with is an HEIC, HDR editing enabled. Full file lives in the cloud, not just a smart preview. There are usually no requests to update AI settings other than when quitting and reopening LrC as described above.
macOS 14.5 on MBP 2020 13" M1 with LrC v13.4 and LrD v7.4.1
iOS v17.5.1 on iPhone 12 with LrM v9.3.1
Copy link to clipboard
Copied
@umlautnord, the behavior you describe does sound like Remove is not operating as intended by the developers (i.e. a true bug under Adobe's definitions). I suggest you submit a separate bug report following these guidelines:
https://community.adobe.com/t5/lightroom-classic-bugs/how-do-i-write-a-bug-report/idi-p/12386373
Include the sample photo you're using, a written step-by-step and a full-resolution screen recording (not a phone video) showing the detailed steps you took:
https://www.descript.com/blog/article/how-to-screen-record-on-windows
https://support.apple.com/en-us/102618
If the files are too big to attach to your post, you'll have to upload them to Dropbox, Google Drive, or similar and include the sharing link.
I understand this is a lot of work. But having worked with Adobe for many years, I know they're much less likely to pay much attention unless they can immediately reproduce the problem (unless many, many people report it).
Copy link to clipboard
Copied
Oof, yes. I will try to pull this together. As I said, it doesn't always happen, but, since you think it sounds like a true bug I'll work on it. Thanks for flagging/the encouragement, @johnrellis .
(Is there a way to share the image file itself with Adobe folks without making it public?)