Re: [ISSUE] [CLOSED] Build Option Request: VAAPI

Re: [ISSUE] [CLOSED] Build Option Request: VAAPI

[ericonr]

[-- Attachment #1: Type: text/plain, Size: 374 bytes --]

Closed issue by dm17 on void-packages repository

https://github.com/void-linux/void-packages/issues/22877

Description:
As requested here: https://github.com/void-linux/void-packages/pull/5219#issuecomment-643661306

I'm wondering if we can get hardware acceleration for modern AMD GPUs in chromium (build_options_default)? It seems pretty common & very useful.
Thanks!

Re: Build Option Request: VAAPI

[dm17]

[-- Attachment #1: Type: text/plain, Size: 391 bytes --]

New comment by dm17 on void-packages repository

https://github.com/void-linux/void-packages/issues/22877#issuecomment-763959147

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).

Re: Build Option Request: VAAPI

[ericonr]

[-- Attachment #1: Type: text/plain, Size: 300 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/22877#issuecomment-763961517

Comment:
As far as I know, the VAAPI build option is no longer required in any way. If the hw accel isn't working correctly / being detected, that's a separate issue.

Re: Build Option Request: VAAPI

[dm17]

[-- Attachment #1: Type: text/plain, Size: 535 bytes --]

New comment by dm17 on void-packages repository

https://github.com/void-linux/void-packages/issues/22877#issuecomment-763966039

Comment:
> As far as I know, the VAAPI build option is no longer required in any way. If the hw accel isn't working correctly / being detected, that's a separate issue.

Such a pain to debug chromium. Perhaps Void should consider replacing chromium with its own custom build of ungoogled-chromium... Wouldn't that be truer to the FOSS message anyway (considering how much tracking comes with chromium)?

Re: Build Option Request: VAAPI

[Logarithmus]

[-- Attachment #1: Type: text/plain, Size: 621 bytes --]

New comment by Logarithmus on void-packages repository

https://github.com/void-linux/void-packages/issues/22877#issuecomment-764012814

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).

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

Re: Build Option Request: VAAPI

[Logarithmus]

[-- Attachment #1: Type: text/plain, Size: 627 bytes --]

New comment by Logarithmus on void-packages repository

https://github.com/void-linux/void-packages/issues/22877#issuecomment-764012814

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

Re: Build Option Request: VAAPI

[dm17]

[-- 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"
```

Re: Build Option Request: VAAPI

[Logarithmus]

[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]

New comment by Logarithmus on void-packages repository

https://github.com/void-linux/void-packages/issues/22877#issuecomment-764022629

Comment:
@dm17 what GPU do you have?
Did you read this: https://wiki.archlinux.org/index.php/Hardware_video_acceleration ?

21 января 2021 г. 2:19:00 GMT+03:00, dm17 <notifications@github.com> пишет:
>> > > 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"
>```

Re: Build Option Request: VAAPI

[dm17]

[-- Attachment #1: Type: text/plain, Size: 240 bytes --]

New comment by dm17 on void-packages repository

https://github.com/void-linux/void-packages/issues/22877#issuecomment-765356181

Comment:
@Logarithmus Yes, read that. I have Polaris 20 (an AMD card with some of the best support in Linux).

Re: Build Option Request: VAAPI

[Duncaen]

[-- Attachment #1: Type: text/plain, Size: 694 bytes --]

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/22877#issuecomment-765436746

Comment:
> Such a pain to debug chromium. Perhaps Void should consider replacing chromium with its own custom build of ungoogled-chromium... Wouldn't that be truer to the FOSS message anyway (considering how much tracking comes with chromium)?

How does this in any way make any sense to you, how would that reduce any work instead of adding more work?
Chromium is FOSS, chromium is the maintained browser, its FOSS there is not more or less FOSS.
Stop spamming us with ungoogled chromium stuff, I've had enough of it, we said no and you have to accept it.

Re: Build Option Request: VAAPI

[Duncaen]

[-- Attachment #1: Type: text/plain, Size: 737 bytes --]

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/22877#issuecomment-765436746

Comment:
> Such a pain to debug chromium. Perhaps Void should consider replacing chromium with its own custom build of ungoogled-chromium... Wouldn't that be truer to the FOSS message anyway (considering how much tracking comes with chromium)?

How does this in any way make any sense to you, how would that reduce any work instead of adding more work?
Chromium is FOSS, chromium is the maintained browser, its FOSS there is not more or less FOSS.
Stop spamming us with ungoogled chromium stuff, I've had enough of it, we said no not once but in multiple different threads and you have to accept it.

Re: Build Option Request: VAAPI

[ericonr]

[-- Attachment #1: Type: text/plain, Size: 186 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/22877#issuecomment-763955188

Comment:
This is fixed on current chromium packages.