Comment 112 for bug 1816497

Revision history for this message
li (minye) wrote : Re: [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

I remember 2022/07/01 two builds I both used. The result is the same.

After I back home, I try to give you the exact information. (With 6 hours)

Lee

On Mon, Jul 4, 2022 at 4:01 PM Sebastien Bacher <email address hidden>
wrote:

> @li, which snap are you trying exactly? using the newest build on
> https://launchpad.net/~nteodosio/+snap/chromium-browser-hwacc/ with the
> flag you are using gives me
>
> libva info: Trying to open
> /snap/chromium/x3/usr/lib/x86_64-linux-gnu/dri//iHD_drv_video.so
> libva info: Found init function __vaDriverInit_1_14
> libva info: va_openDriver() returns 0
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1816497
>
> Title:
> [snap] vaapi chromium no video hardware decoding
>
> Status in chromium-browser package in Ubuntu:
> In Progress
>
> Bug description:
> NEWS:
>
> 1. Download the most recent successful build from
> https://launchpad.net/~nteodosio/+snap/chromium-browser-hwacc
>
> For this you must click the desired build link. In the page that
> loads, download the snap from the "Built files" section.
>
> 2. Install with
>
> sudo snap install --dangerous [downloaded-snap-path]
>
> 3. Open a video, e.g. one from https://github.com/chthomos/video-
> media-samples
>
> 4. Enter about:media-internals in the address bar and note what the
> page says for kVideoDecoderName.
>
> Please report
>
> - The video used for testing, including codec and resolution if possible;
> - The value for kVideoDecoderName from step 4 (success is typically
> {Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg, Vpx}VideoDecoder);
> - Distro version (if in doubt, `grep VERSION= /etc/os_release`);
> - CPU generation (if in doubt, append the output of `lscpu`).
>
> About the last point, it may be that unfortunately only those with
> newer generations of Intel CPUs will have luck with this, but it's
> still an uncertainty. So reports are highly welcome.
>
> ----------Original Bug report ---------
>
> Libva is no longer working for snap installed chromium 72.0.3626.109
> (Official Build) snap (64-bit)
>
> I followed this instruction
> sudo snap install --channel=candidate/vaapi chromium
>
> My amdgpu can use libva
>
> `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
> 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
> vainfo: Supported profile and entrypoints
> VAProfileMPEG2Simple : VAEntrypointVLD
> VAProfileMPEG2Main : VAEntrypointVLD
> VAProfileVC1Simple : VAEntrypointVLD
> VAProfileVC1Main : VAEntrypointVLD
> VAProfileVC1Advanced : VAEntrypointVLD
> VAProfileH264ConstrainedBaseline: VAEntrypointVLD
> VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
> VAProfileH264Main : VAEntrypointVLD
> VAProfileH264Main : VAEntrypointEncSlice
> VAProfileH264High : VAEntrypointVLD
> VAProfileH264High : VAEntrypointEncSlice
> VAProfileHEVCMain : VAEntrypointVLD
> VAProfileHEVCMain10 : VAEntrypointVLD
> VAProfileJPEGBaseline : VAEntrypointVLD
> VAProfileNone : VAEntrypointVideoProc`
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions
>
>