Page 1 of 1

Why mpv.exe as opposed to libmpv.dll?

PostPosted: Sun Dec 14, 2014 5:43 pm
by Starks
I like the idea of a drop-in replacement, but every other mpv player (Baka MPlayer, CMPlayer. etc) has transitioned to libmpv.

Re: Why mpv.exe as opposed to libmpv.dll?

PostPosted: Sun Dec 14, 2014 11:15 pm
by rvm
First I agree with the mpv developers that developing an interface with the slave mode and parsing the output messages is like hell. I wish mplayer had provided something better 8 years ago when I began to implement smplayer.

But that hard work is already DONE, and using the slave mode in mpv is easier than switching to another thing. Besides of that, I previously tested the "qtexample" which is provided by mpv as a test for the client api and it had some issues and crashes, so it didn't caused me a good impression.

Anyway if users like the mpv support then I'll probably try to migrate to use libmpv to provide a better support.

Re: Why mpv.exe as opposed to libmpv.dll?

PostPosted: Mon Dec 15, 2014 1:54 am
by Guest
Sounds like a plan. The client API has only been stable for a few weeks anyway.

Only bug I've seen so far is that I can't figure out how to enable ass and embedded fonts.

Re: Why mpv.exe as opposed to libmpv.dll?

PostPosted: Mon Dec 15, 2014 1:56 am
by Starks
Never mind

"Use custom style" should be disabled for such files