I thought this was kind of interesting. I had a video that made (just a scene from a movie I watched). On my main workstation it played normally. However, on the Beelink I have, it wouldn't play, but if I used mplayer it was fine. With mpv it just showed a screen of a blur with traces of a picture.
I did some searching, and I confess, I wound up going to Claude.ai. The answer turned out to be that mplayer uses vo=xv or other older vo's while mpv seems to use gpu-next, but according to Claude there's some sort of bug
Anyway, the fix, according to Claude.ai, (and all suggested fixes worked) was to either run the video as mpv --vo=xv myvid.mp4 or to add these lines to $HOME/.config/mpv/mpv.conf
I read this a few days ago, and have already forgotten the details, but it may be a bug with mpv, FreeBSD, and handling of AMD gpu's. But figured I'd put these two quick fixes up here. It holds for both Wayland and X.
Doing
doesn't work.
So, if you have a video that won't work with mpv, but will with mplayer, either the edit of mpv.conf or the mpv vo=xv should work.[/file]
I did some searching, and I confess, I wound up going to Claude.ai. The answer turned out to be that mplayer uses vo=xv or other older vo's while mpv seems to use gpu-next, but according to Claude there's some sort of bug
Anyway, the fix, according to Claude.ai, (and all suggested fixes worked) was to either run the video as mpv --vo=xv myvid.mp4 or to add these lines to $HOME/.config/mpv/mpv.conf
vo=gpu-nextgpu-api=openglI read this a few days ago, and have already forgotten the details, but it may be a bug with mpv, FreeBSD, and handling of AMD gpu's. But figured I'd put these two quick fixes up here. It holds for both Wayland and X.
Doing
Code:
mpv --vo=gpu-next
So, if you have a video that won't work with mpv, but will with mplayer, either the edit of mpv.conf or the mpv vo=xv should work.[/file]