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

These are two different features as far as i know. For videoplayback with hardwaredecoding VAAPI videoencoding needs to be supported. For conference tools like google meet chromium needs to support videoencoding and videodecoding with Webrtc. On Windows both functions are implementet. The

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

No, it is not a bug, hardware decoding for video conferencing on google meet only works for very few specific use cases, -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497

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

Indeed, chromim-beta has hardware video acceleration. All videos on youtube are accelerated. But this is not observed in video conferences. Verified in Google Meet. Is this a bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to

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

Thank you, Nathan Teodosio. I installed chromium as described here: https://discourse.ubuntu.com/t/chromium-hardware-accelerated-build-for-intel-based-platforms-available-for-beta-testing/35625?u=d0od That is, like this: To install hardware accelerated Chromium: snap install chromium

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

Hi Peter, thanks, the bug description was not up to date, you need the snap from beta or edge. What is 'snap info chromium' for you? If it doesn't work on those channels, please attach snap run chromium --enable-logging=stderr &> chr.log ** Description changed: To test the snap with VA-API

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

CPU: 12th Gen Intel i5-12400 (12) @ 4.400GHz GPU: Intel Alder Lake-S GT1 [UHD Graphics 730] intel_gpu_top shows 0% Kubuntu 23.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu.

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

With the beta testing release, the hardware decoding is working for several recent Intel GPU architectures (Tigerlake, Aderlake, Raptorlake), so far, we only experienced a problem on Roadwell (Gen8) GPU, the oldest GPU generation we aim to support for this release, we will work to make it working

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

Don't wanna be rude , but don't expect this to work solid one day. I've been asking this to google and canonical for almost 10 years We've worked hours of test and stuff , this is going nowhere. Let's help firefox , time is precious -- You received this bug notification because you are a

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

GPU . Intel® HD Graphics 5500 / Gen8 / Broadwell Chromium : 113.0.5672.24 hwacc/candidate Hardware decoding is not working ! Log: [46128:46128:0511/183800.564351:WARNING:chrome_main_delegate.cc(589)] This is Chrome version 113.0.5672.24 (not a warning)

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

Hardware decode on candidate/hwacc worked out of the box for me, thanks! - VaapiVideoDecoder - Xorg - VERSION="21.1 (Vera)" - Intel Kabylake (Gen9) - Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed

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

** Description changed: To test the snap with VA-API changes, 1. Install the Chromium snap, -    sudo snap install --channel stable/hwacc chromium +    sudo snap install --channel candidate/hwacc chromium 2. Start Chromium,    snap run chromium 3. Open a video, e.g. one

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

- The value for kVideoDecoderName from step 4. Success is typically {Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx,Dav1d}VideoDecoder; FFmpegVideoDecoder - Xorg or Wayland (`echo $WAYLAND_DISPLAY`); xorg - Distro version (`grep VERSION= /etc/os_release`); 22.10 Kinetic - GPU

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

Hey Marc, you can follow https://code.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/+ref/hwacc-dev, -beta and -candidate. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu.

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

Hi again @nteodosio and happy new year! Any progress to report in the last 2 months? Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi

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

> Is there any ETA for finishing the legal review of the inclusion of the non-free driver? I'm afraid not. :( > For these description items: > > - Distro version (`grep VERSION= /etc/os_release`); > - GPU (`lscpu`); > > Do you mean? > > - Distro version (`grep VERSION= /etc/os-release`); > -

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

Unfortunately, no. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in

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

Hardware decode on stable/hwacc worked out of the box for me, thanks! - VDAVideoDecoder - Xorg - VERSION="21 (Vanessa)" - Intel Kabylake (Gen9) - Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to

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

For these description items: - Distro version (`grep VERSION= /etc/os_release`); - GPU (`lscpu`); Do you mean? - Distro version (`grep VERSION= /etc/os-release`); - GPU (`lsgpu`); -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to

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

** Description changed: To test the snap with VA-API changes, 1. Install the Chromium snap, -    sudo snap install --channel beta/hwacc chromium +    sudo snap install --channel stable/hwacc chromium 2. Start Chromium,    snap run chromium 3. Open a video, e.g. one from

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

Hi! From: https://code.launchpad.net/~nteodosio/chromium- browser/+git/chromium-browser/+merge/428038/comments/1137194 Is there any ETA for finishing the legal review of the inclusion of the non-free driver? Thanks! -- You received this bug notification because you are a member of Desktop

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

It's probably better to focus more on Intel until everything is working well enough to close the bug. VAAPI has historically only been reliable on Intel so we risk getting distracted in debugging non-Intel driver issues (which would also be off-topic given this is a Chromium bug). -- You

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

