P: AI Masks Require updating and/or disappear

We use multipe editors and transfer Catalogs from their devices to our devices. Catalog File plus data Folders. We are seeing AI settings not transferring automatically (as set by the editors). we have to update the AI settings. Is there a correct procedure so we would see the AI Settings chose by the editors? (as opposed to the hacks in this thread or maunally updating on our side?

@jrsforums 

I use Presets Groups...carefully named groups.

e.g

Masking Ai / Ground Artificial

Masking Ai / Ground Natural
Masking Ai / Vegetation

etc...

I don't remember the exact name of each preset but I know where to find them.

.

@C.Cella I'm actually not a fan of presets....650!!...how do you ever remember them, much less find them 😀

I really only use presets when the SDK does not provide for it in Loupedeck (or not implemented by them) or no KB shortcut available.  Things such as 'Denoise', 'adaptive Color' (or other profile), 'Landscape mask', etc.

@jrsforums yes that is a workaround but it unfortunately means two steps in history.

1. apply preset (missing Ai).

2. Update Ai Settings

It's catalog bloat.

In theory searching for Presets with Lightroom should be the best way to work but in practice (due due to missing operator) searches return too many results.

I have created over 650 custom presets myself and I can't remember the exact name of each, search supposedly should help us but doesn't.

.

@C.Cella i have eased the problem on Loupedeck by adding a KB shortcut button (ctr-alt+W, as I remember) to do 'Update AI'  works a lot faster than mouse/pen over to press it on screen....and the combo of preset button and update button are a lot faster that searching for preset in left panel.

EDIT: Actually....I just had a thought....Loupedeck has multi-step actions.  I might try to combine them at some point....at least the ones I use the most.

@jrsforums avoid using Loupedeck to apply Presets.

@johnrellis Worth also adding that photo:applyDevelopPreset() has serious usability problems and it is presenting too many modal progress scopes.

The alternative is to use catalog:updateAiSettings() to do the job but that means creating extra history step and bloat catalog.

.

@C.Cella have conversed with there Logitech support multiple times (ticket 4365778)

@jrsforums ok Loupedeck didn't update the code.

They should update it immediately and, you know what, it's actually three letters to add.

I recommend to write their support.

I will write to one of their employees myself. 

@tonyhartphoto CT, Live, & Live S.  Software version 6.2.1.  All work fine with LRc

@C.Cella nope, do not see that until the 'update AI' button is pressed.