Before you get started with microtonal music, you will need two things:
- Find a plugin (VST/whatever), which supports microtonal temperaments: here’s a list with some examples.
- Set up keyboard mapping for that instrument: this needs to be done both in the plugin’s settings and in the host (this app), to overcome the limits of MIDI 1.0. The piano roll works as a microtonal keyboard with a wide key range from 0 up to 2048, and it needs to map every key over 16 MIDI channels, of 128 keys each; then those MIDI messages are sent to the plugin, which needs to know how to interpret them, or how to map them back from multi-channel data.
You can skip the instrument setup steps, if you only want to get familiar with microtonal scales. The default instrument in Helio is silly, but it works out of the box with all temperaments with no setup required, and should give you some idea of how things work.
Otherwise, once you’ve added an instrument to the stage, just pick “Edit keyboard mapping” menu item. The “keyboard mapping” here means mapping MIDI events routed from Midi In node to the plugin node(s).
Note: this describes the key mapping on the host side, but you’ll need to set it up on the plugin’s side as well. Unfortunately, can’t help you with that, as it depends on the plugin, but here’s an example.
The page allows to adjust key mappings manually and preview the mapped keys by clicking on them. The upper limit is set to 2048 keys - this is the maximum number of keys that can fit into 16 MIDI channels. Which would be enough to handle temperaments of size up to 192-EDO:
Some additional actions are available via context menu:
- reset to the default mapping (modulo based),
- load custom channel mapping(s) in Scala .kbm format,
- copy/paste the mapping into/from the system clipboard as a string in Helio’s own format.
While you can set up virtually any custom mapping by hand, there are a couple of (sometimes) more convenient ways, described below.
Note: don’t confuse Scala keyboard mapping (.kbm files) with Scala tuning files. The latter are not of much use for the piano roll, since it doesn’t care about cents and ratios - those are only needed by instruments.
Helio can load Scala keyboard mapping(s), including multichannel mappings which consist of a set of single mapping files with the same name followed by an underscore and a channel number. When you pick a .kbm file, Helio will search for “same_name_*.kbm” files to try to determine whether or not there are multiple channels’ mappings, and try to load them all.
Keep in mind that, on the sequencer side, the mapping will be reversed compared to the same mapping on the instrument side. The piano roll acts like a microtonal keyboard, which needs to overcome the limits of MIDI channels, and thus is mapping all the keys, which are above 127, across multiple channels.
// TODO examples
I think that Scala kbm format is obscure and unintuitive, so let me reinvent the wheel one more time and introduce another keyboard mapping format, supposed to be shorter, cleaner and kind of human-readable. You can use it on the keyboard mapping page by simply copying and pasting the mapping as a string.
Let’s start with an example. The entire multi-channel mapping for Pianoteq 31-EDO could be written like this:
0:0/15,31+ 31:0/16,31+ 62:0/1,31+ 93:0/2,31+ 124:0/3,31+ 155:0/4,31+ 186:0/5,31+ 217:0/6,31+ 248:0/7,31+ 279:0/8,31+ 310:0/9,31+
Or, same, but one octave lower:
0:0/14,31+ 31:0/15,31+ 62:0/16,31+ 93:0/1,31+ 124:0/2,31+ 155:0/3,31+ 186:0/4,31+ 217:0/5,31+ 248:0/6,31+ 279:0/7,31+ 310:0/8,31+
- starting from key
0of the piano roll, map it to the key
14, then map the next
31keys in a sequential manner: for example, key
2/14, and so on,
- starting from key
31, map it to the key
15, and, again, map the next
- and so on.
First, the format assumes the default modulo-based mapping:
- keys 0..127 are mapped as they are to channel 1,
- keys 128..255 are mapped as 0..127 in channel 2, and so on.
Everything that differs from the default values is serialized. The serialized mapping is just a string divided by whitespaces into chunks.
Chunks follow this pattern:
base:key/channel,key2/channel2,key3/channel3. Which means:
basekey in the sequencer, the specified
key/channelwill be sent to the instrument,
- then, for
base + 1key in the sequencer, the next key and channel will be sent, and so on.
If each next key just incrementally moves by 1, the chunk could be shortened like this:
// TODO more examples (if you have set up keyboard mappings, which work well for some of your instruments, feel free to share them to improve these docs)
The most straightforward way to start playing around with microtonal scales is to convert any of your twelve-tone pieces (or a new project) into other temperament.
The project refactoring menus provides two choices:
"Change temperament"command will simply switch the piano roll highlighting and update key signatures,
"Convert to temperament"command will, in addition, update notes: the conversion is made using chromatic scale approximations - see the temperament model description - Helio will use these chromatic maps as the “least common denominators” among temperaments to convert from one to another.
All scale-related tools will only show those scales with octave size matched with current temperament (the piano roll doesn’t distinguish EDO’s from non-EDO’s, all that matters is the number of keys in octave, highlighting, key names, etc).
The default built-in temperaments list includes the most popular ones, 12edo, 22edo and 31edo.
And the built-in scales list only includes 7-tone scales for each of those temperaments, because there are several pieces of the app which still assume working with diatonic scales, e.g. the chord tool or the arpeggiator tool, - so given that limitation, using these tools with any built-in temperament or scale would make at least some kind of sense.