diff options
Diffstat (limited to 'docs/feature_midi.md')
| -rw-r--r-- | docs/feature_midi.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/feature_midi.md b/docs/feature_midi.md index 59ee0114c8..89c6af0508 100644 --- a/docs/feature_midi.md +++ b/docs/feature_midi.md @@ -34,7 +34,7 @@ To enable advanced MIDI, add the following to your `config.h`: If you're aiming to emulate the features of something like a Launchpad or other MIDI controller you'll need to access the internal MIDI device directly. -Because there are so many possible CC messages, not all of them are implemented as keycodes. Additionally, you might need to provide more than just two values that you would get from a keycode (pressed and released) - for example, the analog values from a fader or a potentiometer. So, you will need to implement [custom keycodes](feature_macros.md) if you want to use them in your keymap directly using `process_record_user()`. +Because there are so many possible CC messages, not all of them are implemented as keycodes. Additionally, you might need to provide more than just two values that you would get from a keycode (pressed and released) - for example, the analog values from a fader or a potentiometer. So, you will need to implement [custom keycodes](feature_macros) if you want to use them in your keymap directly using `process_record_user()`. For reference of all the possible control code numbers see [MIDI Specification](#midi-specification) @@ -258,7 +258,7 @@ For the above, the `MI_C` keycode will produce a C3 (note number 48), and so on. <!-- #### QMK Internals (Autogenerated) - * [Internals/MIDI Device Setup Process](internals/midi_device_setup_process.md) - * [Internals/MIDI Device](internals/midi_device.md) - * [Internals/MIDI Util](internals/midi_util.md) + * [Internals/MIDI Device Setup Process](internals/midi_device_setup_process) + * [Internals/MIDI Device](internals/midi_device) + * [Internals/MIDI Util](internals/midi_util) --> |