Skip to main content
D
DanielBoston
Known Participant
June 29, 2021
Question

metadata status still broken

  • June 29, 2021
  • 5 replies
  • 2618 views

Going crazy trying to deal with metadata inconsistency problems. I know that this has been an issue in the past, but it seems that it's still broken. In short, Lr is reporting metadata statuses for large numbers of files in my catalog that seem to be wrong. And when I try to fix them, eg, by selecting all files classified as having been changed in the catalog, and I then save their metadata to disk, the save seems to complete successfully (at least no errors and the file mod times as reported by macOS are updated), but they are still reported as unresolved. The only workaround I've found so far is to (a) save all the files to disk; (b) read their metadata back in (which is slightly worrying because on doing the read, Lr reports, incorrectly I believe, that the metadata will be overwritten). I've noticed other bugs too: the counts of files in the metadata filter panel don't correspond to the actual number of files listed; when I succeed in resolving files, the number still shows thousands of files unresolved but the panel with the tiles is empty.

 

Some more information:

-- I'm running the latest version of Lr on Big Sur. Adobe friends: if I could copy-paste the build number from the about panel I'd include it 🙂

-- This seems to happen on all kinds of files, DNGs, JPEGs and raws, and for even the simplest metadata updates (most notably keywording).

-- I'm not sure I've seen this problem for files stored on my Mac's SSD; it seems to only occur for files on my GRaid external drive.

-- I can reproduce the problem by selecting a single file that is reported as out of sync, then saving to file, noting that the metadata date in Lr matches the new date on disk, and then seeing that it's still reported as out of sync.

 

And yes, in case you're wondering, I do have more than one Lr catalog. I know switching to a single catalog might eliminate this problem, but I'm really loath to do that. I have one active catalog of images I'm currently using in projects, which contains about 50k images, and is kept on SSD, and another one of all images, in which I don't do any editing work except keywording, and that has about 200k images in it, and is kept on an external hard drive. 

This topic has been closed for replies.

5 replies

johnrellis
johnrellis
Legend
June 29, 2021

"I have one active catalog of images I'm currently using in projects, which contains about 50k images, and is kept on SSD, and another one of all images, in which I don't do any editing work except keywording"

 

If the catalogs don't share photos, then there's nothing untoward about having multiple catalogs.

 

However, if you have photos that are in both catalogs, then that can definitely cause metadata status warnings. For example, if you edited a photo in one catalog and did Save Metadata To File, then opened the other catalog, you'd see the status Changed On Disk.  

 

If LR's metadata status worked properly, you could keep your head straight doing this, paying careful attention to the metadata status indicators and doing Read Metadata From File where necessary to transfer the information from one catalog to the other. 

 

But given the flakiness of LR's metadata status, I definitely don't recommend sharing photos between catalogs.

    johnrellis
    johnrellis
    Legend
    June 29, 2021

    "when you read metadata from file, the develop action history gets a new action "From metadata."

    It's not possible that this is actually reckoned as a metadata modification, is it? If so, this would be disastrous. It would mean that immediately after reading metadata from file, a file in the catalog is actually out of sync with the disk, and would appear as changed in the catalog!"

     

    That History step just indicates the action you took.  Normally, Read Metadata From File makes the catalog metadata the same as what's on disk, though as noted above, there's a known bug with non-zero crop angles.

      D
      DanielBostonAuthor
      Known Participant
      June 29, 2021

      Wow, this is a real mess. 

       

      I have no saved/read 5,000 files. I've no idea how many have been corrupted; I'm sure many of them have crop angles and many are B&W.

       

      I tried to import one catalog into the other, and hit another serious bug: the custom order of files in collections (that exist only in the importing catalog but include files that were in the other catalog) has been corrupted. 

      johnrellis
      johnrellis
      Legend
      June 29, 2021

      From the details you've reported, it sounds like there are multiple issues going on, so let's try to carefully tease them apart.

       

      In general, LR's metadata status has always been unreliable. Some versions have had many fewer problem reports than others, but in the last year, it seems there are more reports.

       

      If you're sure that you haven't edited a photo or its metadata in another app, then you can safely trust that the information in the catalog is the "truth", and you can do Metadata > Save Metadata To File. In past versions, that would clear a spurious metadata status indicator. 

       

      In past versions, you could safely follow Save Metadata To File with Read Metadata From File, which was sometimes necessary to clear the indicator. However, LR 10 introduced a reproducible bug where Save Metadata To File wouldn't clear the metadata status, and a subsequent Read Metadata From File wouldn't either.  In addition, if the photo had a non-zero crop angle, Read From Metadata would lose the crop angle in the catalog:

      https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-save-metadata-to-file-doesnt-change-metadata-status-read-metadata-from-file-doesnt-always-work/5fdbda743a4b973cd0edccf0 

       

      There may be other conditions other than using Black & White or non-zero crop angles that trigger the spurious metadata status.  This bug is not yet fixed, so doing Read Metadata From File is definitely unsafe!

       

      If doing Metatadata > Save Metadata To File doesn't clear the spurious status indicator, then I recommend to just ignore it.  It bugs the hell out of me to see it, though.

        D
        DanielBostonAuthor
        Known Participant
        June 29, 2021

        Thanks so much for all this, John. Incredibly depressing though, as it doesn't seem to leave me with any good options, and I'm now worried that by saving and reading metadata I might have corrupted a large number of images. 

        I'm rather astonished that a bug of this severity hasn't been fixed.

        Any thoughts about the "From metadata" action?

        GoldingD
        GoldingD
        Legend
        June 29, 2021

        Just on external media?

         

        Sounds like a MACOS cybersecurity issue. A right to access the external media may have not been setup (usually because the owner overlooked a pop up notice from the MACOS)

         

        trying to remember a link to support the above. perhaps nother member will cortect or add to. This goes back to MACOS Catalina.

         

        Ah, old link, refers to Catalina, but still on point.

        https://nektony.com/duplicate-finder-free/folders-permission

         

        D
        DanielBostonAuthor
        Known Participant
        June 29, 2021

        It's thoroughly inconsistent though. I've been writing from this catalog to the disk forever... And certainly no macOS warning...

        GoldingD
        GoldingD
        Legend
        June 29, 2021

        The MACOS notification would gave come up once. It would have asked yes or no. It would not reappear.

         

        Only a what if observation.

         

        johnrellis
        johnrellis
        Legend
        June 29, 2021

        "I'm running the latest version of Lr on Big Sur. Adobe friends: if I could copy-paste the build number from the about panel I'd include it"

         

        Please do the menu command Help > System Info and copy/paste the first ten lines here. That will tell us precisely which version you're on (there's often confusion about "the latest").  

          D
          DanielBostonAuthor
          Known Participant
          June 29, 2021

          I'm on the verge of giving up, so I'm trying to create a new catalog that merges my two existing ones. And it turns out that although the system info panel will open during import, copy doesn't work :-(. But I can screenshot it -- attached.

          D
          DanielBostonAuthor
          Known Participant
          June 29, 2021

          A followup to my own post.

          I've noticed that when you read metadata from file, the develop action history gets a new action "From metadata."

          It's not possible that this is actually reckoned as a metadata modification, is it? If so, this would be disastrous. It would mean that immediately after reading metadata from file, a file in the catalog is actually out of sync with the disk, and would appear as changed in the catalog!

          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices