- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 Nov 2021 03:51:29 +0000
- To: public-webrtc-logs@w3.org
@chcunningham WebRTC has been implemented on devices with codecs only available in hardware (encoders or decoders or both). The workarounds in WebRTC are a bit clumsy (e.g. having to call createOffer() prior to getCapabilities()), and unpredictable (e.g. it is difficult for an application to guarantee access to resources). I suspect this is what is motivating the MC explorations. At the moment it is not a "hair on fire" situation, although at some point if 4K video and hardware-accelerated next generation codecs become widespread, it isn't hard to imagine the issues limiting the ability to implement use cases like AR/VR. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-svc/issues/49#issuecomment-960433649 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 4 November 2021 03:51:31 UTC