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

[BUG] Hardware decoding not working, works fine in Chrome #208

Open
miromarszal opened this issue Oct 6, 2023 · 6 comments · May be fixed by #248
Open

[BUG] Hardware decoding not working, works fine in Chrome #208

miromarszal opened this issue Oct 6, 2023 · 6 comments · May be fixed by #248
Assignees
Labels
bug Something isn't working

Comments

@miromarszal
Copy link

Describe the bug

I see no signs of hardware decoding when streaming a game. There is a noticeable input lag too.

To Reproduce

  1. Start gfn-electron and launch your favourite game.
  2. Wait until the stream begins.
  3. Observe your GPU usage with an appropriate tool (intel_gpu_top in my case).

Screenshots

GPU usage with gfn-electron
GPU usage with the app

GPU usage with Chrome
GPU usage with Chrome

Operating System

Ubuntu 23.04

Desktop Environment

GNOME 44.3

Display Server

Wayland

Installation method

Source

Version

1.13.0

Is this a fresh install of the app or an update from a past version?

Fresh

Did this issue appear right away upon installation/updating, or spontaneously?

Right after installation

Additional context

The graphics card is Intel® UHD Graphics (CML GT2). Hardware decoding works for me in Chrome with only one additional flag added: -enable-features=VaapiVideoDecodeLinuxGL. I leave out --use-gl, however, I verified that egl does not work and angle does. These are not the same as used by gfn-electron, so I tried the default setting and flags set as above by tweaking the source, in both cases without success. You can see from the screenshot above that hardware decoding does not work.

@miromarszal miromarszal added the bug Something isn't working label Oct 6, 2023
@seedneus
Copy link

didn't it need a permissions set in flatseal? Default is disabled as I can see...

@miromarszal
Copy link
Author

Good point about flatpak installations, there could be issues there. In my case it's a source installation though.

@hmlendea
Copy link
Owner

hmlendea commented Nov 7, 2023

didn't it need a permissions set in flatseal? Default is disabled as I can see...

Which permission are you refering to?

@hmlendea
Copy link
Owner

Is this still an issue in the latest release?

@erik-mueller
Copy link

Yes, I can confirm that this issue still exists. Starting chromium with --enable-accelerated-video-decode works, however this option is not accepted by the geforcenow-electron binary. Is it somehow possible to provide custom arguments to geforcenow-electron?

@hmlendea hmlendea linked a pull request Jul 24, 2024 that will close this issue
@chrispouliot
Copy link

@hmlendea Was the argument passing added in the open PR able to fix this issue? I am wondering if I can use AV1 decode with this but I am hesitant to pay for the higher subscription that offers it if hardware decode is not working. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants