AI Masks need to be updated continuously

[danw94986099]

Masks are not "sticking". Meaning I'll have a mask on the photo and then I'll get the error in this screenshot. The problem is that the update doesn't actually stay. If I check again later on (sometimes a few minutes sometimes the next day) it says the same thing. This happens when I select objects/backgrounds/subjects

Version 14 (although it was happening on 13.5, I just updated to 14 to try again).

MacOS 14.6.1 (23G93)

[JohanElzenga · Accepted solution]

Lightroom Classic stores AI masks and Generative Remove patches in 'Catalogname.lrcat-data'. I've seen problems of masks needed to be updated all the time as a result of this file getting corrupted, or having the wrong preferences. Move it out of your catalog folder to test this. Start Lightroom Classic. You will get a dialog about the missing data; just click 'Continue'. LRC will simply recreate this file. Now try to update one of the masks and see if it sticks this time. If it does, then you will have to update all your masks, but (hopefully) only this one more time.

[danw94986099]

You're a king among men.

This seems to have worked. Thank you!

[Sky Photography]

So, initially, I got nowhere with this online or in this forum. I eventually got a solution (mostly) with a support engineer remotely connected to my machine.

Here's what solved the issue I had with ai not 'saving' and got me working again. It's a corrupt .lr-cat-data file that holds all the ai edits. seems like it corrupts after major LrC updates!!!!

Before taking the following steps, read through them as it's not a complete fix, but it will get it all working again.

1. Close Lightroom

2. Go to the folder that contains your LR catalogue.
3. Rename .Ircat-data file OLD.Ircat-data.

4. reopen Lightroom, lightroom will create a new lrcat-data file. 

5. Ai etc will now work. However there is a big but (excuse me). All the previous ai edits you had made will all need updating. Personally, this wasn't a biggie for me as customer delivery was important. Old delivered files I can update when & if required.

NOTE

I had the issue reoccur this week when updating to LrC 14, and it seems Adobe hasn't fixed this issue.  

[JohanElzenga]

That is exactly the same solution as what I suggest in this thread and what is marked as solution (except I suggest not to rename that file, but to move it out of the catalog folder), so I'm puzzled why you say "I got nowhere with this online or in this forum".

[Sky Photography]

I just reposted my answer from another thread that I opened months ago. Yes, your solution is excellent. Just helping the google bots 🙂 

[nico_shantii]

This worked for me. Changing the name of the catalog to OLD... restarting LRC, continue. Select all images, right click, develop settings, update AI settings. 

[goodomenphoto]

Is this "fix" still working for you? It worked for me the night I deleted the lrcat.data and rebuilt the ai masks (yesterday). Then today, the problem is back and my masks are needing to be updated any time I move off the image and back again. This problem has cost me hours and hours of my life and Adobe needs to address this instead of relying on these half-asked "fixes".

[JohanElzenga]

We have identified a problem (not necessarily the same problem everybody has) where the 'Optimize Catalog' option in the catalog backup procedure strips certain info and makes the dots reappear. So for now, if you make a catalog backup (and that is still advised), uncheck the 'Optimize' checkbox.

[KR Seals]

Does this apply to the "Optimize Catalog" in the menu?

[JohanElzenga]

Yes, don't use that either, because that is the same.

[peachatlga]

Every single time I open LRC to work on my clients wedding photos!!!!!  It is EXHAUSTING!!  I find this  inexcusable on ADOBE's part.  We pay $60/m for this?????  Get the bugs out or i'll be canceling and owning my own software editor from another company!

When does it happen?  every instance of opening LRC from a closed state.

What do i experience? all masks, Remove, heal, clone,blur, Denoise, crop edits that I make from the previous session are needing to be updated.... not just a one button update, but I have to click on every mask created find the subject/object/preset used and update it.  Also if I update the masks first, then go to the Blur and update that, next I have to RE-update the masks, crop, remove/heal/clone, etc... all over again!  

What needs to be fixed?  If I need to update, it needs to analyse and know the sequence of priority for a one button push update on all!   I really should not have to do the update if it would just save to the catalouge properly.  I have LRC set to ask me to save the cat file every time prior to exit.  

This bug is a big time waster and is costing me time and money!  Fix it Adobe! or I'm gone!

Lightroom Classic version: 14.0.1 [ 202410161356-30922cfc ]

License: Creative Cloud

Language setting: en

Operating system: Windows 11 - Home Premium Edition

Version: 11.0.22631

Application architecture: x64

System architecture: x64

Logical processor count: 20

Processor speed: 2.1GHz

SqLite Version: 3.36.0

CPU Utilisation: 3.0%

Power Source: Plugged In

Built-in memory: 65251.0 MB

Dedicated GPU memory used by Lightroom: 14529.3MB / 12115.0MB (119%)

Real memory available to Lightroom: 65251.0 MB

Real memory used by Lightroom: 18163.0 MB (27.8%)

Virtual memory used by Lightroom: 34862.4 MB

GDI objects count: 1167

USER objects count: 4702

Process handles count: 4958

Memory cache size: 779.4MB

Internal Camera Raw version: 17.0 [ 2043 ]

Maximum thread count used by Camera Raw: 5

Camera Raw SIMD optimization: SSE2,AVX,AVX2

Camera Raw virtual memory: 4765MB / 32625MB (14%)

Camera Raw real memory: -133994MB / 65251MB (-205%)

[raronsonphoto]

I have this same problem.  it is driving me crazy and taking soooo long to do anything.  I do not understand the steps to fix it.  Please help!

[goodomenphoto]

There is no real fix. Adobe does not care about us.

[JohanElzenga]

Bug fixes take time. It takes time to identify the cause, it takes time to fix the code, and it takes time to test if the fix does what it is supposed to do and does not introduce a new problem. The last thing you want (and Adobe wants) is that a quick bug fix just introduces another bug.

[iant84813607]

Also having this problem. My first really busy stretch since the start of the plague and I can't mask. (Well I thought I could, but when I went back to look at two days of editing, all the AI masks were gone.) They couldn't have picked a worse time for a failure like this.