james_crowley_5048355's profile

1 Message

 • 

130 Points

Thu, Feb 4, 2016 8:28 PM

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

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.

7 Messages

 • 

122 Points

5 y ago

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. 

18 Messages

 • 

424 Points

5 y ago

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.

11 Messages

 • 

172 Points

5 y ago

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!

8 Messages

 • 

126 Points

5 y ago

So if I have deleeted the original RAWs and only have the HDR dngs, I can't stich my panorama now without erors?

13 Messages

 • 

192 Points

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.

7 Messages

 • 

122 Points

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.

7 Messages

 • 

122 Points

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.

61 Messages

 • 

694 Points

5 y ago

This error still seems to be appearing on 2015.6. HDR-Pano.dngs with my GR

54 Messages

 • 

1K Points

5 y ago

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?

Champion

 • 

6.7K Messages

 • 

112K Points

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 Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

54 Messages

 • 

1K Points

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!

13 Messages

 • 

192 Points

I don't understand why this topic still is marked as "solved", it's not!

1 Message

 • 

60 Points

me neither, still one year from now and I`m having the same issue!

29 Messages

 • 

680 Points

5 y ago

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.