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/03/18 15:10] – [final sections] shane | midi-controller-files [2023/05/08 18:59] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 124: | 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 ==== | ||
+ | |||
+ | To set up a //Korg nanoKontrol 2// controller for controlling the MIDI enable/ | ||
+ | |||
+ | Note that you can always reset your // | ||
+ | - Close //Korg Kontrol Editor// (or any other program using the // | ||
+ | - Disconnect the USB cable from the // | ||
+ | - Hold down the PREV TRACK, NEXT TRACK, and CYCLE buttons while re-connecting the USB cable from the computer. The transport buttons (except CYCLE) will blink when the factory-set default state has been restored. | ||
+ | |||
+ | To set up your // | ||
+ | - Quit Unify (or any other program using the // | ||
+ | - Download and unzip this file: {{ :: | ||
+ | - Double-click the // | ||
+ | - Use the **Communication > Write scene data** function to upload the scene data to your // | ||
+ | - Quit the //Korg Kontrol Editor// program. | ||
+ | - Make sure the // | ||
+ | - Run the Unify stand-alone app, load any patch with several INST layers, and test the " | ||
+ | |||
+ | **NOTE** When Unify loads a patch, all INST layers will normally be enabled (not darkened and responsive to MIDI), but some of the " | ||
+ | |||
+ | At this time, Unify does not do two-way communication with MIDI controllers, | ||
+ | |||
===== Example 2: KOMPLETE KONTROL keyboard ==== | ===== Example 2: KOMPLETE KONTROL keyboard ==== | ||
Line 167: | Line 191: | ||
==== " | ==== " | ||
- | You may have noticed that the comments in the first example mentioned " | + | You may have noticed that the comments in the first example mentioned " |
+ | |||
+ | The next example illustrates " | ||
+ | |||
+ | ===== Example 3 (partial): Akai MPD218 ===== | ||
+ | The [[https:// | ||
+ | |||
+ | <file text Akai MPD218.txt> | ||
+ | # First non-blank, non-comment line is the MIDI controller name (or a prefix thereof) | ||
+ | MPD218 | ||
+ | |||
+ | # Knobs bank A | ||
+ | cc 3 | ||
+ | cc 9 | ||
+ | cc 12 | ||
+ | cc 13 | ||
+ | cc 14 | ||
+ | cc 15 | ||
+ | |||
+ | # Knobs bank B | ||
+ | cc 16 | ||
+ | cc 17 | ||
+ | cc 18 | ||
+ | cc 19 | ||
+ | cc 20 | ||
+ | cc 21 | ||
+ | |||
+ | # Knobs bank C | ||
+ | cc 22 | ||
+ | cc 23 | ||
+ | cc 24 | ||
+ | cc 25 | ||
+ | cc 26 | ||
+ | cc 27 | ||
+ | |||
+ | # Pads bank A: first three pads on top row | ||
+ | no 48 | ||
+ | no 49 | ||
+ | no 50 | ||
+ | |||
+ | # Pads bank A: first three pads on second-from-top row | ||
+ | no 44 | ||
+ | no 45 | ||
+ | no 46 | ||
+ | </ | ||
+ | |||
+ | ==== Knobs sections ==== | ||
+ | The MPD218 has six // | ||
+ | |||
+ | The knobs are set up to control the first eighteen of Unify' | ||
+ | |||
+ | ==== Pads bank A section ==== | ||
+ | The MPD2018 also supports three banks of MIDI-command assignments for the sixteen physical pads, yielding a total of 48 logical pads, but as this is only a partial tutorial example, there are only six " | ||
+ | |||
+ | The first three " | ||
+ | * Tapping pad 13 sets the knob value to 0.0 (all the way to the left) | ||
+ | * Pad 14 sets it to 0.35, about the ten o' | ||
+ | * Pad 15 sets it to 0.67, about two o' | ||
+ | |||
+ | These values were experimentally chosen, to correspond to three different [[patch-variations|Patch Variations]] defined using new features added in Unify 1.6.0 and refined in later versions. See the [[patch-variations|Patch Variations]] page for more details. The upshot of all this is that tapping pad 13 activates the INST1 layer of the patch, pad 14 switches to the INST2 layer only, and pad 15 to the INST3 layer. | ||
+ | |||
+ | The next three " | ||
+ | |||
+ | These last three " | ||
+ | |||
+ | ===== MIDI keys can do more than play notes! ===== | ||
+ | The six " | ||
+ | |||
+ | The example refers to a drum-pad controller, but **you can do the same thing using any MIDI keyboard** in a live-performance setup. | ||
+ | * Maybe you don't have a pad controller, but you do have a small secondary MIDI keyboard. You could set up a MIDI controller file to allow you to switch layers on and off (or mute/solo layers, etc.) using keys on that little keyboard. | ||
+ | * If you have just one 88-key master keyboard, you might want to set up a handful of notes at the very bottom or top end (which you don't expect to actually use to play notes) to trigger other functions in Unify. | ||
===== How Unify works with MIDI controller files ===== | ===== How Unify works with MIDI controller files ===== | ||
Line 185: | 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.1616080254.txt.gz · Last modified: 2023/05/08 18:59 (external edit)