[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding To

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Those following this bug will probably want to follow this also: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] v

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

I get the same result as Olivier: about://gpu says "Hardware accelerated", but about://media-internals says FFmpegVideoDecoder. Complete report --- *GPU: 00:02.0 VGA compatible controller: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] (prog-if 00 [VGA controller]) *lsb_re

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Some of us would like to have use_vaapi on Linux arm64 though :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding To manage notification

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

That's correct, use_vaapi is enabled by default on Linux x64 (see https://source.chromium.org/chromium/chromium/src/+/main:media/gpu/args.gni;l=32?q=%22use_vaapi%22). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchp

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Hi again! @Olivier, maybe I'm a bit lost, but don't we need "use_vaapi = true" in the GN arguments? https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/gpu/vaapi.md#vaapi- on-linux I don't see it set here: https://git.launchpad.net/~chromium- team/chromium-browser/+git/snap-from-

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

After rebuilding the chromium snap with the above patch applied to snap/command-chain/desktop-launch, and running it with the following command line: LIBVA_DRIVER_NAME=iHD LIBVA_DRIVERS_PATH=/snap/chromium/x1/usr/lib/x86_64-linux-gnu/dri LIBVA_MESSAGING_LEVEL=2 snap run chromium --enable- feat

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

A small step in the right direction: bug #1947180, and a proposed fix https://github.com/snapcore/snapcraft/pull/3591 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromi

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Ping @osomon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding To manage notifications about this bug go to: https://bugs.launchpad.net/u

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Hi again @osomon, hope you are doing well. Are there any news regarding this? Should the extension be modified? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chr

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

So what are the next steps then @osomon? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding To manage notifications about this bug

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

I am testing this again (this is supposed to work OOTB now, at least on Intel GPUs), and I'm seeing the following: libva info: VA-API version 1.9.0 libva info: User environment variable requested driver 'i965' libva info: Trying to open /snap/chromium/1568/gnome-platform/usr/lib/x86_6

