Skip to main content
Adobe Photoshop Family

1 Message

 • 

82 Points

Thu, Feb 14, 2019 2:43 PM

Lightroom CC: Date issue with the new HDR Merge and Panorama merge functionality

Hi,
As I was trying the new HDR Merge functionality in Lightroom CC on Windows 10 (which I love by the way, I had been waiting for it for a while!), I realized that the stacks auto-generated after the merge were moved in my library's timeline.

The problem, I figured, was that all the photos from a specific album were taken while my camera was not set to the right time. I first did a batch update of the date/time on all the photos (pushed by 1 hour) and then proceeded to process the HDRs.

After merging, the 4-photos stack were further down in my library (organized by capture date), so I realized that the HDR generated had a date/time of an hour earlier (the time on the camera originally), while the 3 photos used for the merge remained at the previously corrected time. So, somehow, when merging the HDR, the date/time is set to the camera date/time at capture instead of the corrected time in Lightroom. That is nothing major as I could go and manually correct the time on the HDR file, but it is quite annoying.

To me, it seems that the generated HDR should have the same time as it's "parents", even if it was corrected after import in LR.

Also, while writing this report I figured the issue could happen as well with the Panorama merge, and it does. It's the exact same behavior.

Still, I am very happy with the latest update and hope that new enhancements keep coming!

Thanks!

Responses

7.9K Messages

 • 

114.4K Points

2 years ago

Thank you for the report, Raphaël - we've entered report in our system to fix this issue.

Adobe Photography Products
Quality Engineer: Customer Advocacy

7.9K Messages

 • 

114.4K Points

a year ago

Lightroom Desktop 2.3 was released today and contained a fix for this issue. Please update to 2.3 and verify that you are no longer seeing the issue. Thank you!

Adobe Photography Products
Quality Engineer: Customer Advocacy

2 Messages

 • 

134 Points

a year ago

I have just found this issue - I am up to date with 2.3 BUT its still happening - same reason as above