1. Disabled media.ffmpeg.enabled, disabled the Cisco OpenH264 plugin and restarted Nightly: With enhanced-h264ify I confirmed on YouTube that h264 decoding no longer works. 2. With Chromium I shared a [YouTube](https://www.youtube.com/watch?v=jSDWfkmzzV8) tab via https://meet.jit.si. My GPU only supports VP8, not VP9. intel_gpu_top shows 1.51% Video decoding: WebRTC VAAPI works. 3. Disabled media.navigator.mediadatadecoder_vpx_enabled, restarted, re-joined the Jitsi session: VAAPI is not used anymore. 4. Reenabled media.navigator.mediadatadecoder_vpx_enabled, restarted, re-joined the Jitsi session: VAAPI is used again. Yes, bug 1709009 is needed for VP8 VAAPI on stable. At the moment, it is only enabled on Nightly.
Bug 1748862 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
1. Disabled media.ffmpeg.enabled, disabled the Cisco OpenH264 plugin and restarted Nightly: With enhanced-h264ify I confirmed on YouTube that h264 decoding no longer works. 2. With Chromium I shared a [YouTube](https://www.youtube.com/watch?v=jSDWfkmzzV8) tab via https://meet.jit.si. My GPU only supports VP8, not VP9. intel_gpu_top shows 1.51% Video decoding: WebRTC VAAPI works. 3. Disabled media.navigator.mediadatadecoder_vpx_enabled, restarted, re-joined the Jitsi session: VAAPI is not used anymore. 4. Reenabled media.navigator.mediadatadecoder_vpx_enabled, restarted, re-joined the Jitsi session: VAAPI is used again. Yes, bug 1709009 is needed for WebRTC VP8 VAAPI on stable and beta. At the moment, it is only enabled on Nightly.