Open GrzegorzKozub opened 8 months ago
It is unfortunate but this time is spent fully in vkCreateInstance
and vkCreateDevice
, which is outside our control. We don't even request that much extensions.
I've looked at this few months ago, nothing really we can do. On AMD the init time is significantly faster, still noticeable, but clearly not as bad as in your case.
vo/gpu-next/libplacebo: Spent 5.893 ms enumerating instance layers
vo/gpu-next/libplacebo: Spent 68.399 ms enumerating instance extensions
vo/gpu-next/libplacebo: Spent 35.837 ms creating vulkan instance
vo/gpu-next/libplacebo: Spent 23.900 ms creating vulkan device
Only way is to complain to NVIDIA, but I wouldn't get your hopes high.
As a sanity check you can run mpv with higher verbosity (-v
) and observe Available layers:
to see if something is hiding there, but I doubt. Especially that both device and instance is taking long for you.
I ran into the same problem on GNU/Linux, X11, NVIDIA
Important Information
mpv-x86_64-v3-20231126-git-6898d57.7z
Reproduction steps
Run on Windows with NVIDIA and setup mpv to use Vulkan as GPU API. This is my config file:
Expected behavior
The player starts without a delay.
Actual behavior
The player takes about 2 seconds to start and there are reports of delays when creating Vulkan instance and device:
When does it NOT happen
Tested on multiple machines and OS. This does NOT happen in the following situations:
Log file
The relevant part of the log file (also attached as output.txt):
Sample files
This issue is irrelevant of the media file used.