-
Notifications
You must be signed in to change notification settings - Fork 11
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 videos do not play in Chromium 87 or newer #13
Comments
same problem, vp9 decoding not works |
Does libva-vdpau-driver-chromium have vp9 support ? |
|
Right now I'm using |
My bad btw, I misinterpreted the changes in |
So I guess the dev has no interest in this...? |
YouTube only delivers above 1080p in VP9 or sometimes AV1. You can confirm this by listing the available stream formats with |
Yeah that was my point. Without h264ify to force h264, above 1080p videos will play, but they won't use hw decoding. If I want hw decoding, I have to use h264ify which means I'm limited to 1080p which sucks because my main monitors are 2K and I also have a 4K one. Again, this is only with libva-vdpau-driver-chromium, because with libva-vdpau-driver-vp9-git, the videos just won't play as everyone else has demonstrated (starting with v87). |
Is anyone working on this? I would love to help but I'm currently completely lost... |
Here is logs with
|
Still no progress? I would love to help but I know nothing about video decoding or VDPAU, so... |
I have this issue as well, here's a full
|
having the same issue with brave browser (chromium based), I don't know what information to post to help so please inform us. |
I emailed the author of this project a few weeks ago and still haven't received a response. I don't think this bug will ever be fixed unless someone else takes over. |
That's sad. Seems that no one knows how to work it out... |
Apologize for the silence; I haven't had time to maintain this as I had wanted. If anyone is willing to takeover, that's fine with me and I can give them the proper permissions to do so, or approve pull requests, etc. As for this issue, I don't believe the VP9 codec decoding part is returning an error code and suspect it's a problem with the VDPAU/VA-API bridge part. Unfortunately, I know as much about this part as you guys do, so I don't think I would be much help. I would start by seeing if other codecs from the original code upon which this code is based are working properly (e.g., MPEG1, MPEG2, MPEG4, VC1, H264), whether through Chromium or otherwise. Failing that, it would probably require re-compiling Chromium and/or the VA-API library and adding debug lines around the VA-API calls to figure out what's going on exactly. I can't guarantee I'll have any time to look into this, but just wanted to break the silence at least. Andrew |
I have posted a diff between my codebase and Arch. I guess this may be a start point to figure out what's going on. diffs_arch0.74_vp9_src.patch.tar.gz Testing will take me awhile but it's worth looking into vdpau_CreateSurfaceFromV4L2Buf and vdpau_common_Initialize Also worth looking into issues with Chromium 87 itself... |
I don't know how much this helps, but if I downgrade Chromium to 86.0.4240.75, vp9 does still work. I mean I guess that's to be expected but I figured it would potentially be some useful information. |
I don't know if this helps either but in the latest Chromium it now fails silently and just plays the h.264 1080p video. The following errors print in console. [2756:2790:0615/114348.742615:ERROR:token_service_table.cc(140)] Failed to decrypt token for service AccountId-101375343074270199767 |
Yes, I can confirm that the vp9 format doesn't exist for Chromium anymore. But this only happens in conjunction with using vdpau-va-driver-vp9 in a Nvidia environment, In another intel box with same version of Chromium installed from same source the vp9 options are available (vaapi also activated though vp9 hardware acceleration is not supported by graphic card there) Chromium 91.0.4472.27 installed from the Chromium-beta ppa for Ubuntu https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-beta Go to https://base-n.de/webm/VP9%20Sample.html the vp9 sample shows a blackbox Go to https://www.youtube.com/watch?v=h3fUgOKFMNU and check the settings the highest resolution shown in Chromium is 1080p60fps but in Firefox additional options up to 4320p60 are availiable. h264ify is not installed. As far as the h264 streams go vaapi works perfectly. |
I have some time to tinker things recently, and I volunteer to help fix this. (BTW, Chrome still has VP9) |
|
Client must use vaDestroyBuffer to destroy buffers. Fixes: xtknight#13 Signed-off-by: Yuri Konotopov <[email protected]>
Client must use vaDestroyBuffer to destroy buffers. Fixes: xtknight#13 Signed-off-by: Yuri Konotopov <[email protected]>
#15 Fixes this issue. Give it a try (You have to build it manually) And don't upgrade to chromium 95! |
Thanks!!! |
Chromium 95 uses Ozone Platform by default which doesn't support hw accelerated video decoding and there is no option to disable it. I've read in ArchLinux forum that people are having issues with it, so it's better not to upgrade at the moment until a new workaround is found. On Chromium 94 I had another problem that it did fall back to software decoding and I found out I had to kill the 'GPU Process' in chromium's task manager in order to make it work, I'm not sure if there was something wrong with my installation or it affects everyone but if you encounter that, now you know how to fix it. |
I can tell the current maintainer to switch to my branch. If it doesn't happen soon, I'll file to orphan and then adopt the package. I just incorporated some Arch Linux fixes (used in the |
@xuarnruiqi you won't allow issues on your fork, but anyway right now Chromium for some reason is forcing H264. Hardware accelerated decoding is working (I'm looking at GWE) but it won't use VP9. Weirdly though there are no error messages when running from the terminal. A couple hours ago this wasn't an issue. |
@gardotd426 I just enabled issues. That's very strange, I couldn't reproduce this at all. You're sure there's no h264ify running? |
What version of chromium are you on? If you're up to date on Arch it should be 95.0.4638.54-2.
Yeah, I've triple checked. I could just remove the extension, I'll see what that does. Ahhh. So I'd done some hack to try and enable Sync in Chromium (since that was removed), and it added all my old extensions, including enhancedh264ify and it was enabled. So it's working. However, it still doesn't work in Brave, and Brave always worked with GPU acceleration before. It just stopped working like, yesterday. But yeah Chromium is back to playing VP9 |
Chromium 95 might not work with VA-API since they forced OzonePlatform for both X11 and Wayland and it has issues with video acceleration. They fixed it in v96 tho. So it's better to skip v95. |
I have Chromium 95 and it works perfectly. It's just Brave where it quit
working.
…On Fri, Oct 22, 2021 at 8:36 AM Alireza |S.N| ***@***.***> wrote:
Chromium 95 might not work with VA-API since they forced OzonePlatform for
both X11 and Wayland and it has issues with video acceleration. They
fixed it
<https://chromiumdash.appspot.com/commit/a4de986102a45e29c3ef596f22704bdca244c26c>
in v96 tho. So it's better to skip v95.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AM5Y3372WCP57KODPG4MMKDUIFLDXANCNFSM4UCXL3ZA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
@gardotd426 That's good news. Can you share an screenshot from |
Actually I think they shipped the fix (at least a fix) with v95, so it should have no problems. It's working for me without problems; I know nothing about Brave though. |
I have upgraded my chromium to the latest version (currently 87) and VP9 decoding has stopped working. I get this error whenever I try to play a VP9 video on YouTube:
Chromium GPU page shows me this error:
And media page shows this error:
I tried using h264ify extension and h264 videos work just fine with hardware acceleration (MojoVideoDecoder). So only VP9 videos are not playing.
Seems like other people have the same problem too: saiarcot895/chromium-ubuntu-build#102
I'm not entirely sure if this bug is related to this project or not. Feel free to close it if it's not.
Thanks for your help.
The text was updated successfully, but these errors were encountered: