-
-
Notifications
You must be signed in to change notification settings - Fork 15k
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
Mesa 21.0: VAAPI recording broken #123446
Comments
Sadly a look at that thread, it's blocked because something broke, and they're not pushing it to 21.05, so this bug is going to exist until someone figures this out the regression, this patch is only one line of code, maybe it can be supplied as a patch until they get 21.0.3 working? Is there a way to build a patched mesa without rebuilding my entire desktop stack? It's currently stupidly slow on my computer when doing a packageOverride. |
This will not be the only bug people will have to deal with on 21.05 unless we backport a more recent mesa (>=21.1). Alternative we could also start to includes this patch as well. Without it, this will lead to crashes in wine (incl. steam proton) when initializing a GL context on some hardware ( @NixOS/backports Would it be possible to backport the mesa update currently in staging-next (#124095) once it is merged? |
I don't know... this is hard. Maybe after a version has been a couple weeks in |
I'm okay with backporting it, but probably as its own job set, just to get a better idea of regressions. |
I'm not afraid of build-time regressions in this case. Those would be easy (to find). And mesa isn't such a big rebuild now anyway. |
If it's been on unstable for a while, I guess I'm okay with it as well |
I guess we can close this now, I haven't noticed any problems recently. |
Describe the bug
VAAPI records repeated frames (see upstream bug report).
upstream fix: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9995
To Reproduce
Steps to reproduce the behavior:
Expected behavior
full FPS.
Notify maintainers
@primeos @vcunat
Maintainer information:
The text was updated successfully, but these errors were encountered: