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

WebRTC GPU accelerated video decoding on Linux (in Xvfb) #88

Open
zdila opened this issue Jun 17, 2020 · 3 comments
Open

WebRTC GPU accelerated video decoding on Linux (in Xvfb) #88

zdila opened this issue Jun 17, 2020 · 3 comments

Comments

@zdila
Copy link

zdila commented Jun 17, 2020

Hello,

Is it possible to patch and compile Chromium to enable WebRTC hardware video decoding on Linux?

I asked also on https://groups.google.com/a/chromium.org/forum/#!topic/chromium-discuss/GZVkDB-EiEI

I would rather ask on Launchpad.net but I get HTTP 500 when logging-in there.

Thanks in advance

@mattklein123
Copy link

I've been trying to get this working also in an effort to keep my laptop from melting while video conferencing all day.

I know very little about any of this and all of the permutations are very confusing, but I see that the arch patches seem to explicitly enable webrtc hw video encode/decode.

ungoogled-software/ungoogled-chromium-archlinux#33 (comment)

Chrome://GPU shows my machine supports hw encode/decode and I wonder if access to the above flags would turn it on? Or is there more involved?

@dgunay
Copy link

dgunay commented Feb 17, 2022

This is turning out to be a major obstacle for me (working on improving the performance of an app that does a lot of WebRTC video decoding in Chromium for Linux). Most of the patches I'm seeing on the internet don't touch the kDisableWebRtcHWDecoding flag or leave it disabled on Linux.

I would turn to Firefox nightly since it does have it, but that has some challenges of its own - mainly observability. Hard to confirm whether all the arcane switches and libraries I've enabled are actually working without a very long feedback loop, whereas chrome://webrtc-internals displays the decoder used for each peer connection.

@Alex-Bujorianu
Copy link

Hi, has anything been done regarding this issue? I see that it's still disabled on the .deb version of the latest Chrome on Ubuntu. I am told it works on ChromeOS though, so presumably, the functionality is there somewhere (I know ChromeOS does not use Wayland or X11).

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

4 participants