Skip to content
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

Video passthrough doesn't seem to work #124

Open
Cqoicebordel opened this issue Apr 9, 2022 · 4 comments
Open

Video passthrough doesn't seem to work #124

Cqoicebordel opened this issue Apr 9, 2022 · 4 comments

Comments

@Cqoicebordel
Copy link

Cqoicebordel commented Apr 9, 2022

I just updated to the 101 version (Chromium 101.0.4951.15 Ubuntu 20.04) and the video decoding seems broken.
In chrome:gpu it looks ok (Video Decode: Hardware accelerated) but videos are not accelerated (as shown in the devtools/media tab. I've double checked it, as I have looked at the usage of the GPU video HWA, which stayed at 0.
Just to note, the previous version worked, so I can really see the difference.

I've tried multiple things (like switching on Vulkan for a spell, switching flags here and there) but nothing seems to make it work.
I also tried to activate --use-gl=egl instead of desktop, but I got a black screen.

I'm attaching the GPU page, and the verbose output of chromium, running with chromium-browser --verbose --enable-features=VaapiVideoDecoder --enable-accelerated-video-decode 2> chromium.log (note that the log have been anonymised, I hope not too much or not much enough, but I have a clean copy, just in case)

chromium-gpu.log
chromium.log

This bug is a FYI more than a request for help. I gratefully appreciate any and all work you have done here thus far :)

@vmarkovtsev
Copy link

Same here but on Intel GPU instead of Nvidia: Chromium 101, Ubuntu 20.04. It used to work with version 97.
The log shows this:

[65185:65185:0425/201003.500039:VERBOSE1:vaapi_wrapper.cc(939)] Unsupported value 2 for VAConfigAttribRateControl

when I play 1080@30 or 60 fps video on Youtube.

btw @Cqoicebordel you leak a few private emails in the log.

@Cqoicebordel
Copy link
Author

@vmarkovtsev thanks a lot. I didn't think to check for email addresses. Was stupid of me. I edited my post.

@vmarkovtsev
Copy link

Follow up: I returned back VAAPI by specifying this cmdline argument: --disable-features=UseChromeOSDirectVideoDecoder

@Cqoicebordel
Copy link
Author

It didn't work for me. Still video decode shown as hardware accelerated in :gpu, still nothing done on GPU.
The fact that GpuMemoryBuffers Status shows all as Software only is not a good sign I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants