Skip to main content
Known Participant
May 20, 2019

P: Time Zone changed after Pano Merge

  • May 20, 2019
  • 15 replies
  • 831 views

After a Pano merge of several raw images, the time zone is shifted on the merged dng image so it is different from the original raw (Nikon D850 nef) images in the stack. This results in the stack being moved to a different place in the grid sorted by capture date and it seems at first like the images are lost.

I shoot with UTC time zone in camera (so I don't have to keep changing time zones on travel). I keep that UTC for my catalogues. In the several cases that this problem occurred images were shot in Central Asia (UTC +5) and LR CC pano merge shifted the time by -5 hrs for the merged image as if it were trying to force it to UTC, when it was already set that way, apparently based on the GPS location stored in the image.

Always happens, I believe. This does not happen with a merge done in LR Classic, only in LR CC, apparently.  Version 2.3.

Urgently needs fixing.

This topic has been closed for replies.

15 replies

Rikk Flohr_Photography
Community Manager
Community Manager
July 15, 2019
Thomas, 

The root cause has been discovered in that the photoshop:DateCreated is missing time zone info in your xmp sidecar files. Correct this issue and the merges happen as expected and with the expected time zone.

How are these sidecar files created? 
Rikk Flohr: Adobe Photography Org
Rikk Flohr_Photography
Community Manager
Community Manager
July 10, 2019
Contacted you direct via Email. 
Rikk Flohr: Adobe Photography Org
Known Participant
July 10, 2019
Yes,

I believe it happened with all the panos I made from photos taken with either a Nikon D850 (with an attached di-GPS unit) and with a Z7 connected to an iPhone XsMax via bluetooth and Nikon's SnapBridge app. They are in stacks in the Adobe Cloud. I can share a folder with you. Maybe you can contact me by the email associated with this account and I can give you the link. There are 9 D850 stacks and 13 from the Z7.

They were taken in 2 different time zones and uploaded to the cloud (via an iPad) in probably 2 Central Asian time zones and some in San Francisco and maybe Dubai. My memory is foggy but the incorrect offset  wasn't only -5 hours as stated in the original post but sometimes was other maybe even a +7 (not sure) and might be dependent on the timezone of uploading...
Rikk Flohr_Photography
Community Manager
Community Manager
July 10, 2019
Thomas,

We've been unable to reproduce this in-house. Do you have any sample images you could share with us that exhibit the problem?
Rikk Flohr: Adobe Photography Org
Rikk Flohr_Photography
Community Manager
Community Manager
May 31, 2019
We have a bug logged to investigate this.  Thanks for your report. 
Rikk Flohr: Adobe Photography Org