Hi. Can confirm this issue on Ubuntu 22.04 with Mate desktop env in X11 session. No video acceleration is present. When i try to start chromium in terminal i'm getting following output: chromium-browser --use-gl=desktop --enable-features=VaapiVideoDecoder

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

** Description changed: To test the snap with VA-API changes, 1. Install the Chromium snap,    sudo snap install --channel beta/hwacc chromium 2. Start Chromium,    snap run chromium 3. Open a video, e.g. one from https://github.com/chthomos/video-media- samples.

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

Desktop: wayland OS: Kinetic CPU: i5-12600k GPU: Intel Alderlake_s (Gen12) I hit this error: vaapi_wrapper.cc(2389)] vaCreateSurfaces (import mode) After which chromium seems to fall back to ffmpeg. [135904:14:0913/135753.793304:INFO:decoder.cc(41)] DecryptingVideoDecoder

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

** Description changed: To test the snap with VA-API changes, 1. Install the Chromium snap, -    sudo snap install --channel candidate/hwacc chromium +    sudo snap install --channel beta/hwacc chromium 2. Start Chromium, -snap run chromium +    snap run chromium 3.

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

** Tags added: kivu performance -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser

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

My T460P (nvida + intel GPU): snap X11 works. video decoder with hardware acceleration. ubuntu frame with WayLand test: proper display. Only problem is no video hardware decode. (I think it is not the snap problem, the native version is also not support.) It is nearly a perfect build.

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

The snap in the hwacc channel has been updated. Now it automatically detects Wayland or Xorg and sets flags accordingly. ** Description changed: To test the snap with VA-API changes, 1. Install the Chromium snap,    sudo snap install --channel candidate/hwacc chromium - 2. If on

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

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

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

A user reported VDAVideoDecoder in testing this under Wayland, but if he tries to play a Youtube video on fullscreen on 3 4K displays, it stops playing after ~10 s; Unmaximizing it resumes it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed

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

