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]: DRI3 implementation lacks vaPutSurface() #1737

Open
terr72 opened this issue Nov 7, 2023 · 2 comments
Open

[Bug]: DRI3 implementation lacks vaPutSurface() #1737

terr72 opened this issue Nov 7, 2023 · 2 comments
Assignees

Comments

@terr72
Copy link

terr72 commented Nov 7, 2023

Which component impacted?

Not sure

Is it regression? Good in old configuration?

None

What happened?

  1. I'm using Linux Mint 21.2 Xfce, which is based on Ubuntu Jammy.

  2. It currently comes with libva2 2.14.0-1 and iHD 22.3.1.

  3. Run xine -V vaapi --verbose "xvdr+tcp://127.0.0.1:37890#nocache" or xine -V vaapi --verbose randomrecording.ts

  4. This results in a black screen with only audio playing. The verbose log quickly fills with repeated video_out_vaapi Error : vaPutSurface(): unknown libva error entries.

The problem seems to be a lack of vaPutSurface() support in your DRI3 implementation.
See also this libva issue report, which affects hardware decoding in Chromium as well.

What's the usage scenario when you are seeing the problem?

Playback

What impacted?

xine, vdr-sxfe, vdr-plugin-xineliboutput
Apparently also chromium.

Debug Information

  1. libva2 2.14.0-1 and intel-media-driver 22.3.1
  2. by-path card0 renderD128
  3. 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:46d1]
  4. vainfo.log

Do you want to contribute a patch to fix the issue?

None

@atic-atac
Copy link

While there is a workaround of using...

export LIBVA_DRI3_DISABLE=1

to your environment, it's not a great long term solution.

Is Intel working on this ?

@terr72
Copy link
Author

terr72 commented Nov 26, 2023

Is Intel working on this ?

@atic-atac From my understanding this is an issue where both involved parties point fingers at each other.
The Intel devs say "hey, you could fix this with a simple patch in your code" while the libva team states "you need to implement this in your code". I can understand both sides, but being an end user caught between the stools, this is a pretty unsatisfying situation.

@Jexu Jexu removed their assignment Apr 25, 2024
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