- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Wed, 11 Jul 2018 08:48:43 +0200
- To: public-webrtc@w3.org
Den 11. juli 2018 02:26, skrev Iñaki Baz Castillo: > On Tue, 10 Jul 2018 at 22:30, Bernard Aboba <Bernard.Aboba@microsoft.com> wrote: >> [BA] There are other disadvantages as well: >> >> >> b. Inability to vary the spatial scaling to the same extent as is possible for simulcast today. This could prevent spatial scalability (supported in VP9 and AV1) from substituting for spatial simulcast in some applications. >> >> >> c. Inability to support more sophisticated robustness schemes in the future. The original design of RTCRtpRtxParameters and RTCRtpFecParameters (since removed from WebRTC 1.0) provided support for differential protection (e.g. applying RTX or FEC only to the base layer). > > > The problem of having each SVC layer defined in a > RTCRtpEncodingParameters entry (within encodings array) is that all > those entries belonging to the same stream must share LOT of fields > (such as pt, ssrc, etc). Super error prune IMHO. > RTCRtpEncodingParameters doesn't contain either pt or ssrc. Perhaps it should have for the simulcast case (didn't we have an issue on that?), but at present it doesn't. These would be read-only, I think, so the only source of error is the browser, not the user's app.
Received on Wednesday, 11 July 2018 06:49:12 UTC