这是indexloc提供的服务,不要输入任何密码
Skip to content

input-default-bindings affects the key bindings that can't be overridden via input.conf #17001

@github-account1111

Description

@github-account1111

mpv Information

mpv v0.40.0-423-g454d9eb36 Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
 built on Oct 30 2025 00:12:05
libplacebo version: v7.357.0 (v7.351.0-89-g06992a5-dirty)
FFmpeg version: N-121582-g746650dfe
FFmpeg library versions:
   libavcodec      62.17.100
   libavdevice     62.2.100
   libavfilter     11.9.100
   libavformat     62.6.101
   libavutil       60.16.100
   libswresample   6.2.100
   libswscale      9.3.100

Other Information

- Windows version: 10 22H2
- GPU model, driver and version: Radeon 780M, 32.0.22021.1009
- Source of mpv: https://github.com/shinchiro/mpv-winbuild-cmake/releases
- Latest known working version:
- Issue started after the following happened:

Reproduction Steps

  1. input-default-bindings=no in input.conf
  2. Open a video and press a media key

Expected Behavior

Media controls control playback.

Actual Behavior

Nothing.

input-default-bindings description says:

Enable default-level ("weak") key bindings (default: yes). These are bindings which config files like input.conf can override.

... which makes sense from a whitelist perspective (being able to selectively reenable things after disabling everything).

The problem is media control keys (#14338) can't be defined via input.conf, yet are affected by input-default-bindings. So when I use input-default-bindings=no, unlike with all the other keys which I can manually define via input.conf, I can't use media keys, period.

Log File

output.txt

Sample Files

No response

I carefully read all instruction and confirm that I did the following:

  • I tested with the latest mpv version to validate that the issue is not already fixed.
  • I provided all required information including system and mpv version.
  • I produced the log file with the exact same set of files, parameters, and conditions used in "Reproduction Steps", with the addition of --log-file=output.txt.
  • I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
  • I attached the full, untruncated log file.
  • I attached the backtrace in the case of a crash.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions