Starting with your original DNGs, using Auto Tone and Auto Align for the HDRs and any of the Projection options worked for the Pano, itself. Is there anything special I need to be doing? These images are different than what you show the error with, initially:
Also, I asked if the HDRs where created in LR CC 2015.6, the pieces before you merge them to a Pano, or are you starting with HDRs that you merged with LR CC 2015.5.1 or earlier, and just doing the Pano in LR CC 2015.6?
Starting with the raw files in 2015.6, then merging to hdr and then to pano, IE from scratch. Did you have no issues when merging to pano.dng? No message appearing after a while? The files you've merged are identical (Ricoh GR dngs) to the one in the original screenshot.
I don't know exactly what you mean by delete Cache, but I purged both cache options in Preferences>File handling. It would be interesting to see if anyone else is having a similar issue.. View the image in the Develop module and the message appears after a couple of seconds
It took about 10 seconds once I switched to Develop and it happened when I resized the side panel which may or may not have had anything to do with it, but it did happen, finally:
What happens if you start with native raw files, not DNGs? And for the photos you uploaded, were the DNGs created by LR 2016.6 or using a prior version?
I too am having this problem. Using 2015.5 when I create a pano from two HDR images the resulting pano is displayed with the "The image appears to be damaged" message. My original files are Sony RAW files from the a7R II.
LR 2015.6 is the current version. Supposedly something regarding this error was fixed between LR 2015.5 and LR 2015.6 but apparently not everything; however, if the error is occurring in a way that prevents you from stitching the panorama then perhaps it would be wise to update to LR 2015.6.
Hi Steve: I did upgrade to 2015.6 and the problem persists. The issue is 100% reproducible. It may only be cosmetic. But I don't know that. If, in fact, my image is damaged then I'd like to see some urgency in Adobe's response.
The quickest way for me to duplicate the issue is to combine three images into an HDR within Lightroom (^H). Then, combine abother 3 images into an HDR. Finally, merge the two HDRs into a panorama using Lightroom (^M). Lightroom displays the final image with large banner across the screen which reads "The image appears to be damaged".
I'm having a very similar issue. When I do a large merge to pano DNG, if I export that then as a TIFF in LR2015.6, then that file crashes my Photoshop. If I convert that DNG in ACR however, no problems. (Also using Sony A7RII)
Thanks for narrowing this down. I can also reproduce the bug in the HDR Pano step. Bug #4166115 for reference. We'll investigate and try to get this resolved ASAP.
Responses
steve_sprengel
Champion
•
2.6K Messages
•
33.7K Points
5 years ago
Can we see the example raws used to make the HDRs? Upload some to www.dropbox.com and post a public link, here.
Have you created the HDRs for the panos with LR CC 2015.6 or were they from before?
0
0
frenchfries
61 Messages
•
694 Points
5 years ago
The HDRpanos which give the errors were indeed created with the latest 2015.6 update.
0
0
steve_sprengel
Champion
•
2.6K Messages
•
33.7K Points
5 years ago
Starting with your original DNGs, using Auto Tone and Auto Align for the HDRs and any of the Projection options worked for the Pano, itself. Is there anything special I need to be doing? These images are different than what you show the error with, initially:
Also, I asked if the HDRs where created in LR CC 2015.6, the pieces before you merge them to a Pano, or are you starting with HDRs that you merged with LR CC 2015.5.1 or earlier, and just doing the Pano in LR CC 2015.6?
7
dave_burbank
5 Messages
•
132 Points
5 years ago
3
0
glen_pearson_7290116
5 Messages
•
120 Points
5 years ago
1
0
chris_castleberry
Employee
•
381 Messages
•
7.6K Points
5 years ago
Thanks for narrowing this down. I can also reproduce the bug in the HDR Pano step. Bug #4166115 for reference. We'll investigate and try to get this resolved ASAP.
Regards,
- Chris
0