Akemi
commented
1 month ago on a side note, your version v0.37.0-1071-g0125d35954 seems kinda weird. it should say 0.38. did you build it yourself, or where is this build from?
anyway your vulkan driver/moltenvk seems to be broken and it can't initialise a vulkan context. it's falling back to libmpv/cocoa-cb and that is running in a opengl emulation layer (from Apple) via metal. this is not recommended on ARM macs, and probably not recommended at all anymore since the introduction of that emulation layer by Apple and various things that Apple changes with opengl.
the source of the problem is most likely this commit. reverting this will fix that problem, but will introduce others problems again. like mentioned above, nothing we can do about and you should get vulkan/moltenvk working on your system.
[ 0.034][v][vo/gpu/vulkan] Initializing GPU context 'macvk'
[ 0.034][v][vo/gpu/libplacebo] Initialized libplacebo v6.338.2 (API v338)
[ 0.034][d][vo/gpu/libplacebo] Available instance version: 1.3.280
[ 0.034][d][vo/gpu/libplacebo] Spent 0.111 ms enumerating instance layers
[ 0.034][d][vo/gpu/libplacebo] Available layers:
[ 0.034][d][vo/gpu/libplacebo] Spent 0.104 ms enumerating instance extensions
[ 0.034][d][vo/gpu/libplacebo] Available instance extensions:
[ 0.034][d][vo/gpu/libplacebo] VK_EXT_debug_report
[ 0.034][d][vo/gpu/libplacebo] VK_EXT_debug_utils
[ 0.034][d][vo/gpu/libplacebo] VK_KHR_portability_enumeration
[ 0.034][d][vo/gpu/libplacebo] VK_LUNARG_direct_driver_loading
[ 0.034][v][vo/gpu/libplacebo] Creating vulkan instance with extensions:
[ 0.034][v][vo/gpu/libplacebo] VK_KHR_get_physical_device_properties2
[ 0.034][v][vo/gpu/libplacebo] VK_KHR_portability_enumeration
[ 0.034][v][vo/gpu/libplacebo] VK_KHR_surface
[ 0.034][v][vo/gpu/libplacebo] VK_EXT_metal_surface
[ 0.034][d][vo/gpu/libplacebo] Spent 0.052 ms creating vulkan instance
[ 0.034][v][vo/gpu/libplacebo] Failed creating instance: VK_ERROR_INCOMPATIBLE_DRIVER
[ 0.034][v][vo/gpu/libplacebo] Failed initializing vulkan instance
...
[ 0.035][v][vo/gpu-next/vulkan] Initializing GPU context 'macvk'
[ 0.035][v][vo/gpu-next/libplacebo] Initialized libplacebo v6.338.2 (API v338)
[ 0.035][d][vo/gpu-next/libplacebo] Available instance version: 1.3.280
[ 0.035][d][vo/gpu-next/libplacebo] Spent 0.098 ms enumerating instance layers
[ 0.035][d][vo/gpu-next/libplacebo] Available layers:
[ 0.035][d][vo/gpu-next/libplacebo] Spent 0.098 ms enumerating instance extensions
[ 0.035][d][vo/gpu-next/libplacebo] Available instance extensions:
[ 0.035][d][vo/gpu-next/libplacebo] VK_EXT_debug_report
[ 0.035][d][vo/gpu-next/libplacebo] VK_EXT_debug_utils
[ 0.035][d][vo/gpu-next/libplacebo] VK_KHR_portability_enumeration
[ 0.035][d][vo/gpu-next/libplacebo] VK_LUNARG_direct_driver_loading
[ 0.035][v][vo/gpu-next/libplacebo] Creating vulkan instance with extensions:
[ 0.035][v][vo/gpu-next/libplacebo] VK_KHR_get_physical_device_properties2
[ 0.035][v][vo/gpu-next/libplacebo] VK_KHR_portability_enumeration
[ 0.035][v][vo/gpu-next/libplacebo] VK_KHR_surface
[ 0.035][v][vo/gpu-next/libplacebo] VK_EXT_metal_surface
[ 0.035][d][vo/gpu-next/libplacebo] Spent 0.049 ms creating vulkan instance
[ 0.035][v][vo/gpu-next/libplacebo] Failed creating instance: VK_ERROR_INCOMPATIBLE_DRIVER
[ 0.035][v][vo/gpu-next/libplacebo] Failed initializing vulkan instance
rgaufman
mpv Information
UPDATE: I fixed the problem with: brew install molten-vk
Other Information
Reproduction Steps
Opening a video, you cannot grab and drag the window or resize it, it appears stuck, after a few seconds it glitches and allows resizing or moving the window.
Expected Behavior
It should allow grabbing and moving and/or resizing the window without lagging / glitching.
Actual Behavior
You grab the window title and drag the window and nothing happens for a few seconds until it snaps to where the mouse pointer is after a substantial delay.
Log File
Full log: output.txt
This happens with any video, but here's an example:
Sample Files
Happens on any video file, tried mkv/h264, mp4/h265, wmv, etc.
I carefully read all instruction and confirm that I did the following:
--log-file=output.txt.