[vlc-devel] Bounty "Add RTP with FEC": SMPTE 2022-1 receiver in access/rtp
Abdev
abdev222 at proton.me
Tue Oct 27 21:10:41 UTC 2026
Hi,
I would like to work on the "Add RTP with FEC" bounty (SMPTE 2022-1),
starting with the receiver.
What I see in master (6836ae7):
- modules/access/rtp has no FEC support; rtp_dgram_thread() polls the
RTP socket only.
- rtp_dequeue() gives up on a gap max(3 x jitter, 25 ms) after the
first packet past the gap was received, and rtp_decode() then drops
the missing packet as late. A column FEC packet can only be sent once
its whole column is out, i.e. about L x D packets later: ~100 ms for
a 10x10 matrix at 10 Mbit/s.
Proposed approach:
1. A self-contained fec.c (no I/O): takes media and FEC packets,
matches them via SNBase/offset/NA, and XOR-rebuilds a packet when it
is the only loss in its row or column. Unit tests.
2. An opt-in --rtp-fec option: OpenURL() opens port+2 (column) and
port+4 (row) next to the RTP socket, like rtcp-port does, and the
thread polls all three.
3. Recovered packets go back through rtp_queue(), which already orders
packets and drops duplicates. With FEC on, rtp_dequeue() uses a
lower bound derived from the matrix span instead of the fixed 25 ms.
4. The sender in stream_out/rtp.c, as a separate MR.
Interop testing uses FFmpeg's prompeg output as the reference sender,
with induced packet loss.
Questions:
- Is this bounty still open, and is the wiki amount (1200 EUR) still
valid? Does the receiver alone qualify, or are both sides required?
- With SRT and RIST already supported, is 2022-1 FEC still wanted?
- Rémi, as the main author of the RTP input, would you review this, or
should I ask someone else?
Thanks,
Abdev
More information about the vlc-devel
mailing list