Community Manager

해결됨

P: New AI-powered Generative Remove (Early Access) available across all surfaces.

Forum|Forum|3 years ago
January 22, 2023
894 답변들
706766 조회

This post applies to Lightroom Classic and the Lightroom Ecosystem products.
Post Camera Raw feedback here

This thread is now closed. Please update to LrC 14.x or LrD 8.x. If you wish to provide feedback, please go to the new article.

The Lightroom team is sharing an early look at Generative Remove, which makes it easier to remove unwanted objects and distractions, even on complex backgrounds, with a simple brush stroke. Generative Remove is powered by Firefly AI.

How to use Generative Remove on a desktop:

You can find Generative Remove under the newly renamed Remove panel (aka “Heal”).
Make sure the “generative AI” checkbox is enabled before you start brushing (note: when unchecked, Lightroom will use Content-Aware Remove to fill your brushed spots).
By default, you will be given a moment to refine your selection with an add or subtract brush. Remember to include shadows for a more accurate result! You can also skip this step by holding down ‘CTRL’ on windows or ‘CMD’ on mac as you finish your brush stroke.
Once you’re ready to apply and have accepted the terms, Generative Remove will use Firefly AI to remove your distractions and intelligently fill in the space that’s left by the removed objects.
Note: stable internet connection is required to use this feature.
Generative Remove also lets you choose from multiple variations, so you can pick the one you like best, giving you full creative control.

Checkout the FAQ and Best Practices

Please give it a try and share feedback and/or report variations in this community forum. It would greatly help to include details like which app you are using (i.e., Lightroom Classic or Camera Raw) and other system details. Our team will continually monitor this thread to track issues to improve the future experience.

Lisa Ngo: Lightroom Product Manager
Posted by: Rikk Flohr

Update (Dec 2024): With the new release, it is no longer necessary to perform Generative Remove Operations prior to Cropping.

Update:

Here are some tips if you are having issues with the feature replacing your object instead of removing it.

Enlarge your selection - if your brush stroke is too tight, you will have unexpected results.
Remember that removing an object means painting over it, its shadow, its reflection, and any non-contiguous pieces. If you leave behind a shadow, a reflection, or a disconnected piece (e.g., a hand on a shoulder), the AI will attempt to create something to cast the shadow, reflect, or complete the unbrushed discontinuous item. You can avoid these issues by following the guidance provided in this linked tutorial. https://www.lightroomqueen.com/generative-remove-replace

The recommended order for applying edits is:

Denoise
Heal (includes Generative AI Remove)
Crop (includes traditional Cropping, Lens Correction, Transform, or any operation changing the geometry of the image, including round-tripping to PS to use Gen-Expand)
Global Edits
AI Selective edits (Sky, Person, etc)

If you deviate from that, you may see the removed object remain as a ghost image. If this occurs, you will have to use Update AI Settings, which can be found under the Develop module 'Settings' menu.

최고의 답변: daleducatte

Hi, I'm getting the same error messages, as are some other people. There's a recent post on Reddit from an Adobe employee that Adobe is aware of the problem and is working on it. See here:

https://www.reddit.com/r/Lightroom/comments/1fka2el/suddenly_unable_to_use_the_remove_tool_due_to/

이전 답글 보기

C

colettes63259829

Participant

Not really efficiate

SADDLE-UP

Participating Frequently

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.

johnrellis

Legend

@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.

SADDLE-UP

Participating Frequently

John it acts more like spot removal and seems no different than the heal
brush – or am I using it wrong?
Click on the object you want to clone and it searches the picture for
something to replace it with UNLIKE Photoshop where I can actually CLONE
the item / object / from the spot you have clicked on.
Just make it the same tool as Photoshop!

Carthie

Participating Frequently

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.

johnrellis

Legend