It is, but since that bug targets both Chromium and Firefox, I believe it would be significantly harder to keep track of context of each piece of feedback (unfortunately we don't have threading here), judging by the interactions we have had in this one, both for developers and users. Also, I

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

This appears to be a duplicate of bug 1424201. Can we close this bug? ** Changed in: chromium-browser (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu.

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

The native chromium works. So I did not think it is a ubuntu-frame bug. I test the previous snap chromium version before, and it also works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu.

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

It would be nice if you could run your test on normal Ubuntu Wayland, as it could be a bug in Ubuntu Frame. Especially given https://github.com/MirServer/ubuntu-frame/issues/75, it would be reasonable to disregard your failure report. ** Bug watch added: github.com/MirServer/ubuntu-frame/issues

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

Sorry I did not make clear describe the problem. (I thought the previous version is working, so the current is a small problem.) I am using ubuntu-frame to make Wayland test: https://github.com/MirServer/ubuntu-frame If the ubnutu-frame is started, the Wayland display is ready. So I just used

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

> I already setup WAYLAND_DISPLAY=wayland-99. I setup a wayland display. Hmm, I'm not sure if this is clear: The variable WAYLAND_DISPLAY is set as a consequence of a Wayland session being started. One should not manually set WAYLAND_DISPLAY; that does not start Wayland. > The WAYLAND_DISPLAY

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

I already setup WAYLAND_DISPLAY=wayland-99. I setup a wayland display. I confirmed the native chromium-browser did work with --enable- features=VaapiVideoDecoder --disable- features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland. The WAYLAND_DISPLAY will displayed chromium browser. The

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

I get the exact error you report on #161 if I try the Wayland command (chromium --enable-features=VaapiVideoDecoder --disable- features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland) under Xorg. Please double check you are not under Xorg when trying the Wayland command. -- You received

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

Wait, > chrome://flags/#ozone-platform-hint , not work. 1. What does "not work" mean here? Does Chromium not even launch, or does it start but not hardware accelerated? If the former, does dropping the flags (--enable-features=VaapiVideoDecoder etc.) makes it launch? > I remember in previouse

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

does wayland mode conflict with vaapivdideodecoder feature ? I know in the 22.04 version the default GUI mode is Wayland. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu.

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

I remember in previouse snap it is working, but withtout vaapivideodecoder working. It is another problem, but the wayland is sure working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu.

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

sure, I already enable wayland. chromium --enable-features=VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland [14225:14225:0807/073546.382350:ERROR:wayland_connection.cc(210)] Failed to connect to Wayland display

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

So it works in Xorg (great to hear!) but not in Wayland for you? It seems that you need one additional flag in Wayland, --ozone- platform=wayland. I.e., can you please try chromium --enable-features=VaapiVideoDecoder --disable- features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland

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

https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454 chrome://flags/#ozone-platform-hint , not work. [30855:30855:0806/092525.830999:ERROR:wayland_connection.cc(210)] Failed to connect to Wayland display [30855:30855:0806/092525.831041:ERROR:ozone_platform_wayland.cc(226)]

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

Wao, perfecter build. It is the first time my Nvidia/intel CPU, get a snap chromium support video decoder. I need not manually maintain my native chromium environment. Thanks for your hardwarking. -- You received this bug notification because you are a member of Desktop Packages, which is

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

My apologies, Li, I didn't realize that Snapcraft 7.1.1 had to reach the builder, not the installer machine; as such, your test still suffered the lack of LIBVA_DRIVERS_PATH. I uploaded a rebuilt snap (from hwacc-debug, with vainfo) to candidate/hwacc and made sure that the snapcraft changes made

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

## snap info chromium 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 license: unset description: | An

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

** Changed in: chromium-browser (Ubuntu) Assignee: Olivier Tilloy (osomon) => Nathan Teodosio (nteodosio) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title:

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

If you updated Snapcraft as indicated, at least the LIBVA path should be right, so could you please `snap run --shell chromium` and tell us the output of `env | grep LIBVA` and `vainfo`? And thank you for your perseverance testing this. -- You received this bug notification because you are a

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

My t460p, Nvida, Intel GPU. Insalled with sudo snap install --channel candidate/hwacc chromium LIBVA_MESSAGING_LEVEL=2 chromium --disable-features=UseChromeOSDirectVideoDecoder --enable-features=VaapiVideoDecoder ``` Gtk-Message: 19:02:47.866: Failed to load module "canberra-gtk-module"

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

** Description changed: To test the snap with VA-API changes, 0. If you have Nvidia GPU, you need Snapcraft >=7.1.1. Check `snap info snapcraft`. At the time of writing, -sudo snap refresh --channel 7.x/beta snapcraft +    sudo snap refresh --channel 7.x snapcraft 1. Install

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

Snapcraft 7.1.1 is now on the stable channel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in

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

** Description changed: To test the snap with VA-API changes, - 1. Install the snap with + 0. If you have Nvidia GPU, you need Snapcraft >=7.1.1. Check `snap info + snapcraft`. At the time of writing, + +sudo snap refresh --channel 7.x/beta snapcraft + + 1. Install the Chromium snap,

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

The Nvidia/Intel issue mentioned in #127 has been addressed in Snapcraft 7.1.1 , which is already available in the 7.x/candidate channel. Now I will be working on the merge of the hwacc into latest/{beta,edge}. -- You received this bug

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

@seb128 & @nteodosio: is there any more tests to do? Is there any ETA for this to be released to the latest/* channels? Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu.

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

Is it possible to add chromium-wayland-vaapi driver in the snap. Check whether wayland mode works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi

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

I tried this https://launchpad.net/~nteodosio/+snap/chromium-browser- hwacc/+build/1821034 Good snap package, my old N3450 works. ## Gtk-Message: 17:56:38.503: Failed to load module "canberra-gtk-module" Gtk-Message: 17:56:38.507: Failed to load module "canberra-gtk-module"

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

> It means chromium is bind the old libva 2.6. It is a little strange. Not really. It's just that the vainfo bundled in the snap is from the focal deb which is 2.6 and what it reports as 'libva version' is just its own version. If you wget the vainfo from impish in the snap it will tell libva

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

Thank you for your clear response. It means chromium is bind the old libva 2.6. It is a little strange. Current both my two machines are unable to work with the good snap package. But the native chromium version could. It is a little sad. -- You received this bug notification because you are

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

Li, Vainfo depends on Libva. Since Focal repositories are used, Vainfo gets Libva 2.6, which Vainfo reports. See https://github.com/intel/libva- utils/blob/1c4f53bc72e36385d301ac0aecfbf40d748e4483/vainfo/vainfo.c#L37-L38 and https://github.com/intel/libva-

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

snap run --shell chromium LIBVA_DRIVERS_PATH=/snap/chromium/current/usr/local/lib/x86_64-linux-gnu/dri vainfo libva info: VA-API version 1.14.0 libva info: User environment variable requested driver 'iHD' libva info: Trying to open

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

I make the same test as #139 libva is back for normal usage LIBVA_MESSAGING_LEVEL=2 snap run chromium --enable-features=VaapiVideoDecoder Gtk-Message: 07:25:45.539: Failed to load module "canberra-gtk-module" Gtk-Message: 07:25:45.542: Failed to load module "canberra-gtk-module" libva info:

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

> Use this prefix will solve uncertainty. But it doesn't really make sense in context of the snap since the library and drivers aren't installed under /usr but under /snaps/chromium/current/usr, would that be a better prefix choice? -- You received this bug notification because you are a member

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

>>It shouldn't matter where the libva is built, only where it is installed, which is usr/lib/$ARCH_TRIPLET/. What you said is correct. (I did not make a clear expression.) In post #110 ./autogen.sh --prefix=/usr <<== give the install path so driver will search from this path. I build

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

> This is what I understand that there are two libva in the snap: one is default libva 2.6, anther is libva 2.14 build from path. To me it is a riddle to me why libva 2.6 keeps showing up; libva2=2.7.0-2 is being unstaged, that is clear. I wonder if the dependencies being of older versions (the

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

I still think the libva source build and install is not use the proper default path, so the related app is unable to find driver from /usr/local/, these apps only use /usr/ lib search path. -- You received this bug notification because you are a member of Desktop Packages, which is

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

Try https://launchpad.net/~nteodosio/+snap/chromium-browser- hwacc/+build/1819056 The libva seems not working. run: LIBVA_MESSAGING_LEVEL=2 snap run chromium --enable-features=VaapiVideoDecoder log: Gtk-Message: 07:27:15.926: Failed to load module "canberra-gtk-module" Gtk-Message:

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

The libva 2.6 is not the my native ubunut. As many users reported: Post #135, #134, #130, the libva 2.6 is comes from snap package. It is default apt install libva version. In the snap build, there is libva source build for latest 2.14, but the path is not overridden the default install path.

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

@li, how do you get libva 2.6? that's different from what you posted in #129, what did you change? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi

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

The libva library is the same as me. >>snap: vainfo: VA-API version: 1.14 (libva 2.6.0) The old libva impacted my hardware configeration. It is not correct in fact. I expect the depended libva could be solved so my hardware could use this snap packages. expected： snap: vainfo: VA-API version:

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

I've tested this today and the acceleration works. - kVideoDecoderName: "VDAVideoDecoder" - Distro: Ubuntu 22.04 - GPU: AMD Radeon RX 5600 XT - CPU: AMD Ryzen 5 3600 Also about the libva native: vainfo: VA-API version: 1.14 (libva 2.12.0) [installed libva packages are at version 2.14] snap:

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

I've tested this again with the updated instructions: $ sudo snap refresh --channel candidate/hwacc chromium $ snap run chromium --disable-features=UseChromeOSDirectVideoDecoder --enable-features=VaapiVideoDecoder And it also worked OK. The only thing is that I'm seeing the following warnings

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

Hey Li, yes, the latest build is only for logging, which can be enabled by passing --enable-logging=stderr. Please bear in mind that that build area is mostly a testing ground; not all new builds therein will be relevant, neither will they always be in a clean, refined state. Of course, feel free

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

The latest: https://launchpad.net/~nteodosio/+snap/chromium-browser- hwacc/+build/1814664 From the code, there is only video log parts change, so the result won't change. I run on my T460p, the result is the same. How could I let the video log display? I am sure the T460P and N3450 machine,

[Desktop-packages] [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 Desktop Packages, which is subscribed to chromium-browser in Ubuntu.

[Desktop-packages] [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])

[Desktop-packages] [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 Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware

[Desktop-packages] [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 Desktop Packages, which is subscribed to chromium-browser in

[Desktop-packages] [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-

[Desktop-packages] [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-

[Desktop-packages] [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 Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497

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

Ping @osomon -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu:

[Desktop-packages] [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 Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497

[Desktop-packages] [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 Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in

[Desktop-packages] [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

Re: [Desktop-packages] [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

[Desktop-packages] [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

[Desktop-packages] [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

[Desktop-packages] [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 Desktop Packages, which is subscribed to chromium-browser in Ubuntu.

[Desktop-packages] [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

[Desktop-packages] [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 Desktop Packages, which is subscribed to chromium-browser in Ubuntu.

[Desktop-packages] [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

[Desktop-packages] [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:

[Desktop-packages] [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 Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title:

[Desktop-packages] [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 Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no

[Desktop-packages] [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

[Desktop-packages] [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

[Desktop-packages] [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)]

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

* now not working -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in

[Desktop-packages] [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:

  1   2   >