From: dm17 <dm17@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Build Option Request: VAAPI
Date: Thu, 21 Jan 2021 00:18:45 +0100 [thread overview]
Message-ID: <20210120231845.fsZ3_1SJzbUkK5W0zRhKt6TKInrG6tBYOnXx1JbgnDM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22877@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
New comment by dm17 on void-packages repository
https://github.com/void-linux/void-packages/issues/22877#issuecomment-764017685
Comment:
> > > This is fixed on current chromium packages.
> >
> >
> > Have you verified it using the method of looking in about:media-internals?
> > I tried many times and I still see the non-hardware-accelerated codec being used for Vimeo & YouTube videos (VpxVideoDecoder).
>
> @dm17 Just install **enhanced-h264ify** chromium extension, block everything except h264 and it will work like a charm (if you use Xorg, not Wayland). For Nvidia there's https://github.com/xtknight/vdpau-va-driver-vp9
I use Xorg. I did try this extension, but it did not change the fact:
"If it says FFmpegVideoDecoder or VpxVideoDecoder, accelerated video decoding is not working"
https://www.linuxuprising.com/2018/08/how-to-enable-hardware-accelerated.html
about:media-internals:
```
"Failed to initialize DecryptingVideoDecoder"
"Failed to initialize MojoVideoDecoder"
"Failed to initialize VpxVideoDecoder"
"Failed to initialize Dav1dVideoDecoder"
kIsVideoDecryptingDemuxerStream | false
kVideoDecoderName | "FFmpegVideoDecoder"
```
next prev parent reply other threads:[~2021-01-20 23:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22877@inbox.vuxu.org>
2021-01-20 21:21 ` ericonr
2021-01-20 21:21 ` [ISSUE] [CLOSED] " ericonr
2021-01-20 21:26 ` dm17
2021-01-20 21:31 ` ericonr
2021-01-20 21:39 ` dm17
2021-01-20 23:08 ` Logarithmus
2021-01-20 23:09 ` Logarithmus
2021-01-20 23:18 ` dm17 [this message]
2021-01-20 23:28 ` Logarithmus
2021-01-22 12:12 ` dm17
2021-01-22 14:25 ` Duncaen
2021-01-22 14:26 ` Duncaen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210120231845.fsZ3_1SJzbUkK5W0zRhKt6TKInrG6tBYOnXx1JbgnDM@z \
--to=dm17@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).