Bug 1748862 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
AFAIK `media.ffmpeg.vaapi.enabled` now enables VA-API for ffmpeg, ffvpx and vpx - keeping ffmpeg in the name is thus somewhat confusing.

Similarly, `media.navigator.mediadatadecoder_vpx_enabled` can be confusing as IIUC it is needed for WebRTC when using VPx codecs, but not h265 (which is provided by ffmpeg and thus `media.ffmpeg.vaapi.enabled` is sufficient to enable it for WebRTC as well). Although I'm not even sure if now that ffvpx also supports VA-API this is still the case.

Lets consider some more self-explanatory names, for example  `media.ffmpeg.vaapi.enabled` ->  `media.vaapi.enabled`
Revision 1 by
on 
AFAIK `media.ffmpeg.vaapi.enabled` now enables VA-API for ffmpeg, ffvpx and vpx - keeping ffmpeg in the name is thus somewhat confusing.

Similarly, `media.navigator.mediadatadecoder_vpx_enabled` can be confusing as IIUC it is needed for WebRTC when using VPx codecs, but not h264 (which is provided by ffmpeg and thus `media.ffmpeg.vaapi.enabled` is sufficient to enable it for WebRTC as well). Although I'm not even sure if now that ffvpx also supports VA-API this is still the case.

Lets consider some more self-explanatory names, for example  `media.ffmpeg.vaapi.enabled` ->  `media.vaapi.enabled`

Back to Bug 1748862 Comment 0