mpv to show currently active keybindings in OSD

Created on 5 Oct 2017  Â·  31Comments  Â·  Source: mpv-player/mpv

Is there a way that mpv will show active keybindings from input.conf as osd message. It's hard to remember rarely used keybindings. If there's a way to show them as osd , it'll be easier to see keybindings without opening input.conf

Most helpful comment

@negativeions

HEY

MY OPINION > YOUR OPINION

AND I THINK YOU SHOULD GO SUCK A COCK

All 31 comments

mpv --input-test --force-window --idle

I wanted list of all enabled keybindings.

mpv --input-test --force-window --idle

May not be correct at times. Possibly for no-input-default-bindings in my mpv.conf

Well, you could use the whole content of input.conf together with show-text or something..

With some unconeventional formatting, presumably. This is not a text editor. But you could probably bend something together with ASS codes, maybe.

or have a GUI for it like normal people.

I'm not sure what you mean

you could use the whole content of input.conf together with show-text or something

I thought about that. It's not efficient. I have edit different portions separately.

@negativeions mpv doesn't come with an official gui.

@negativeions maybe a player like VLC is more the right choice for you.

Your luser opinion is not gospel.

@negativeions

HEY

MY OPINION > YOUR OPINION

AND I THINK YOU SHOULD GO SUCK A COCK

Also, duplicate of #2590.

@negativeions use bomi or VLC and be done with it. Why the butthurt? Why do you even care?

if someone is willing to do a GUI, let 'em

that's why there are many GUI frontends on the wiki page to choose from.

Alternatively, maybe you should learn how to use a computer, you massive pleb.

lol ok fight me 1v1 bitch I'll sock you in the mouth

Being an asshole won’t get you a better player any sooner though. You can’t just go around insulting people and their work, telling them what to do in their free time. You are not our employer, either.

(That’s beside the point, but we’re also having bigger trouble on macOS than a fancy GUI right now. Hard enough to get basic playback right on the latest versions of that buggy garbage. Which is one of the reasons why there are so few good players on there in the first place…)

Okay, y'all need to cut the kindergarten crap in here..

Well, it seems by per using this issue tracker that Windows users are much less entitled, so there's that.

but mpv is a good player :(

My point being that we Windows users, know it's garbage. It's public knowledge for a very long time.

It's a fricking ASCII text file. The docs are pretty much excellent. You need to put a little bit more effort in it.

macOS is buggy garbage? And windows is any better?

Completely beside the point.

Okay, I give you that this is something the average end user usually can't know, so I'll explain it here in a concise variant:

The problem media players in general and mpv specifically have with macOS, and that is currently being worked on by many hard-working volunteers on this project on here, is that Apple decided to ditch their support for OpenGL, which means that users on macOS are stuck with an almost ancient version of that API. Which sucks, because it makes cross-platform support a really nasty pain in the ass..

HALP HOW DO I USE ME MAC IT NO WORK

Working hard on that "toxicity" in tech etc. pp. 🙄

Hey, I was just trying to help..

The dude arrived at the issue tracker with a very clear goal on his mind, judging by all his opened issues history. He never asked for help in resolving the hurdles he was facing as a end-user in a sensible manner. His whole thing seems to be the lack of a fricking GUI, wth really.

@negativeions

Do you need to learn how to operate a film/digital projector when I go to the theatre to watch a movie? Do I need to learn how to use dentist tools when I want to get my teeth checked?

Maybe you should pay somebody to use mpv for you, like you do when you go to a movie theater or the dentist.

You dumb fuck.

I can be a mpv chauffeur, cheap hourly rates!

@negativeions
For me mpv is user friendly precisely because it has no GUI. No, I am serious.
I have one document which describes how to do everything, one file with config, one file with keybindings. I can edit the files however I want (gedit, vim, notepad.exe). I can search the documentation however I want. With GUI like mpc-hc I'd have to search through many tabs and checkboxes aimlessly until I find the option that interests me. That's not going to work in case of mpv because of sheer amount of its configuration parameters. (At very least you'd get a blob such as Miranda IM, whose GUI was a complete mess and I always lost half an hour there whenever I wanted to change something.)

For developers, it also means they can focus on important things, not needing to invest their time and energy into integrating UI toolkits such as GTK or QT / implementing hundreds of UI controls. Instead, they offer a well-designed config mechanism. They can also just offer the most important stuff (volume control, seek bar etc.) and OSD with libass.

I believe it's a very elegant solution. If mpv was to get menu bars and windows, I'd see them only as bloatware and be painfully aware how that GUI can't ever be capable of controlling even half of the config parameters due to their number.

I understand mpv is not for everyone, but really, why shitpost here? I seriously urge you to look something that fits your expectations more - be it VLC or one of the aforementioned frontends on the wiki (I didn't look through them). I don't know why you're saying VLC is so bad. (regressions will be eventually fixed, mpv has them too.) mpv isn't some magical video player that will magically render your 240p video in 1080p quality. At its core, it's just an interface to your video card's OpenGL, just like VLC is. So I really don't know why you're saying "I want to use mpv but I can't". The reason why "you can't" use it is because you're not appreciating mpv's biggest feature, which is its simplicity of config, its simplicity of design and the places that simplicity can take you. But if you dismiss that feature, what's left then? Why would you want to use it?

@rr- post brings me back to 1997 when I bought my first Linux book and learned that pretty much all settings for programs in the *nix world were made by editing ASCII text files. You run a website that serves its contents with Apache and you need to change a simple setting? Just edit you apache.conf file. A simple ASCII text file!

I was gobsmacked for life. It wasn't long before I read in the same book about RFCs and then started telneting into POP3 servers...

I have no idea what's going on in this thread; but if you want mpv to absolutely never implement a feature ever, this is certainly the best way of accomplishing that.

Also, @rr- hits the nail on the head. mpv is designed to be a CLI media player and it will stay a CLI media player; because this is its main selling point.

To be fair, this user interface concept is alien to users of operating systems like Windows or macOS. Those platforms are not first-class citizens to mpv, and likely never will be. Sure it might work just as well as on *nix, but it blatantly ignores platform user interface guidelines. Writing a GUI around mpv is not that hard, but there are still very, very few people with the skills and incentive to do so, and they’re clearly not part of the core mpv development team—which probably couldn’t design a friendly enough, tested UI to save their lives because they simply like mpv the way it is, so let’s leave that to people who would actually use such a thing.

On a general note, we like to leave GUIs to other projects (which can embed libmpv) because we don't want to depend on big GUI frameworks, or deal with them, or even handle general UI programming issues.

Was this page helpful?
0 / 5 - 0 ratings