1 Pinned Reply
Update (Dec 2024): With the new release, it is no longer necessary to perform Generative Remove Operations prior to Cropping.
776
Replies
@Alan27416038d67j, your screen recording shows you're trying to remove objects from the edge of the photo, and LR is generating some other object as a replacement:
This usually happens when there are pixels beyond the edge that have been cropped out due to Crop, Transform, or Lens Corrections. So undo any of those you've applied and then do the Remove.
See this article for more details:
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.
Thanks for the reply, but the interesting thing is that I didn't crop the photo at all, it's exactly as I took it from the camera, I'll put it here for you to test. Another thing, look, I repeated it again, making sure there was no crop in the photo and look how cool, now it added a mini ball. I did it again and finally he got it right.
Anyway, it worked.
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
@Alan27416038d67j: " I didn't crop the photo at all"
You're tripping over a bug that affects many cameras. When I apply Remove to the JPEG you provide, it does quick work of getting rid of the objects and shadow in the corner:
The metadata indicates you were editing a raw from a Nikon Z fc. That camera's raw sensor is 5600 x 3728 pixels (aspect ratio ~ 1.50215), and the Camera Raw engine in LR automatically crops it to 5568 x 3712 (aspect ratio = 1.5). That cropping is invisible to the user and always occurs.
The problem is that Remove looks at all the pixels in the photo, including those that get cropped out (16 pixels on each side and 8 pixels top and bottom). But you can't see those pixels, and if you don't select them, Remove generates a replacement that matches them.
See here for how to select those hidden pixels and ensure Remove doesn't try to match them:
During the Early Access period, we weren't allowed to submit formal bug reports, so the many reports about this misbehavior got buried in the thousands of replies in the previous version of this thread. Now that it's out of Early Access (beta), it's on my list to submit a formal bug report.
release 14.0
just upgraded and my first attempt was flawless with LR. I has worked good up to this point but this was a complicated background
AdChoices
