Noted! that was not by far the purpose, at least made some laughs. I've tried to lower the amount of acronyms in the About and Overview section, adding links to the relevant pages that describe the acronyms, however, it's rather difficult to remove the acronyms without losing the meaning. thanks for the feedback.
I use mpv + mpvc, started using it heavily a couple of years ago.
Eventually, I started implementing features I was missing such as play,
and search Youtube music, manage playlists/playstate, minimal TUI, fzf
support, an equalizer. And last year decided to publish the changes on https://github.com/gmt4/mpvc/. I try to keep a log of the features I miss/implement at https://gmt4.github.io/mpvc/logbook.html.
Just came here to chime that I've been playing with mpv + fzf + notify-send, and as a result mpvc-tui has got now some cool fuzzy search + desktop notifications. I've included a bunch of screenshots showing the updates at: https://gmt4.github.io/mpvc/
That's definitely worth keeping an eye on, but actually its not that bad.
Take this with a grain of salt, as I only have a user view, not mpv developer. I consider the JSON IPC API quite stable, well documented through mpv(1) and https://mpv.io/manual/stable/. Almost every command-line option documented in mpv(1) is mapped 1:1 to the JSON IPC, so mpv(1) documents both the command-line, and, the JSON IPC.
The MPD & its clients are quite more complete, providing features such as: media library, indexing, extended searches, tags. etc.
Instead mpvc is just a simple client that provides a mpc-like interface, and communicates with the mpv running on the same machine over a Unix Socket. So YMMV depending on how many MPD features you require.
Good to know, and thanks! I started using mpv recently, about year ago, and also found that mpv is simple, works, and the documentation has you covered.
Note that the aim/need is not on providing a complete player/interface replacement, but on co-existing, and having an easy way to control the running mpv from the terminal, so if I'm working from the terminal I don't need to switch to the player window/terminal.
One example of the above, is when you're listening music and want to filter the playlist to a specific artist. That's easy, just issue: "mpvc save | awk '/artist/' | mpvc load", then, the playlist is good and want to save it for later use: "mpvc autosave good.m3u", or the good part of the track starts at minute 34, so I can "mpvc time 34m".
For more complex uses, as applying audio/video filters to the running player, things like "mpvc cmd af toggle lavfi=[loudnorm=I=-16:TP=-3:LRA=4]" are possible.
The mpvc-tui covers a similar purpose: that last song/artist/section was good, what's the name?, start mpvc-tui and have a quick look at the playlist, or status.
And as you say, I also found out that I didn't require much fancy from a media player, just a player that worked, and a bit of shell scripting to cater my needs.
Previous HN: https://news.ycombinator.com/item?id=34013149
reply