Re:On the Road to WebRTC 1.0, Including VP8
by ksec on Tuesday March 12, 2019 @03:31PM
(#19372039)
Under what situation is H.264 not available in WebRTC and require the use of VP8?
[ Parent
| on HN ]
Re:On the Road to WebRTC 1.0, Including VP8
by rhn_mk1 on Tuesday March 12, 2019 @03:41PM
(#19372127)
Free software. The Cisco H.264 codec supplied with Firefox cannot be distributed with other software, despite being "open". From https://www.openh264.org/ , there seem to be licensing costs involved with the usage of this code, which have been waived for some uses, implying they were not waived for others:
> We will not pass on our MPEG-LA licensing costs for this module, and based on the current licensing environment, this will effectively make H.264 free for use on supported platforms.
EDIT: To clarify, such licensing requirements on H.264 may make codecs fall outside of the guidelines of software distributions allowing only free software, making them supply their browser without one.
Re:On the Road to WebRTC 1.0, Including VP8
by detaro on Tuesday March 12, 2019 @03:45PM
(#19372170)
If I remember correctly, only decoding for online video streaming doesn't require licensing fees. Cisco hits the fee cap with the products they sell already, so letting everyone use their binaries doesn't cost them anything.
Re:On the Road to WebRTC 1.0, Including VP8
by TingPing on Tuesday March 12, 2019 @06:35PM
(#19373794)
Right the core problem is you have to use their binaries so Mozilla can't build it and ship their own.
Re:On the Road to WebRTC 1.0, Including VP8
by kodablah on Tuesday March 12, 2019 @04:45PM
(#19372830)
Also includes lots of people w/ custom Chromium-based browsers that don't ship with these codecs (and libs like CEF don't compile with them enabled by default).
Many RTC stacks (and specifically openh264) also only support H.264 baseline profile. So you are likely to get higher quality with VP8 (subject to variations in the quality of the implementations on each endpoint, of course).
Some services use WebRTC in a "hub and spoke" model rather than true peer-to-peer, and they often require VP8 due to a desire to support low-end Android devices that don't have hardware H.264 decoding.