Closed masterofobzene closed 3 months ago
It’s the other way around for me - MPC-BE opens faster, although I use the built-in parser. On yt-dlp the opening speed is approximately the same. So here you need to look at what format/resolution both players open in, it’s not the speed of Youtube parsing - but the speed of opening links.
Give this link to the video.
I had mpc-be configured to use yt-dlp instead of the built-in parser, that made a lot of difference. Both were configured at the same 1440p res. Now I left mpc-be with built in parser and so far so good.
mpc-hc takes 2 seconds more to parse (calls yt-dlp) then starts playback 1 or 2 seconds faster than mpc-be.
I will close this since in the end both behave more or less equal now using built in parser in mpc-be.
thanks
MPC-BE struggles to parse/open video. It takes too much time to do this task.
I include a comparison video with MPC-HC. Both are using the same yt-dlp.exe.
https://github.com/Aleksoid1978/MPC-BE/assets/94469116/274b45be-0d08-49d1-93e2-0ffc0c82b345
I would really like to use MPC-BE because its great playlist management (aka paste from clipboard 😁).