• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • Stop struggling with Lightroom! There's no need to spend hours hunting for the answers to your Lightroom Classic questions. All the information you need is in Adobe Lightroom Classic - The Missing FAQ!

    To help you get started, there's a series of easy tutorials to guide you through a simple workflow. As you grow in confidence, the book switches to a conversational FAQ format, so you can quickly find answers to advanced questions. And better still, the eBooks are updated for every release, so it's always up to date.
  • 14 October 2024 It's Lightroom update time again! See What’s New in Lightroom Classic 14.0, Mobile & Desktop (October 2024)? for Feature updates, new cameras and lenses, Tethering changes, and bug fixes.

Import CR2 files show defects in LrC

Status
Not open for further replies.

Rob.H

New Member
Joined
Jan 15, 2019
Messages
12
Lightroom Experience
Advanced
Lightroom Version
Lightroom Version Number
13.3
Operating System
  1. Windows 11
Hi, this is an issue that pursuess me since a long time, several years. Does not depend on the new LrC / Camera RAW version, I've seen it throughout different PC generations since LR 6 or so. Especially some of my older CR2 files taken with EOS 7D show as defective in LrC and PS but do not in windows explorer or Canon Digital Photo Professional (DPP). In Bridge grid view the pics first are shown correctly, the error is added after some seconds. Looks like it is a problem of Camera RAW. I Created dng files from them with Adobe DNG Converter, the defect is transported to the dng's. Sometimes it is really annoying. Any idea what's the reason and how to get over it?
 

Attachments

  • Screenshot 2024-06-12 DPP Grid View.jpg
    Screenshot 2024-06-12 DPP Grid View.jpg
    113 KB · Views: 52
  • Screenshot 2024-06-12 LrC Grid View.jpg
    Screenshot 2024-06-12 LrC Grid View.jpg
    112.4 KB · Views: 51
  • Screenshot 2024-06-12 LrC Grid View2.jpg
    Screenshot 2024-06-12 LrC Grid View2.jpg
    66.9 KB · Views: 44
  • Screenshot 2024-06-12 LrC single pic #4665 dng.jpg
    Screenshot 2024-06-12 LrC single pic #4665 dng.jpg
    114.5 KB · Views: 51
  • Screenshot 2024-06-12 Windows Explorer.jpg
    Screenshot 2024-06-12 Windows Explorer.jpg
    89.4 KB · Views: 51
Solution
What you are seeing is corruption in the RAW data block of the file.
The initial thumbnail is the camera JPEG produced by the camera. After a few seconds LrC will replace that with a thumbnail derived from the RAW data block. If that data block is not delineated properly, the Demosaic conversion to RGB pixels will fail. All other apps only expose the JPEG thumbnails.

Does this happen if you import the CR2 file or when the CR2 file is converted to DNG?
Older files will experience “bit rot” over time on the disk drive. If that is your situation, the only way to recover these files is to resort to one of your system backups.

Sent from my iPad using Tapatalk
What you are seeing is corruption in the RAW data block of the file.
The initial thumbnail is the camera JPEG produced by the camera. After a few seconds LrC will replace that with a thumbnail derived from the RAW data block. If that data block is not delineated properly, the Demosaic conversion to RGB pixels will fail. All other apps only expose the JPEG thumbnails.

Does this happen if you import the CR2 file or when the CR2 file is converted to DNG?
Older files will experience “bit rot” over time on the disk drive. If that is your situation, the only way to recover these files is to resort to one of your system backups.

Sent from my iPad using Tapatalk
 
Solution
Hi Cetus, these pictures have been imported to LrC years ago, maybe at LR 5 times already. Especially a two days series I took with Canon EOS 7D is affected. From time to time some change from a correct view to corrupted. This is independent from what I do, usually happens already when I open the folder in LrC grid view in library. Looks like it's the mentioned "bit rot" or damages from pc crashes from that time.

I was on the wrong way with explorer or Canon DPP, in grid view they obviously show the embedded jpg, in single view they show the corrupted RAW.

I have no backup from 10 years ago so I tried several things and programs if I could save or repair anything. There is another picture viewing and processing program called xnview which was able to create at least non-corrupted TIF 8bit from the CR2 originals (maybe also based on the embedded jpg). I will go on trying.

Since several years I've been running a RAID5 for my RAW's, since two years I'm running RAID6, so I hope It won't go further.

Thanks a lot for your explanation!
 
I have no backup from 10 years ago
The aforementioned "bit-rot" and disk failure are the reasons the you run a system back up app on a schedule. Of course, it goes without mention that periodically you need to check the backup volumes for file integrity.

In addition to TimeMachine that comes free with MacOS, I also use Acronis (which is also available for WindowsOS) creating 3 separate backups (one Acronis, two TimeMachine) of all of my critical data including my image files that go back as far as 2007.
 
The aforementioned "bit-rot" and disk failure are the reasons the you run a system back up app on a schedule. Of course, it goes without mention that periodically you need to check the backup volumes for file integrity.
Any folks want to describe how they check the backup volumes for file integrity, or give recommendations?
 
It can be nasty when an old photo gets corrupted and then gets backed up, and you don't notice it for a year or two (or more). Very few people have backups older than a year or so. My Time Machine backups go back about 9 months (on two 20 TB backup drives). Last year I enabled "Forever Version History" in Backblaze, which isn't cheap ($0.006/GB/month, or an extra $72/TB/year).

LR doesn't have file-integrity checking built-in. The late Rob Cole had a plugin that computed checksums and stored them in the catalog, and you can probably find that archived on Github, but I vaguely recall someone saying it didn't work in newer versions of LR (not sure about that).

One thing I do is periodically delete and rebuild image previews. Re-rendering is very likely to flag corrupted files. I rebuild previews in attempts (only sometimes successful) at working around the spurious "photos modified" bugs with LR publish services.
 
Status
Not open for further replies.
Back
Top