Is there any plan to add WHEP demuxer for playing WebRTC?

[flying1314]

Just see the title.

[winlinvip]

WHIP is a publisher, and FFmpeg WHIP is responsible for pushing RTP packets to a WHIP server. On the other hand, WHEP is a player, with FFmpeg WHEP functioning as a player that retrieves RTP packets from a WHEP server.

Please be aware that as of June 2023, WHEP is still in draft status, having been drafted on March 29, 2023, and is not yet considered a stable protocol.

From a technical perspective, WHIP is relatively straightforward, allowing for the reuse of many existing FFmpeg features such as HTTP, SRTP, and RTP. Although DTLS is more complex, existing libraries like OpenSSL can be utilized. The most intricate aspect involves congestion control algorithms, including NACK, FEC, and GCC.

WHEP requires all the functionalities provided by WHIP, with the most critical and complex aspect being the jitter buffer, a crucial feature in WebRTC players. The jitter buffer is responsible for managing out-of-order packets, sending NACK requests for lost packets, parsing FEC packets, and controlling the maximum timeout for packet waiting.

In summary, supporting WHEP is indeed valuable, but it presents a challenging task. It would be best to concentrate on WHIP implementation first.

[jiajialaixi]

obs 使用libdatachannel 实现whep 与whip 后续会已这种方式实现嘛