1 Pinned Reply
Update (Dec 2024): With the new release, it is no longer necessary to perform Generative Remove Operations prior to Cropping.
827
Replies
@willy_9983: "It's about the remainder of a person on the bottom right of the image. I can't get rid of that."
With your attached .jpg, Remove immediately removed the remainder of the person from the bottom-right corner:
The image's metadata indicates that you cropped the image along all four sides. So when you applied Remove to the bottom-right corner, Remove was trying to match the unselected, cropped-out pixels. Adobe wants you to remove first, then crop (which doesn't match many people's natural workflow).
See this article for more details on how to remove objects more reliably:
https://www.lightroomqueen.com/generative-remove-replace/
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
@lex_9408: "any removal with or without object removal selection replaces the subject (wife and dog) with a unwanted substitute (repetiveley)"
Be sure to select the shadow cast the by the woman and dog. If you don't select it, then Remove will try very hard to replace them with an object that also casts that shadow:
But when you add the shadow to the selection, it easily removes the woman and dog:
It's too bad that Detect Objects hasn't been trained to include shadows and reflections -- that would help users avoid this common problem.
FWIW I myself am unable to remove a window despite painting a very large area.
I tried to refresh more times and never I was able to get a result
In Photoshop by instructing the Ai and typing "Wall empty" I got 2 usable results.
So IMO without instruction Generative Remove is failing too much in LrC.
.
.
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
Interesting, that's the first example of several dozen posted here where the object didn't remove easily. After about 5 minutes of experimenting, I was able to remove the window by selecting the discoloration underneath it -- it looks like Remove is treating that discolored area like a shadow and trying to generate something to cast the shadow. I agree that allowing the user to provide prompts as in Photoshop would make this example easier.
Here's my result, along with the same selection with Opacity = 1 to show the original image:
@johnrellis
If one look carefully even very small "holes" have blur
Yes it is hard to spot but the blur is there so it's not only for upscaled patches.
It is sufficient to paint a stroke and the blur, the different color, the hard edges become very evident.
Grain helps to blend the patch and neutralise the blur (or add mroe if one does global Grain) BUT doens't solve the hard edge and the different colors.
I don't know which setting is responsible for the colors (pm_gamma_type or pm_black_level).
Generative AI deleting should have it's own mode - 4th in the remove panel. Or at least, remove tool should reset to deafult after using, because now it saves feature tha was used before, which is often waste of time to change it manually by unchecking 'generative ai' or both 'detect object' and 'generative ai'.
@NickiG: "It has stopped working since the newest version came in. "
If it's not generating any replacements at all, even bad ones, then check that the Opacity slider is set to 100.
After you click Remove, it will appear with the other controls that let you modify the removal:
If that doesn't help, then describe in more detail what you're seeing.
Salve ho un problema con la rimozione generativa di LRC. Quando provo a rimuovere qualcosa mi esce sempre un messaggio di errore. Come si può risolvere questo problema?
The remove option in LrC is not good enough when trying to remove cables and lines. It just replaces the line with another line, when I just want it completely gone...
AdChoices