Copy link to clipboard
Issue: Lightroom Classic 11.4 does not render local adjustments for older files unless they are first opened in Develop
Steps to reproduce:
Expected result: file will be rendered with masks, in step 1Actual result: file is rendered without masks, at all, in step 2
An update, version 11.4.1, was released on June 28th, for Lightroom Classic. It contains a fix for this issue as well as a couple of bugs causing intermittent crashes for some customers. If you do not see the update in your Creative Cloud Application, you can refresh it by hitting [Ctrl/Cmd]+[Alt/Opt]+[ R ].
Thank you for your patience.
I am not able to reproduce what you are seeing. The Library-exported and the Develop-exported are identical and contain the masking.
I should have added it to the description: this only happens to older files to me (I mention it in the video).
I can provide example photos (DNG with embedded XMP) as well as NEF+XMP sidecar that show how the XMP differs, before and after taking such photos to the Develop module.
Since they're my original raw files I won't link them publicly here but if you can give me an email address I'll happily provide them.
I understand. However, the files I tested with haven't been edited in several years.
It affects hundreds of my files. I'm sure it is related to the "unmodified files are marked as modified to republish" bug.
Again, I'd be happy to provide example files. One DNG in my catalog is 55.8 mb BEFORE I switch to Develop, and 59.1 mb afterwards. (auto-save XMP is on, but even manually saving XMP from the Library does not change it - only switching to Develop does.)
I am not experiencing this issue. LrC 11.4, Windows 11
I'm sure it is related to the "unmodified files are marked as modified to republish" bug.
I don't see the connection. Can you explain why you think these are connected?
Internally, something is getting updated (for example, from Split Toning to the expanded Color Grading, or from "old local adjustments" to "New Masking") that triggers a republish, and it has been like that for a long time.
Now in LR 11.4 those files do not have their masks rendered anymore, at all - so that's the connection.
Every photo that has this problem also shows as "Modified to Republish" as soon as I switch to Develop.
Well, I have to disagree with that connection, but who really knows?
So maybe connection is the wrong word for you. Thanks for your participation.
How old ate these photos, these edits, are they so old that the process version is not 5?
Good idea; I have already tried to limit it to something logical and visible. It happens with photos that are in PV5 as well as photos in older PV's, unfortunately.
After some digging, it appears that (most? all?) my photos prior to Lightroom Classic version 11 are affected by this. The newest affected photo that I found is from September 2021 (LrC 11 with new masking was introduced in October 2021).
More precisely, the "MaskSyncID" and "CorrectionSyncID" properties in the metadata are assigned new values as soon as I open those files in Develop. I assume that this is causing the "mark to republish" update.
What's more, the updated metadata is not written to XMP, even though the Catalog preferences setting is on. Only manually using "Save metadata to file" will update the on-disk XMP data with the one that's in the catalog.
Regardless, these files export fine in LRC 11.3 and they export without their masking/local adjustments in LRC 11.4.
I'm attaching two XMP sidecar files; one saved before switching to Develop, the other saved after switching to Develop.
I am able to reproduce this bug. Here is an example. Only difference is going into Develop, do nothing, and go back to Library.
This was a file with PV2. Here is a file with the current process version from not so long ago but from before the latest updates:
The local edits are clearly not getting applied in the export until I enter Develop, do nothing and go back to Library. The preview stays correct.
@alexskunz I am able to repro the issue at my end where old local corrections are not getting rendered during export from Library if that image was never opened in develop in 11.0 or later. We will file a bug and investigate. Thanks for reporting the issue.