597
Replies
LRc 14.0.1 ; WIndows 11 23H2
scrolling through pictures with AI masks increases GPU VRAM use very fast. Reaching 100% slows down LR. Only restart of LR helps for short time.
@John R Ellis Gen
I did my test and remove has two "pm_clio_model_version" and alternates between the two.
Core Model is : 1.0.5-beta.1-1.2_1.2-8c2cea4
Then Remove can have either use:
-a6
-0.1.27.1r16.2,
In LrC 13.5 I have created 2 Gen Remove (normal and Objects) and they have each one of the "sub-models".
But maybe Remove is retroactive, since is powered by Firefly.
Remove Detect Objects is using the same ModelVersion as Objects in Masking (I.e. ModelVersion = 234881976 ) BUT the team has changed the "Auto expand" that is applied on the resulting mask.
E.g
In LrC 13.5 the Remove Detect Objects was expanding, let's say X pixels.
In LrC it expands 2X pixels.
Those familiar with Photoshop know that any Ai selection can be "Expanded" in Ps...and more
Camera Raw is kinda doing the same BUT we have no control on the "Expand" for Remove Detect Objects.
.
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
@bonnieleek: "instead of removing the objects it just kept them in place and trhe "variations" had shaddows of them. "
Make sure the Opacity slider is set to 100:
You'll have to make at least one brush stroke to see the slider.
If that doesn't help, 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 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.
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
@NetHawk: "if I want to remove a hydrant, for example, it gets replaced by another type of hydrant instead of being removed altogether. "
With your attached JPEG, Remove quickly removed the hydrant:
The photo's metadata indicates you had cropped the original raw along the bottom. Remove looks at all the photo's pixels, including those cropped out by Crop, Lens Corrections, and Transform. So undo the crop, apply Remove, then redo the crop.
See this article for more details on this and other tips for removing objects more reliably:
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
Remove easily removed the pole and its shadow from your screenshot:
Your screenshot shows that you've cropped and applied masking. In general, you should Remove first, then crop and use AI masking. 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.
Well, the generative removal tool does not seem to work on power lines. Photo of a setting sun (so lots of orange); power lines with no background other than the orange sky) - attempts to select the power lines themselves proved fruitless. After a few seconds of "thinking" the power lines were not altered in any way.
Running on a MacBook M3 Pro - 18GB RAM, Sonoma 14.5.1
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
@f8lee: "After a few seconds of "thinking" the power lines were not altered in any way."
Working with the low-resolution export you attached, I can easily remove the power lines one by one:
Since that export stripped all the clueful metadata, I can't give precise remedies, but things to check:
- Make sure the Opacity slider is 100.
- When you select a line, make sure you select the entire line -- if you leave any bits unselected, Remove will generate a matching replacement.
- Detect Objects often doesn't work very well with lines -- uncheck it.
- If you had previously applied Crop, Transform, or Lens Corrections, undo those, apply Remove, and then redo them. Remove will match the unselected cropped-out pixels on the edges otherwise.
But if this doesn't help, please attach a full-resolution JPEG exported from the unmodified original photo, including all metadata.
When removing objects against a uniform sky, Remove sometimes doesn't do a good job of blending in the replacement. I got better-blended replacements by making the edges of the selected ragged and selecting the lower three lines in one selection:
AdChoices
