SRS only supports H.264 Baseline profile in WebRTC, not High profile

[Tangpriest]

I have been exchanging SDP information between WebRTC and SRS and noticed that the encoding only supports the H.264 Baseline profile. It appears that SRS does not support the High profile for H.264. Can you confirm if this is the case?

[jiang335]

The function SrsRtcConnection::negotiate_publish_capability() is hardcoded to only support the codec 42e01f.

TRANS_BY_GPT4

[xengine-qyt]

Actually, it doesn't make much sense, because even if you push other streams, they can be played. I don't know how WebRTC handles this internally.

[winlinvip]

This is essentially a compatibility issue. WebRTC typically does not support the High profile, but there is an RTP extension defined in an RFC that does support High. This means that some devices may be able to support this extension protocol, while others may not; even if you test and find that higher versions of Chrome support it, it doesn't necessarily mean that other devices will support it.

Generally, the High profile implies higher latency, which is not an issue for streaming media in live broadcasts, but it is a significant problem for WebRTC. This is the fundamental reason why WebRTC does not have good support for the High profile, as it is not the core application scenario for WebRTC.

Therefore, I do not believe that this feature can be effectively utilized in real-world application scenarios, as it would encounter various issues.

TRANS_BY_GPT4