Skip to main content
marchyman
marchyman
Participating Frequently
April 19, 2022

P: DNG file is damaged yet it can be processed in other applications

Issue:

Lightroom claims a DNG file is damaged yet it can be processed in other applications.


Provide Lightroom Classic version:
11.3 Release Camera Raw 14.3
Build [202204051513-7a25c809]

Provide OS and version:
macOS Monterey
Version 12.3.1
iMac (Retina 5K, 27-inch, 2019)
Processor 3.6 GHz 8-Core Intel Core i9
Memory 64 GB 2667 MHz DDR4
Startup Disk Macintosh HD
Graphics Radeon Pro 575X 4 GB


Issue:
When attempting to edit a handful of DNG images in my library Lightroom claims:
"The file appears to be unsupported or damaged."
That message appears in a popover on an imbedded preview.

Of interest:

  • Mac finder can process the image.
  • Mac Preview.app can process the image.
  • Affinity Photo can process the image.
  • Exiftool can read the image metadata

 

My workaround is to convert the image to another format using Finder or Preview or Affinity Photo.

Also of interest: Every damaged DNG was created by a Leica  camera and subsequently modified by an older version of Lightroom Classic, specifically Adobe Photoshop Lightroom Classic 9.0 (Macintosh).  Exif data says:
   History Action : saved

   History Instance ID : xmp.iid:375df6ee-7fb1-479c-8be6-e122486b8583
   History When : 2019:11:30 22:16:20-08:00
   History Software Agent : Adobe Photoshop Lightroom Classic 9.0 (Macintosh)
   History Changed : /metadata

 

I can not reproduce damaged files upon demand.  I uploaded an example of a damaged image.  Out of approximately 6,000 DMG images in my library less than 20 are damaged. 

 

Expected result:
Lightroom Classic should be able to edit the image.  At a minimum I should be given the option to attempt to render the image regardless of the report of damage.

 

Actual result:
Lightroom Classic can not edit the image. I must first convert the image to a different format using some other application

このトピックへの返信は締め切られました。

返信数 19

前の返信を表示
Rikk Flohr_Photography
Community Manager
Rikk Flohr_PhotographyCommunity Manager
Community Manager
May 16, 2022

Updating Bug Status

