Lightroom: "The file appears to be damaged" - Merge To Panorama with large Canon 5Ds files.

  • 7
  • Problem
  • Updated 2 years ago
  • Solved
  • (Edited)
I am attempting to create high resolution HDR Tilt-Shift Panoramas with Lightroom's Merge To HDR and Merge To Panorama functions. I have taken multiple images with a tilt-shift lens on a Canon 5Ds. Each finished photograph would be composed from 15 or 21 separate images. I take 5 or 7 photographs, 1 stop apart, from the center position then 5 or 7 from the shift right position and the same from the shift left position. Each set of 5 or 7 is merged to hdr to create one dng file. This process works fine. The resulting 3 hdr images are then merged to panorama which completes successfully. When I switch to the develop module or open the panorama file in camera raw I get a message stating "The file appears to be damaged". I have reproduced this error on different computers. My Lightroom version is the 2015.4 Release and Camera Raw is v9.4. Both computers are running Windows 10. It seems to me that Lightroom is struggling with the large file sizes coming from the 5Ds. Has anyone else experience this issue.
Photo of JimmieCrow

JimmieCrow

  • 1 Post
  • 0 Reply Likes

Posted 3 years ago

  • 7
Photo of Yavor Ivanov

Yavor Ivanov

  • 7 Posts
  • 0 Reply Likes
I have experienced the same bug but with much smaller files from Nikon D90, so it is not about size. Windows 10x64 Pro Lightroom CC 2015.5
Photo of Danie Bester

Danie Bester

  • 7 Posts
  • 0 Reply Likes
Agree. It is not size. I have the same issue with a 6D and creating HDR - Pano's
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 15462 Posts
  • 2292 Reply Likes
Thanks. We're investigating this issue. Should be addressed in our next update.
(Edited)
Photo of Danie Bester

Danie Bester

  • 7 Posts
  • 0 Reply Likes
Jeffrey, the error message still persist after the latest release 2015.6. I create loads of hdr-panos with tilt-shift lenses as part of my workflow when shooting architecture and large interiors. I absolutely prefer dng format over tiff and would like to stick with my lightroom workflow. Any news on why these annoying errors exist?
Photo of Ron Robertson

Ron Robertson

  • 8 Posts
  • 1 Reply Like
This is happening to me as well. I am using Lightroom 2015.5 with Camera Raw 9.5 For me one example is making a panorama consisting of 14 sets of HDR with 3 images each. The image is able to be edited in the develop module. The image size of my files is about 18 megapixels.
Photo of Nick West

Nick West

  • 45 Posts
  • 11 Reply Likes
I have the same issue.
Canon 5D Mark III 
Canon 17mm TS-E 17mm
.CR2 Raw Files
LR 2015.5
Mac OSX 10.10.5 (3.5GHz i7, 32GB, GTX 780M 4GB)

1) Merge to HDR (3 frames with 5 bracketed exposures)
2) Create Pano (from 3 merged frames)
3) 'The file appears to be damaged'

This doesn't appear to happen if you set 'Boundary Warp' to 100%

Very frustrating.
Another broken update brought to you by Adobe.
(Edited)
Photo of Pedr

Pedr

  • 25 Posts
  • 12 Reply Likes
Same issue merging multiple images from a 5D Mk3 (three or more).
Sigma Art 50
LR v 2015.5

Performance overall and especially for HDR and Pano just getting worse and worse with every release. 
Photo of Carlos Cardona

Carlos Cardona

  • 432 Posts
  • 91 Reply Likes
You've had 4 weeks now Jeffrey, on this clearly reproducible issue. Any updates?
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2672 Posts
  • 347 Reply Likes

If you're asking when the next update will be released, Adobe doesn't usually answer "when" questions and you just have to wait for the update to be released.  They have at least said there'll be a x.5.1 update so we don't have to wait the customary 3 months for the .6 version to have some of the bugs fixed.  Apparently there were quite a few issues so it's taken longer than normal to get the x.x.1 version out.

If you're asking whether Adobe has been able to reproduce the issue so a fix can be included in whatever update they choose to include it in, Jeffery did say they ARE investigating the issue, and this thread is marked with an IN PROGRESS status, so Adobe is working on it by all indications.

It's always possible that the fix requires more work than Adobe feels comfortable with including in a rushed .x.x.1 version, but hopefully not.

(Edited)
Photo of Yavor Ivanov

Yavor Ivanov

  • 7 Posts
  • 0 Reply Likes
