avih

> So it should be possible from mpv as well? It's not possible currently, and in my opinion it should not be possible.

> run this: > `mpv --no-config --player-operation-mode=pseudo-gui --script-opts=osc-visibility=always http://vps.radioduepuntozero.it:9080` > The memory occupation starts growing, at first really fast (like 2MB per second) then it progressively slows down, but still...

Sure, with OSD/OSC it uses more ram (and grows quicker initially), because libass has a big cache. However, that should eventually stop growing. I don't know how big is the...

Hmm.. or maybe it could be a command prefix, similar to `no-osd` and `osd-message`, maybe there could also be `osd-scroll` or `osd-log` or some such?

There's no need to document it because there's now (for some years) a new official and documented API which does the same thing https://mpv.io/manual/master/#lua-scripting-mp-create-osd-overlay(format)

Basically the info (all available ytdl tracks info) is already exposed as track metadata when using `all-formats=yes`. Maybe not enough for everyone, but definitely enough for many/most, and improvements here...

> it should be straightforward to add functionality that allows users to specify arbitrary mouse zones in a config file The `Zones`[1] user-script already does exactly that. I'm pretty sure...

> More importantly, and I may be wrong, I don't think zones would fix the problem at all because afaik, you still can't get around single target mouse dispatch. So...

For what it's worth, when building with mingw (tested: MXE on ubuntu), the global LDFLAGS makes mpv's configure considerably slower (every configure test links with these too). In my mpv-build...

Thanks. The code looks generally good, though I have no experience embedding libmpv, nor with GTK, so this is not a review, just some comments. - You probably want to...