I'm testing with empty profiles on both, so they have exactly the same config. package.use: www-client/firefox -jack -libproxy -screencast hwaccel -selinux -sndio -wayland -wifi MOZ_LOG="PlatformDecoderModule:5" firefox-bin 'https://www.youtube.com/watch?v=HmZKgaHa3F': [RDD 982297: MediaSupervisor #1]: D/PlatformDecoderModule FFmpeg decoder supports requested type 'video/avc' [RDD 982297: MediaSupervisor #1]: D/PlatformDecoderModule FFMPEG: FFmpegVideoDecoder::FFmpegVideoDecoder MIME video/avc Codec ID 27 [RDD 982297: MediaPDecoder #1]: D/PlatformDecoderModule FFMPEG: Initialising VA-API FFmpeg decoder [RDD 982297: MediaPDecoder #1]: D/PlatformDecoderModule FFMPEG: Format h264 is accelerated [RDD 982297: MediaPDecoder #1]: D/PlatformDecoderModule FFMPEG: codec h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 MOZ_LOG="PlatformDecoderModule:5" firefox 'https://www.youtube.com/watch?v=HmZKgaHa3F': [RDD 972250: MediaSupervisor #1]: D/PlatformDecoderModule FFmpeg decoder supports requested type 'video/avc' [RDD 972250: MediaSupervisor #1]: D/PlatformDecoderModule FFMPEG: FFmpegVideoDecoder::FFmpegVideoDecoder MIME video/avc Codec ID 27 [RDD 972250: MediaPDecoder #1]: D/PlatformDecoderModule FFMPEG: Initialising FFmpeg decoder [RDD 972250: MediaPDecoder #1]: D/PlatformDecoderModule FFMPEG: codec h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 [RDD 972250: MediaPDecoder #1]: D/PlatformDecoderModule FFMPEG: Set get_buffer2 for customized buffer allocation [h264 @ 0x7f3a50154c00] Requested frame threading with a custom get_buffer2() implementation which is not marked as thread safe. This is not supported anymore, make your callback thread-safe. [h264 @ 0x7f3a5017b300] nal_unit_type: 7(SPS), nal_ref_idc: 3 [h264 @ 0x7f3a5017b300] nal_unit_type: 8(PPS), nal_ref_idc: 3 I'm not sure if I should report this directly to the Mozilla team, since it's working fine with the bin version.
Despite not using Wayland, in order to use hardware decode, I had to set the wayland USE flag for firefox.