-
Notifications
You must be signed in to change notification settings - Fork 20
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
mpv flatpak falling back to vo: [xv] #590
Comments
Have you tried On my Intel Laptop, the link works wfine.
|
Graphics drivers are up to date and I am NOT forcing vo=xv. I guess I will stick with debian's older version of mpv which works as expected on my system. $ inxi -G $ mpv --version $ flatpak run io.mpv.Mpv --version |
Flatpak uses mesa 24.3.1. This gpu seems to be 16 years old, I'm not sure if it's still supported by latest mesa. You may install
|
$ flatpak run --env=LIBGL_DEBUG=verbose org.freedesktop.Platform.GlxInfo > flatpak_glxinfo.txt output file flatpak_glxinfo.txt attached |
Some additional information: $ flatpak run org.freedesktop.Platform.VaInfo $ flatpak run org.freedesktop.Platform.VdpauInfo These errors do not occur when I run $ vainfo and $ vdpauinfo on my debian 12 system $ vainfo > debian_vainfo.txt $ vdpauinfo > debian_vdpauinfo.txt |
so mesa fallbacks to software rendering. There may be no driver for this gpu
|
There is a driver, but it's in Mesa Amber: https://docs.mesa3d.org/amber.html Mesa was split into two so that the ancient stuff can be separate. I'm not sure if flatpak packages Amber, though it would be nice if it would. |
freedesktop-sdk flatpak runtime doesn't package mesa amber and doesn't plan to do so in the future. |
Yes, they left it up to flathub. There really is no reason for flathub not to package it, other than nobody who still needs it wanting to do it I guess. |
I am guessing the problem is "[vo/gpu/opengl] Suspected software renderer or indirect context."
Is this due to the version of Mesa you are using?
debian's version mpv 0.35.1 works fine on my system.
● Video --vid=1 (h264 1280x640 29.97 fps) [default]
● Audio --aid=1 --alang=eng (opus 2ch 48000 Hz) [default]
File tags:
Date: 20241222
Uploader: Linus Tech Tips
Channel_URL: https://www.youtube.com/channel/UCXuqSBlHAE6Xw-yeJA0Tunw
[vo/gpu/opengl] Suspected software renderer or indirect context.
[vo/gpu/drm] VT_GETMODE failed: Inappropriate ioctl for device
[vo/gpu/drm] Failed to set up VT switcher. Terminal switching will be unavailable.
[vo/gpu/drm] Failed to create DRM atomic context, no DRM Atomic support
[vo/gpu/libplacebo] Found no suitable device, giving up.
[vo/gpu/libplacebo] Failed initializing vulkan device
[vo/gpu-next/opengl] Suspected software renderer or indirect context.
[vo/gpu-next/drm] Can't handle VT release - signal already used
[vo/gpu-next/drm] Failed to set up VT switcher. Terminal switching will be unavailable.
[vo/gpu-next/drm] Failed to create DRM atomic context, no DRM Atomic support
[vo/gpu-next/libplacebo] Found no suitable device, giving up.
[vo/gpu-next/libplacebo] Failed initializing vulkan device
[vo/vdpau] Error when calling vdp_device_create_x11: 23
[vo/xv] Warning: this legacy VO has bad quality and performance, and will in particular result in blurry OSD and subtitles. You should fix your graphics drivers, or not force the xv VO.
[ffmpeg] AVHWDeviceContext: Cannot load libcuda.so.1
[ffmpeg] AVHWDeviceContext: Could not dynamically load CUDA
Using hardware decoding (vaapi-copy).
[autoconvert] Converting nv12 -> yuv420p
AO: [pulse] 48000Hz stereo 2ch float
VO: [xv] 1280x640 => 1280x720 yuv420p
The text was updated successfully, but these errors were encountered: