-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
recordPath doesn't make any sense #3969
Labels
Comments
I think the problem is the |
aler9
added
bug
Something isn't working
and removed
question
Further information is requested
labels
Dec 20, 2024
aler9
added a commit
that referenced
this issue
Dec 20, 2024
aler9
added a commit
that referenced
this issue
Dec 20, 2024
Thanks for reporting the issue, this is fixed by #4062 |
aler9
added a commit
that referenced
this issue
Dec 20, 2024
aler9
added a commit
that referenced
this issue
Dec 21, 2024
This issue is mentioned in release v1.11.0 🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: