Exif date/time isn't parsed correctly about immich

[scrampker]

I'm seeing similar problems on my GrapheneOS phone as well. Seems to impact videos and photos differently. Sometimes tagged with local time zone, other times, UTC. -- but odd, because it's not just the wrong time zone, it can be the wrong day in UTC. IE videos I took last night are saying they're in the future -- for tonight.

[fmartingr]

I see similar issues on my end. In my case I my pictures where saved into iCloud Photos from a DJI Osmo 3, and when the app imported them into Immich the datetime was wrong by 2 hours.

I removed all pictures and tried to import them manually via
the web interface, same result.

Attaching one of the pictures that has that issue.

DJI_20240511164405_0094_D.JPG

[scrampker]

Yeah most of my issues result from my Osmo Pocket 3 as well. My guess is this is because the photos lack GPS data, but it would be nice if it still had accurate time. One thing I considered is that I tend to rename the lrf files to MP4 so I can upload those, and I keep the full size media elsewhere for editing. Perhaps DJI does something weird with the LRF exif.

…

-------- Original Message --------

On 5/12/24 2:31 AM, Felipe Martin wrote: I see similar issues on my end. In my case I my pictures where saved into iCloud Photos from a DJI Osmo 3, and when the app imported them into Immich the datetime was wrong by 2 hours. I removed all pictures and tried to import them manually via the web interface, same result. Attaching one of the pictures that has that issue. [DJI_20240511164405_0094_D.JPG](https://github.com/immich-app/immich/assets/812088/00b825d3-c5c5-433c-9f49-1954bfe2b007) — Reply to this email directly, [view it on GitHub](#9331 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ADS37XGWX2MKMKSP6ADBLC3ZB4ED3AVCNFSM6AAAAABHM2D23KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGEZTONJXGY). You are receiving this because you commented.Message ID: ***@***.***>

[ygaeon]

Anyone from the project that can comment back?

[TekkertheChaot]

Chiming in; same behavior here with older photos shot on a Motorola Moto G (1. Gen), additionaly it dates it far back (photo from 2016, Immich dates it as 2002)
For comparison, Windows Explorer seems to parse the information correctly.
I have my external library bound via a read only share, might this be a cause for the metadata not being processed correctly? (I am aware that manual changes to the metadata to these files cannot be saved, as it has no write access on the source folder)

EDIT: Okay, I just learned that Windows Explorer doesn't always read EXIF data.
In my case, windows explorer read the base file attribute but there ACTUALLY IS a "Created"-Date with an actual 2002-date for some reason (inspected with ExifTool). Hopefully that helps some people further diagnosing their metadata ✌️