Question 1

How to fix MediaMTX source URL not interpreting regex capture groups like $1?

Accepted Answer

Update MediaMTX to a version that includes PR #5779. In the path configuration, use regex capture groups in the path pattern, and reference them with $1, $2, $3, etc. in the source field. Example configuration:
```yaml
paths:
  ~^mycam/([^/]+)/([^/]+)/(.+)$:
    source: rtsp://$1:$2/$3
```
This enables dynamic RTSP proxying without static per-camera config.

Question 2

How to fix HLS version mismatch error in MediaMTX low latency mode?

Accepted Answer

In MediaMTX 1.18.0 with the lowLatency HLS variant, the master playlist incorrectly uses version 9 while media playlists require version 10, causing strict validators (e.g., Akamai) to reject the stream. This bug is fixed in the gohlslib library (PR #363). Upgrade to a MediaMTX version that includes the fix, or temporarily switch to the standard HLS variant as a workaround.

Question 3

How to stream MPEG-TS over WebTransport with MediaMTX?

Accepted Answer

Use Media-over-QUIC, which is implemented in MediaMTX (PR #5815). It serves as a bridge between any protocol and WebTransport. You can publish an MPEG-TS stream and read it via Media-over-QUIC/WebTransport. Implementing a direct MPEG-TS to WebTransport link is now redundant.

Question 4

How to fix 'invalid user control type: 32' error when streaming RTMP to MediaMTX?

Accepted Answer

This error appears when the RTMP source sends an unknown user control message type 32, which is safe to ignore. It was a known issue in gortmplib (the underlying RTMP library) and is fixed in PR #75. Update MediaMTX to a version that includes this library fix (v1.15.5 or later). No configuration changes are needed.

Question 5

How to fix WebRTC stream not working when PC has no network (airplane mode) in MediaMTX?

Accepted Answer

This is a browser limitation: Chrome and Firefox block RTCPeerConnection when no network interface with an IP address is active. Workaround for Chrome: connect to the stream while a network is available, then disable the network (stream continues). For Firefox, you must have a network interface up with an assigned IP (even without internet access). For example, activate a loopback interface or a dummy virtual adapter with a static IP like 192.168.100.1 before starting the browser. If running locally, using '127.0.0.1' instead of 'localhost' may help. This is not a MediaMTX configuration issue.

mediamtx

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects