Canon 5D Mark III
Canon 17mm TS-E 17mm
.CR2 Raw Files
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%
Another broken update brought to you by Adobe.
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.
"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.
I'd trade one stable high performance release over regular updates with 'new features' if they are the only two options these days.
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....
Then also, the platform has become really slow.
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.
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?