Any update? On Thursday, August 8, 2019 at 10:20:00 PM UTC+3 [email protected] wrote:
> LGTM. In the past Microsoft Edge has supported this for H.264 via ORTC and > really helped for conferencing scenarios especially on low end devices with > limited resources. Look forward to this! > > > On Sunday, July 21, 2019 at 7:04:06 AM UTC-7, Harald Alvestrand wrote: >> >> Contact emails >> >> [email protected], [email protected] >> >> Explainer >> >> None - the spec at https://w3c.github.io/webrtc-svc/ is pretty >> self explanatory. >> >> Design doc/Spec >> >> https://w3c.github.io/webrtc-svc/ >> >> >> The WEBRTC WG chairs have been asked about triggering the TAG review >> process. >> >> Summary >> >> Implement Scalable Video Coding (SVC) controls for WebRTC. >> >> >> Motivation >> >> Many video codecs (VP8, VP9, AV1, H264-SVC) have modes that allow an >> encoder to send out video data in such a format that it's possible to strip >> out certain packets from the stream and reconstruct a lower quality video >> stream from the result. This makes providing video at differing qualities >> to multiple destinations for the same video stream easier, which is a Good >> Thing in conferencing scenarios. >> >> This extension allows a standard control surface for picking between >> possible SVC configurations. >> >> Risks >> >> Interoperability and Compatibility >> >> Describe the degree of interoperability and compatibility risk >> <https://sites.google.com/a/chromium.org/dev/blink?pli=1#TOC-Policy-for-shipping-and-removing-web-platform-API-features>. >> >> For a new feature, the main risk is that it fails to become an >> interoperable part of the web platform if other browsers do not implement >> it. For a removal, please review our principles of web compatibility >> <https://docs.google.com/document/d/1RC-pBBvsazYfCNNUSkPqAVpSpNJ96U8trhNkfV0v9fk/edit> >> . >> >> Edge: No signals, spec editor from Microsoft. >> >> Firefox: No signals. >> >> Safari: No signals. >> >> Web / Framework developers: Meetecho developers are positive. >> >> >> Ergonomics >> >> This will be used by people using WebRTC RTCPeerConnection >> >> in videoconferencing scenarios. >> >> Activation >> >> This feature can't be polyfilled. Detecting the feature is easy. >> >> Debuggability >> >> No special considerations. >> >> We should consider showing video configuration in >> chrome://webrtc-internals, but this is not required for shipping. >> >> Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, Chrome OS, Android, and Android WebView)? >> >> Yes. >> >> >> Link to entry on the feature dashboard <https://www.chromestatus.com/> >> >> >> https://www.chromestatus.com/feature/5769626174619648 >> >> >> >> Requesting approval to ship? >> >> No. >> > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/7e40f9dc-223d-4260-a6a2-1880f2d4accfn%40chromium.org.
