-
Notifications
You must be signed in to change notification settings - Fork 2k
Description
Which version are you using?
v1.15.0
Which operating system are you using?
Linux amd64 Docker
Describe the issue
When using WHEP sources, the track gathering timeout is hardcoded to 2 seconds and ignores the webrtcTrackGatherTimeout configuration setting
Describe how to replicate the issue
-
start the MediaMTX with config containing:
...
webrtcTrackGatherTimeout: 5s
...
100:
source: <wheps_source>
sourceOnDemand: yes -
observe that track gather timeout happens after 2 seconds making WHEP sources unreliable
mediamtx-1 | 2025/09/22 18:09:54 DEB [path 100] [WebRTC source] peer connection state: connecting
mediamtx-1 | 2025/09/22 18:09:54 DEB [path 100] [WebRTC source] peer connection state: connected
mediamtx-1 | 2025/09/22 18:09:54 INF [path 100] [WebRTC source] peer connection established, local candidate: host/udp/?.?.?.?/56984, remote candidate: host/udp/?.?.?.?/44446
mediamtx-1 | 2025/09/22 18:09:57 DEB [path 100] [WebRTC source] peer connection state: closed
mediamtx-1 | 2025/09/22 18:09:57 ERR [path 100] [WebRTC source] deadline exceeded while waiting tracks
mediamtx-1 | 2025/09/22 18:10:02 DEB [path 100] [WebRTC source] connecting
mediamtx-1 | 2025/09/22 18:10:02 DEB [path 100] [WebRTC source] peer connection state: connecting
mediamtx-1 | 2025/09/22 18:10:02 DEB [path 100] [WebRTC source] peer connection state: connected
mediamtx-1 | 2025/09/22 18:10:02 INF [path 100] [WebRTC source] peer connection established, local candidate: host/udp/?.?.?.?/57581, remote candidate: host/udp/?.?.?.?/44446
mediamtx-1 | 2025/09/22 18:10:04 DEB [path 100] [WebRTC source] peer connection state: closed
mediamtx-1 | 2025/09/22 18:10:04 ERR [path 100] [WebRTC source] deadline exceeded while waiting tracks
mediamtx-1 | 2025/09/22 18:10:09 DEB [path 100] [WebRTC source] connecting
mediamtx-1 | 2025/09/22 18:10:10 DEB [path 100] [WebRTC source] peer connection state: connecting
mediamtx-1 | 2025/09/22 18:10:10 DEB [path 100] [WebRTC source] peer connection state: connected
mediamtx-1 | 2025/09/22 18:10:10 INF [path 100] [WebRTC source] peer connection established, local candidate: host/udp/?.?.?.?/41536, remote candidate: host/udp/?.?.?.?/44446
mediamtx-1 | 2025/09/22 18:10:12 DEB [path 100] [WebRTC source] peer connection state: closed
mediamtx-1 | 2025/09/22 18:10:12 ERR [path 100] [WebRTC source] deadline exceeded while waiting tracks
mediamtx-1 | 2025/09/22 18:10:17 DEB [path 100] [WebRTC source] connecting
mediamtx-1 | 2025/09/22 18:10:18 DEB [path 100] [WebRTC source] peer connection state: connecting
mediamtx-1 | 2025/09/22 18:10:18 DEB [path 100] [WebRTC source] peer connection state: connected
mediamtx-1 | 2025/09/22 18:10:18 INF [path 100] [WebRTC source] peer connection established, local candidate: host/udp/?.?.?.?/45665, remote candidate: host/udp/?.?.?.?/44446
mediamtx-1 | 2025/09/22 18:10:20 DEB [path 100] [WebRTC source] peer connection state: closed
mediamtx-1 | 2025/09/22 18:10:20 ERR [path 100] [WebRTC source] deadline exceeded while waiting tracks
mediamtx-1 | 2025/09/22 18:10:25 DEB [path 100] [WebRTC source] connecting
mediamtx-1 | 2025/09/22 18:10:26 DEB [path 100] [WebRTC source] peer connection state: connecting
mediamtx-1 | 2025/09/22 18:10:26 DEB [path 100] [WebRTC source] peer connection state: connected
mediamtx-1 | 2025/09/22 18:10:26 INF [path 100] [WebRTC source] peer connection established, local candidate: host/udp/?.?.?.?/38662, remote candidate: host/udp/?.?.?.?/44446
mediamtx-1 | 2025/09/22 18:10:26 INF [path 100] [WebRTC source] ready: 1 track (H264)
MediaMTX configuration
No response
MediaMTX logs
No response
Network dump
No response