P: Metadata issues with video files on M1 Macs

Providing a couple of sample videos would go a long way towards ensuring a bug report with a recipe that Adobe can easily reproduce.  Upload them to Dropbox, Google Drive, or similar and post the sharing link here.  

Also, by "importing directly from iPhone on M1 Pro Mac", do you mean you've attached the phone to the Mac with a USB cable?

I took the time to jump through all the support hoops with Adobe's support team. They google my issue, point to this thread and say a fix was released. I tell them there are still issues. Of course they doubt me. After multiple days of troubleshooting, they finally are able to verify the issue with the engineering team. At some point the bug might get fixed, though they closed my support ticket so clearly I won't hear about it. @Rikk Flohr: Photography , would love your assistance or comments for those of us following this thread.

BTW: I was the original poster who reported this issue back in Aug 2021. The community migration unlinked the post from my user account. I have seen slight metadata improvements in subsequent releases, but the bulk of the issue remains.

When importing directly from iPhone on M1 Pro Mac...

Standard Videos display the following:

Date Time Original: [blank]

Date Time Digitized: Correct date/time displayed

Date Time: Date the file was imported into Lightroom

GPS: Correct coordinates displayed

Model: Correct model displayed

Videos from Live Photos display the following:

Date Time Original: [blank]

Date Time Digitized: Date/time appears to be off by the amount of my UTC offset

Date Time: Displays the date the file was imported into Lightroom

GPS: [blank]

Model: [blank]

With the new version of Lightroom CC, importing via an Intel Mac is no longer a reliable workaround. On some files it imports correct metadata and others it now exhibits the same issues as the M1 Mac described above. I will gladly provide annotated screen shots or anything else that will help to resolve this issue.

Hi @Rikk Flohr: Photography  Even with the latest version of Lightroom Classic I am still experiencing issues with metadata for videos imported on M1 Macs. What information can I provide to help your team troubleshoot?

"Here's a screenshot of the time difference with .mp4 files coming from a Osmo Action. ... So, for a video i just tested with at 11:15am, ... Classic shows 7:15pm."

This sounds like the longstanding issue with capture dates in Quicktime video:

https://community.adobe.com/t5/lightroom-classic-bugs/p-video-capture-time-shifted-by-time-zone-offset/idc-p/12258901#M3088 

Are you in time zone UTC - 8 (PST)?  Attach a short sample .mp4 here and I can verify.

@Rikk Flohr: Photography Here's a screenshot of the time difference with .mp4 files coming from a Osmo Action. Classic is +5 hours off.
And to make this even more confusing, it appears that MacOS 12.2 is off by +3 hours as well. So, for a video i just tested with at 11:15am, the Finder shows 2:15 pm and Classic shows 7:15pm. And yes, the time is set correctly in the camera.

It also appears now that Classic is unable to sort correctly by Capture Time if file types are not the same. I have a folder of heic, mov, and jpg and when i sort by Capture, the images are not in the correct order, with the jpgs being out of order.

Thanks for the info, @Rikk Flohr: Photography but the issue is still present in v11.2.
Imported video files show an incorrect capture time when compared in the Finder. Previously it was the time when imported into Lr, and now it's just random variations depending on file type. 
And i need to test, but it looks as if Classic may even be re-writting the capture time metadata on imported .heic files. Even though the .heic files are showing the correct time in Lr, the Finder is displaying the time when imported to Classic.

This is a massive mess right now.

Worked for me as well.

thanks a lot!

Andi

Hi @Rikk Flohr: Photography , 
Thank you so much for releasing the fix. It worked!!
I need to remove and reload video files to LR to see Exif data, but it's much better than nothing.
Thanks,
Satoshi