Copy link to clipboard
Cropped size in pixels is now missing in Library, the full original size is just repeated
I can duplicate this BUG. It is only in the "Default" where it is wrong. In "EXIF and IPTC" it is correct.
EXIF and IPTC
I can reproduce on Windows (not on Mac) and have logged a bug with the team.
Thanks for the report and the subsequent clarification.
@Rikk Flohr: Photography
I reproduced this on may Intel Mac
"I reproduced this on may Intel Mac"
Interesting, on my LR 11.3 / Intel Mac, the Metadata > Default tagset is showing correct Dimensions and Cropped. There must be some more involved conditions triggering the problem.
The mystery gets even deeper!! This only occurs on SOME photo in my test catalog. Others display the correct "Cropped" in the Default view in Library. The problem photos also display the CORRECT dimensions in in Information Overlay in Loupe along with the "EXIF and IPTC" view.
Also to add, I can recrop the problem photos and it does not correct the issue.
[Neither @Bob Somrak nor I can post in the original thread any more. Moderators, @Rikk Flohr: Photography, please merge with:
Bob Somrak and I have observed on Mac that exiting LR and deleting "<catalog> Helper.lrdata" causes Cropped in the Metadata > Default tagset to display correctly, at least temporarily.
It would appear that the performance improvements in 11.3 to make Metadata display faster rely on cached information in Helper.lrdata (like folder counts), and that caching may be a little glitchy.
An update to the Lightroom Classic (Version 11.3.1) was released on 4/20/2022 and contains (2) bug fixes.
Please install the update via your Creative Cloud Desktop App.
You may need to refresh the Creative Cloud App for desktop software to show an update. ([Ctrl/Cmd]+[Alt/Opt]+ [ R ])
Thank you for your patience.
Two people report that 11.3.1 hasn't fixed this bug, even after they deleted Helper.lrdata (on the theory it contained staled metadata):
I am still experiencing this problem on both my computers an iMac and a Windows PC. The problem started with LrC 11.3 and continues in LrC 11.3.1.
The info on my tests are described in the thread at the link below.
I have done further checking with other users who are experiencing this bug and it is apparent that it affects users who do not have "Automatically write metadata to xmp" selected in Catalog settings.
That option is not the default in LrC and therefore does not provide any relief. I also find it strange there is no update in Adobe Camera Raw plug-in to match 14.3.1 in LrC.
Here's a screen recording that shows a step-by-step recipe for reproducing the problem in LR 11.3.1 / Mac OS 11.6.2:
Good work @johnrellis
Surely Adobe LrC and ACR beta testers should be working with default features to ensure the applications are functioning correctly.
Surely LrC beta testers and engineers are checking using default settings to ensure the Application is functioning as designed?
I think it would be just luck to find an obscure bug like this in beta. When I first duplicated the bug I got lucky and picked a photo with the issue. Several photos around it did not have the issue.
@Bob Somrak this begs the question what are the engineers doing with features that require "Automatically write to xmp" to be selected? See this other bug.
Unfortunately the bug list in LrC keeps getting longer an LONG term bugs are not getting fixed, even fairly severe ones. I used to have a list of bugs I was keeping track of and would test at most of the releases but finally gave up.
"this begs the question what are the engineers doing with features that require "Automatically write to xmp" to be selected?"
I don't think this is deliberate -- over the years, there have been a number of disparate bugs that could be worked around by manually doing Save Metadata To File or checking Automatically Write Changes To XMP. I'm sure that the LR code that handles metadata is extremely complicated, and I don't find it surprising that saving metadata to file takes a different path through complicated, tangled code, which avoids or corrects a metadata bug.
There are many contributing factors: messy industry standards that have changed significantly over LR's lifetime, the addition of new file types, the addition of new Library and Develop features, attempts to improve performance, successive generations of engineering teams of varying abilities (regressing to the mean, as is typical for mature software products), and Adobe's public statements about focusing their product efforts of LR Classic on Develop rather than Library.
Hi, I don't know if the following is part of the issue. Since the update on 4/20/2022 Lightroom didn't recognize my external drivers. I have two and in both on them appear the legend "Didn't found the file". Please I need help I couldn`t work.
@Baltazar24158793k0ps, you have a different issue. Are you on Mac?
Thanks @johnrellis I guess it is a little different but since de update. Its so strange now. I work on Mac; my two external drives are not readable in Lightroom since the updated. At the beggining also I reinstaled it, then verify catalogs, the issue is that my drives appear in green in Lt, but it can't find the files! Also since Friday, the date I update, I couldn't save in those drives. I can seee the files, open it, work on them, but when I tried to save, didn't let me do it. I have not issues before in any of the two drivesr mentioned.
Something changed in Mac OS 12.3.1, and many people are finding they need to grant LR Full Disk Access. See these instructions: