Skip to main content
Participating Frequently
January 6, 2018
Question

Lightroom CC Classic Metadata Conflict Detected message

  • January 6, 2018
  • 8 replies
  • 5036 views

I have seen many old discussions of this but nothing recent.

I had been using Lightroom desktop and upgraded to Lightroom CC in 2017.  Since then I have had frequent occurrences of the 'conflict detected' in metadata status.

I have not modified these image files with other software since last working with them successfully in Desktop LR.

Using the 'Import settings from disk option' wipes out all the keywords but gives apparently correct capture data.

Using the 'Overwrite settings' option wipes out all the capture data and substitutes the current date for the capture date and adds an all zeros entry for GPS data.

This is impacting thousands of images so an image by image correction process is useless.

I tried both approaches today on sample images from 2012 to document the problem, these do not seem to be some 'old metadata format' referenced in other discussions.

This is a severe problem for me. Neither option gives acceptable results. I have thousands of images cataloged and keyworded as to trip, day of trip, place, subject and more. Since I can't lose all that information I will have to go to backups and reverse my 'upgrade' and go back to the older product version if there is no fix.

My System info:

Lightroom Classic version: 7.0.1 [ 1142117 ]

License: Creative Cloud

Operating system: Windows 10

Version: 10.0

Application architecture: x64

System architecture: x64

Logical processor count: 8

Processor speed: 3.6 GHz

Built-in memory: 32667.8 MB

This is a desktop system.

Thanks.

    This topic has been closed for replies.

    8 replies

    Participating Frequently
    April 21, 2018

    I encounter a similar problem, showing a number of aspects mentioned above but also some new ones:

    TIFF files (scans of slides) that worked just fine before were now moved (from within LR V7.3) to a volume on a NAS. Afterwards a large but seemingly random part of the moved images exhibited various metadata alerts (some are "conflicts", some are "errors when writing metadata", some are "external changes to metadata" -- sorry for imprecise wording, I am using a non-english language version). The files certainly have not been edited outside of LR. The alerts appeared right after the move to the NAS (from the internal drive where the catalogue still resides).

    The origin of conflicts and errors is unclear. The metadata shows creation/exposure dates that seem to reflect the time when the data was written to the NAS. The permissions on the NAS are set to read/write for my account for the entire volume so a permission problem seems unlikely.

    When solving a "conflict" by using the metadata from disk, this seems to erase all previous information on the images (e.g. orientation, which has been changed for some).

    When solving a "conflict" or or "external changes" alert by using the metadata from the catalogue, the alert is never fully resolved immediately but usually first turned into a "error writing the metadata". An "error" is then (sometimes) resolved when clicking the (new) alert.

    There are very frequent error messages during these processes (i.e. trying to resolve the alerts): Either "unknown data formats" or "fotos are write protected" (which they are definitely not). Repeating the process several times seems to resolve the problem eventually.

    Just selecting all fotos in the catalogue and repeatedly "solving" the alerts is not a solution: If I select all fotos in a folder in order to speed up the process, I get error messages for about 30 to 80% of the included fotos for which the alerts are then not resolved. If I keep the resolved fotos in the selection for the next attempt at resolving the alerts, then some of these fotos get new alerts again.

    Thanks in advance for any suggestions!

    wendy69786
    Participant
    September 15, 2018

    Did you resolve this problem? I am having the same issues with LR.

    Participating Frequently
    December 19, 2018

    Wendy--unfortunately, I have not been able to fix the problem.

    I have explained some more detail in a separate thread (here) and I have just been pointed to another (3-year old) thread, which seems to explain some of the causes (here​). A user there has made a very good analysis and while he can not give a solution it does help (me) to deal with the problem.

    You may want to have a look if this helps in your situation. Good luck!

    Participating Frequently
    April 6, 2018

    I am experiencing similar problems as well with metadata conflicts, with random files (not all files affected from any given session).  

    I compared the metadata from finder>info with the library info inside Lightroom. In situations where a .psd file was created after editing a RAW file in photoshop, it appears Lightroom retains the creation date of the RAW file when creating the .psd file; whereas finder keeps the edited date for the created date (kind of makes sense since a new file was created).  In this situation, I'd prefer to have Lightroom overwrite the metadata.  HOWEVER, when choosing this option, finder doesn't inherit ANY of the correct metadata, and instead gets a new creation date of TODAY.  WHY?  And isn't there technically going to be metadata conflict still?  I'm assuming I'm getting the error because the dates don't match, but if after overwriting finder's metadata they still don't match, why don't I still have a conflict? 

    If I choose to import settings from disc, NOTHING seems to change anywhere except the conflict goes away.  i.e. Finders' date is still the date the .psd file was created (still not the actual creation date of the RAW image) and Lightroom's date stays the same as the RAW file's creation date and time.  This seems like the better option, I suppose.  Or maybe just live with the exclamation points...

    I haven't tested out other scenarios (other than the .psd file date conflicts), but I'm assuming that my metadata conflicts are not all based on file types...

    Participating Frequently
    April 1, 2018

    I am experiencing a similar problem with metadata conflicts.  Imported from disk and it killed my keywords.  Running LR 7.2.  Original image files on a NAS.  There were NO conflicts on the original drive (USB 3).  And the changes seem to randomly crop up.  Never experienced this before and files that were ok in the past are all of a sudden show the conflict icon.  It would be VERY VERY helpful to have a utility that shows a comparison of the data that would allow me to select the correct answer or choice as to which one should be 'final'

    Participant
    March 11, 2018

    I am having a similar problem in Lightroom Classic version: 7.2 [ 1156743 ]

    except I'm not getting the error stated in this post. I'm just not see metadata I know is there.

    I've posted my issue here:

    Lightroom Classic CC not seeing GPS Location Data

    Tom PDXAuthor
    Participating Frequently
    January 11, 2018

    This appears to be fixed in 7.1.  I used the import settings from disk on one image and it loaded the metadata and preserved the tags.  Other photos in the sequence were corrected as well and I have not encountered the message since.

    Thanks!

    Tom PDXAuthor
    Participating Frequently
    January 7, 2018

    Yes but it backs up all my files and LR is only having problems with some. It appears more likely that LR lost the metadata when it converted the catalog from pre-CC to CC.

    Tom PDXAuthor
    Participating Frequently
    January 6, 2018

    On a local hard drive.

    Just Shoot Me
    Legend
    January 6, 2018

    Do you use any automatic backup software? If you do it could be writing something to the file, that it has been backed up, and that is what LR is seeing.

    Just Shoot Me
    Legend
    January 6, 2018

    First update LR Classic CC to version 7.1.

    Where are your images stored? On a local drive inside your computer, an external drive or on some type of networked drive like a NAS.