Highlighted

Wrong timestamp applied to AVCHD (.mts) video on import

New Here ,
Sep 14, 2019

Copy link to clipboard

Copied

When I import photos and videos into Lightroom CC from my Sony A6000, the correct 'captured' time is recorded for photos but the .mts video files (AVCHD format) are 12 hours behind, despite displaying the correct capture time when I view them on the camera itself.

 

e.g. I record a movie at 12:30pm on Saturday. The camera display shows the correct time, but when I import it into Lightroom CC the capture time says 12:30am on Saturday. 

 

I did a bit of research and it seems that Lightroom might be ignoring the video's info file that stores the camera's timezone settings, so it resets it to Sony's default time zone (I'm in New Zealand so it makes sense we'd be in the region of 12 hours ahead). But the articles I read on this were from 2016/2017 so I would have thought there'd be a fix in place. Or is the issue something else? 

Topics

Import and share, Problem or error

Views

150

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Wrong timestamp applied to AVCHD (.mts) video on import

New Here ,
Sep 14, 2019

Copy link to clipboard

Copied

When I import photos and videos into Lightroom CC from my Sony A6000, the correct 'captured' time is recorded for photos but the .mts video files (AVCHD format) are 12 hours behind, despite displaying the correct capture time when I view them on the camera itself.

 

e.g. I record a movie at 12:30pm on Saturday. The camera display shows the correct time, but when I import it into Lightroom CC the capture time says 12:30am on Saturday. 

 

I did a bit of research and it seems that Lightroom might be ignoring the video's info file that stores the camera's timezone settings, so it resets it to Sony's default time zone (I'm in New Zealand so it makes sense we'd be in the region of 12 hours ahead). But the articles I read on this were from 2016/2017 so I would have thought there'd be a fix in place. Or is the issue something else? 

Topics

Import and share, Problem or error

Views

151

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Have something to add?

Join the conversation