You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Investigate supporting SMPTE ST 2022-5 FEC streams #86
The repair stream uses the UDP/FEC protocol and has no format list, so it has no RTP payload type, rtpmap or fmtp.
How sdpoker Handles These Files Today
sdpoker rejects the repair stream's m= line:
Line 11: m=application 30000 UDP/FEC should be of the form 'm=mediaType udpPort RTP/AVP payloadType'
The pattern for the m= line requires RTP/AVP and a payload type. That error makes sdpoker skip all the ST 2110 tests, including those for the source stream.
What Support Would Need
Accept an m= line with the UDP/FEC protocol and no format list, and exclude that stream from the RTP tests (rtpmap, fmtp, payload type matching).
Decide which ST 2110-10 tests apply to a repair stream, for example ts-refclk, mediaclk and source-filter.
Tell repair streams apart from ST 2022-7 duplicate streams, which are currently the only reason sdpoker expects more than one m= line.
Check the RFC 6364 attributes: a=group:FEC-FR, fec-source-flow, fec-repair-flow and repair-window.
Decide which ST 2022-5 and IS-05 constraints to check, such as one source stream with one or two repair streams for each leg.
Add fixtures based on the IS-05 example.
nmos-cpp made the format list optional for UDP/FEC streams when it added this support. See the review discussion in sony/nmos-cpp#505, and sony/nmos-cpp#515, which was merged.
Activity