Skip to main content
Participating Frequently
October 27, 2021
Released

P:(Masking) Add auto update recompute to subject /sky masking after copy/paste

  • October 27, 2021
  • 139 replies
  • 30088 views

Love the auto subject detection in the new lightroom classic update.

 

Idea: add an auto recompute feature to the subject masking when working with multiple images.

 

Observation: I'm a wedding photographer. When working with multiple images and auto sync is turned on, all of my edits to one image are synced across all selected images. When working with the auto mask subject selection, LRC basically creates a mask "preset" for the visible image but won't apply that "preset" to all other images until you manually select the  "recompute subject" button on the mask pannel. 

 

Why not have LRC do this automatically across all selected images? Seems like a nice improvement.

139 replies

Participating Frequently
November 16, 2021

Sorry, in any other community, when there is a button answer, it answers to the entry where I click it.

So I have to reformulate my previous answers globaly!

So Yes, do please upvote this thread, to show how important this is.

and adobe co-workers, please ask your fellow evangelist, why on earth (or in heaven) one has to ask for this feature.

If there is a need to recalculate, there should be a way to do it

Or is that to easy for an IT-Analyst to grasp? Sorry perhaps to harsh but... really!

That said, the new masks are a killer feature, I'm sure!

As for the filter I read about, thats good to know, but there should still be the trigger to recalculate.

One thing that for me make sens: There could be an option to recalculate a selection of pictures, And for those who want it, an optional auto-recalc function, but I insist optional, as my UX is, that you have to check the result to eventualy become aware of some consequent inconsistencies

Participating Frequently
November 16, 2021

Thats good to know. But there is still no trigger to DO it.

Participating Frequently
November 16, 2021

Yes, and please ask the evangelist, why on earth (or in heaven) one has to ask for this feature.

If there is a need to recalculate, there should be a way to do it?

Or is that to easy for an IT-Analyst?

That said, the new masks are a killer feature, I'm sure!

johnrellis
Legend
November 15, 2021

"I don't understand why there isn't an error image on the individual images in Develop OR Library mode? It would be super helpful to have an overview of "errors" that exist in my gallery, even if it's a mask-needs-to-be-recomputed error."

 

You can use the Any Filter plugin to find all photos with masks that need recomputing:

https://community.adobe.com/t5/lightroom-classic-discussions/finding-photos-with-select-subject-sky-masks-that-need-updating/m-p/12503157 

 

Hopefully the next release of LR will avoid the need to do this altogether.

Participating Frequently
November 15, 2021

All of this -- also -- when the "subject needs to be recomputed" it's clearly an error, but I don't understand why there isn't an error image on the individual images in Develop OR Library mode? It would be super helpful to have an overview of "errors" that exist in my gallery, even if it's a mask-needs-to-be-recomputed error. 

Also, has anyone else experienced the phenomenon where it doesn't save your auto-generated-subject-selection masks if you input changes from an editor to your lightroom catalog?? 

I have to go through each image that was already edited and find the mask errors, select "recompute," wait for it to recompute (it can't do it in the background, so I just sit there for 10 seconds while it loads) and then manually, one by one, go through my images to see if there are masking errors. 

Participant
November 14, 2021

100% agree. Would make my workflow much faster and came here to suggest it 🙂 

Inspiring
November 8, 2021

In my opinion AI masks actually needs two improvements:

  1.  Option to compute actual masks for target photos when pasting/syncing settings (rather than just copying mask type). The same way it was implemented for Upright, where you can choose to copy actual correction or just correction type and recompute correction for target photo.
  2.  Ability to recompute AI masks for selected images in batch.

 

Also, it would be nice to optimize mask calculation.

There is no need to compute subject or sky for multiple masks on the same photo because it does not change - just compute it once.

Inspiring
November 7, 2021

Hi.

With LrC 11 it's now possible to apply AI masks.

But when you copy settings from one image to another, mask type (Select Subject or Select Sky) is copied, but the mask itself is not calculated.

Then it's required to open masking panel on target photo and click "Update".

After doing so the mask is calculated - great.

But currently it's impossible to do this in batch.

User needs to do this for EVERY image, which is a pain if you copied settings to 10, 20 or more images.

Please add possibility to batch update AI masks after selecting group of images.

Thank you.

Aundrea406
Participant
November 6, 2021

I agree. It would save so much time if I could auto recompute the masks! I don't want to fall in love with this feature until I can auto recompute. I love it already, but don't want to use it because it's killing my time editing going in every single image and manually recomputing every mask for similar photos. Please make this a thing 🤩

jdavidbuerk
Participating Frequently
November 5, 2021

In addition to adding the ability to mass-recompute Subjects / Sky / etc, Lightroom needs to apply the (re)computed Subject mask to all adjustment layer - as it stands right now, if you paste two adjustment mask layers onto a photo, with both adjustment layers containing Subject Masks, the Subject must be recomputed twice, or once for each Subject Mask.

 

This makes no sense, as the Subject doesn't change in the same image.  See the screenshot below, where the "Sky Pop" Mask has had both Sky and Subject recomputed already, and the "Couple Pop" Mask is still missing the Subject Mask and is still asking for it to be recomputed, eventhough it's already been computed once on this image.  Not only is this annoying and a waste of time, it's a waste of processing power.