Consider increasing the signaled H264 level
Categories
(Core :: WebRTC: Signaling, task)
Tracking
()
People
(Reporter: pehrsons, Unassigned)
References
(Depends on 1 open bug)
Details
By default all our signaled H264 variants use level 3.1 which allows essentially 1280x720@30fps.
At least on desktop we should have no problem receiving better video than this. (On Android we have no fallback of our own, and both the hw and sw codecs provided by the platform may have resolution limits).
Higher levels and what they allow (ish):
| level | ~max capability |
|---|---|
| 3.2 | 720p@60 |
| 4 | 1080p@30 |
| 4.1 | 1080p@30 (With higher bitrate than level 4) |
| 4.2 | 1080p@60 |
| 5 | 1440p@30 |
| 5.1 | 4k@30 |
| 5.2 | 4k@60 |
| 6 | 8k@30 |
| 6.1 | 8k@60 |
| 6.2 | 8k@120 |
libwebrtc does not support more than 5.2 at the moment.
We should consider increasing the signaled level. If we max out at 5.2 it seems some machines will struggle with this, so that may warrant some machine/perf gate. We have some new codec plumbing for mediaCapabilities that could be used to make this decision. Perhaps it needs to be iterated upon to make the lower layers report more reliable values for smooth. I don't think we want to signal decoder support if decoding is not going to be smooth.
Description
•