This function extends all layer modes (except push) with octave, velocity, or note length splits.
It is quite frustrating that the normal TNR limits the “playable” range of one block to the range of the selected scale and the octave setting. This new feature allows the octave to be one higher, or one lower, than the selected setting dynamically.
The SWL-01 chip can actually produce a much more interesting range of notes than the TNR will allow it, in particular by allowing modification of the note velocity away from the default of 100. This new feature allows the velocity to be changed per note (from 3 options), allowing, for example, more musically dynamic drums and other effects.
Finally, this feature allows the sound length to be dynamically halved, or doubled, allowing a larger range of expression.
This function is a property of the layer, and is selected under the layer menu.
These features - only one of which can be selected at a time - act to sacrifice the top 3 pitched notes of the block, and use these to select which of the three octaves/velocities/sound lengths are wanted. Thus the note range is “split” into normal instrument notes (bottom 13) and expression (top 3).
For layers where pitch increases vertically - i.e. score, random, draw - the top 3 rows of the TNR adjust the octave/velocity/note length. For layers where pitch increases horizontally - i.e. bounce, solo - the rightmost 3 rows of the adjust the octave/velocity/note length. This feature is not implemented for push.
The middle of the three split notes represents the “baseline” octave, velocity (100) or note length, as set by the layer. The top of the split represents +1 octave, +27 velocity (127) and double default note length. The bottom of the split is -1 octave, -27 velocity (73) or 1⁄2 note length.
The split modified is retained until the next split modifier, i.e. the split latches. This is easily seen in score mode, and is fun to use in bounce mode, using the bounce to vary the velocity randomly.
In score mode, a split directive in the same column as a note will strictly apply (i.e. before) that note plays. This is required in order to make “chords” in score mode behave predictably. For the other layer types, this has not been enforced, and depends on the order in which the notes were originally entered.
Loading songs/blocks saved in previous releases may confuse the split code, and unexpected results may occur.
First included in A015.