I'll try to summarize what we know. - Reports so far are on Windows. - Comment 5 reports this even with Chrome as the sender, suggesting a receive-side bug. - `media.navigator.mediadatadecoder_vpx_enabled` controls this. - Both Alex' and Andrew's about:support info indicates they have intel graphics cards that support hw decoding both VP8 and VP9. This narrows down where to look. I have a windows machine with an nvidia card that supports vp9 decoding. I'll see if that is a common factor too.
Bug 1637658 Comment 24 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I'll try to summarize what we know. - Reports so far are on Windows. - Comment 5 reports this even with Chrome as the sender, suggesting a receive-side bug. - `media.navigator.mediadatadecoder_vpx_enabled` controls this, and allows hw decoding of vp8 and vp9 on Windows. - Both Alex' and Andrew's about:support info indicates they have intel graphics cards that support hw decoding both VP8 and VP9. This narrows down where to look. I have a windows machine with an nvidia card that supports vp9 decoding. I'll see if that is a common factor too.