Re: [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Google has not removed API access. They have stopped a google key from working. It works fine, as far as I can tell. But you need to get your own key. The well known PPA with VAAPI, https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev, has always worked like this. I use Fedora on anothe

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Sorry to use this bug report as a forum but IMO it is useless to spend more time on chromium. Ubuntu & users should define a Blink-based open source browser like Brave that could be supported nicely upstream unlike whats google is doing by removing sync API access with google services -- You rec

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Hi Olivier. Sorry to insist, but it's been now 4 months since the last news on this and I think people would like to know if this is still on the roadmap, or if those who want video decoding acceleration should move to Chrome or PPAs. Thanks again! -- You received this bug notification because y

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Hi again Olivier, Now that the 88.x version hit stable, can we expect to have this in place in the foreseeable future? Thanks for your work on this! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/181

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

For once I'll make some noise : It's been months , we are using chromium snap and Vaapi support is still not really there on the stable branch, what's wrong ? Migrating to snap has been painful to some users and the point for canonical was to free some time to polish things , which I totally unde

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Hi Olivier, Is this branch (and thread) dead? From your last comment, it sounds like the VA-API code is getting merged into a more mainline branch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

You're right Marc, the snap currently in the edge channel is missing pieces (specifically building and bundling recent versions of the drivers), I'm still working on merging my changes from the experimental VA-API support branch. -- You received this bug notification because you are a member of U

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Hi Olivier, As per your comment here: https://discourse.ubuntu.com/t/desktop-team- updates-monday-2nd-november-2020/19154/7 I tried this with the latest/edge version of the snap: $ snap info chromium ... tracking: latest/edge refresh-date: today at 10:13 CET channels: latest/stable:86

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Hi Olivier, Have you had a chance to look into why hardware decoding seems to broken now? Thanks, Matt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Most of us have tryed h264ify it dose not help the issue seem to be with the build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding To m

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

If you want to test this, force YouTube to serve H264, which your card supports judging by the vainfo results. A 4k 60fps YouTube video won't be in a codec your hardware can handle, I guess. There are 'h264ify' extensions for Chromium. -- You received this bug notification because you are a membe

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

I also can't get the hardware acceleration on Youtube. With Netflix I do get DecryptingVideoDecoder. Also there is no "Hardware-accelerated video decode" in flags. Chromium snap version 84.0.4147.135 from candidate/vaapi channel. $ vainfo libva info: VA-API version 1.7.0 libva info: Trying to

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

I'm seeing the same problem. Debug information below. LIBVA_MESSAGING_LEVEL=2 snap run chromium [20382:20382:0821/200854.560443:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [20548:13:0821/200904.074169:ERROR:batching_media_log.cc(38)] Media

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

* now not working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding To manage notifications about this bug go to: https://bugs.launchpad.

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Was working last week even with vp9: vainfo output: libva info: VA-API version 1.7.0 libva info: User environment variable requested driver 'iHD' libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_7 libva info: va_openDriver()

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Tested the snap package and it works fine! Running on DELL XPS13 Version 84.0.4147.89 (Official Build) snap (64-bit) + using the h264ify extension in the browser to force Youtube (VP9 by default) to run on h264 $ sudo snap install --channel=candidate/vaapi chromium $ cat /etc/lsb-release DISTR

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

This used to do the trick for me. Since an upgrade to 20.04 the decoding is not working properly. Chromium (86 here) is not calling MojoVideoDecoder. https://www.linuxuprising.com/2018/08/how-to-enable-hardware-accelerated.html That may be related to a switch to the iHD driver (active now accord

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

can I beg the favor of having `rtc_use_pipewire` turned on for your branch? otherwise I'm happy to fork, just let me know :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Correct. I'ts a Polaris chip = UVD6.3 (https://en.wikipedia.org/wiki/Unified_Video_Decoder#UVD_6). no vp9 or av1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium n

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Mojo is the decoder you want for hardware-accelerated video decoding. So you're good with H264. As for VP9 and AV1, I suppose your GPU doesn't support those? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bu

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

VP9 decodes in software with VpxVideoDecoder ``` 00:00:00.294error "{\"causes\":[{\"causes\":[],\"data\":{},\"stack\":[{\"file\":\"../../media/filters/decrypting_video_decoder.cc\",\"line\":53}],\"status_code\":264,\"status_message\":\"\"}],\"data\":{\"Decoder name\":\"DecryptingVideoDeco

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

That's great news Liz! What does chrome://media-internals report as the video decoder when watching H264 videos? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium n

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

although Vulkan is showing as off in chrome://gpu, I _am_ seeing better performance now when switching tabs, watching youtube, and using webgl :) or maybe that's the placebo effect at work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubun

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

from x11 without wayland: ``` LIBVA_MESSAGING_LEVEL=2 snap run chromium Gtk-Message: 12:36:55.257: Failed to load module "canberra-gtk-module" Gtk-Message: 12:36:55.262: Failed to load module "canberra-gtk-module" /usr/share/libdrm/amdgpu.ids: No such file or directory libva info: VA-API version 1

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Aha, it's a detection issue on wayland. passing `LIBVA_DRIVER_NAME=radeonsi` does a trick. ``` LIBVA_DRIVER_NAME=radeonsi LIBVA_MESSAGING_LEVEL=2 snap run chromiumGtk-Message: 12:41:29.046: Failed to load module "canberra-gtk-module" Gtk-Message: 12:41:29.049: Failed to load module "canberra-gtk-

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

``` Gtk-Message: 12:30:13.823: Failed to load module "canberra-gtk-module" Gtk-Message: 12:30:13.826: Failed to load module "canberra-gtk-module" /usr/share/libdrm/amdgpu.ids: No such file or directory libva info: VA-API version 1.7.0 libva error: vaGetDriverNameByIndex() failed with unknown libva

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Thanks for testing and the feedback Liz. The version of mesa-va-drivers in the snap is the one from bionic- updates (20.0.8-0ubuntu1~18.04.1), as confirmed from the build log and by comparing checksums after unpacking the snap. What's the output of `LIBVA_MESSAGING_LEVEL=2 snap run chromium` ? -

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

>From X11 without Wayland: Vulkan still shows as disabled but the init error doesn't turn up. Log Messages [18061:18061:0719/145212.290039:ERROR:sandbox_linux.cc(374)] : InitializeSandbox() called with multiple threads in process gpu-process. [18061:18061:0719/145432.791528:ERROR:shared_image_man

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

The problem also might be that I'm running Chromium inside XWayland rather than natively on X11. I'll try popping over to X11 to see whether it works... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/18

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Can we try pulling in https://packages.ubuntu.com/bionic-updates/mesa- va-drivers instead of the base bionic package pulled right now by the https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source- enable-vaapi build config (which doesn't use Bionic-Updates)? -- You received this bug

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Now we're getting somewhere! chrome://gpu shows: ``` Vulkan: Disabled ... Video Acceleration Information Vulkan Information Device Performance Information Log Messages [4784:4784:0719/142605.755018:ERROR:vaapi_wrapper.cc(511)] : vaInitialize failed: unknown libva error [4784:4784:0719/142605.96757

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap- from-source/commit/?id=ff07991f41f89a21355b6e1c77a4db4393321d47 hopefully fixes it -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/181

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

`stage-packages libdrm-intel1` still fails despite skipping the build steps. Needs a selector to skip it on !amd64/i386. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chr

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Tentative fix to enable building on !amd64: https://git.launchpad.net /~chromium-team/chromium-browser/+git/snap-from- source/commit/?id=d8f8bf958810e0b48a1dd9e480fbe2def7e8f9f1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://b

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

As was pointed out by @jon-nettleton, the intel parts are not required to build, and only are used for intel onboard graphics, which necessarily won't be present on ARM64. Is it possible to make it conditional to build those parts depending upon architecture? https://launchpad.net/~lizthegrey/+sna

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Oddly enough, you do include it in the snap definition as of May 13... ``` build-packages: - gcc - libc6-dev - libdrm-dev - libgl1-mesa-dev - libwayland-dev - libx11-dev - libxext-dev - libxfixes-dev - pkg-config ``` -- You received this

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

@osomon: I see linux-libc-dev is installed in the snap build process but not libc6-dev. I know that normally libc6-dev is included in build- essentials when building .deb files, but is it possible that it isn't in the default set of things for a snap build environment? -- You received this bug no

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

No worries, let me see if @jon-nettleton can have a look. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding To manage notifications about

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Sorry for the lack of feedback Liz. I attempted a build on arm64 and ran into errors (https://code.launchpad.net/~chromium-team/+snap/chromium- snap-from-source-enable-vaapi/+build/995860) when building the intel- gmmlib part. I spent a bit of time trying to figure those out, unsuccessfully. -- Y

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

@osomon: did you build for arm64? should I try again? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding To manage notifications about thi

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

@Michel: can you share the output of "LIBVA_MESSAGING_LEVEL=2 snap run chromium" ? @Liz: that channel is built for amd64 only, I'll attempt an arm64 build. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bug

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

I'm unable to find the channel/branch on arm64. Can you also publish an arm64 snap in that branch? ``` $ sudo snap switch --channel=latest/candidate/vaapi chromium "chromium" switched to the "latest/candidate/vaapi" channel $ sudo snap refresh chromium error: requested a non-existing branch on lat

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Failure report : - distro version : Ubuntu 20.04 - GPU Hardware used : Intel pentium 5000 so HD630 ? - Codec used : VP9 On youtube , H264 on vimeo video is totally scrambled on H264/VP9 or even does not start on vimeo. Netflix and bitmovin DRM test Works great, which means that Widevine does

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

This is now ready for testing again in the candidate/vaapi channel (rebased on the latest stable chromium release, 83.0.4103.97): revision 1191. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 T

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Pietrek: https://git.launchpad.net/~chromium-team/chromium-browser/+git /snap-from-source/commit/?id=77dc6ad516a8f5ce9dbf8306f4d4f8297a1c7654 should do the trick. I'll trigger a rebuild in a moment, if you're still on the candidate/vaapi channel you should be getting a refresh within the next 24 ho

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

** Description changed: News : - - Beta Chromium 80 Snap with vaapi enabled : + - Candidate Chromium 81 Snap with vaapi enabled can be installed with : - https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from- - source-enable- - vaapi/+build/918074/+files/chromium_81.0.4044.113

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Hi, I can't get MojoVideoDecoder to work on an AMD Ryzen laptop. LIBVA_MESSAGING_LEVEL=2 snap run chromium spits: libva info: Trying to open /snap/chromium/1163/usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so libva info: va_openDriver() returns -1 [7926:7926:0603/095431.761821:ERROR:vaapi_wra

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

hw is working now, 4k vp9 youtube video 8 to 15 % cpu usage, without that jumps to 80% -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding

Re: [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Vaapi seems to be working for mpv and Firefox under wayland though. Glad to be of help! :) El mié., 20 de may. de 2020 a la(s) 11:21, Olivier Tilloy ( olivier.til...@canonical.com) escribió: > @Nicolás: thanks, that's very useful feedback. > > @Michel: thanks, that's the problem indeed. > > -- >

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

@Nicolás: thanks, that's very useful feedback. @Michel: thanks, that's the problem indeed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decod

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

@nicolas :that s because of https://bugs.launchpad.net/libva/+bug/1698287 I guess -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding To

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

I just tried in X11. It seems to be working :) Sadly, most videos in YouTube seem to be av1 so it took me a while to get a vp9 video, but that's another issue altogether. Thanks! LIBVA_MESSAGING_LEVEL=2 snap run chromium /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) G

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Yes, I suspect chromium (or at least the vaapi patches we apply) isn't sufficiently wayland-aware. Nicolás, could you test in an X11 session just to let us know whether accelerated HW video decoding works there? That would be a useful data point. -- You received this bug notification because you

Re: [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

It doesn't work here. Intel i5-7200u running Ubuntu 20.04 on wayland. Maybe wayland is the issue? $ LIBVA_MESSAGING_LEVEL=2 snap run chromium /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) Gtk-Message: 10:15:51.783: Failed to load module "appmenu-gtk-module" Gtk-Message:

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

It's working here with an Intel Core i5-7200U CPU (Intel HD 620); "intel-gpu-top" confirms it is. Both VP9 and h264 are accelerated. CPU usage is around 20 to 35% while playing a 1080p video on Youtube (VP9), and a bit higher on Twitch (h264). Though it's way better than with software decoding. $

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Everyone: a new snap is ready for testing in the candidate/vaapi channel (revision 1163): snap refresh chromium --channel=candidate/vaapi Please test and report CPU usage while playing back HD video in the browser (you might want to use the h264ify extension for youtube and the like). Run the

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Thanks Olivier. I'll keep my eye out for that, so I can test -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding To manage notifications ab

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

A note of interest: when testing the snap, use this command line to output more libva debug information: LIBVA_MESSAGING_LEVEL=2 snap run chromium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/181

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

@Matt and others: I'm still working on this. I got chromium to build with the latest libva release, and there's an ongoing build with the latest releases of the corresponding drivers, which in my local tests is working fine. If everything goes well this should be available to test in the candidate/

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

HW acceleration doesn't work for me in the latest build. I noted that Olivier was going to build with a newer version of libva so I went ahead an installed the latest version, as per this guide: https://github.com/intel/media-driver/wiki/How-to-build-and-use-media- driver%3F. Unfortunately that did

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

@osomon If bionic provides only libva-driver-abi-1.1, maybe its time to move chromium snap to core20? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hard

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Still working on this. I had to patch chromium's vaapi code to enable it to build against a custom libva: https://chromium- review.googlesource.com/c/chromium/src/+/2204178. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

@Alain: thanks for the info. That might explain it, indeed. intel-media-va-driver{,non-free} depends on libva-driver-abi-1.7, but libva in bionic only provides up to libva-driver-abi-1.1. I'll look into building the snap with a newer version of libva. -- You received this bug notification becau

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

** Attachment added: "journalctl" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+attachment/5369734/+files/journalctl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Same "libva error" issue here, with an Intel Core i5-7200U CPU (Intel HD 620). I attached the output of running "chromium --enable- logging=stderr", the chromium's journalctl entries (from installation to first and second launch) and vainfo. The iHD VAAPI driver wasn't available until Ubuntu 19.04

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

** Attachment added: "vainfo" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+attachment/5369735/+files/vainfo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title:

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

I am using Ubuntu 20.04. Here is the output of snap info: name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap li

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

@Michel: sorry for the late feedback. On that Pentium N5000 system, could you please include the full output of running "chromium --enable- logging=stderr", and the corresponding journalctl entries, filtered on "chromium"? @Miguel: which OS/version are you running the chromium snap on? Can you ple

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

I have tried the 81.0.4044.113 vaap candidate, but it is showing this warning at startup: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) For reference, this is the output of vainfo: libva info: VA-API version 1.7.0 libva info: Trying to open /usr/lib/x86_64-li

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Test on 20.04 on Pentium N5000 : - Chromium show "unknown libva error" from the start. - VAAPI is not used -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no vide

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

** Description changed: + News : + + - Beta Chromium 80 Snap with vaapi enabled : + + https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from- + source-enable- + vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap + + Install it with --devmode + + + --Original Bug

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Here is my few tests from yesterday : Platform : pentium Kabylake mobile - YouTube VP90 1080p : MojoVideoDecoder - 15% CPU - 8-10W battery - Netflix H264 720p ? ( https://bit.ly/3apopqR) : DecryptingVideoDecoder - 20% CPU - 12-15W battery I'm then looking for info about DecryptingVideoDec

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Thanks for the testing and feedback Matt, much appreciated! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding To manage notifications abo

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Hi Olivier, Many thanks for starting that back up! I have install Chromium from the candidate/vaapi channel and the HW acceleration is working for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/181

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

I have updated the enable-vaapi branch and test snaps are currently building for amd64 and i386 at https://code.launchpad.net/~chromium- team/+snap/chromium-snap-from-source-enable-vaapi. ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Thank you for the recommendation. Brave is now my default browser. First impression is quite good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardwa

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

If anyone doesn't mind, Brave has vaapi support out the box. 1. install gstreamer-vaapi 2. go to brave://flags and enable Override software rendering list, restart browser. 3. go to brave://gpu/ and look at Video Acceleration Information: -- You received this bug notification because you are a

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

It does appear to be abandoned, unfortunately. I had hoped that the official addition of VAAPI support to Firefox would be an alternative but it is dependent on Wayland, which is not currently default supported by Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bu

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

I can also confirm this. Is VAAPI Chromium snap abandoned? It really makes a huge difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware dec

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Can confirm it is still not working. I don't like the idea of using a ppa in software as sensitive as a browser. But also, vaapi acceleration makes a really important deference, specially in a laptop. The snap was a great solution, it is a shame it is not longer working. -- You received this bug

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

The landing page for the build has disappeared: https://code.launchpad.net/~osomon/+snap/chromium-snap-from-source- enable-vaapi so it's possible that your installation has reverted to the main branch again. For what it's worth, there is another working option available that we can try: https://la

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Hi, with Version 74.0.3729.131 the decoder has become FFmpegVideoDecoder once again and does not turn gpu decoder. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromiu

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

I have a slightly newer chipset (Kabylake) so VP9 is supported in my case. Thanks for the suggestion though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no vid

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

@Matt have you tried h264ify extension from the chrome store? It ensures that only h264 videos are loaded. On my Broadwell hardware decoding of VP9 is not supported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpa

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

I wonder if my problem may be related to this error in the chrome://gpu log: - [20257:20257:0414/133034.932196:ERROR:gl_implementation.cc(280)] : Failed to load /snap/chromium/686/usr/lib/chromium-browser/libGLESv2.so: /snap/chromium/686/usr/lib/chromium-browser/libGLESv2.so: cannot open shared ob

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Interesting. Since I'm only getting VpxVideoDecoder decode, I guess I have an installation issue of some kind. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no v

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

As far as i know, Chromium uses a new video decoding backend. If chrome ://media-internals is showing MojoVideoDecoder as VideoDecoder it's using VA-API. Otherwise it falls back to FFMpegVideoDecoder or VPXVideoDecoder. With the latest snap from candidate/vaapi (73.0.3683.86 REV-686) media- intern

[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

Some updates: - I can confirm that 'sudo snap install --channel=candidate/vaapi chromium' installs correctly, as of today, with the same version indicated in the build log. - HW accelerated decode is not available when I apply the '--ignore-gpu-blacklist' flag - HW accelerated encode is availa

  1   2   >