[Webkit-unassigned] [Bug 173141] No VP8/VP9 Video Codec Support in WebRTC

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Feb 19 13:14:47 PST 2018


https://bugs.webkit.org/show_bug.cgi?id=173141

--- Comment #20 from Jeremy Noring <jeremy.noring at gmail.com> ---
(In reply to youenn fablet from comment #12)
> 
> If you happen to have all clients of a session with hardware H.264 support,
> VP8 is not the right choice obviously. It would be great for your users if
> your service could also handle that case, which might not be uncommon.
> 
> Also, while I can understand pushing for VP8 software decoding, I haven't
> yet heard about any clear benefit of VP8 encoding if hardware H264 encoding
> is available.

I do not have all clients in a session with hardware H.264 support.  And correct me if I'm wrong, but the "right choice" is dictated by the *mandatory to implement* codecs in the WebRTC standard per https://tools.ietf.org/html/rfc7742, and not by concerns over hardware support.  In other words, no--webkit should not be deciding "the right choice" here because the right choice is either of the MTI codecs in WebRTC.

As it is, if webkit lacks VP8 support, then the features page should be updated to indicate that webkit has partial support of WebRTC.  There is no nice way to say it: Webkit currently is in blatant violation of rfc7742.

Lastly, the benefit is clear to me: if all clients implement these two codecs, then there are no significant interop issues that developers have to work around.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180219/d87f4b0d/attachment.html>


More information about the webkit-unassigned mailing list