-
-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong time after upload #488
Comments
That's a known problem I'll turn off by default this feature in the next major release. |
I can add that I have the same problem.
The photo was taken with and OffsetTime of +2:00 from UTC Uploading with immich-cli use the correct dates. Would it possible to manage the OffsetTime exif data in immich-go? |
I think it's more complex than that, cause I have other photos for which immich-go uploaded the date correctly. This is the complete exif of the foto downloaded from Amazon: Log was this:
This is its exif data:
Then I've checked the import I've done from the photo backup of my wife's Phone, directly copied to my Synology file with DS Files, so it's basically the original file (not uploaded elsewhere in Amazon).
In Immich I correctly see the date 21:35:10 +2:00 This is its complete exif:
I've compared the exifs with sdiff but the dates look to have similar format to me... Thanks! |
Hi @simulot, I've found the issue for my case and possibily also for @people-rus. It's the filename that tricks immich-go. it seems that if you have a filename with dates/timestamps, immich-go ignores the exif data. Is it possibile? Proofs: Look at this:
This is the output from a immich-go dry-run:
THEN, I realized that one filename has the date in it, so I renamed the file from Amazon with the date to "test.heic" and boom..... no more mistakes:
Hope that helps! Cheers. |
I believe these are the lines that have impactred this "bug", immich-go uses the full path to take the time FIRST!!! immich-go/browser/files/localassets.go Lines 280 to 300 in 7ee54ba
|
This version isn't ready for the prime time. However you can give it a try here: |
This version without specifing too much additional options like the "--capture-date-method " works fine with the filename as a timestamp. The date is correct. I'm experimenting also with the --device-uuid, but the Immich app on my iPhone sees always a Remainder asset to be backed up... I've checked with the API that the asset device uuid is correctly applied in the database tough... but that's for another topic I believe. |
Another alpha version: https://github.com/simulot/immich-go/releases/tag/v0.23.0-alpha2 |
I've uploaded yesterday nearly 27k assets with 1.0.0-alpha1, I got not issues with the timestamps, just for your reference. What's changed in 0.23.0-alpha2? |
When I import a photo saved on my PC, the time zone is lost when loading and because of this the loaded photo has an incorrect time, in my case +3 hours.
I run the server and import on Windows.
I tried different scenarios:
The result is always the same.
Work log:
│ INFO | scanned image file | file=IMG_20240814_090047.jpg time="2024-09-19T09:19.25 MSK"
│ INFO | uploaded | file=IMG_20240814_090047.jpg "capture date"="2024-08-14 09:00:47 +0000 UTC" time="2024-09-19T09:19.26 MSK"
I use 0.22.0 version of immich-go.
exiftool command:
if I upload it through immich Android or web - all right
The text was updated successfully, but these errors were encountered: