Keyboard media play keys not working

msch1979msch1979 Member
in Bugs

Hi again.

Text and testing on my local computer supported by Notion KI (GPT 5.6 Sol). The problem seems to be a few months, but finally had the time to test many scenarios in detail.

Bug report:

  • Environment: Windows 11, Logitech Signature K650 connected through its USB receiver, Logi Options+ installed.
  • The keyboard and receiver are working correctly. An AutoHotkey v2 test detected all three standard events: Media_Play_Pause, Media_Prev and Media_Next.
  • Stopping all Logi Options+ processes, including its update process, made no difference.
  • In a second AutoHotkey test, F10, F11 and F12 were mapped to the standard Windows media commands. With the Astiga Windows app completely closed, these commands correctly controlled VLC, Windows Media Player, YouTube videos in Chrome and videos in IrfanView.
  • As soon as the Astiga Windows app is running, none of those applications respond to the same media commands. Astiga itself does not respond to them either. Closing Astiga immediately restores media-key control in the other applications.
  • Volume up, volume down and mute continue to work and are not affected.
  • The Astiga web player shows a related problem. With the Windows app closed, media keys control YouTube in Chrome but not the Astiga tab. Even when the Astiga tab is focused and playback was started manually there, pressing Play/Pause continues to control the YouTube video in another tab instead of pausing Astiga.

The results exclude the keyboard hardware, USB receiver, Logi Options+ key assignments and Chrome alone as the primary cause. They suggest that Astiga either does not register a usable Windows/Chrome media session or captures global media commands without processing or releasing them correctly. This may affect both the Windows wrapper and the underlying web player.

Expected behaviour:

  • The Astiga web player and Windows app should respond to Play/Pause, Previous and Next when Astiga is the active or most recently used media player.
  • When Astiga is idle or running in the background, it should not prevent other applications from receiving global media commands.
  • If exclusive media-key handling is intentional, the Windows app should provide an option to disable it.

Questions for support:

  • Is this a known issue with the current Windows app or web player?
  • Does Astiga use the browser Media Session API and Windows System Media Transport Controls for these commands?
  • Is there an existing setting or workaround to release or disable Astiga's global media-key handling?


Comments

  • gravelldgravelld Administrator

    Thanks - it hasn't been recorded, but I'll write up a ticket and I'll answer your questions when I analyse with more time.

  • gravelldgravelld Administrator

    Confirmed issues at the web app (not correctly emitting playback status so that keyboard handlers can route to it) and Electron (almost the opposite - takes exclusive use of hardware media keys and ignores them).

    Answers to questions:

    • As above, it wasn't recorded before, but is now.
    • We do use Media Session, with the caveat above. We don't use SMTC, instead the framework for the app (Electron) uses globalShortcut which bypasses SMTC.
    • No workarounds - the exclusive capture issue is fixed by closing the app (as you reported).
Sign In or Register to comment.