Closed M6ZeroG closed 6 years ago
Hey there,
thanks a lot for the detailed description. I will look into this as soon as I can (definitely within this week). Should be fairly easy to fix. I might drop the version checking part in Node-MPV completely since it's been like 2 years since they changed the ipc command command line flag.
Should be the easiest and safest fix. It just uses the new ipc command and the user of the library can pass the old one if he wishes to use a fairly outdated version of mpv (or has to).
Thank you! :)
Hey,
sorry it's taking so long. I have troubles compiling the latest MPV version because I can't get a new enough version of ffmpeg. I'm further looking into the issue. Really sorry.
Still looking into it. I have a version where I removed the checking and rely on the user to input the ipc option and using the later one (used since mpv 0.17.0) as a default.
However I'd like to keep the ability to decide on the argument automatically that's why I'm hesitant to remove it.
What you can do for now is set the command by hand. So if you create the mpv object do it like this
let mpvPlayer = new mpv({
'ipc_command': '--input-ipc-server'
});
along with your other options. That should skip the version checking (since you provided the command yourself) and your player should run.
Meanwhile I'm further working on resolving the issue, sorry it's taking so lang.
Super sorry it took so long :(
This mostly beacuse of the mpv version strings changed recently like this:
And the previous version is still in this format:
Link : https://github.com/mpv-player/mpv/commit/49e704cb19dfe72b293fd286395e37ed1d3c3d99