midi-controller-files
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
midi-controller-files [2021/09/11 16:07] – [Other ways to use "no" lines] shane | midi-controller-files [2023/05/08 18:59] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== MIDI Controller Files ====== | ====== MIDI Controller Files ====== | ||
**This page describes a Unify feature which is both ADVANCED and EXPERIMENTAL. Limited support will be provided. Please do not attempt to follow these instructions unless you are sure you understand them.** | **This page describes a Unify feature which is both ADVANCED and EXPERIMENTAL. Limited support will be provided. Please do not attempt to follow these instructions unless you are sure you understand them.** | ||
- | |||
- | **This version of the page is valid for Unify v1.4.x only.** | ||
The stand-alone Unify app can make use of // | The stand-alone Unify app can make use of // | ||
Line 126: | Line 124: | ||
* It is necessary to use the //Korg Kontrol Editor// app to CHANGE the controller configuration, | * It is necessary to use the //Korg Kontrol Editor// app to CHANGE the controller configuration, | ||
- | **These new parameters are highly | + | **These new parameters are still experimental** and should not be considered " |
==== Setting up the Korg nanoKontrol 2 ==== | ==== Setting up the Korg nanoKontrol 2 ==== | ||
Line 245: | Line 243: | ||
==== Pads bank A section ==== | ==== Pads bank A section ==== | ||
- | The MPD2018 also supports three banks of MIDI-command assignments for the sixteen physical | + | The MPD2018 also supports three banks of MIDI-command assignments for the sixteen physical |
The first three " | The first three " | ||
Line 282: | Line 280: | ||
- Some devices (the KORG nanoKONTROL2 is a major example) generate MIDI CC messages which are normally reserved for special purposes, e.g. CC#0 (default assignment for the first slider) would normally be interpreted by Unify and most other MIDI instruments as //MIDI Bank Select//. With MIDI controller files, you can effectively intercept such messages, and specify exactly how they are to be interpreted, | - Some devices (the KORG nanoKONTROL2 is a major example) generate MIDI CC messages which are normally reserved for special purposes, e.g. CC#0 (default assignment for the first slider) would normally be interpreted by Unify and most other MIDI instruments as //MIDI Bank Select//. With MIDI controller files, you can effectively intercept such messages, and specify exactly how they are to be interpreted, | ||
+ | ===== Suppressing specific MIDI messages ===== | ||
+ | **As of Unify v1.9**, you can put the word // | ||
+ | |||
+ | This was added in response to feedback from a user who found that a Roland D-50, used as a MIDI controller, sends a MIDI CC#123 (all notes off) message when the last key is released, and this can cause problems with some plug-ins. Adding the line | ||
+ | |||
+ | cc 123 suppress | ||
+ | to the active MIDI Controller file will cause this message to be suppressed (filtered out). | ||
midi-controller-files.1631376459.txt.gz · Last modified: 2023/05/08 18:59 (external edit)