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.

Official Solution

Adobe Administrator

 • 

10.9K Messages

 • 

143.5K Points

5 y ago

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.

13 Messages

 • 

192 Points

No! The problem still remains!
I tried today after updating with whole new pictures but "the file appears to be damaged". 

Adobe Administrator

 • 

16K Messages

 • 

296.7K Points

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.

Sr. Product Manager, Adobe Digital Imaging

13 Messages

 • 

192 Points

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.

13 Messages

 • 

192 Points

... strangely it happend only with 2 out of 12 HDR-Panoramas

Champion

 • 

2.6K Messages

 • 

33.7K Points

Can you put the 9 raws out somewhere on www.dropbox.com and post a public share link, here?

8 Messages

 • 

126 Points

6 y ago

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

7 Messages

 • 

122 Points

Agree. It is not size. I have the same issue with a 6D and creating HDR - Pano's

Adobe Administrator

 • 

16K Messages

 • 

296.7K Points

6 y ago

Thanks. We're investigating this issue. Should be addressed in our next update.

7 Messages

 • 

122 Points

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?

8 Messages

 • 

192 Points

6 y ago

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.

54 Messages

 • 

1K Points

6 y ago

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.

29 Messages

 • 

680 Points

5 y ago

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. 

799 Messages

 • 

11.5K Points

5 y ago

You've had 4 weeks now Jeffrey, on this clearly reproducible issue. Any updates?

Champion

 • 

2.6K Messages

 • 

33.7K Points

5 y ago

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.

8 Messages

 • 

126 Points

5 y ago

It is fixed now in the latest release 2015.5.1 :) Good luck to all

8 Messages

 • 

126 Points

5 y ago

So the latest update 2015.5.1 is out and no fix in it? :(

Adobe Administrator

 • 

16K Messages

 • 

296.7K Points

No. Hoping it will be fixed in the next update.

Sr. Product Manager, Adobe Digital Imaging

13 Messages

 • 

192 Points

5 y ago

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.

13 Messages

 • 

192 Points

I'm actually also merging files from a Tilt/Shift lens on a 5DMkII, same situation as thread opener.

29 Messages

 • 

680 Points

5 y ago

Hoping it will be fixed in the next update.
But knowing it won't be.

54 Messages

 • 

1K Points

5 y ago

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.

29 Messages

 • 

680 Points

It might sound strange, but this is actually a feature of Creative Cloud. Lots more updates, but ones that fail to address the biggest existing bugs whilst also introducing new ones and reducing performance yet further. And the best bit is that there is absolutely nothing any of us can do about it because we are now trapped subscribers.

29 Messages

 • 

680 Points

Yes. This is exactly it. They need to concentrate on performance and stability. 

8 Messages

 • 

126 Points

Yes, obviously there Q&A department is not doing there job!

8 Messages

 • 

268 Points

5 y ago

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....

13 Messages

 • 

192 Points

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.

8 Messages

 • 

126 Points

The error is because LR cant make a normal preview, thats all.

9 Messages

 • 

170 Points

5 y ago

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.