MediaMTX regression breaks AV1 RTMP-to-RTSP ingestion since version 1.16.0
A regression in MediaMTX v1.16.0 causes AV1 video ingested over RTMP to become undecodable when delivered via RTSP, while HLS delivery remains unaffected. The issue, linked to code changes in the internal codec processor, has been verified across multiple subsequent versions using FFmpeg and other publishers.
Key Takeaways
- The regression specifically breaks RTSP output for AV1 streams, resulting in zero decoded frames and "forbidden bit" errors in FFmpeg.
- Bisection identifies the breaking change in v1.16.0, which removed the dedicated 'internal/codecprocessor/av1.go' package in favor of a generic filtering process.
- HLS delivery from the same RTMP ingest remains fully functional, confirming the bug is isolated to RTP packet construction rather than internal decoding.
- The issue persists regardless of fragmentation size or bitrates, and has been verified with both FFmpeg and independent Android-based RTMP publishers.
Why It Matters
This bug disrupts the critical protocol-bridging utility of MediaMTX for the industry's rapidly growing AV1 pipelines. As major distributors increasingly adopt AV1 to reduce bandwidth costs by 30-50%, regressions in open-source media routers force technical teams back to legacy H.264 or specialized HLS-only workflows. For engineers building low-latency security or broadcast stacks, this failure breaks the interoperability between RTMP ingestion and legacy RTSP monitoring tools. Watch for a patch in the v1.20 tree or a revert of the unified codec filtering logic introduced in PR #5324.
Additional Context
The regression arrives as the streaming industry faces a major transition toward AV1. Per reports from Meta in June 2026, the codec is now the primary standard for real-time communication on WhatsApp and Messenger, where it has reduced bitrate requirements by 20% compared to H.264. Netflix and YouTube have also scaled their AV1 deployments significantly, with Netflix reporting in late 2025 that 30% of its total streaming hours are served via AV1. This widespread adoption is supported by a massive expansion in hardware decode availability; per 2026 industry tracking, 88% of large-screen devices certified since 2021 now include native AV1 hardware support.
Simultaneously, the development of open-source tooling is accelerating to keep pace with these corporate deployments. FFmpeg released version 8.0 "Huffman" in August 2025, introducing major infrastructure upgrades including Vulkan compute-based AV1 encoding and the 'Whip' muxer for ultra-low latency WebRTC ingestion. These updates allow platforms like Twitch to roll out enhanced broadcasting at 1080p60 while maintaining high visual quality. MediaMTX (formerly rtsp-simple-server) has positioned itself as a critical 'media router' in this ecosystem, providing the logic to bridge these evolving standards. However, as noted by developers on GitHub in mid-2026, the complexity of managing multiple concurrent protocols like RTMP, RTSP, and the newer Media-over-QUIC often leads to edge-case regressions when internal processing logic is refactored for performance.
Read full article at github.com
Enjoy our coverage?
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source