Skip to main content
Inspiring
February 4, 2016

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

  • February 4, 2016
  • 50 replies
  • 1023 views

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.

This topic has been closed for replies.

50 replies

Inspiring
September 19, 2017
me neither, still one year from now and I`m having the same issue!
Participating Frequently
July 12, 2016
I don't understand why this topic still is marked as "solved", it's not!
Participating Frequently
July 12, 2016
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. 
Known Participant
June 22, 2016
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!
Victoria Bampton LR Queen
Community Expert
Community Expert
June 22, 2016
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.
Victoria - The Lightroom Queen
Inspiring
June 22, 2016
Why would they test the fixes? The most important thing is that there are lots of 'fixes' listed under the 'What's New' section for the update. It doesn't matter if they are fixed or not. As long as most people think that they are fixing things. This allows them to avoid actually fixing any of issue and concentrate on some new tool that no-one wants or needs.
Known Participant
June 22, 2016
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?
Danie Bester
Participating Frequently
June 19, 2016
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?
Inspiring
June 16, 2016
This error still seems to be appearing on 2015.6. HDR-Pano.dngs with my GR
Danie Bester
Participating Frequently
June 10, 2016
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.