[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:

https://community.adobe.com/t5/lightroom-classic-discussions/strange-trouble-with-generative-erase-tool/m-p/14715423#M370897

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:

porterhouse_89

Participant

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

Ian Lyons

Community Expert

@porterhouse_89

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.

johnrellis

Legend

@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:

https://community.adobe.com/t5/camera-raw-bugs/p-retouch-circle-automatically-becomes-smaller-on-images-with-transform-adjustments/idi-p/13902283

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.

R

raikulipoika

Participant

Hi,

enhoying the generative ai so far. For some reason it doesn't remove completely black / darck objects though. Cannot figure out why.

johnrellis

Legend

@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.

Pacoh

Known Participant

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.

johnrellis

Legend

@Pacoh, please attach a full-resolution JPEG exported from the original (unmodified) photo.

kapplegate44

Participant

This feature is AMAZING. Nice job Adobe! Game changer in many ways.

J

Jordan26437343lemp

Inspiring

I'm trying to get into using Lightroom's new AI Generative Erase tools, but odd (I think) behavior I've experienced was with an image in which I was trying to remove a car from the foreground. The good news is that in a way it did so, but the bad news is that it just replaced it with a different car! As if my problem wasn't the presence of the car itself but what kind of car it is! Obviously that's not the case -- what I was hoping for was a normal-looking street where the car was located. Is this is a known bug, or am I doing something wrong here? Thank you.

johnrellis

Legend

[Oops, the forum sent me your original post just now as a "new" message. Ignore my reply.]

~~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.

johnrellis

Legend

That's incredible work!

To answer your question, though, the one I was specifically trying to remove was that minivan -- the first (almost) full vehicle on the road. You wanted the original photo so that's what I provided, but in reality, I had already cropped the image a bit so that the first one you see just a little of was no longer even there without my having to erase anything.

So, in the spirt of "teaching a man to fish," just to be clear, you clicked on the icon that looks like a little padlock, made sure the second little padlock was selected (not heal or clone), left "object aware" and "generative AI" checked, brushed over it, and just clicked "Apply?"

@Jordan26437343lemp, I've attached a screen recording showing Remove mode removing that car from the uncropped original photo, using the options Generative AI and Object Aware.

"in reality, I had already cropped the image a bit so that the first one you see just a little of was no longer even there without my having to erase anything."

That crop is causing Remove to replace the car with another car. I've attached a second screen recording showing exactly what happens.

Remove always looks at all the pixels of a photo, even those that have been cropped out. When you crop out part of the car and then select it with Remove, not all the pixels of the car get selected. As it always does, Remove tries to replace the selected pixels with a new generated image that best matches the surrounding unselected pixels. Since there are bits and pieces of car surrounding the selection, Remove does a good job of generating a replacement that matches! It can't simply replace the partially selected car with pavement since that would look very jarring against the remaining unselected parts of the car.

So the rule is: Remove first, then Crop. (Or remove an existing Crop, then Remove, then reapply the Crop.) The article above explains that there are other ways pixels can get cropped out: Lens Corrections, Transform, and with some cameras, the hidden cropping that occurs when you first import the photo.

This is tripping up many, many people, as seen in this thread. Adobe has designed all the Remove tools (Remove, Heal, Clone) to be applied first, before you use Crop or AI Masking. But that doesn't match the natural workflow of many people, who want to do the "big" edits first (Crop, Exposure, adjust with masks), decide if the photo is a keeper, and only then clean up instrusive objects and spots. In that workflow, it would be wasting time to clean up the photo first with Remove only to decide it's not a keeper.

Screen_Recording_2024-07-02_at_10-43-07 AM.zip

Screen_Recording_2024-07-02_at_10-49-10 AM.zip

C

chelseyl46600433

Participant

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.

johnrellis

Legend

@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)?

C

chelseyl46600433

Participant

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.

T

ThierryH7727272

Inspiring

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.

Thanks a lot.

johnrellis

Legend

@ThierryH7727272: "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:

https://www.lightroomqueen.com/community/threads/more-complications-with-remove-and-cropped-pixels.50382/

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.

답글 더 보기

가입하기

소셜 로그인

커뮤니티에 로그인

소셜 로그인

파일을 바이러스 검사 중입니다.

이 파일은 다운로드할 수 없습니다