Skip to content
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

Closed
SamDecrock opened this issue Nov 21, 2024 · 3 comments · Fixed by #4062
Closed

recordPath doesn't make any sense #3969

SamDecrock opened this issue Nov 21, 2024 · 3 comments · Fixed by #4062
Labels
bug Something isn't working record playback

Comments

@SamDecrock
Copy link

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

paths:
  all_others:
    record: yes
    recordPath: ./recordings/%Y-%m-%d/%path--%Y-%m-%d--%Hh%M
    recordSegmentDuration: 30m
    recordDeleteAfter: 0s

But when checking the files being created, I see

$ 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

@KosrenDQ
Copy link

KosrenDQ commented Dec 7, 2024

I think the problem is the recordSegmentDurction: 30m configuration. MediaMTX will create segments that are at least 30 minutes long. As the example configuration suggests, try a lower value, such as `1s. '

@aler9 aler9 added question Further information is requested record playback labels Dec 7, 2024
@aler9 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
When a stream contained an Opus, MPEG-4 audio or AC3 track, timespan in
the segment file name was increased at twice the speed.
aler9 added a commit that referenced this issue Dec 20, 2024
When a stream contained an Opus, MPEG-4 audio or AC3 track, timestamp in
the segment file name was increased at twice the speed.
@aler9
Copy link
Member

aler9 commented Dec 20, 2024

Thanks for reporting the issue, this is fixed by #4062

aler9 added a commit that referenced this issue Dec 20, 2024
When a stream contained an Opus, MPEG-4 audio or AC3 track, timestamp in
the segment file name was increasing at twice the speed.
aler9 added a commit that referenced this issue Dec 21, 2024
When a stream contained an Opus, MPEG-4 audio or AC3 track, timestamp in
the segment file name was increasing at twice the speed.
Copy link
Contributor

github-actions bot commented Jan 3, 2025

This issue is mentioned in release v1.11.0 🚀
Check out the entire changelog by clicking here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working record playback
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants