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
$ TZ=utc ls -l
total 68176
-rw-r--r-- 1 root root 13984850 Nov 21 19:34 mycamera--2024-11-21--19h04.mp4
-rw-r--r-- 1 root root 13977877 Nov 21 20:04 mycamera--2024-11-21--20h04.mp4
-rw-r--r-- 1 root root 13979416 Nov 21 20:34 mycamera--2024-11-21--21h04.mp4
-rw-r--r-- 1 root root 13961680 Nov 21 21:04 mycamera--2024-11-21--22h04.mp4
-rw-r--r-- 1 root root 13892649 Nov 21 21:34 mycamera--2024-11-21--23h04.mp4
The first filename makes sense. Recording started at 19h04 and took 30 minutes, hense the modification date of 19:34. But then the follow up filenames don't make any sense anymore. Especially if you look at the last one. It's like it's from the future 😮
Server logs
No response
Network dump
No response
The text was updated successfully, but these errors were encountered:
Which version are you using?
1.9.3
Which operating system are you using?
Linux amd64 Docker
Describe how to replicate the issue
I'm running the following docker image of MediaMTX in Kubernetes:
bluenviron/mediamtx:1.9.3
The config is set to
But when checking the files being created, I see
The first filename makes sense. Recording started at 19h04 and took 30 minutes, hense the modification date of 19:34. But then the follow up filenames don't make any sense anymore. Especially if you look at the last one. It's like it's from the future 😮
Server logs
No response
Network dump
No response
The text was updated successfully, but these errors were encountered: