-
Notifications
You must be signed in to change notification settings - Fork 212
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
Use of UTC for video files #682
Comments
I think the problem lies with the metadata parsing part: The pigallery2/src/backend/model/threading/MetadataLoader.ts Lines 20 to 93 in 3e6bb7b
My guess would be that |
This is what Phil Harvey says: https://exiftool.org/forum/index.php?topic=15052.0 The Quicktime creation date indeed is not using the right timezone. If that field can be made to use UTC, the time will be correct. |
Ahh so its Quicktime specific. Can you send me a file with what I can reproduce? Like do you have the same issue on these files (random Google search): https://file-examples.com/index.php/sample-video-files/sample-mov-files-download/ |
mov_sample_non-UTC.2023-01-01_12-00-00.movmov_sample_UTC.2023-01-01_12-00-00.movmp4_sample_non-UTC.2023-01-01_12-00-00.mp4mp4_sample_UTC.2023-01-01_12-00-00.mp4I've attached four files:
UTC was processed as follows (to show which fields I updated): Non-UTC was processed as follows (to show which fields I updated): Results in my instance:
|
a - mov_sample_non-UTC.2023-01-01_12-00-00 what pigallery2 sees:
Here: pigallery2/src/backend/model/threading/MetadataLoader.ts Lines 20 to 93 in 3e6bb7b
The app uses |
Not sure what the call to action is. Does it mean PG2 should be updated to reflect the timezone? Or to use a different timefield? Up to you of course. Or should I update my date/times differently with Exiftool (I think with UTC is the best way, but I can be flexible). |
I gave it some tought since my last comment.
We can decide how to understand the timezoneless date communing from
ffprobe. I need to check what Date.parse does, but I assume it does in
local time. I think that should be rather in UTC.
If I understand correctly that is basically what is this request about.
The othe approach is to dedust the idea of using exiftool in the background
and outsource the problem:)
The problem with that the last time we tried it was extremely slowly
compared to what we have. See: now
#294
…-- Sorry for being brief, sent from my phone.
On Fri, 4 Aug 2023, 09:52 mcwieger, ***@***.***> wrote:
Not sure what the call to action is.
Does it mean PG2 should be updated to reflect the timezone? Or to use a
different timefield? Up to you of course.
Or should I update my date/times differently with Exiftool (I think with
UTC is the best way, but I can be flexible).
—
Reply to this email directly, view it on GitHub
<#682 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABZKA5VNWFXHE5HQMBOB623XTSS2ZANCNFSM6AAAAAA22OLLXI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I think #710 helps with this issue. Can you check? I rerun my little tests with some better explanation.
Based on this the app reads the best time it can read. At least I do not see any better creation date that it could read. |
Appreciate the follow-up! Not sure what/how to test. Is there a new field you're taking the date from? In that case, which field should I include in my Exiftool command so it also gets the correct UTC date? |
I would recommend not changing the date at all as the app assumes that the
date can be in any timezone and then display it in UTC.
If you change the date and set the timezone to +0000, there is not much the
app can do. It can only show that date as it shown in the previous post.
Yes there is a change where the date is from. Earlier it was only from the
first stream. Now it's checks both the stream and the container.
…-- Sorry for being brief, sent from my phone.
On Thu, 14 Sept 2023, 09:54 mcwieger, ***@***.***> wrote:
Appreciate the follow-up!
Not sure what/how to test. Is there a new field you're taking the date
from? In that case, which field should I include in my Exiftool command so
it also gets the correct UTC date?
—
Reply to this email directly, view it on GitHub
<#682 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABZKA5XYX5RDFVBUF7SZKULX2KZ3TANCNFSM6AAAAAA22OLLXI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I will close this due to inactivity. (a bug cleanup ahead of the next release) Feel free to reopen if you think otherwise. |
I am facing this same issue: I have both photos and videos (mp4) taken with the same device and the sorting provided by PG2 is incorrect in the same way as described above. It seems as if PG2 is mixing date/time from photos (with time zone info) with UTC date/time from videos (interpreting these as local) The only way I found to make the files appear in the correct order is to update the mp4 tags with exiftool without using the QuickTimeUTC=1 flag, but this leave the files with local date/time in those tags where AFAIK they are intended to contain UTC timestamps. (BTW, thanks very much for PiGallery2) |
Video files do not appear to use UTC, but seem to display the GMT timezone value.
I set the following (Quicktime) tags to make sure all possible dates used for videos are correct:
All times are set to 18:53:30 with my timezone. However, date in PiGallery2 shows 16:53:30. Can UTC be implemented for video files as it was done for pictures in #480 and #469?
Environment
Used app version
The text was updated successfully, but these errors were encountered: