You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have files with names in the format YYYY-MM-DD_hh-mm-ss.png and the format seems to be recognized by immich-go, however, regardless of the value I pass in the -time-zone parameter, the 'capture' date is always set to the parsed timestamp in UTC. Setting the timezone globally before calling the script does not have an effect either (e.g. TZ=America/Los_Angeles ./immich-go upload ...)
Took a peek at the code, it looks like UTC is always set as the timezone of the parsed timestamp:
Wondering if the value of -time-zone should instead be passed through to the code parsing the timestamp from the filename and using it (if provided) instead?
The text was updated successfully, but these errors were encountered:
I have files with names in the format YYYY-MM-DD_hh-mm-ss.png and the format seems to be recognized by immich-go, however, regardless of the value I pass in the -time-zone parameter, the 'capture' date is always set to the parsed timestamp in UTC. Setting the timezone globally before calling the script does not have an effect either (e.g.
TZ=America/Los_Angeles ./immich-go upload ...
)Took a peek at the code, it looks like UTC is always set as the timezone of the parsed timestamp:
immich-go/immich/metadata/namesdate.go
Line 41 in 3598281
Wondering if the value of
-time-zone
should instead be passed through to the code parsing the timestamp from the filename and using it (if provided) instead?The text was updated successfully, but these errors were encountered: