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

Adapter_name field not affecting vaapi on Linux #1573

Closed
3 tasks done
ZeoWorks opened this issue Aug 28, 2023 · 3 comments
Closed
3 tasks done

Adapter_name field not affecting vaapi on Linux #1573

ZeoWorks opened this issue Aug 28, 2023 · 3 comments
Labels

Comments

@ZeoWorks
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Is your issue described in the documentation?

  • I have read the documentation

Is your issue present in the nightly release?

  • This issue is present in the nightly release

Describe the Bug

Hi, I thought to leave this issue here to be addressed;
adapter_name in the configuration file has no affect on the render device used for vaapi on Linux.
This can be set to anything and there will be no affect regardless.

Looking at video.cpp is clear that the hw-device-buffer is returned prior to any interaction with adapter_name.

Expected Behavior

No response

Additional Context

No response

Host Operating System

Linux

Operating System Version

22.04

Architecture

64 bit

Sunshine commit or version

0.20.0

Package

Linux - deb

GPU Type

AMD

GPU Model

RX 580

GPU Driver/Mesa Version

23.1.6

Capture Method (Linux Only)

No response

Config

adapter_name = #

Apps

No response

Relevant log output

null
@ISAndreiva
Copy link

Is there any workaround to force a vaapi vendor until this is fixed?

@LizardByte-bot
Copy link
Member

It seems this issue hasn't had any activity in the past 90 days. If it's still something you'd like addressed, please let us know by leaving a comment. Otherwise, to help keep our backlog tidy, we'll be closing this issue in 10 days. Thanks!

@LizardByte-bot
Copy link
Member

This issue was closed because it has been stalled for 10 days with no activity.

@LizardByte-bot LizardByte-bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants