VAAPI doesn't actually work on version 75(beta) flatpak
Categories
(Core :: Audio/Video: Playback, defect)
Tracking
()
People
(Reporter: medeirosdez, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
Have vaapi up and running on my up-to-date Fedora 31 system (checked via "vainfo" and VLC);
Install Firefox 75 beta flatpak from official Mozilla source, then run once:
flatpak override --env=GDK_BACKEND=wayland org.mozilla.firefox --user
Make sure "widget.wayland-dmabuf-vaapi.enabled = true", as well as
"layers.acceleration.force-enabled = true"
"gfx.webrender.all = true"
Check about:support to see if WebRender is my compositor, and if Window Protocol is "wayland/drm";
Run Firefox from terminal with the command:
flatpak run --socket=wayland org.mozilla.firefox --MOZ_LOG="PlatformDecoderModule:5"
Try any YouTube video with and without h264ify just to make sure.
Actual results:
VAAPI doesn't actually work with the following output on terminal:
[Child 72: Main Thread]: D/PlatformDecoderModule Sandbox decoder rejects requested type
[Child 72: Main Thread]: D/PlatformDecoderModule Sandbox decoder rejects requested type
[Child 72: Main Thread]: D/PlatformDecoderModule Sandbox decoder rejects requested type
[Child 72: Main Thread]: D/PlatformDecoderModule Sandbox decoder rejects requested type
[Child 72: MediaPlayback #3]: D/PlatformDecoderModule Sandbox decoder rejects requested type
[Child 72: MediaPlayback #3]: D/PlatformDecoderModule Sandbox decoder rejects requested type
[Child 72: MediaPlayback #1]: D/PlatformDecoderModule Sandbox decoder rejects requested type
[Child 72: MediaPlayback #1]: D/PlatformDecoderModule Sandbox decoder rejects requested type
[Child 72: MediaPDecoder #1]: D/PlatformDecoderModule Initialising FFmpeg decoder.
[Child 72: MediaPDecoder #4]: D/PlatformDecoderModule Initialising VA-API FFmpeg decoder
[Child 72: MediaPDecoder #4]: D/PlatformDecoderModule Decoder does not support VAAPI device type
[Child 72: MediaPDecoder #4]: D/PlatformDecoderModule Couldn't find ffmpeg VA-API decoder
[Child 72: MediaPDecoder #4]: D/PlatformDecoderModule Initialising FFmpeg decoder.
[Child 72: MediaPDecoder #1]: D/PlatformDecoderModule FFmpeg init successful.
[Child 72: MediaPDecoder #3]: D/PlatformDecoderModule AudioTrimmer[0x7fb3437ba020] ::operator(): sample[0,23219] no trimming information
[OpenH264] this = 0x0x7fb3515ec800, Info:CWelsDecoder::SetOption():DECODER_OPTION_TRACE_CALLBACK callback = 0x7fb34a740330.
[libopenh264 @ 0x7fb3515eb000] [OpenH264] this = 0x0x7fb3515ec800, Info:CWelsDecoder::init_decoder(), openh264 codec version = 7137401, ParseOnly = 0
[libfdk_aac @ 0x7fb3515e9800] 2 channels - front:2 side:0 back:0 lfe:0 top:0
[Child 72: MediaPDecoder #3]: D/PlatformDecoderModule AudioTrimmer[0x7fb3437ba020] ::HandleDecodedResult: sample[0,23219] (decoded[0,23219] no trimming needed
[libopenh264 @ 0x7fb3515eb000] [OpenH264] this = 0x0x7fb3515ec800, Info:eVideoType: 1
[Child 72: MediaPDecoder #4]: D/PlatformDecoderModule FFmpeg init successful.
[libopenh264 @ 0x7fb3515eb000] [OpenH264] this = 0x0x7fb3515ec800, Info:WelsRequestMem(): memory alloc size = 864 * 480, ref list size = 5
[libopenh264 @ 0x7fb3515eb000] [OpenH264] this = 0x0x7fb3515ec800, Info:SyncPictureResolutionExt(), overall memory usage: 10917343 bytes
[libopenh264 @ 0x7fb3515eb000] [OpenH264] this = 0x0x7fb3515ec800, Info:DecodeFrameConstruction(): will output first frame of new sequence, 864 x 480, crop_left:0, crop_right:5, crop_top:0, crop_bottom:0, ignored error packet:0.
[libopenh264 @ 0x7fb3515eb000] No frame produced
[Child 72: MediaPDecoder #4]: D/PlatformDecoderModule Got one frame output with pts=33366 dts=-9223372036854775808 duration=33367 opaque=-9223372036854775808
[Child 72: MediaPDecoder #1]: D/PlatformDecoderModule AudioTrimmer[0x7fb3437ba020] ::operator(): sample[23219,46439] no trimming information
[libfdk_aac @ 0x7fb3515e9800] 2 channels - front:2 side:0 back:0 lfe:0 top:0
[Child 72: MediaPDecoder #3]: D/PlatformDecoderModule AudioTrimmer[0x7fb3437ba020] ::HandleDecodedResult: sample[23219,46439] (decoded[23219,46438] no trimming needed
Expected results:
VAAPI should be used and CPU usage should be minimal, just like in any other VAAPI software on my laptop, like VLC Player, for example.
System specs:
Intel i3-7020U with Intel HD 620 graphics;
both Mesa 19.2.8 and 20.1 tested with latest Fedora vanilla kernel (5.5.8 and 5.5.9);
Firefox beta flatpak versions 75b3 and 75b5 have been tested;
It seems sandboxed flatpak apps use Mesa 19.3.3 as per Firefox about:support report;
flatpak update and dnf update/upgrade have been run and system is 100% up-to-date
VAAPI works system-wise, so my drivers and related packages have been correctly installed.
|
||
Comment 1•6 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
|
||
Comment 2•6 years ago
|
||
Please use https://nightly.mozilla.org for the moment.
|
Reporter | |
Comment 3•6 years ago
|
||
(In reply to Jan Andre Ikenmeyer [:darkspirit] from comment #2)
Please use https://nightly.mozilla.org for the moment.
*** This bug has been marked as a duplicate of bug 1622425 ***
Thanks for the reply.
I can't seem to find any information on a nightly flatpak version. I'm assuming VAAPI is only enabled on the flatpak version, am I right?
|
||
Comment 4•6 years ago
|
||
I think there is no nightly flatpak version (it was removed with official flatpak beta support).
So you'll have to run nightly from tarball as @darkspirit mentioned or wait until flatpak gets fixed.
|
|
||
Comment 5•6 years ago
•
|
||
(I have no clue about Flatpak.)
It seems experimental:
bug 1278719 comment 22 has unoffical packages.
bug 1441922 comment 59 seems to test one official Beta package.
At the moment, https://nightly.mozilla.org should be used for VAAPI testing as there are still open bugs (bug 1610199).
|
|
||
Updated•6 years ago
|
|
|
Reporter | |
Comment 6•6 years ago
|
||
|
|
Reporter | |
Comment 7•6 years ago
|
||
I have downloaded the tarball and run it natively on my system.
I can confirm VAAPI is working, at least on MESA 20.1.
Watching a 1080p60 YouTube video with h264ify extension enabled, I get:
"Web Content" process %CPU = 97.3 (flatpak beta, VAAPI broken)
"firefox-bin" process %CPU = 12.3 (flatpak beta, VAAPI broken)
"Web Content" process %CPU = 28.2 (tarball, VAAPI working)
"firefox-bin" process %CPU = 20.9 (tarball, VAAPI working)
Thank you guys for the swift response, it is much appreciated.
Description
•