1 Pinned Reply
It has been reported that one cause of this issue is the use of the Imagen AI Plugin.
@johnrellis has provided two workarounds in his post in this thread.
- Deleting the <catalog>.LRCAT-data file, or
- Using Imagen AI's Bridge workflow, which downloads .xmp sidecars rather than writing into the catalog.
You can find additional details in the thread.
Update 8/12/2025
Greetings all,
A new update for the Adobe Photography products has been released. The August update contains an updat
...
353
Replies
I started getting the same thing in Photoshop... It just started today when I tried to use adaptive profiles in the Camera Raw Filter. I was wondering, "What the [heck]".
By @Fotomaker01RA
As Camera Raw does not store this info in a central database, but with each image separately, this cannot be the same problem. The Adaptive Profile does indeed have to be updated regularly depending on what you do next, so this might be as expected.
Thanks! What do you mean by 'apply Remove'?
I do use people masks and clone skin on top of that (perhaps this is too complex of a task for LrC?). Here is an example of a couple of days ago when Adobe Chat Support reassured me they could get my AI edits back. This is one of the two weddings I had to reedit after noticing during export that my changes were gone.
There is another less common glitch that another colleague has reported: ghosting. I have encountered this 4x, and in the end I take the raw file to PS to fix. Since this situation is rare, I forgot to report. I only remembered now looking through screenshots I took during my support chat.
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
I'll reply with a couple of separate posts.
"There is another less common glitch that another colleague has reported: ghosting. "
These ghosts are usually caused by applying the Remove tool on top of an AI mask. In this case, it looks you had created an AI mask that included the wall and then darkened the wall. Then you used Remove to remove the leash. But the mask didn't include the leash's pixels, so after removing, they look like the original lighter tone of the wall.
Prior to LR 14.4, when you did this, there would be a red dot under the Masking icon in the Develop. Now, the orange-circle icon to the right of the Masking icon lights up. You can click that icon and then Update, or do the menu command Settings > Update AI Settings -- this causes the AI mask to be recomputed.
@luzye_photo: "I do use people masks and clone skin on top of that"
LR's rendering was designed with the intention that the Remove tool (including Heal and Clone modes) would be applied first, and then you'd apply masking. The AI masks are generated based on the image after Remove has been applied.
But when you apply masking first and then Remove (which is often a more intuitive order), LR will warn you with the orange circle icon, which shows this when you click it:
When you click Update, LR will then "properly render your edits". Often there isn't much change, but sometimes, as with the leash example, the changes are quite noticeable, since the masks get recomputed, taking notice of what was removed (or healed or cloned). (Prior to LR 14.4, the need to update AI settings was indicated with red dots.)
So you should get in the habit of always updating the AI settings whenever the orange circle appears so that LR has "properly rendered your edits". Otherwise you can end up with surprises like your face example.
AdChoices