mpv-player / mpv-player/mpv

No key binding found for arrows keys on Windows tablet keyboard

Open
#15,993 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

os:win
Dominant language
C
Stars
37k
Forks
3.5k
Avg merge
1d 10h
Merged PRs (30d)
22

Description

mpv Information
mpv v0.39.0-929-gee07dcf4c Copyright © 2000-2025 mpv/MPlayer/mplayer2 projects
 built on Mar  2 2025 00:10:18
libplacebo version: v7.350.0 (v7.349.0-38-g02f4f98-dirty)
FFmpeg version: N-118594-ge8d4c5598
FFmpeg library versions:
   libavcodec      61.33.102
   libavdevice     61.4.100
   libavfilter     10.9.100
   libavformat     61.9.107
   libavutil       59.58.100
   libswresample   5.4.100
   libswscale      8.13.100
Other Information
- Windows version:
  Windows 10 32-bit (Microsoft Windows [Version 10.0.19044.5487])
  Windows 11 (Microsoft Windows [Version 10.0.26100.3194])
- GPU model, driver and version:
  Intel HD Graphics on Intel Atom Z3735G
  Intel UHD Graphics on Intel Core i3-8145U
- Source of mpv: https://github.com/shinchiro/mpv-winbuild-cmake/releases/tag/20250302, i686 and x86_64-v3
- Latest known working version: n/a
- Issue started after the following happened: n/a
Reproduction Steps
  1. Enable touch keyboard on taskbar: https://support.microsoft.com/en-us/topic/enable-and-disable-the-touch-keyboard-in-windows-e2b05375-908d-45ec-b7f7-729349a10c7a
  2. Start mpv and open the touch keyboard from the taskbar
  3. Type ` to activate REPL
  4. Type the arrow keys on the touch keyboard
Expected Behavior

It should work like the old accessibility On-Screen Keyboard. It seems they use different key codes for some reason.

Actual Behavior

Shows error No key binding found for KP_{LEFT,UP,RIGHT,DOWN}

Windows 10 32-bit: Image
Windows 11:

Image

Log File

output.txt

Sample Files

https://www.youtube.com/watch?v=dQw4w9WgXcQ

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start by reproducing the issue in mpv's REPL with the Windows touch keyboard, then trace how its arrow-key input becomes KP_* names and compare that with the accessibility On-Screen Keyboard behavior. Done means the touch-keyboard arrows are recognized by the expected bindings without the reported error.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.