So the latest update 2015.5.1 is out and no fix in it? :(
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 15446 Posts
  • 2282 Reply Likes
No. Hoping it will be fixed in the next update.
Photo of Andreas Madl

Andreas Madl

  • 13 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled LIGHTROOM 2015.5.1 - "image appears to be damaged" after stitching HDR Panoramas.

"image appears to be damaged" after putting together a panorama from 3 Hdr's (also created with LR!). Does not appear (sometimes even then) only when using the same tool directly in CameraRAW via PS.
Photo of Andreas Madl

Andreas Madl

  • 13 Posts
  • 0 Reply Likes
I'm actually also merging files from a Tilt/Shift lens on a 5DMkII, same situation as thread opener.
Photo of Pedr

Pedr

  • 25 Posts
  • 12 Reply Likes
Hoping it will be fixed in the next update.
But knowing it won't be.
Photo of Nick West

Nick West

  • 45 Posts
  • 11 Reply Likes
Why does it always feel like every CC update just results in us all having to play 'find what's broken now' as opposed to any actual improvements.. and then the inevitable weeks/months of waiting for a fix (healing brush, liquify tool and now this).

I'd trade one stable high performance release over regular updates with 'new features' if they are the only two options these days.
Photo of Pedr

Pedr

  • 25 Posts
  • 12 Reply Likes
Yes. This is exactly it. They need to concentrate on performance and stability. 
Photo of Yavor Ivanov

Yavor Ivanov

  • 7 Posts
  • 0 Reply Likes
Yes, obviously there Q&A department is not doing there job!
Photo of Erik Pawassar

Erik Pawassar

  • 7 Posts
  • 3 Reply Likes
I am dealing with the exact same issue (using the exact same camera and process).
But it seems that you can just ignore the warning and keep working on the files and successfully export them. So i guess what Lightroom is saying is that the file only APPEARS to be damaged when it actually isn't. Thanks Lightroom for letting me know....
Photo of Andreas Madl

Andreas Madl

  • 13 Posts
  • 0 Reply Likes
True, but it's annoying and I can't tell if there is no error for sure. 

I tried to export the DNG file as DNG file, reimport the new DNG and there is no more error message. Or alternatively stitch the images in CameraRAW.
Photo of Yavor Ivanov

Yavor Ivanov

  • 7 Posts
  • 0 Reply Likes
The error is because LR cant make a normal preview, thats all.
Photo of John Doogan

John Doogan

  • 9 Posts
  • 0 Reply Likes
Same thing has been happening to me for months. Have ignored it as it doesn't stop me working on the files. Annoying though. Mac Pro and Macbook Pro, latest versions of LR CC. Error happens on both systems. No updates have fixed the problem, still getting it today.
Photo of Danie Bester

Danie Bester

  • 7 Posts
  • 0 Reply Likes
I have the same issue - building HDR's and then creating Panoramas shot with any of my Tilt-Shift Lenses and the Canon 6D. After successfully merging the image, Lightroom says "the image appears to be damaged" even though I can edit the image in the Develop module and even successfully export it as a jpeg.

Then also, the platform has become really slow. 
(Edited)
Photo of Dennis G

Dennis G

  • 18 Posts
  • 0 Reply Likes
Same here. Lightroom 2015.5.1, Camera RAW 9.5.1. Created two HDRs and merged to a panorama. Everything working great, just when opening preview/develop I get the "The file appears to be damaged" message. Never seen that before.
Photo of Karen F

Karen F

  • 10 Posts
  • 0 Reply Likes
29 May 2016 - I encountered this problem for the first time today, did a web search and found this forum, noticed that LR had interrupted restart after installing new updates, restarted and problem still there! From the comments above, it would seem the file is fine, so I will proceed as if there was no error!
(Edited)
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5593 Posts
  • 1182 Reply Likes
Official Response
This should now be fixed as of the CC2015.6/6.6 update released today. You can find more details here: http://blogs.adobe.com/lightroomjournal/2016/06/lightroom-cc-2015-6-now-available.html

However, to correct the issue, the images have to be merged again. The bug was with how the resulting DNG was created so HDR and pano DNGs created before the fix, will still show the error.
(Edited)
Photo of Andreas Madl

Andreas Madl

  • 13 Posts
  • 0 Reply Likes
No! The problem still remains!
I tried today after updating with whole new pictures but "the file appears to be damaged". 
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 15462 Posts
  • 2292 Reply Likes
Hi Andreas, did you merge the images from the originals again? The bug was with how the resulting DNG was created so HDR and pano DNGs created before the fix, will still show the error.
Photo of Andreas Madl

Andreas Madl

  • 13 Posts
  • 0 Reply Likes
Yes, I merged 3 new original pictures that I shot TODAY, and before starting LR I updated! So there is no chance I had an old DNG with the error already in it.  
I merged 9 RAW's to 3 DNG's to 1 HDR Panorama and voila there is the error again.
Photo of Andreas Madl

Andreas Madl

  • 13 Posts
  • 0 Reply Likes
... strangely it happend only with 2 out of 12 HDR-Panoramas
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2672 Posts
  • 347 Reply Likes
Can you put the 9 raws out somewhere on www.dropbox.com and post a public share link, here?
Photo of Andreas Madl

Andreas Madl

  • 13 Posts
  • 0 Reply Likes
I just saw the panoramas with the error were only made with 2 DNG's out of 6 RAW's but still the error appears. Here they are:
https://www.dropbox.com/sh/mig8u95ikm8wbzu/AADbxloEFpUS6t0QIjtIufoCa?dl=0
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2672 Posts
  • 347 Reply Likes

I am able to stitch the HDR-Pano using ACR 9.6 on Windows 7 just fine.  I need to get to my better computer with more memory to test in LR.

What are your HDR options?  You cannot have Auto Align enabled because that changes the width and height of the result image to something slightly smaller and slightly different for each HDR DNG, but you need to have the HDR output the same size for each pano source DNG, so Auto Align must be off. 

The only HDR options I have turned on are Ghost:  High and Show Overlay, mainly because of the people and moving cars in the first set.  Both Auto Align and Auto Tone need to be off.

I was able to get both panos to look reasonably correct by using Perspective and Boundary Warp 100%, although I did use Upright - Full to make things completely squared up.

If I get any different (non-working) results in LR I'll report back.  The only non-Adobe-default setting I used for the HDR source CR2s was Chromatic Aberration=On.

Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2672 Posts
  • 347 Reply Likes

LR 5015.6 worked flawlessly.  I cleared my CR cache using LR / Prefs / File Handling, and otherwise the same settings described for ACR, just above.  I started with just the CR2s, ignoring what other files were on dropbox:

(Edited)
Photo of Yavor Ivanov

Yavor Ivanov

  • 7 Posts
  • 0 Reply Likes
"but you need to have the HDR output the same size for each pano source DNG, so Auto Align must be off.  "

Why is that, I used it before and there was no problems!? But now I cant stich my photos...
Photo of Andreas Madl

Andreas Madl

  • 13 Posts
  • 0 Reply Likes
Thanks Steve for your feedback!
I merge HDR as a first step before I do any editing on the pictures. My HDR options are reduce ghost effects ON (or whatever the proper name is, my LR is in german), auto allign ON and auto tone ON. So maybe thats the reason why it doesn't work properly? And to save time I like using the shortcuts (Shift + Ctrl + H / M).
The other files in the dropbox folder are the merged HDR and Pano files with the error just to show you I'm not making this up.
Thanks for quick respond!
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2672 Posts
  • 347 Reply Likes

Have you turned off Auto Align during the HDR step? 

When stitching with ACR, I was getting an error when I had Auto Align still on, where the two HDR DNGs were 3 pixels different in size from each other and more than 10 pixels smaller than the original photos.  The error was that the image was too large to stitch.

The Ghost option is not just off and on, it is a range, and I used the strongest to get rid of the most movement.

Photo of Andreas Madl

Andreas Madl

  • 13 Posts
  • 0 Reply Likes
Yes right, I always use the light ghost option, I had Auto Allign turned on of course. I need these things to work properly, can't understand why it takes endless months to fix this. Obviously I'm not the only one who has still the same problems. 
(Edited)
Photo of Yavor Ivanov

Yavor Ivanov

  • 7 Posts
  • 0 Reply Likes
So if I have deleeted the original RAWs and only have the HDR dngs, I can't stich my panorama now without erors?
Photo of Andreas Madl

Andreas Madl

  • 13 Posts
  • 0 Reply Likes
No, there is a way! Try to export the HDR/Panorama file as a DNG file, reimport the new DNG, error should be gone (worked that way before the last update)! You just lose time in your workflow doing this with every single image.
Or stitch the files in the CameraRAW dialogue in PS.
(Edited)
Photo of Danie Bester

Danie Bester

  • 7 Posts
  • 0 Reply Likes
Downloading LR 2015.6. Unfortunately; the error message still persist when building HDR's and Panoramas. Maybe it will be fixed with the next update, I hope.
Photo of Danie Bester

Danie Bester

  • 7 Posts
  • 0 Reply Likes
Downloading LR 2015.6. Unfortunately; the error message still persist when building HDR's and Panoramas. Maybe it will be fixed with the next update, I hope.
Photo of Frenchfries

Frenchfries

  • 59 Posts
  • 1 Reply Like
This error still seems to be appearing on 2015.6. HDR-Pano.dngs with my GR
Photo of Nick West

Nick West

  • 45 Posts
  • 11 Reply Likes
I am also still having this problem.

So everyone has this issue, Adobe acknowledge it, release an update which claims to fix it yet the problem still exists. This is very reminiscent of the great healing brush fiasco last year when every new update not only failed to rectify the problem but created new ones *cough - liquify tool..*  I lost all faith in that ever being fixed so I've stuck with PS 2014 and removed myself from receiving any updates from that thread due to the appalling communication from Adobe staff.

All I ask is this, Adobe: why not TEST your updates before releasing them, all you had to do was try and stitch some HDR'd files to see that the problem still exists. Why are your paying customers doing this for you?
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4937 Posts
  • 1918 Reply Likes
They do test their fixes, but there can be multiple different causes with similar symptoms. Ever played whack-a-mole?  You fix one thing and another pops up somewhere else.
Photo of Nick West

Nick West

  • 45 Posts
  • 11 Reply Likes
I'm not sure how this could have been missed, we have specified OS, camera bodies, file types and the exact process. All they had to do was repeat this.

And yes we regularly play whack-a-mole every time the 'Update' but is hit on our CC apps!
Photo of Andreas Madl

Andreas Madl

  • 13 Posts
  • 0 Reply Likes
I don't understand why this topic still is marked as "solved", it's not!
Photo of Chico Morais

Chico Morais

  • 1 Post
  • 0 Reply Likes
me neither, still one year from now and I`m having the same issue!