Copy link to clipboard
Copied
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.