Comments on: Surviving WebRTC CPU requirements in large group calls https://bloggeek.me/webrtc-cpu-group-calls/ The leading authority on WebRTC Sat, 22 Aug 2020 18:15:36 +0000 hourly 1 By: Marcus Belcher https://bloggeek.me/webrtc-cpu-group-calls/#comment-123023 Sat, 22 Aug 2020 18:15:36 +0000 https://bloggeek.me/?p=72194#comment-123023 In reply to Tinashe James Chinyanga.

Yes/No. To expand on Tsahis answer:

V-Nova sits on top of another codec. If you have a base application with the v-nova codec it will gain its advantages (e.g. decode at 1080p/4K), if not you will decode the base codec at a lower quality e.g. VP8 or H.264 at say 360p.

So a default browser without their codec would still work as that is how their codec has been engineered, but you would not see the optimizations.

If you had control over the users end to end experience such as Electron, iOS, Android, Native desktop (macOS, Windows 10), had a V-Nova license, and appropriately codec binaries, and a dev team which can modify the codecs WebRTC can see it would be a great optimization. The same method applies to all new codecs which are not found as default.

]]>
By: Tsahi Levent-Levi https://bloggeek.me/webrtc-cpu-group-calls/#comment-122613 Thu, 09 Jul 2020 20:52:13 +0000 https://bloggeek.me/?p=72194#comment-122613 In reply to Tinashe James Chinyanga.

This is proprietary technology and codec as far as I understand. You won’t be able to use it in browsers with WebRTC. You might be able to stitch it into WebRTC for native applications by modifying the baseline WebRTC code, but that won’t work for you in browsers.

]]>
By: Tinashe James Chinyanga https://bloggeek.me/webrtc-cpu-group-calls/#comment-122611 Thu, 09 Jul 2020 19:11:31 +0000 https://bloggeek.me/?p=72194#comment-122611 Thank you for the insights. Please advise, is the tech offered by https://www.v-nova.com/v-nova-video-compression-technology/ applicable in a WebRTC based application?

]]>