Lightroom Classic: Damaging raw files

  • 1
  • Problem
  • Updated 9 months ago
  • Solved
  • (Edited)
I installed Lightroom Classic.  When it first started after upgrading my library it happened to be looking at my flickr pblished photos.  It immediately started re-classifying my published photos to need to be re-published even though nothing was changed.  After some searching I managed to find how to reclassify them as up to date.  Then I decided to import some additional photos.  Lightroom showed the photos as imported but would not release the memory card.  I shut down Lightroom and rebooted to release the card.  When I went back to Lightroom it said the RAW files were corrupted.  Indeed even Windows Preview could not view the files.  In addition there seemed to be performance issues with LR Classic.

After all of this I have uninstalled LR Classic and reverted to LR CC 2015.  Everything is back to normal and I was able to re-import the same RAW files with no problems.  I will wait at least until the first bug fix for Classic before upgrading again.

I have loved Lightroom since the 1.0 beta and have consistently upgraded with each version.  I hesitated to sign up for the subscription model but went with it when the pricing became sensible.  Like many others I am very discouraged and upset to see Adobe changing their emphasis from professional grade software for serious photographers to serving casual photographers who are mainly concerned with posting to social media.  I have over 1TB of photos and with Comcast limiting upload speed to 5 Mbps there is no way the new CC will be practical for serious use until ISPs change bandwidth limitations.  I am also concerned that Adobe rushed to release Classic simply because they wanted to release the new CC.  Classic does not appear to have been properly tested.

Running on Windows 7.
Photo of John Goudey

John Goudey

  • 5 Posts
  • 0 Reply Likes
  • Scared, Anxious

Posted 9 months ago

  • 1
Photo of EP Stern

EP Stern

  • 13 Posts
  • 5 Reply Likes
Here is the solution I came up with John.  I went into my desk top first and completely wiped out everything that has an Adobe name or identifier.  The I went to my Ipad Pro 10.5 and dumped everything that had the Adobe name on it.

Far be it for me tell you what to use, and I won't.  But there are just too many good options out there for anyone to put up with the kind of mind-bending issues you just put up with.  It simply makes no sense to continue to deal with a company that is worth billions and could not care one little rat's ass about their customers or for that matter how much grief their new software entries cause.

But to each their own John.  Good luck with everything because you'll need it if you stick with Adobe. :)
Photo of Alan Harper

Alan Harper

  • 412 Posts
  • 82 Reply Likes
Hi John

I don't want to deny what you experienced, but I think that you misinterpreted what happened.

First, I have never had Lightroom write to a raw file. (There is a setting "Write date or time changes into proprietary raw files" which I leave OFF). If Lightroom is not writing to a raw file, then it is not possible for it to corrupt that file.

Second, if the raw files were in fact corrupt, installing an older version of Lightroom wouldn't fix the problem. The files would remain corrupt.

I don't deny the symptoms you saw, but I truly doubt your diagnosis. Since I have never seen anything like this, and because I use Macintosh, I can't guess what actually caused your problem.

Alan
Photo of Alan Harper

Alan Harper

  • 412 Posts
  • 82 Reply Likes
Ah. I misunderstood. The files were corrupted after being copied to your hard disk . I take back my comment that this couldn't happen. Thanks for the clarification.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1410 Posts
  • 434 Reply Likes
1. Could you reproduce the corruption if you manually copy the files to some folder on the internal drive and import from there? The cable for the memory card could be defective.
2. If the file is still showing damaged, could you upload and share one of the raw image files online somewhere so that we can investigate?
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1410 Posts
  • 434 Reply Likes
What OS this is happening?
Photo of John Goudey

John Goudey

  • 5 Posts
  • 0 Reply Likes
Simon
Thank you for your interest. Unfortunately our internet is currently down. Comcast says it will not be back until late today. I will be away for most of the day tomorrow so I may not be able to respond until Wednesday. The OS is Windows 7 Pro, 64 bit. The reader is built into the computer and still works with the previous version of LR so I think it is okay.
John
Photo of John Goudey

John Goudey

  • 5 Posts
  • 0 Reply Likes
Simon
Here is a link to one of the damaged files.
https://1drv.ms/u/s!ApNbMSM-ZwLZeCBQdN7PqB_HEig
So far I have not had a chance to do more testing.
John
Photo of John Goudey

John Goudey

  • 5 Posts
  • 0 Reply Likes
This problem has been resolved.  I am not sure exactly what fixed it but there have not been any hardware changes or fixes.  I did uninstall LR Classic and also uninstalled and re-installed the Creative Cloud App Manager.  Today I re-installed LR Classic which installed 7.0.1.  Maybe that made the difference.  I hope so since I was never able to install the previous version correctly.  I was able install some version of 6 (6.1?) but could never get back to my previously installed version (6.4?).  The version installers do not seem to work.

You may consider this posting as solved.

Long live LIGHTROOM CLASSIC (or whatever you decide to call it).
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1417 Posts
  • 436 Reply Likes
The _MG_2716.CR2 does appear to be corrupted. I tried to import it in Lr CC 2015.12/Lr Classic CC/ACR, all reported not being able to read the file.