Kontrol master editor Patch#

The shortcut is implemented by creating a folder with the extension. вЂњChange screen resolutionвЂќ) and they will get the right control panel options as search result. This allows users to type what they want to do (e. This matches the behavior of вЂњnoвЂќ lines in Unify versions prior to v1.6.2, when support for numeric values was added.The functionality that was discovered and named Master Control Panel or God Mode was designed as the base folder for searching control panel options using the new start menu's search function. These last three вЂњnoвЂќ lines don't have a numeric value at the end, so Unify internally uses the default value 1.0, which is ideal for triggering binary and toggle-type parameters. Tapping these buttons thus allows you to switch each of these layers on and off in any combination, separately from the three specific combinations set up by the Macro8 knob. These allow toggling (switching on and off) the MIDI-enable state of the INST1, INST2, and INST3 layers individually. The next three вЂњnoвЂќ lines are for pads 9, 10, and 11, on the second row of the MPD218's pads array.

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.

Kontrol master editor Patch#

See the Patch Variations page for more details. These values were experimentally chosen, to correspond to three different Patch Variations defined using new features added in Unify 1.6.0 and refined in later versions. Pad 15 sets it to 0.67, about two o'clock. Any parameter paths which don't correspond to actual layers simply won't do anything. (If you were to remove the 0.8 scale factor, or change it to 1.0, the level would go all the way to +10 dB.)Д«ecause Unify safely ignores вЂњinvalidвЂќ linked parameter-paths, this mapping of eight sliders will work just fine even for patches where you have fewer than eight INST layers. As a result, the mix-level control for the INST1 layer will move, but only up as high as 80% (0.8) of the maximum, which corresponds to exactly 0 dB. So this first line indicates that when you move the first of the nanoKONTROL2's sliders, the MIDI CC#0 message which results is interpreted as a value between 0.0 (slider all the way down) and 0.8 (all the way up), which is then assigned to the linked parameter 'inst/1/mixLevel'. The rest of the line is a parameter path, the same as you would use for parameters linked to Unify's Macro knobs. The 0.8 indicates that the fractional value will be scaled to the range 0.0-0.8 before being used. The cc 0 part identifies MIDI CC#0, which is sent by the nanoKONTROL2's leftmost slider by default. Unify interprets the value range 0-127 as a fraction 0.0-1.0, and each of the lines in these sections indicates what it does with these fractional CC values. MIDI continuous controllers (CC's) send out messages with associated values between 0 and 127. If you have used the KORG Kontrol Editor app to change these assignments, you will have to edit the CC numbers in the file to match. This example uses the nanoKONTROL2's default CC assignments.

The KORG nanoKONTROL2 features eight vertical sliders and eight rotary knobs, each of which generates MIDI CC messages using a different CC number. # IT WILL NOT WORK WITH THE DEFAULT/FACTORY SETUP!Д¬c 71 unify/midiEnable/8 Comments and Controller name # NOTE THIS WILL ONLY WORK IF THE NANOKONTROL 2 IS CORRECTLY SET UP. # 'R' buttons enable/disable individual layers at the MIDI level. # 'M' buttons toggle the MUTE state of individual layers # 'S' buttons toggle the SOLO state of individual layers # Knobs control AUX1-send levels of 1st 8 layers, up to 80% (0 dB) # Sliders control mix-levels of 1st 8 layers, up to 80% (0 dB) # The first non-blank, non-comment line must be the MIDI controller name # 'no' lines have a MIDI note number followed by an OSC control path. # optionally followed by a maximum value, e.g.

# 'cc' lines have a MIDI CC number followed by an OSC control path, # Active lines can begin with 'cc' or 'no'. NanoKontrol mix and enable.txt # This is a comment, and blank lines are also ignored We'll look at its various parts individually in the sections below.

The following is an example of a MIDI controller file to set up a KORG nanoKONTROL2 MIDI device to control mix and effect-send levels and MIDI enablement for up to eight layers.