Rikk Flohr: Adobe Photography Org
    G
    garryfuller
    Participating Frequently
    May 16, 2022

    When rolling back did you uninstall current LR first or did you keep current version installed and just install a second copy of LR?

    B
    boris24464888lbxy
    Participant
    May 16, 2022

    Having the exact same issue with my Leica M262 - all started like a week or two ago - I thought it's my camera/SD card but it looks like I'm not the only person with this problem... Hope Adobe can fix this...

    johnrellis
    johnrellis
    Legend
    May 13, 2022

    Someone else finally uploaded sample DNGs from a Leica, and the problem is definitely a bug in LR / Camera Raw:

    https://community.adobe.com/t5/lightroom-classic-discussions/unreadable-files-on-nas/m-p/12941302#M274269 

     

    As a workaround, roll back to LR 11.2.

      D
      Douglas Fry
      Participating Frequently
      May 11, 2022

      An odd thing is happening, we have several 24TB NAS boxes, where we store client DNGs and all has been fine for years.

      We recently had cause to go back to 2016 for a client to retrieve some images but found that 10 or so files in the catalogue were 'unreadable' they had the correct file size etc just cant be opened. LR showed a small thumbnail in the catalogue only.

      Same with Bridge or trying to open in PS, 'cannot read this file type or unsupported file type'
      I was worried so as a last resort I set up a new catalogue in CaptureOne and it built all the previews no problem reported no errors and I could export all files etc..

       

      Why would only LR not show these 'unreadable files? I tried making new catalogues and switching GPU on and off on our M1 macs, no joy.

       

      The files that cant be read are only from one camera (a Leica M240) my other cameras are all fine from any time, but as I say its only Adobe, with this issue.

      Any suggestions?

      https://www.piranhaphotography.com>Douglas Fry<br />https://www.piranhaphotography.com
      D
      dj_paige
      Legend
      May 11, 2022

      The files have been corrupted. More than likely, this is a hard disk malfunction on your NAS. You need to restore the files from their backups.


      What happens in other software is irrelevant, by Adobe's rules these files are corrupted and unusable.

      D
      Douglas Fry
      Participating Frequently
      May 11, 2022

      Thanks for the reply, the corruption shows on all NAS's suddenly and on all the same files, so unlikely to be a disk malfunction. but if I browse images in C1Pro and choose to edit in photoshop, photoshop opens the image correctly at full resoltution. Its weird that one small element of the DNG file goes rogue for Adobe but CaptureOne ignores it and opens all images fine.

       

      We have another backup NAS in a separate office and that shows the same issues too on the same file numbers.

       

      If I export the file as a DNG from C1Pro and open it in Photoshop etc, its fine.

       

      I'll keep an eye on it and see if the number of corruptions increase, otherwise I'll wait till I need files and work on them in C1Pro instead

      https://www.piranhaphotography.com>Douglas Fry<br />https://www.piranhaphotography.com
      O
      Old Man With a Camera
      Participant
      May 5, 2022

      I shoot with a Leica M (Typ 262).  On my last couple of imports of the Leica's native DNG files to Lightroom Classic (11.3.1) I have run into several files not being loaded.  My standard procedire is to first move the files from the SD card to disk with Bridge (14.3) and then Import from the computer disk.  In recent instances I will have one or more DNG files displayed with a "Preview unavailable for this file" message instead of the preview.  These files will not be imported into the catalog, wher I get an Iport Results dialog stating "Some import functions were not performed" along with a window stating "The files appear to be unsupported or damaged" along with a list of the affected files. Interestingly, this seems to happen to only the first few files in the import, as well as the very last file in the series.

      Has anyone else run into this problem?  Is there a solution?  I can see image previews in Windows' files manager, but Photoshop will not open them as being "not the right kind of document."  

       

      I run the Adobe software on  Dell XPS 15 9550; Windows 10 Home, version 21H2, OS Build 19044.1645

        D
        dj_paige
        Legend
        May 5, 2022

        Could be the files are damaged, like the message says. Can you upload one such photo to Dropbox or similar and provide us with the link?

        johnrellis
        johnrellis
        Legend
        May 8, 2022

        There have been a number of recent reports of problems importing Leica DNGs, and it's not clear whether this a bug in LR or simply coincidence that a number of Leica users have bad hardware corrupting some of their files. So dj_paige's suggestion would help identify whether there might be a bug.

        johnrellis
        johnrellis
        Legend
        April 21, 2022

        Here's another report of Leica DNGs with similar problems:

        https://community.adobe.com/t5/lightroom-classic-discussions/some-dng-files-are-nt-compatible-anymore/m-p/12896237

         

        This might have something to do with Leica-generated DNGs. On the other hand, it could be the issue has nothing to do with Leicas per se, but rather that a disproportionate percentage of DNGs cataloged in LR come from Leicas, one of the few cameras to generate DNGs natively. So if someone experiences hardware failure causing DNG file corruption, there's a higher-than-average probability the camera is a Leica.

        marchyman
        marchyman作成者
        Participating Frequently
        April 21, 2022

        Yes.   But...  there's always a but, isn't there 🙂  I have about 6,500 Leica DNG files in my catalog.  Only a handful of them, less than 20, are being reported as damaged.  All of the damaged images were updated by LrC 9.  That could, of course, be pure coincidence.  Also, the Leica generated DNG could have had something incorrect which didn't cause issues until the file was updated by LrC 9.

         

        LrC 9 had no problem opening the files.  LrC 9 had no problem saving metadata to the files.  LrC 11.3 reports the files are damaged.  This leads me to believe either the files were damaged (written incorrectly) by LrC 9 or the files were damaged in some unknown way sometime after LrC 9 updated the DNGs.  In either case Adobe products are giving up on processing the image where at least some other software has no issue.

         

        A
        andreas24134253ee9o
        Participant
        April 21, 2022

        After changing to new Ps and LrC I can´t open some of my DNGs created with one particular camera, others from same camera, from same series work well. The files are declared damaged by both programms but can be easyly be opened with Preview on Mac.

        D
        dj_paige
        Legend
        April 21, 2022

        Many of the non-Adobe programs show you the JPG preview that is embedded in the DNG file. Many times, the JPG preview is undamaged while the DNG is damaged. 

         

        So, almost certainly the DNG is damaged and Lightroom Classic can't use it. You can try transferring the DNG file to your computer from the camera again, to see if that clears up the problem. Also, you can try this transfer with different hardware to see if that makes a difference.

          A
          andreas24134253ee9o
          Participant
          April 21, 2022

          It´s a Leica M Type 240 the DNGs come from. The embaded RAW Converter should handle DNGs from this model. Affinity Photo opens the RAW file while Ps can´t handle it at all.

          TheDigitalDog
          TheDigitalDog
          Inspiring
          April 19, 2022

          Can you re-convert them to DNG either using LR (again) or the DNG converter? 

          Can you open the 'damaged' DNG in Camera Raw? 

          That the DNG was directly from a camera, I have to wonder if that camera isn't following the DNG spec's properly or if it is using a very old version of DNG. In the DNG converter, the most up to date version of the spec is V14, hence converting these using this utility and that setting might be worth looking into. 

          Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"
          marchyman
          marchyman作成者
          Participating Frequently
          April 20, 2022

          Can not re-convert using LrC.  DNG  converter fails, too -- "There was an error parsing the file". 

           

          Didn't try ACR (don't have Ps on this system) but I suspect it will be the same.

           

          Did you miss the part where I mentioned that all of the bad DNG files were not directly from the camere, but last updated use the Save (cmd-S) option in LrC version 9?  I suspect whatever it is that LrC doesn't like today was caused by saving metadata changes using LrC in 2019.  Don't know if the error occurred then or of today's LrC is being overly picky.  I suspect both... LrC 9 did something wrong and the current LrC et al are being extra picky.  exiftool gives a minor warning for the bad files:

           

          Warning                         : [minor] Bad offset for MakerNotes tag 0x0301

          Warning                         : [minor] Error reading value for MakerNotes entry 2

           

          but I don't know that such minor errors are what is causing LrC to not process the files.  Good thing I can convert the files to jpg, heic, tif, etc., using non Adobe apps.

          TheDigitalDog
          TheDigitalDog
          Inspiring
          April 20, 2022

          Not good news; seems these DNGs may really are corrupted based on your reporting. But you can edit, then render (export) JPEGs or TIFFs? 

          Hopefully, you have backups and you really want to check out that your drive isn't wonky and causing this. 

           

          Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"
          契約条件Accessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices