-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VP9 video playback is broken when hw video accel is enabled #8679
Comments
This is funny because for me it is exactly the other way around. With HW acceleration enabled I can watch VP9 videos, but h264 video content is severely broken #7706 It is true that Chromium with enabled HW accel has no issues, so it is Brave specific. |
@Nuc1eoN can you share some system details? Which GPU do you have? what does |
I do not have the new However Brave clearly misbehaves only when HW accel is active in settings, so I guess it makes use of some functionality 🤔 |
No. Chromium with vaapi enabled has different names according to the distro. Since I'm using Fedora the package name is In Archlinux is available as Any of the packages should provide a solid base to update Brave patching/enabling of VAAPI for Linux users. |
I'm having the same issue described here, couldn't test Any changes so far? Did you get working? |
No progress on my side. Going to re-test once 1.7.x is out |
Someone need to add this patch to brave. It will fix the Intel VP9 issue. Honestly there are many issues with chromium atm. (egl backend is busted in the current build and issue with Mesa). @Nuc1eoN Your issue is with mesa rgb10 configs. You need to disable it. Add |
Humm according to their tree they need 3 patches?
About stability: I have zero issues with chromium-freeworld and it is a lot better on cpu/laptop battery than Brave is. hum |
This is not required. |
Hey, is there any kind of process we can follow to accelerate the revision of this issue? This patch chromium-fix-vaapi-on-intel.patch seems to be being applied virtually everywhere (Ubuntu, Fedora, Arch) and the lack of acceleration is a bit of a PITA. Thanks! |
I use an extension to force x264 in youtube (https://chrome.google.com/webstore/detail/h264ify/aleakchihdccplidncghkekgioiakgal) as a workaround and it works great (lower cpu usage). Would this also enable VP9 hardware acceleration in WebRTC (google meet?) since that would be a huge advantage... |
On arch linux https://aur.archlinux.org/packages/chromium-vaapi/ (last updated: 2020-07-07) gives me vp9 acceleration, while the latest chromium packages don't (only x264 acceleration). |
Everything seems to work great now (it has been for a while) Version 1.20.47 Chromium: 88.0.4315.7 (Official Build) nightly (64-bit) |
For me it's the other way round. It was fixed for a while but the latest few releases caused a regression, namely many youtube videos are simply "white" with hw acceleration enabled. |
Perhaps you are hitting this ? |
Thank you, that seems exactly like my issue! |
Yes I confirm that this looks solved. I didn't noticed because I've been using Just tested VP9 playing with Closing the issue. |
Description
In a Linux system (Fedora 31) with VAAPI and hardware video acceleration enabled ( #ignore-gpu-blacklist ), if a webpage has a video encoded in VP9 format, the video playback is stuck. Hardware-accelerated video playback works normally for h624-encoded videos.
This means that either you play all videos in software-mode or only play h264-encoded videos when hardware acceleration is available.
chromium-vaapi
in the same test scenarioIn chromium, despite having #ignore-gpu-blacklist and accelerated video playback, it doesn't affect VP9. So, chromium is not affected
This leads that the underling Chromium that Brave is using is missing some library/feature/compilation flag.
Steps to Reproduce
sudo dnf install libva libva-utils intel-media-driver libva-intel-driver
Actual result:
Video playback is stuck.
Expected result:
Videos playing normally with hardware acceleration enabled
Reproduces how often:
Every time
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
Related bugs: #1024 and #7706
Some chromium-vaapi articles in the Fedora/Linux world:
vainfo:
The text was updated successfully, but these errors were encountered: