Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Midi transport commands #24854

Open
1 of 4 tasks
oemsysadm opened this issue Jan 22, 2025 · 1 comment
Open
1 of 4 tasks

[Feature Request] Midi transport commands #24854

oemsysadm opened this issue Jan 22, 2025 · 1 comment

Comments

@oemsysadm
Copy link

Feature Request Type

  • Core functionality
  • Add-on hardware support (eg. audio, RGB, OLED screen, etc.)
  • Alteration (enhancement/optimization) of existing feature(s)
  • New behavior

Description

Expand current Midi capability with the Start (0xFA), Continue (0xFB), and Stop (0xFC) commands.

https://wiki.cockos.com/wiki/index.php/MIDI_Specification

It might also be useful to get support for Program Change and Midi Clock functionality - including the ability to act as a Midi Clock source, and receive Midi Clock from other devices.

@b4ssrp
Copy link

b4ssrp commented Feb 1, 2025

You actually can use midi_send_byte(&midi_device, 0xF{A/B/C}); or midi_send_{continue/start/stop}(MidiDevice* device); in process_record_user() function in your keymap.c file.

You just have to add a custom keycode as in qmk custom_quantum_functions.md.

Afaik there is no keycodes for midi transport already availabe like for midi notes (MI_C, MI_Ds).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants