llyyr
This is an amdgpu bug, not a mpv one. mpv crashes as a result of your gpu resetting, not the other way around. >[ 1777.234990] [drm:amdgpu_job_timedout [amdgpu]] ERROR ring gfx...
can reproduce on wlroots with amdgpu as well. only happens when direct scanout is active
Can you produce a log with `PIPEWIRE_DEBUG=5 mpv [...]`? I can't reproduce this fwiw
Nothing seems unusual there, it might be a KDE menu bug because it tries to display that string in the "Application" tab of the volume control
That makes it worse in every way, you even start getting worse display-resample performance, it's not really needed anymore imo. Anyway, it's broken for all push AOs, not just pulse.
Yeah, I'm not convinced that the diff in the original is a possible solution anymore so I'll remove it. But the delay calculation for all push-based AOs is still wrong,...
This issue is now "hidden" on master by d93f53b3241a1715833f1ba28d0e7f601d085911, but the clamping doesn't work for `--play-dir=-` so we can still see the bug in effect when playing the file in...
+1 for `include/mpv` I like that better than current as well
this is already possible with `--load-scripts=no` then explicitly load scripts with `--scripts=foo.lua:bar.lua:...` Please read the manual
Try each option individually and see which one causes it?