Copy link to clipboard
Copied
The recommended order for applying edits is:
Copy link to clipboard
Copied
I LOVE IT!!!! Im a newborn, baby and family photog and Im always dealing with drool and spit on stains on clothes and it is a great time saver!!! If you brush in in the direction of the pattern it works 100%. So far I have not had an issue. THANKS for this!!! If you do it in smaller sections its perfect. So far so good!!!
Copy link to clipboard
Copied
I am a full time photographer, I use Generative Remove for lighting corrections ( distracting shadows and spill )on set for live theatre. It works amazingly, saving me time and saving the the shot where everyone is perfect "except for the distracting ".... Not perfect yet, however, so much quicker and easier to make the correction in lightroom than exporting into Photoshop and the clone tool would take longer trying to find the matching pattern. angle etc.
An example is when the theatre black out blinds got bumped during a dress rehearsal and resulted in a light streak across the carpet in a drawing room scene... AI matched the pattern in the carpet excellently.
LC
Copy link to clipboard
Copied
I did more tests with respect to the guidelines. I wanted to remove/replace something along the picture's border e.g. replace the white triangle (bottom-left) with the expected tent rope.
I imported the raws in LrC using a preset with lens corrections (default). Unchecking those wouldn't really help: LrC is replacing the content with a similar white item most of the time.
I imported the raw again and without any crop nor transformation, LrC is more likelly to replace the white triangle with some kind of tent rope. While there are examples on the picture to relate to, the results are weird most of the time.
Bug: In all of the cases, LrC won't initially select the whole selected area, espacially at the picture borders. I need to re-select part of it with the Mask Refinement brush.
Note: moving the Heal source, its content does not always appear in the destination. Heal and Clone do not always find similar content. Implementing Alt+Click (cfr. PS) might help?
Tip: Like before, it helps to choose the better result and to use the (e.g. Remove) tool again, instead of clicking Refresh again.
Note: While the 1024 pixel limitation can be overcome in PS, this limitation can't be in Lr. It will only be useful in blurred and darkened areas.
It might be useful to have a Select Object button and a Remove/Replace switch to solve all of this post's related issues.
Copy link to clipboard
Copied
@ThierryH: "replace the white triangle (bottom-left) with the expected tent rope. I imported the raws in LrC using a preset with lens corrections (default). Unchecking those wouldn't really help: LrC is replacing the content with a similar white item most of the time."
When an object along the edge of a raw photo is consistently replaced by variants of the object rather than surrounding background, that invariably indicates there are hidden pixels. Using the JPEG you attached, the white triangle was replaced by grass and rope on the first try:
further indicating there are hidden pixels along the edge of the raw photo that Remove is matching.
In addition to Crop, Transform, and Lens Corrections (which you said you disabled), there's a fourth way of getting hidden pixels. Many cameras produce raw files that are a little bit bigger than a standard aspect ratio. The Camera Raw engine then automatically crops the image to the standard ratio, and you can't undo that crop (most users don't even know about it). But Remove still looks at the cropped pixels and tries to match them.
For example, your Canon EOS 90D produces raws that are 6984 x 4660 (aspect ratio ~ 1.4987), and LR / Camera Raw automatically crops the raws to 6960 x 4640 (aspect ratio = 1.5 = 3:2). In your example photo, there is a 10 - 12 pixel-wide border that's been cropped out. When you select the white triangle, unless you also select the hidden white pixels in that border, Remove will try to match them with white replacements.
Luckily you can select those hidden pixels with careful brushing. See this post (linked from the tutorial article) for details on how to do that:
If that doesn't help, then please attach the original raw here, or if the forum doesn't let you, upload it to Dropbox, Google Drive, or similar and include the sharing link.
Adobe knows about the issue with Crop -- one of the tips shown in LR say to Remove then Crop. I don't know if Adobe is aware of the similar problems that occur with Lens Corrections, Transform, and the invisible initial Camera Raw cropping. Removing distracting objects from the edges of photos is a very common use case, as exemplified by all the posts her, and currently Remove is very fussy about it. Many or most users will never know to disable Crop, Lens Corrections, and Transform and then to select the automatically cropped borders.
Copy link to clipboard
Copied
Currently very frustrated with the generative remove in Lightroom.
I use it on a photo, go to the next and then when I go back to the one I used the generative remove on, it's not applied and is showing each spot as an error (with the exclamation point over each spot).
Has anyone had any issues with this? I've reset the preferences, changed the graphic driver preferences, and tried different computers.
Copy link to clipboard
Copied
@chelseyl46600433: "I use it on a photo, go to the next and then when I go back to the one I used the generative remove on, it's not applied and is showing each spot as an error (with the exclamation point over each spot)."
Do you get similar symptoms if you use AI masking (e.g. Sky or People masks)?
Copy link to clipboard
Copied
I do! I just noticed that the same thing happens with masking.
Say I use a radial grad to brighten a face and then subtract the background using the AI option. If I leave the photo and then go back to it, the radial grad is still there, but the AI subtraction from the mask is now gone.
Copy link to clipboard
Copied
The catalog file <catalog>.lrcat-data, where LR stores computed masks, is probably corrupted or not writeable for some reason, which has happened to a fair number of people in the last couple of years.
1. Do Catalog Settings > General > Show, which will open Finder / File Explorer with the current catalog folder selected.
2. Exit LR.
3. In that folder, move the <catalog>.lrcat-data to your Desktop.
4. Restart LR.
5. In Library, select some of the affected photos and do the menu command Photo > Develop Settings > Update AI Settings. This will recompute the Generative Removes and AI masks.
Does the problem go away for those photos? If so, then select all the photos in your catalog and do Update AI Settings -- it could take a while.
Copy link to clipboard
Copied
You. Are. An. Angel! Seems to have worked like a charm! Thank you so much 🙂
Copy link to clipboard
Copied
This feature is AMAZING. Nice job Adobe! Game changer in many ways.
Copy link to clipboard
Copied
I'm having trouble removing a dark rectangular area at the top left corner of an image. Blue sky surrounds it. It should be an easy task, but neither the new AI fill nor the older tools do a decent job of it. Whether I select the entire rectangle or just a piece of it (with some surrounding sky included in either case), both remove and heal operations leave black patches in the sky an much of the leftmost portions of the image.
A few times I have had the source area show up, but moving it does not solve the problem.
Copy link to clipboard
Copied
@Pacoh, please attach a full-resolution JPEG exported from the original (unmodified) photo.
Copy link to clipboard
Copied
Hi,
enhoying the generative ai so far. For some reason it doesn't remove completely black / darck objects though. Cannot figure out why.
Copy link to clipboard
Copied
@raikulipoika, see this article for how to remove objects:
https://www.lightroomqueen.com/generative-remove-replace/
If that doesn't help, please attach here a JPEG exported from the original unmodified photo and a full-resolution screenshot of the results you're getting.
Copy link to clipboard
Copied
Works ok, but not well enough to replace PS, which ideally it should do.
A common issue I find is that the size of the brush will progressively get smaller with each click, despite me not touching the size slider or shortcut keys. Quite frustrating to then have to constantly re-size the brush with each click
Copy link to clipboard
Copied
The size of the brush reducing with each click of the mouse is a known bug. It can be avoided by temporarily turning off Lens Correction and Transform.
Copy link to clipboard
Copied
@porterhouse_89, building on Ian's reply, that bug affects all the Remove modes (Remove, Heal, and Clone) and isn't specific to just Generative Remove:
The symptoms have been reported for a year, and it's not clear why Adobe hasn't prioritized a fix (they rarely comment on such things). Please add your upvote and a constructive opinion to the bug report.
Copy link to clipboard
Copied
My understanding is that the issue is also in Camera Raw and Lightroom Desktop, albeit not as obvious since they use different brush size scaling. The actual fix needs to be made in Camera Raw.
Copy link to clipboard
Copied
@Ian Lyons : "The actual fix needs to be made in Camera Raw. "
I think that's why the bug report is filed in the Camera Raw forum (and thus hard to find by LR Classic users).
Copy link to clipboard
Copied
@johnrellis "I think that's why the bug report is filed in the Camera Raw forum (and thus hard to find by LR Classic users)."
The original bug report was file by me internally in early May 2023, and referenced here in Lightroom Classic form in early July 2023. It was some months later (September 2023) that it was identified internally as being an ACR bug. It was then that it was moved to the ACR forum. Moving bugs such as this to ACR forum isn't unusual, but does make it difficult (i.e near impossible) for LrC users to find.
Copy link to clipboard
Copied
Hallo,
nach meinen bisherigen Erfahrungen werden randständige Objekte, die nur unvollständig im Bild sind, oft nicht entfernt, sondern modifiziert, offenbar speziell, wenn sie mit kräftigen Farben einhergehen. Die Abwahl von "objektorientiert" erzeugt ähnliche Ergebnisse.
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.]
@Carthie: "peripheral objects that are only partially in the image are often not removed but modified"
The photo Original.jpg has been significantly cropped (2000 x 1333 from a 8256 x 5504 raw). So it appears that you were applying Remove to a cropped raw. The general rule is to Remove first, then Crop. See this article for details:
https://www.lightroomqueen.com/generative-remove-replace/
And see my recent post with screen recordings illustrating the same issue:
When I use Remove on your Original.jpg (exported from the cropped raw and containing no cropped-out pixels itself), Remove removes the red object perfectly:
Copy link to clipboard
Copied
Absolutely love it BUT, please make the CLONE stamp work the same as Photoshop (ie) select brush size, select item to clone, click alt and clone away!
The Lightroom clone stamp has a mind of its own!
Thank you.
Copy link to clipboard
Copied
@SADDLE-UP: "The Lightroom clone stamp has a mind of its own! "
Could you be more specific about how it's not working well for you? Full-resolution screenshots (not phone pics) might be very helpful.
Copy link to clipboard
Copied