Synergy is a semi-modular MIDI sequencer.

In a nutshell, its main features are:

  • MIDI event routing, transformation, and monitoring

  • Linear and / or pattern based sequencing

  • Polymetric and polyrhythmic sequencing

  • Multi-instantiable sequencer / processing "nodes"

    • e.g. a "tracker" style sequence editor (features pattern zooming and freely configurable column layouts)

    • Dedicated drum and automation editors

    • Timeline / clip editor (arranger)

  • Advanced preset system for single nodes or complex multi-node setups

  • Standard MIDI file import and export

  • Page-oriented UI that requires very little "mousing"

    • Very few dialog windows to minimize "attention context switching"

    • Fast workflow: Keyboard shortcuts for almost everything

    • Many UI and replay functions can be mapped to MIDI controllers (remote control)

  • Built-in synth editors

    • Roland MKS-50 / Alpha Juno

    • Oberheim Matrix 1000

    • Elektron Analog Rytm (librarian)

    • DSI Prophet 12

Concept and Feature Overview

The main concepts and features of this software are:

  • A hierarchical "node"-based MIDI event flow

    • Nodes are grouped into "pipes"

      • Master pipe output is sent to all pipes

      • Each pipe processes MIDI input / output events separately

        • The output of devices marked as "global" will be available in subsequent nodes

      • The output of all pipes is merged before it is being sent out via MIDI

    • Multi-instancing of nodes

      • Polyrhythmic and polymetric sequencing

      • Node organization / grouping (e.g. drums / bass / lead / chords)

      • Synchronized pattern changes during editing and / or replay

        • e.g. automation node linked to tracker node

        • lctrl-x HOME or END to show dialog and send out program change on auto device A (HOME) or B (END) to all pipes

    • Each node can store up to 127 patterns

  • Nodes can be sequenced by other nodes (A+B "auto devices")

    • Via sequencer-internal MIDI messages (program change, RPN)

    • Common control features:

      • Change patterns

      • Change play offset

      • Mute / unmute tracks

      • Velocity scaling and offset

      • Note duration scaling and offset

      • Note transposition

      • Restart / Reset / Seek

      • Time scaling (speed up / slow down)

      • Clock+Gate signals

    • + other node-specific remote control options

    • Example applications:

      • Create complex rhythms without resorting to sliced sample loops

      • Trigger automation sequence fragments

      • Decouple note and timing information

  • Export standard MIDI files

    • For further processing in other sequencers / DAWs

  • Full (N)RPN support

  • Polyphonic key pressure (aftertouch) support

  • SysEx support

  • Page oriented UI (very few dialog windows)

  • Keyboard-friendly UI

    • Lots of shortcuts

    • Large parts of the application can be used without touching a mouse

  • Mouse-friendly UI

    • e.g. most number edit fields can be used like dials and support undo

  • MIDI input monitor (view RAW or transformed input events)

  • MIDI input mapper / transformer ("morph scenes")

    • Redirect and / or transform MIDI controller input to other MIDI devices

    • 4 parallel "scene" slots with 16 entries each

      • Incoming events are first processed by scene A. The remaining events are then processed by scenes B, C, D.

  • MIDI output monitor (view RAW events)

  • MIDI map contexts

    • Remote-control the application via MIDI

    • Global map context

      • Can be forced by pressing 'g' or by MIDI controller events assigned to the MMC_FORCE_GLOBAL map target

    • Per-page / node map contexts

  • Some nodes support Ableton Push (e.g. for arranging node clips)

  • Generic Ableton Push support: Note / Controller mode

    • Configurable octave

    • Configurable key and mode (major, minor, ..)

    • Dual (horizontal / vertical) and Quad split modes

      • MIDI channel per split region

  • Support for Roger Linn’s Linnstrument128

    • via the "/seq/linnstrument arranger" Script node preset

  • Device name aliases (can load projects on other machines or if the MIDI device names have changed)

  • Device profiles (e.g. for controller names and hardware input type definitions (e.g. buttons))

  • Sequencer-internal virtual MIDI devices (e.g. "play_a", "play_b", ..)

  • Per-project controller aliases

  • MIDI timing clock (configurable per device)

  • MIDI transport control (MMC) (configurable per device)

  • Comment editor (per node and pipe)

  • Autosave (with configurable interval / number of files)

  • OpenGL based user interface (reduced CPU load, especially at higher resolutions)

    • Windowed or fullscreen mode

    • x1..x4 scaling modes

    • Post processing effects (e.g. scanlines, colorization)

    • V-Sync

    • FPS limiter

    • Transparency effects

  • SysEx manager for Elektron Analog Rytm (AnalogRytm node)

  • SysEx editor for Roland Alpha Juno / MKS-50

  • SysEx editor for Oberheim Matrix 1000 (works with early 1988 "black" models)

  • SysEx editor for DSI Prophet 12 synthesizer

Getting Started

Installation

Unpack the downloaded application, then run "synergy.exe".

Tip It is recommended to change the default (app-path relative) project directory (see Settings→Preferences) and point it to some absolute location (e.g. f:/synergy_data/).
Tip After installing new application releases, it is recommended (but not required) to sync the PROJECT_DIR/presets folder and copy any new presets to your custom project directory.

Device Setup

Once the application is running, go to Settings→Device Setup and select the MIDI devices you want to use (tick the "Use" checkbox).

Caution To be on the safe side, choose the devices you want to open, then save the configuration and restart the application (dynamically opening / closing devices usually works fine but in case it doesn’t, save the project and configuration, then restart the app).
Tip

It is highly recommended to assign device alias names since

  • MIDI device names may sometimes change after reconnecting USB devices

  • Non-USB MIDI ports usually have non-descriptive names like MIDISport 4x4 Anniversary In A, for example

Basic device settings

Each MIDI device has a couple of basic settings that are edited via the device table checkboxes:

Name Description

Use

When checked, open and start device

Echo

When checked, copy incoming events back to the default output device (see additional device settings). This option should be enabled when the MIDI device is set to "local off".

Clock

Send MIDI timing clock

Rec

Send MMC record message when MMC recording starts (e.g. start audio recording in DAW when lshift - ENTER is pressed)

Play

Send MMC start message when playback starts (e.g. start audio playback in DAW when ENTER is pressed)

Input device event filter

Each input device has a MIDI message filter that can be configured by clicking the "Input Filter.." button. All ticked message types will be filtered out.

Additional device settings

By clicking a device entry, additional device properties can be edited. These include the device alias name, the corresponding output device (for input devices), note-off mode (output devices only), MIDI cache (when enabled, filter out redundant output controller events), and the Global setting which determines whether events sent to a device will become available in subsequent pipes.

In addition to that, a MIDI synth profile can be selected for each MIDI channel. Synth profiles are used to display more senseful controller and note names in the UI (e.g. "Feedback Amount" instead of just "CC#114"), and classify controller types (e.g. absolute values, delta-type inc/dec rotary controllers, button-type controllers). The controller classification is necessary for MIDI map contexts, e.g. for remote-controlling the application via MIDI.

Finally, profiles are also used to assign synth editors (via the dataClass and formClass attributes). In order to be able to edit a synth with one of the built-in editors (Prophet12, Matrix1000, AlphaJuno), it is required to assign the proper synth profile(s) to the respective MIDI channel(s).

Synergy comes with a number of preset profiles for synths like the DSI Prophet 12, Oberheim Matrix 1000, Roland Alpha Juno, Moog Sub37, Elektron Analog Rytm, and various controllers like the Akai MPK49 or Korg Nano Kontrol.

The profiles are read from ASCII files located in the midi_synth_profiles/ directory which is scanned during application startup. In order to add a new synth profile, duplicate one of the existing profile files that is most closely resembling the new synth / controller, and edit it (it would be nice if you’d send me a copy so I can include it in future releases!).

Last but not least, a device setup can be Project specific, which is mostly useful when using an uncommon hardware setup (e.g. when synths are swapped in and out for a certain project), and / or for virtual MIDI devices.

Virtual MIDI devices (internal)

By default, the application creates 9 virtual MIDI devices that can be used for routing data within the application. Virtual MIDI devices names are enclosed in '<' / '>' and are displayed with a yellow background color.

Keep in mind that, unless a device is configured as "Global", the initial event data is reset in each pipe (e.g. the virtual "<Scratch>" device).

Virtual MIDI device naming scheme

While virtual MIDI device names can be chosen arbitrarily, it does make sense to use a certain naming scheme.

For example, the default project template uses the following internal virtual MIDI device name aliases:

Internal Device Name Alias Suggested Use

<Scratch>

<Scratch>

Temporary events (within pipes)

<internal_1>

<play_a>

Arpeggiated sounds, leads

<internal_2>

<play_b>

Bass

<internal_3>

<play_c>

Chords

<internal_4>

<play_d>

Drums

<internal_5>

<global>

Events available in subsequent nodes

<internal_6>

<playlist>

Node pattern selection / mute / seek control (usually sent from Arranger nodes)

<internal_7>

<control>

Can be used as MIDI mapper output ports for MIDI controllers that only provide input devices

<internal_8>

unassigned

Virtual MIDI devices (external)

In order to exchange MIDI data with other applications, it is recommended to install a virtual MIDI device driver, like for example Tobias Erichsen’s excellent loopMIDI.

Example setup for Propellerhead Reason

In order to sequence and control Reason devices, the following loopback device setup can be used:

Loopback Device Name Alias Suggested Use

reason_master

-

Currently focused device instance + Transport control ("Akai MPK49")

reason_a

a:arps

Bus A: Arpeggiated sounds, leads

reason_b

b:bassline

Bus B: Bass

reason_c

c:chords

Bus C: Chords

reason_d

d:drums

Bus D: Drums

reason_ctl_a

-

Control Surface 1 (remote overrides) (generic "MIDI Multichannel Control Keyboard")

reason_ctl_b

-

Control Surface 2 (remote overrides) (generic "MIDI Multichannel Control Keyboard")

reason_ctl_c

-

Control Surface 3 (remote overrides) (generic "MIDI Multichannel Control Keyboard")

reason_ctl_d

-

Control Surface 4 (remote overrides) (generic "MIDI Multichannel Control Keyboard")

Note Even when the actual master keyboard is not an Akai MPK49, selecting this device profile in Reason will enable MIDI transport controls (e.g. start / stop / record).
Note In practice, a single control surface (reason_ctl_a) will usually suffice since each device supports up to 16 MIDI channels (⇒ around 2000 unique continuous controller numbers).
Tip In Reason, the "Advanced MIDI device" tab is used to map MIDI bus A..D events to the rack devices. Events from the Control Surface devices can be mapped to device parameters via the "remote override" feature.
Tip

In order to keep track of the Reason "remote override" controller mappings, it is highly recommended to name the mapped controllers in Synergy via the CtlTag page.

In order to do so, press ` on US keyboards or ^ on german keyboards, then click Add to name the last seen controller.

Naming controllers this way will override default MIDI synth profile controller names (i.e. useful in many cases, not just with Reason).

MIDI input and output devices

One important thing to understand is that all sequencer nodes operate on output devices only.

In the early days of MIDI, regular serial ports were used for data exchange and the list of inputs and outputs was always symmetrical since each (physically present) port served as both an input and output.

Since the advent of USB MIDI and virtual MIDI devices, these I/O port lists are not necessarily symmetrical anymore. A USB MIDI controller for example may provide several input ports and no output ports, other devices may only have output ports, and so on.

In order to control nodes with MIDI controllers, the controller events need to be transformed to output devices, which can either be actual output devices (e.g. synthesizers), or virtual output devices (e.g. for controllers that don’t provide an actual output device).

Record and Play events

Even though all events processed by sequencer nodes will be "output events", i.e. associated with output devices, a distinction between "record" and "play" events will still be made.

"Record" events are events received from actual input devices (e.g. MIDI controllers). When these events are processed by sequencer nodes, they will remain "record" events.

"Play" events are events that have been synthesized by sequencer nodes (e.g. by playing back a Tracker pattern).

This separation is necessary to distinguish event origins when e.g. using MIDI learn functions while the replay is running.

MIDI Mapper (morph scenes)

All incoming input events are routed through the MIDI Mapper (see Input→MIDI Morph Scenes, tap ` twice (^ on german keyboards)), whose job it is to transform input to output events.

The MIDI mapper supports eight "groups" (A, B, C, D, E, F, G, H), and each group supports up to 16 "scenes" of which one can be active at a time. Groups / scenes can be selected either via the keyboard (F3/F4, F5/F6, F7/F8, F9/F10 (A..D), and lalt-F3/F4, lalt-F5/F6, lalt-F7/F8, lalt-F9/F10 (E..H)), or by assigning MIDI controllers to the global GLOBAL_SCENE_* map targets.

Incoming MIDI events will first be processed by group A, and all events that do not match any of the map entries in the active scene of group A will be handed over to group B, and so on.

Note For example, in order to control different synths with a single master keyboard, several scenes can be used, each with the same source filter(s) but different destination(s).
Tip Scene selection can be remoted-controlled via the global MIDI map context (see GLOBAL_SCENE_* targets)

Most of the time, event processing in the MIDI mapper involves only basic copy operations where the input event type matches the output event type.

It is possible, however, to morph event types (e.g. NRPN to CC), or transpose / remap / discard certain event values / ranges.

It is also possible to match only certain input values or ranges, or clip them. This can be used to create keyboard splits, for example.

Tip Keep in mind that all incoming events will be processed by sequencer nodes, which allows for much more sophisticated event transformations (e.g. via ModMatrix nodes).
Tip Also keep in mind that the output of the "master pipe" (the first pipe) will be made available to all other pipes. For this reason, it is usually preferable to place any input-processing nodes in the master pipe.

MIDI Map Contexts

Each UI page and node editor is associated with a MIDI Map Context that can be used for remote-controlling application features via MIDI input events (before they are processed by the MIDI mapper).

In addition to that, a global map context exists (see Input→UI Global) that is available everywhere but has lower priority than the page or node editor map contexts.

It is possible to force the global context by holding down g or by assigning a MIDI controller to the global MMC_FORCE_GLOBAL map target.

At the time of writing (early 2018), Synergy supports over one thousand map targets, which are too numerous to list here (todo!).

Some interesting targets include:

  • Transport Control (start / stop / record / song position / song markers / loop mode and region)

  • Song speed (BPM, tap)

  • UI navigation (e.g. page selection, input focus, value editing, and basic yes / no dialog responses)

  • Node navigation (prev / next pipe / node)

  • MIDI Mapper scene selection

  • Input controller utilities (discard, collect, resend)

  • Ableton Push mode (MMC / kbd / ctl / usr)

  • Ableton Push Arranger clip-matrix mode configuration

  • Pattern selection (during node editing)

Tip When mapping targets to Ableton Push input events, the input event often determines the pad number for bidirectional feedback (pad colorization and / or rotary encoder labels)
Tip press lctrl - m to edit the map context of a UI page or node editor

Push and Linnstrument MIDI controller support

Ableton Push

When a Push controller is connected and its input and output devices are enabled in the Device Setup (the device aliases must be set to "Push"), it can be used as following:

  • General:

    • Select main pages via top row pads

      • PipeMap, PipeRoot, Pipe, Node, MidiDevs, SubSongs, MidiMon, Project

    • Context-sensitive rotary encoder functions (e.g. select pattern nr, select BPM and loop length, etc)

    • Touching the rotary encoder below the "Metronome" button will temporarily override the current map context and activate the global context

  • PipeMap page:

    • Select edit mode (edit / mute / solo / move) (first 4 pads of row 5) and exec the selected action by tapping on a node pad (lower left 6x4 pad area)

    • Select patterns (right bottom area)

  • Arranger node editor page:

    • Clip matrix

      • Timeline play mode must be disabled for this to work

      • Each column is associated with a node

      • Each row represents a clip matrix scene (up to 128).

        • Each scene stores the pattern number, duration, and number of loops for each node (see Push display).

        • The currently active scene will flash periodically

      • Scenes can be imported via the "Auto Generate" button in the "Scene" tab

      • The buttons right next to each row (1/16t, 1/16, ..) are used to select / queue a scene

      • Depending on the current mode (selected by the first 4 pads of the second row from the top), tapping a node pad will either select a node or play / queue the node pattern

        • When immediate mode is enabled, the action will be performed instantly, otherwise the pad has to be tapped twice

  • Tracker node editor page:

    • Push pads can be used to set/clear notes and move blocks. To be honest, it’s easier to use the regular interface, though.

    • (todo) document me

  • CtlTag page

    • Push pad pressure can be used to send MIDI events

    • (todo) document me

The main drawback here is that the Push functions are tied to specific UI pages, i.e. the clip matrix for example can only be used when an Arranger node is being edited.

Last but not least, keep in mind that the pad functions can be configured in the MIDI map context editor. While editing a map context, the pad colors can be configured by pressing the "Tap Tempo" button.

Keyboard Mode

In addition to the aforementioned functions, the Push controller can also be used in keyboard mode, which is toggled via the global PUSH_TOGGLE_KBD map target (bound to the Push "Select" button in the default project template).

In this mode, it acts like some sort of poor man’s Linnstrument. The pad grid can be split horizontally and / or vertically. Each split is assigned a dedicated MIDI channel, i.e. the first split sends events on <push>:1, the second one on <push>:2, and so on.

The rotary encoders are used to configure the current octave, row-add, key (C,C#,D,..) , mode (major/minor/..), and horizontal shift.

The keyboard mode is available regardless of the currently active UI page.

It’s not only useful for actual note input: In combination with a ModMatrix or Script node, the note on events can be converted to program change events (⇒ node pattern selection).

Tip In order to convert note ons to (used) pattern selection program changes, insert a Script node before the node you want to control (in the same pipe), and load the “/note/note_to_usedpatnr” preset. In the "I/O" tab, select the note input device and channel, and the program change output device and channel (should match the other node’s auto-dev A or B setting). In the "Param" tab, there’s a combobox that lets you choose the MIDI base note (i.e. the note that corresponds to the first (used) pattern. C-3 by default).
Important Keep in mind that node processing works with output devices only. I.e. in order to use the Push keyboard events, they have to be mapped to an output device via a MIDI "morph scene". The easiest way to do this is to map all incoming “Push” events to a virtual MIDI device named “<push>”.

Roger Linn Linnstrument128

Setup

(Extended) Support for the Linnstrument is implemented via the Script node. First you need to instantiate a Script node in the master pipe (the first one), then load the “/seq/linnstrument arranger” preset.

In the "I/O" tab, the variable “linn” has to be set to the actual Linnstrument device (usually called “linnstrument”), while the variable “linn_mapped” has to be set to a (virtual) output device (i.e. one of the “<internal 1..16>` devices. It is usually a good idea to assign an alias name in the Device Setup, e.g. "`<linnstrument>”).

You will also need to set up (and activate) a MIDI morph scene that forwards all “linnstrument” input device events to the virtual “<linnstrument>” output device.

Important It may be necessary to turn the MIDI cache off for devices that are used to send out MPE events. Some synths expect a CC#74 brightness event immediately before a note on, even when the CC value has not changed since the last note on.

In order to toggle between regular Linnstrument mode and the arranger mode, simply mute / unmute the script node. When the node is muted, the first (top-most) Linnstrument preset is loaded. When the node is unmuted, the last (bottom) Linnstrument preset is loaded.

This last preset must be configured as following:

  • Split point: 12 columns left, 13 columns right

  • Row per channel mode (both left and right)

  • No row offset

  • Channels left: 1..8

  • Channels right: 9..16

  • Transpose left: octave:+1, lights:+6

  • Transpose right: octave:-1, lights:-6

  • Pitchbend range left: 24 semitones

  • Footswitch function set to CC65 (Portamento SW)

    • tested with a (regular) mono footswitch pedal

Note If you don’t have a foot pedal, just route / transform another MIDI event with a ModMatrix node, e.g. a note on/off or CC event generated by a MIDI controller button

The footswitch is used to toggle between arranger and fader mode. It can be set to either toggle or momentary mode in the "Param" tab.

General

Each Linnstrument pad row corresponds to one output port. These ports are configured in the source code and the default configuration looks like this:

Note row number 1 is the bottom row, row number 8 the top row
Note and Program Change Ports

Row

Device

Channel

Intended Purpose

1

<play_d>

1

Drums (bd, sd, cp, ..)

2

<play_d>

2

Drums (lt, mt, ht, ..)

3

<play_d>

3

Drums (ch, oh, cy, ..)

4

<play_d>

4

Drums (fx)

5

<play_b>

1

Bass

6

<play_a>

1

Keys

7

<play_a>

9

Lead

8

<play_c>

1

Chords

Note Technically speaking, the note and program change ports can be configured separately (left_note_ports and right_prgchg_ports arrays, see script source). By default, they use the same setup.
Modulation Ports

Row

Device

Channel

Intended Purpose

1

vst_d

1

Drums (bd, sd, cp,..)

2

vst_d

2

Drums (lt, mt, ht,..)

3

vst_d

3

Drums (ch, oh, cy,..)

4

vst_d

4

Drums (fx)

5

vst_b

1

Bass

6

vst_a

1

Keys

7

vst_e

1

Lead

8

vst_c

1

Chords

These modulation ports are configured by the left_modulation_ports array (see script source).

The "intended purpose" is just a suggestion, of course. Feel free to use those ports as you see fit.

Arranger mode

The left hand side (left split) pads are used as CC#1 modulation wheel faders. In addition to that, pressure and y-position send CC#2 breath control and CC#11 expression events.

Note When the “Send Notes” option is enabled (Param tab), the left hand side pads will also send MIDI notes to the program change output ports. This can be used to play TrigSeq tracks or select arranger marker clips. When the “Send Notes (Midi Map)” option is enabled, the pads send button events that can be mapped in a MIDI map context (i.e. for remote-controlling the application).

The right hand side pads are used to select the current play pattern for the first node that corresponds to the row’s program change port (i.e. the node’s auto-dev A or B port has to match the row’s output port).

In addition to that, x-pos, y-pos, and pressure generate pitchbend, CC#74 brightness, and channel pressure events.

Arranger mode toolbar

The right-most pad column is used as a toolbar:

Row

Color

Function

1

Orange

While held down, discard MIDI events

2

Cyan

While held down, collect MIDI events and send them when the pad is released

3

Green

Select prgchg mode / toggle pattern pages 1+2

4

Blue

Select fader mini-mode / toggle fader pages 1+2

5

White

Clear modifier (clear fader or scene)

6

Lime

Toggle node navigation mode (when active, tap pattern pad to open its editor)

7

White

Open next arranger editor

8

Yellow

Toggle scene menu (hold pad + tap scene pad to save scene, tap scene pad to load scene)

Arranger mode fader mini-mode

When the fader midi-mode is active, the right hand side pads turn into faders.

Horizontal movement sends CC#16 general purpose 1 (fader page 1), or CC#18 general purpose 3 (fader page 2) events.

Vertical movement (pad y-pos) sends CC#17 general purpose 2 (fader page 1), or CC#19 general purpose 4 (fader page 2) events.

Fader mode

The fader mode is activated (or toggled) by pressing the footswitch pedal (CC#65).

In this mode, 16 faders can be edited per current output port. The current output port is set when a pattern or CC fader is tapped (in non-fader mode).

Tip Hold down the "discard" modifier (orange toolbar pad) to just select a port without changing the current fader value (or selecting a pattern).
Fader mode toolbar

Like in the arranger mode, the right-most pad column is used as a toolbar:

Row

Color

Function

1

Orange

While held down, discard MIDI events

2

Cyan

While held down, collect MIDI events and send them when the pad is released

3

-

-

4

-

-

5

White

Clear modifier (clear fader or scene)

6

-

-

7

-

-

8

Yellow

Toggle output port selection menu

Scenes

All fader states and current pattern selections can be stored in up to 24 scenes.

Scenes are saved by activating the scene menu (in arranger mode), then holding down the scene menu pad and tapping one of the scene slots (in the upper two rows).

Vice versa, scenes are loaded by tapping a scene slot while the scene menu is active.

Note The rightmost pad color of each fader indicates whether the fader value is unknown (white), or valid (orange). When a scene is loaded, only the valid faders will generate CC/pitchbend/channel pressure events. In order to invalidate a fader, hold down the clear modifier (white toolbar pad) and tap one of the fader pads.
Note Clearing a left-hand-side fader in arranger mode also clears the pattern selection. Hold down the discard modifier to only clear the pattern selection, or the discard_collect modifier to only clear the modwheel/breathcontrol/expr fader values.
Note When loading a scene, holding down the discard modifier (orange toolbar pad) will only load the pattern selection, while holding down the discard_collect modifier (cyan toolbar pad) will only load the fader values
Last but not least
  • You can use as many Linnstrument script nodes as you like. Just make sure only one is active at a time.

  • Any script modifications are saved with the project file (e.g. the output port mapping)

  • By targeting an <<node_arranger,Arranger> node that has one or more markers, pattern selection can become a scene selection, i.e. selecting one of the arranger markers will change the patterns of any number of nodes

  • Take a look at the Params tab which contains many additional settings (e.g. footswitch polarity inversion)

  • While the script node is being edited, the status bar will display additional info messages

  • The “mpe latch ccScript preset can be used to e.g. latch the y-position (cc#74 brightness) at note on. This can be useful for avoiding unintended "smear" effects.

Node Overview

The following (multi-instantiable) sequencer nodes are currently available.

Tracker

Tracker
Figure 1. Tracker

This is the most complex, and most versatile sequencer node in this application.

Main features:

  • Undo / redo (with configurable history size)

  • Arbitrary pattern length

  • Arbitrary number of tracks per pattern

  • Arbitrary step resolution / pattern zooming / microtiming

  • 32bit floating point precision for all controller values

  • Instrument-based MIDI device+channel selection (any instrument can play on any track)

    • Instrument selection can optionally trigger MIDI program change and / or bank select

  • Multiple note / velocity / duration / pressure controllers per track (for chords)

  • Customizable track / cel layouts and colors

    • Cels can be displayed as hex, letter (0..9, A..Z, a..z), 2 or 3 digit pattern number, 4/8/16/32 char wide bars (to visualize envelopes), or colored rectangles (for orientation)

    • Auto-colorization (via lctrl-x k, preserves custom cel colors)

  • User definable controller cels (CTL_USR[1..16])

    • CC, (N)RPN, Program Change

    • (Optional) controller reset values (automatically sent when instrument is selected)

    • Can send controller events to MIDI devices/channels other than the one selected in the instrument

    • MIDI learn function

  • Auto-note-off mode

    • Note duration is scaled by current "Duration" (see Play tab)

  • Recording of MIDI controller input and / or output from previous nodes (can be filtered and quantized)

  • Loop or oneshot pattern mode

  • Arpeggiator mode

  • External clock sync mode (clock, gate)

  • Controller / track / pattern block editing modes

  • Mini-hex editing mode

    • lshift + 0..9,A..F to enter values without moving the cursor down to the next step

    • also works with bar-style cels

  • Slide effect (via MIDI pitchbend)

    • A CTL_INSTR event > 0 will force the note to be retriggered

  • Track delay effect

  • Note repeat effect

  • Break / seek effect (continue replay at step 'x' or stop pattern replay)

    • Seek time is scaled by current "Off / Len" (see Play tab)

  • Per-step mute / unmute effect

  • Controller injection via auto device RPNs

    • Temporarily replace parts of a pattern by data sent from other nodes

  • PolyStep play

    • Trigger arbitrary pattern steps by other nodes (via RPN auto device messages)

    • The TrigSeq node has a dedicated "SingleTrack Polystep" output mode for this

  • Chord-clear-step mode

    • Auto-clear step note events when new chord is recorded via MIDI

  • Chord-advance mode

    • Move cursor to next step not until all chord notes have been released

  • Tap mode

    • Timed recording of steps from other pattern

    • Default source pattern is the last pattern copied to the clipboard (lctrl-c)

    • Notes >= C-4 select / record source pattern step #n, < C-4 advances source pointer to next step (and records it)

  • Background recording mode

    • Recording continues even when the tracker node is not currently being edited

  • Overdub and raster recording modes

    • Raster recording mode clears the current recording steps unless no event has been recorded since the last pattern loop

  • "KeyJazz" (play/enter notes with PC keyboard) (a MIDI keyboard is highly recommended, though)

    • Can be locked to a specific node and track (useful for editing controller patterns/tracks)

  • Import Elektron Analog Rytm drum machine patterns

  • Import drum patterns from TrigSeq node

  • Import standard MIDI files

    • e.g. for ReCycle .mid output

  • Graphical envelope editor

    • Freedraw, line, and cubic bezier spline editing modes

    • Replace-mode restricts editing to already existing events

Arranger

Arranger
Figure 2. Arranger

This node is used for arranging patterns / clips of other nodes on a timeline.

It can also be used for the live-arrangement of patterns via an Ableton Push controller.

Main features:

  • Graphical, DAW-like timeline editor

    • Editing tools: Select, Draw, Erase, Razor, Mute

    • Multi-clip editing

    • Insert snapshot of currently playing patterns

    • Undo / redo (with configurable history size)

  • Nodes can be assigned to specific arranger nodes

  • Change / start node patterns

    • Configurable play offsets OR free-running pattern changes

  • Can record pattern and mute / solo state changes

  • Ableton Push clip-matrix support

    • Auto-create arranger setup by scanning available node patterns

  • Timeline Marker clips / regions

    • Especially useful when using multiple arranger nodes

    • Can be triggered by index via auto-dev note-on (C-3..)

    • Can be triggered by pattern nr via auto-dev prgchg (0..n)

    • Aligned to 16th notes (see 16th setting in "Play" tab)

    • Marker play modes:

      • "Mrk: Change": Jump into next marker region via modulo offset

      • "Mrk: Reset": Restart next marker region from the beginning

      • "Mrk: Reset All": Restart next marker region from the beginning and force track clip start offsets

TrigSeq

TrigSeq
Figure 3. TrigSeq

This node is tailored towards percussion / drum sequences.

Main features:

  • Up to 16 tracks

  • Individual track lengths and speeds (step note durations)

  • Micro timing (LMB drag step in upper area or via lshift-cursor)

    • Per step

    • Per track offset

  • Mini undo / redo

  • Non-destructive quantization

  • Swing / shuffle (per track)

  • Shift / Reverse / Randomize functions

  • Various output modes (e.g. notes, program change+offset, temporary mutes, polystep, clock+gate, ..)

    • Output mode dependent step replay arguments:

      • Arg1: Usually the velocity index (0..3) (visualized by step color)

      • Arg2: Optional per-step argument in the range 1..n (LMB drag step in lower area or via lctrl-x cursor)

      • Arg3: Per-track argument that can be offset for all tracks (see Pattern tab)

    • Polystep output for tight coupling with tracker node (trigseq for timing, tracker for note/step data)

      • see "polystep_*" pipe presets

  • MIDI step recording

    • Via the "auto device" MIDI port

    • Default base note is C-3 (36)

    • Roll note is F-4 (53)

  • Note repeat (roll)

    • Note length can be configured per track

    • Repeat can be enabled globally per pattern, per track, and / or per step

  • Euclidean pattern generator

  • External clock sync mode (clock, gate)

  • Foldable tracks

  • Micro-timing track support

    • Configured in track setup ('t')

    • Timing will be applied to all tracks

    • Timing presets (load / save)

  • Auto-Dev notes:

    • Tracks can be triggered via auto-dev note-on/off (C-3..D#4)

    • Tracks can be (temporarily) repeated via auto-dev note-on/off (C-5..D#6)

    • Tracks can be (temporarily) muted via auto-dev note-on/off (C-7..D#8)

    • The global mute auto-dev note is G-4

    • The global repeat-trigs auto-dev note is A-4

    • The global repeat-all auto-dev note is B-4

ModMatrix

ModMatrix
Figure 4. ModMatrix

This node is the swiss army knife for transforming and combining MIDI events.

Main features:

  • User definable presets

  • Transform and even generate MIDI events in various ways

    • Copy, test, add, mix, mul, blend, scale, logic ops (and, or, ..), clamp, wrap, select, ..

    • Scale filters (phrygian, lydian, ..)

  • Graphical mini programming language that allows for very complex modulations

    • No typing required

    • Modulation setups can also be generated from text-based script files

    • Text-based scripts can be generated from modulation setups (e.g. for sharing on web forums)

  • Arbitrary number of modulation entries

  • Up to 4 macro controls that can be referenced in modulation entries

  • Can generate (smoothed) random values

  • Persistent internal registers for advanced use (e.g. LFOs)

  • (Quantized) Sample&Hold of input values

  • Value range conversion modifiers (e.g. 7bit ⇒ -1..1)

  • Graphical input / output monitoring

  • MIDI learn function

Monitor

Monitor
Figure 5. Monitor

This node is meant to be used as MIDI monitor and "tape"-like scratchpad recorder.

  • Capture MIDI controller input or output from previous nodes

  • Input can be filtered

  • Record incoming events to a ringbuffer

    • Can be used as a scratchpad MIDI recorder

      • Let it run in the background to capture any "happy accident" melody / chord progressions

  • Single-frame overdub recording

    • Toggle frame-Lock via 'l' or 'd' shortcut

  • Basic editing functions (e.g. merge or delete frames)

  • Ringbuffer replay can be controlled by other nodes

    • Seek absolute, seek relative, play frame, ..

    • Ringbuffer frames can be triggered via auto-dev note-on (C-3..)

      • Dynamic trigger note duration: Override note duration

      • Velocity modes: Keep, Replace, Multiply, Add

  • Ringbuffer replay can be transformed to other MIDI device+channel

CtlMorph

CtlMorph
Figure 6. CtlMorph

This node can blend between user definable controller sets, e.g. for patch morphing.

Main features:

  • Supports all regular MIDI controller message types (CC / (N)RPN)

  • Up to 8 controller groups per pattern

  • Arbitrary number of controllers per group

  • Min / Max / Center values per controller

  • Master input controller to control min..max blending (per group)

  • Symmetric and asymmetric blending (configurable per controller)

  • Various utility functions to create morphs between controller sets

  • Can copy current MIDI output state to controller set

  • Controller rate limiter and temporal distribution

  • MIDI learn function

  • Cyclic Multi-Morph

    • Pattern Offset, Range, and morph position

    • The node can be configured to send an initial morph position when it is being reset

    • All parameters can be overridden by sending RPNs to the auto device MIDI port(s)

Important For the "Copy MIDI output state to center values" (lctrl-o) Tools menu function to work as expected, the synth must be set to local off and a MIDI morph scene must be created that routes events from the synth’s input device to the synth’s output device (software echo).

Auto

Auto
Figure 7. Auto

This node is dedicated to controller automation envelopes.

Main features:

  • Arbitrary number of controller tracks

  • Arbitrary number of lanes per track

  • Multiple curves can be stacked and combined via various operators

    • similar to layers in a graphics editor like Photoshop

  • MIDI learn function

KeyMap

KeyMap
Figure 8. KeyMap

This is a utility node for mapping note on/off input events to various output events.

Main features:

  • Input events can be mapped to output note / polyphonic key pressure / pitchbend / modwheel / expression / breathcontrol / program change events

  • For example, this node can be used to select patterns via MIDI keys, or create keyboard splits

  • Different kinds of velocity curves can be applied to outgoing note events

MonoPoly

MonoPoly
Figure 9. MonoPoly

This node distributes incoming note and controller events to multiple output devices.

Main features:

  • Unison, Round Robin, Random, Newest, Oldest, Highest, Lowest, .. trigger modes

  • Can mirror output events to another device (for layering)

  • Originally developed for use with a Vermona Perfourmer synthesizer

    • ..but can be used with any other MIDI synth, too

Note The easiest way to copy all events within a pipe from one MIDI port to another is to use a MonoPoly node with the trigger mode set to "Unison"

Buffer

Buffer
Figure 10. Buffer

This node records incoming events and replays them using up to four play heads (fugue-like).

Main features:

  • Play heads can be transposed and filtered by various scales (major, minor, pentatonic, ..)

  • Play heads can cycle through different parts of the recording buffer

  • Configurable recording raster sizes (1/64 .. 1/1)

  • Hold mode

  • Double-buffer mode

  • Arpeggiator mode

AnalogRytm

AnalogRytm
Figure 11. AnalogRytm

This is a utility node that was especially designed for Elektron’s Analog Rytm drum computer / synthesizer.

  • Receive, send, manage patterns, kits, mute and performance controller states

  • Send track sounds

  • Map Analog Rytm hardware interface controls to arbitrary MIDI events or actions (e.g. load kit/mute state)

Delay

Delay
Figure 12. Delay

This node delays incoming MIDI events.

Main features:

  • Input device and channel filter

  • Configure delay time as ticks or 16ths

  • Automate delay time

    • Hold automated delay time for "n" ticks (or indefinitely)

  • Applications:

    • MIDI echoes

    • "Swing"

Proxy

Proxy
Figure 13. Proxy

The proxy node acts as a link to synth-specific editors.

It is currently supported by the builtin Prophet 12 editor and has the following features:

  • Temporary parameter changes via NRPN

    • The NRPNs are received on the MIDI port configured as "Input"

      • The MIDI port should be set to the "Prophet 12" synth profile in the device configuration

    • When the replay starts, the patch automatically reverts to its original configuration

      • The patch can be reset at any time by sending the "Com: Reset" RPN to the "Auto Device"

  • Virtual program changes and bank selects

    • Received as RPNs on the MIDI port configured as "Auto Device"

      • The MIDI port should be set to the "internal" synth profile in the device configuration

    • The program is changed by sending the differences to the current patch via NRPN

  • Realtime morphing between patches

    • Either by setting the src / dest program and bank and the blend amount via multiple RPNs

    • Or by using the multi-morph position RPN to morph between patches in the project-specific bank P17

      • A single RPN message will configure the src / dest / blend amount settings in this case

        • RPN value 0 = first patch, 16383 = last patch in the morph range

      • The morph program offset and range is configured in the UI and it can be overridden via RPNs

      • The node can be configured to send an initial morph position when it is reset

    • The morph settings are received as RPNs on the MIDI port configured as "Auto Device" (A and / or B)

AutoDevice MIDI Implementation

The following table shows which nodes react to which "auto device" MIDI events (see node "Play" tabs).

Please notice that some nodes support node-specific events which are not listed in this table. Please refer to the application tooltips (RPN selection) or the "midi_synth_profiles/internal.msp" text file for further info.

Some nodes (e.g. AnalogRytm, Auto, Buffer, ModMatrix, MonoPoly, Proxy) also use additional input devices that support additional MIDI events.

Event
AnalogRytm
Arranger
Auto
Buffer
CtlMorph
Delay
Keymap
ModMatrix
Monitor
MonoPoly
Proxy
Tracker
TrigSeq

Note

-

y

-

y

-

-

y

-

y

-

-

y

y

PrgChg

-

y

y

y

y

-

y

y

y

y

-

y

y

RPN Com: Reset

-

-

y

-

-

-

y

y

y

-

y

y

y

RPN Com: Run

-

-

y

-

-

-

-

-

y

-

-

y

y

RPN Com: Clock + Gate

-

-

-

-

-

-

-

-

-

-

-

y

y

RPN Com: Clock

-

-

-

-

-

-

-

-

-

-

-

y

y

RPN Com: Gate

-

-

-

-

-

-

-

-

y

-

-

y

y

RPN Com: Gatetime

-

-

-

-

-

-

-

-

-

-

-

y

y

RPN Com: Gatetime Mul

-

-

-

-

-

-

-

-

-

-

-

y

y

RPN Com: Gatetime Div

-

-

-

-

-

-

-

-

-

-

-

y

y

RPN Com: Retrig

-

-

-

-

-

-

-

-

-

-

-

y

-

RPN Com: Restart

-

-

y

-

-

-

-

-

y

-

-

y

y

RPN Com: Mute

y

y

y

y

y

y

y

y

y

y

y

y

y

RPN Com: Transpose

-

-

-

-

-

-

-

-

y

-

-

y

y

RPN Com: Mute Temp

y

y

y

y

y

y

y

y

y

y

y

y

y

RPN Com: Mute Toggle

y

y

y

y

y

y

y

y

y

y

y

y

y

RPN Com: Mute Temp Toggle

y

y

y

y

y

y

y

y

y

y

y

y

y

RPN Com: UI Node Mute

y

y

y

y

y

y

y

y

y

y

y

y

y

RPN Com: UI Node Solo

y

y

y

y

y

y

y

y

y

y

y

y

y

RPN Com: UI Pipe Mute

y

y

y

y

y

y

y

y

y

y

y

y

y

RPN Com: UI Pipe Solo

y

y

y

y

y

y

y

y

y

y

y

y

y

RPN Com: UI Node PrgChg

y

y

y

y

y

-

y

y

y

y

-

y

y

RPN Com: Off/Len Scale

-

-

-

-

-

-

-

-

-

-

-

y

y

RPN Com: Off/Len Multiplier

-

-

-

-

-

-

-

-

-

-

-

y

y

RPN Com: Off/Len Divisor

-

-

-

-

-

-

-

-

-

-

-

y

y

RPN Com: Offset

-

-

-

-

-

-

-

-

y

-

-

y

y

RPN Com: Length

-

-

-

-

-

-

-

-

y

-

-

y

-

RPN Com: Seek Offset

-

y

y

-

-

-

-

-

y

-

-

y

-

RPN Com: Seek Relative (Pre)

-

-

-

-

-

-

-

-

y

-

-

y

-

RPN Com: Seek Relative (Post)

-

-

-

-

-

-

-

-

y

-

-

y

-

RPN Com: Offset Add

-

-

-

-

-

-

-

-

y

-

-

y

-

RPN Com: Offset Queued

-

-

-

-

-

-

-

-

-

-

-

y

-

RPN Com: Length Queued

-

-

-

-

-

-

-

-

-

-

-

y

-

RPN Com: Sig Beats

-

-

-

-

-

-

-

-

-

-

-

y

-

RPN Com: Sig NoteLen

-

-

-

-

-

-

-

-

-

-

-

y

-

RPN Com: Speed

-

-

y

-

-

-

-

-

y

-

-

y

y

RPN Com: Position Scale

-

-

y

-

-

-

-

-

y

-

-

y

y

RPN Com: Vel Scale

-

-

y

-

-

-

-

-

y

-

-

y

y

RPN Com: Vel Offset

-

-

y

-

-

-

-

-

y

-

-

y

y

RPN Com: Dur Scale

-

-

y

-

-

-

-

-

y

-

-

y

y

RPN Com: Dur Offset

-

-

y

-

-

-

-

-

y

-

-

y

y

RPN Com: PolyStep *

-

-

-

-

-

-

-

-

-

-

-

y

-

Keyboard Shortcuts

Note These lists assume a US keyboard layout. On a german keyboard for example, swap 'z' for 'y', ']' for '*', '`’ for '^', and so on.

Global

Key Sequence

Description

F3

Select previous MIDI morph scene "A"

F4

Select next MIDI morph scene "A"

F5

Select previous MIDI morph scene "B"

F6

Select next MIDI morph scene "B"

F7

Select previous MIDI morph scene "C"

F8

Select next MIDI morph scene "C"

F9

Select previous MIDI morph scene "D"

F10

Select next MIDI morph scene "D"

lalt - F3

Select previous MIDI morph scene "E"

lalt - F4

Select next MIDI morph scene "E"

lalt - F5

Select previous MIDI morph scene "F"

lalt - F6

Select next MIDI morph scene "F"

lalt - F7

Select previous MIDI morph scene "G"

lalt - F8

Select next MIDI morph scene "G"

lalt - F9

Select previous MIDI morph scene "H"

lalt - F10

Select next MIDI morph scene "H"

F12

Toggle metronome click

(NUMPAD) ENTER

Start/stop replay

(NUMPAD) lshift - ENTER

Start/stop replay and send/don’t send MMC record event(s)

(NUMPAD) 1

Transport: Go to previous bar

(NUMPAD) 2

Transport: Go to next bar

(NUMPAD) 3

Transport: Toggle cycle/loop

(NUMPAD) 4

Transport: Go to previous marker

(NUMPAD) 6

Transport: Go to next marker

(NUMPAD) 7

Transport: Go to previous beat

(NUMPAD) 9

Transport: Go to next beat

(NUMPAD) /

Transport: Decrease cycle length

(NUMPAD) *

Transport: Increase cycle length

(NUMPAD) .

Transport: Save scratch marker

(NUMPAD) 0

Transport: Load scratch marker

(NUMPAD) 5

Transport: Load marker (key 0..9 follows)

(NUMPAD) 8

Transport: Save marker (key 0..9 follows)

(NUMPAD) -

Decrease BPM (beats per minute)

(NUMPAD) lshift - -

Half BPM (beats per minute)

(NUMPAD) +

Increase BPM (beats per minute)

(NUMPAD) lshift - +

Double BPM (beats per minute)

(NUMPAD) lctrl - 1

Show pipemap page

(NUMPAD) lctrl - 2

Show preferences page

(NUMPAD) lctrl - 3

Show current node editor page

(NUMPAD) lctrl - 4

Show MIDI devices setup page

(NUMPAD) lctrl - 5

Show project page

(NUMPAD) lctrl - 6

Show MIDI map page

(NUMPAD) lctrl - 0

Show SysEx page

(NUMPAD) lctrl - ENTER

Show MIDI input monitor page

(NUMPAD) lctrl - +

Show MIDI output monitor page

(NUMPAD) lctrl - x 0

Select multi-scene 1 OR subsong 0 (main) [see config]

(NUMPAD) lctrl - x 1

Select multi-scene 2 OR subsong 1 (main) [see config]

(NUMPAD) lctrl - x 2

Select multi-scene 3 OR subsong 2 (main) [see config]

(NUMPAD) lctrl - x 3

Select multi-scene 4 OR subsong 3 (main) [see config]

(NUMPAD) lctrl - x 4

Select multi-scene 5 OR subsong 4 (main) [see config]

(NUMPAD) lctrl - x 5

Select multi-scene 6 OR subsong 5 (main) [see config]

(NUMPAD) lctrl - x 6

Select multi-scene 7 OR subsong 6 (main) [see config]

(NUMPAD) lctrl - x 7

Select multi-scene 8 OR subsong 7 (main) [see config]

(NUMPAD) lctrl - x 8

Select multi-scene 9 OR subsong 8 (main) [see config]

(NUMPAD) lctrl - x 9

Select multi-scene 10 OR subsong 9 (main) [see config]

b

Go to previous page (back)

n

Go to next page (forward)

q

Go to previous or parent page

g

Force global MIDI map context (as long as key is held down)

lctrl - m

Edit current MIDI map context

p

Start/stop replay

lctrl - s

Toggle pipe solo

lctrl - d

Toggle node solo

lctrl - lshift - d

Toggle node mute

right menu key

Toggle keyboard focus selection mode

`: (once)

Edit controller aliases (^ on german keyboards)

`: (twice)

Edit current MIDI morph scene (^ on german keyboards)

RIGHT MENU KEY

Toggle keyboard focus selection mode

ESC

Go to previous or parent page / cancel dialog

lshift - q

Quit application (dialog)

PipeMap

Key Sequence

Description

UP

Select previous pipe

DOWN

Select next pipe

LEFT

Select previous pipe or node

RIGHT

Select next pipe or node

lshift - HOME

Select first node

lshift - END

Select last node

PAGEUP

Select next action

PAGEDOWN

Select previous action

1

Select 'EXEC' action

2

Select 'EDIT' action

3

Select 'MUTE' action

4

Select 'SOLO' action

5

Select 'MOVE' action

r

Show pipe root

a

Show pipe or node context menu

s

Toggle pipe or node solo

lctrl - s

Toggle pipe solo

d

Toggle pipe or node mute

lctrl - d

Toggle pipe mute

INSERT

Insert new pipe or node

lshift - INSERT

Clone pipe or node

DELETE

Delete pipe or node

lshift - LEFT

Move node to the left

lshift - RIGHT

Move node to the right

lshift - UP

Move pipe up

lshift - DOWN

Move pipe down

f

Select next arranger node

lctrl - lshift - c

Edit node comment

HOME

Select next used node pattern

END

Select previous used node pattern

(NUMPAD) lshift - 1

Select used node pattern #1

(NUMPAD) lshift - 2

Select used node pattern #2

(NUMPAD) lshift - 3

Select used node pattern #3

(NUMPAD) lshift - 4

Select used node pattern #4

(NUMPAD) lshift - 5

Select used node pattern #5

(NUMPAD) lshift - 6

Select used node pattern #6

(NUMPAD) lshift - 7

Select used node pattern #7

(NUMPAD) lshift - 8

Select used node pattern #8

(NUMPAD) lshift - 9

Select used node pattern #9

(NUMPAD) lshift - 0

Select empty pattern (--/)

Node (common)

Key Sequence

Description

lctrl - lshift - LEFT

Select previous node

lctrl - lshift - RIGHT

Select next node

lctrl - lshift - UP

Select previous pipe

lctrl - lshift - DOWN

Select next pipe

lctrl - g

Enter pattern number

HOME

Select next edit+play pattern (+1)

lctrl - HOME

Select next edit+play pattern group (+4)

lctrl - lshift - HOME

Select next used pattern

END

Select previous edit+play pattern (-1)

lctrl - END

Select previous edit+play pattern group (-4)

lctrl - lshift - END

Select previous used pattern

lctrl - x 1

Set pipenode 'A'

lctrl - x 2

Set pipenode 'B'

lctrl - x d

Toggle pattern manager

lctrl - x z

Jump between pipenodes 'A' / 'B' ('y' on german keyboards)

lctrl - x HOME

Global program change (master pipe, auto dev+ch A)

lctrl - x END

Global program change (master pipe, auto dev+ch B)

lctrl - lshift - c

Edit node comment

lctrl - c

Copy pattern to clipboard

lctrl - w

Cut pattern to clipboard

lctrl - v

Paste pattern clipboard

lctrl - r

Clone pattern (4)

lctrl - lshift - r

Clone pattern (1)

lctrl - x F3

Delete pattern

lctrl - s

Solo pipe

lctrl - d

Solo node (within pipe)

lctrl - lshift - s

Mute pipe

lctrl - lshift - d

Mute node

(NUMPAD) lshift - 1

Select used node pattern #1

(NUMPAD) lshift - 2

Select used node pattern #2

(NUMPAD) lshift - 3

Select used node pattern #3

(NUMPAD) lshift - 4

Select used node pattern #4

(NUMPAD) lshift - 5

Select used node pattern #5

(NUMPAD) lshift - 6

Select used node pattern #6

(NUMPAD) lshift - 7

Select used node pattern #7

(NUMPAD) lshift - 8

Select used node pattern #8

(NUMPAD) lshift - 9

Select used node pattern #9

(NUMPAD) lshift - 0

Select empty pattern (--/)

Arranger

Global

Key Sequence

Description

1

Select 'Scene' tab

2

Select 'Pattern' tab

3

Select 'Timeline' tab

4

Select 'Play' tab

Timeline | Tool Selection

Key Sequence

Description

q

Select 'Select' / 'Move' tool

w

Select 'Draw' tool

e

Select 'Erase' tool

r

Select 'Razor' tool

t

Select 'Mute' tool

Timeline | Common

Key Sequence

Description

RETURN

Edit first selected clip (same as RMB-click)

CURSOR keys

Select clips (+shift to add to selection, +lctrl to select on all tracks)

INSERT

Insert silence

lshift - INSERT

Insert silence (all tracks)

DELETE

Delete selected clips

lshift - DELETE

Delete selected clips and move

lctrl - DELETE

Delete selected clips (muted only)

lctrl - lshift - DELETE

Delete selected clips and move (muted only)

lctrl - a

Select all track clips (when clip is selected), then all clips, then none

c

Loop selected clip(s)

d

Center display to replay offset

lshift - d

Toggle center display to replay offset lock

f

Toggle zoom to selected clip(s)

lshift - f

Toggle show-all

g

Choose pattern for selected clip(s) (popup)

h

Toggle track lock (last selected clip track)

lshift - h

Invert track locks

lctrl - h

Clear track locks

l

Align selected clips to grid

m

Show / hide marker track

p

Select next play mode (cycle)

s

Toggle snap-to-grid

v

Insert silence (all tracks)

lshift - v

Insert snapshot of all currently playing pattern (all tracks)

lshift - HOME

Go to start (offset 0)

lshift - END

Go to loop start

lctrl - HOME

_Increment pattern nr of selected clips by +4

HOME

_Increment pattern nr of selected clips by +1

lctrl - END

_Decrement pattern nr of selected clips by -4

END

_Decrement pattern nr of selected clips by -1

SPACE

Start / stop replay

lctrl - SPACE

Stop replay and don’t rewind to start offset

RCTRL

Toggle clip mute+patternr state recording

lshift - RCTRL

Copy clip mute+patternnr state from arranger (at edit offset)

a

Show tools and options menu

lshift - a

Focus grid size widget

lshift - ]

Zoom in

lshift - [

Zoom out

Tracker

Edit

Key Sequence

Description

lalt - e

Open Edit pulldown menu

rctrl

Toggle edit mode

backspace

Toggle relative shift mode

lshift - ]

Zoom in

lshift - [

Zoom out

' or f

Toggle zoom preset (a-umlaut on german kbd)

lshift - a

Enter step resolution / zoom (focus widget)

lshift - d

Enter default note duration (focus widget)

lctrl - 0

Set step advance to 0 steps

lctrl - 1

Set step advance to 1 step

lctrl - 2

Set step advance to 2 steps

lctrl - 3

Set step advance to 3 steps

lctrl - 4

Set step advance to 4 steps

lctrl - 5

Set step advance to 5 steps

lctrl - 6

Set step advance to 6 steps

lctrl - 7

Set step advance to 7 steps

lctrl - 8

Set step advance to 8 steps

lctrl - 9

Advance to next event after editing a step

lctrl - lshift - 0

Set micro-shift to 96 ticks

lctrl - lshift - 1

Set micro-shift to 1 tick

lctrl - lshift - 2

Set micro-shift to 2 ticks

lctrl - lshift - 3

Set micro-shift to 3 ticks

lctrl - lshift - 4

Set micro-shift to 4 ticks

lctrl - lshift - 5

Set micro-shift to 6 ticks

lctrl - lshift - 6

Set micro-shift to 8 ticks

lctrl - lshift - 7

Set micro-shift to 12 ticks

lctrl - lshift - 8

Set micro-shift to 24 ticks

lctrl - lshift - 9

Set micro-shift to 48 ticks

lctrl - x o

Toggle chord clear-step mode

lctrl - x t

Start / stop tap mode

lctrl - t

Collapse pattern to scratch and start tap mode

lctrl - f

Detail-edit value

lctrl - z

Toggle note on / off or detail-edit value

lctrl - x x

Toggle timing view

lctrl - lshift - x x

Toggle timing view move lock

lctrl - \

Toggle timing view (< on german kbd)

lctrl - lshift - \

Toggle timing view move lock (< on german kbd)

lctrl - y

Undo

lctrl - lshift - y

Redo

lctrl - lshift - TAB

Toggle envelope view

lctrl - x TAB

Toggle pattern / play / arp views

Cursor

Key Sequence

Description

lalt - c

Open Cursor pulldown menu

lctrl - x q

Toggle autoscroll mode

lctrl - x r

Toggle wrap-around mode

lshift - TAB

Move cursor to previous track

TAB

Move cursor to next track

lctrl - LEFT

Move cursor to first cel or previous track

lctrl - RIGHT

Move cursor to next cel or next track

UP

Move cursor to previous row

PAGEUP

Move cursor "n" rows up and align

lctrl - UP

Move cursor "n" rows up

DOWN

Move cursor to next row

PAGEDOWN

Move cursor "n" rows down and align

lctrl - DOWN

Move cursor "n" rows down

lshift - HOME

Move cursor to first row

lshift - END

Move cursor to last row

LEFT

Move cursor to previous cel

RIGHT

Move cursor to next cel

lctrl - lalt - LEFT

Move cursor to previous column group

lctrl - lalt - RIGHT

Move cursor to next column group

lctrl - PAGEUP

Move cursor to previous event

lctrl - PAGEDOWN

Move cursor to next event

lctrl - x SPACE

Show cel select / edit / add / delete dialog

Replay

Key Sequence

Description

lalt - r

Open Replay pulldown menu

lctrl - RETURN

Set replay pattern

RETURN

Play step

lshift - RETURN

Play note cel and cycle

SPACE

Start / stop pattern replay

lctrl - SPACE

Start / stop pattern replay from current row

lctrl - x w

Toggle stop-and-goto-bookmark mode

lshift - SPACE

Set (editor) pattern replay start offset

lctrl - x g

Toggle freerun-loop mode

RSHIFT

Start recording (press RETURN to undo+restart)

Track

Key Sequence

Description

lalt - t

Open Track pulldown menu

lctrl - x s

Edit track layout

lctrl - x i

Add cel

lctrl - x n

Add note cel

lshift - e

Reverse track

lshift - o

Rotate track up

lshift - p

Rotate track down

lctrl - x l

Lock keyjazz to current track and node

lctrl - x k

Auto-colorize cels (preserves custom cel colors)

Pattern

Key Sequence

Description

lalt - p

Open Pattern pulldown menu

lctrl - n

Create new pattern

lctrl - lshift - n

Create new pattern (sub)

lctrl - r

Clone pattern

lctrl - lshift - r

Clone pattern (sub)

lctrl - x F3

Free pattern

lshift - BACKSPACE

Clear pattern

lctrl - x c

Copy pattern to clipboard

lctrl - x v

Paste pattern clipboard

lshift - F7

Import pattern from AnalogRytm node (pattern clipboard)

lshift - F8

Import pattern from TrigSeq node (current play pattern)

lshift - F9

Import pattern from Monitor node (pattern clipboard)

lctrl - lshift - F9

Import pattern from Monitor node (pattern clipboard). Temporarily enable Play→"Filter"+"All")

END

Edit previous pattern (-1)

lctrl - END

Edit previous pattern (-4)

HOME

Edit next pattern (+1)

lctrl - HOME

Edit next pattern (+4)

lctrl - l

Edit pattern length

lctrl - lshift - l

Set pattern length to cursor position

lshift - n

Edit pattern name (focus widget)

lctrl - o

Double pattern length

lctrl - lshift - o

Double pattern length and duplicate events

lctrl - x e

Reverse pattern

lctrl - x PAGEUP

Rotate pattern up

lctrl - x PAGEDOWN

Rotate pattern down

Events

Key Sequence

Description

lalt - v

Open Events pulldown menu

lctrl - BACKSPACE

Delete cel envelope

DELETE

Delete step (current ctl) or clear block

lctrl - DELETE

Delete tick (current ctl) or clear block

lshift - DELETE

Delete step or block (all ctls)

lctrl - lshift - DELETE

Delete tick (all ctls)

\

Clear event or clear block (when there is a selection)

lshift - \

Clear event(s) (all ctls)

INSERT

Insert step (current ctl)

lctrl - INSERT

Insert tick (current ctl)

lshift - INSERT

Insert step (all ctls)

lctrl - lshift - INSERT

Insert tick (all ctls)

lctrl - x m

Show Multiply delta times by constant dialog

lctrl - x f

Calc delay ticks (microshift to CTL_DELAY)

lctrl - x RSHIFT

Toggle note-off recording

lctrl - x RCTRL

Toggle CTL_DUR recording

lctrl - x RETURN

Toggle quantized recording

lctrl - x h

Toggle audio latency compensated recording (see prefs)

lctrl - x UP

Increase step or block controller value(s) (coarse)

lctrl - x DOWN

Decrease step or block controller value(s) (coarse)

lctrl - x RIGHT

Increase step or block controller value(s) (fine)

lctrl - x LEFT

Decrease step or block controller value(s) (fine)

Block

Key Sequence

Description

lalt - b

Open Block pulldown menu

lctrl - x b

Cycle through block modes

lctrl - b

Set block start

lctrl - e

Set block end

lctrl - a

Select entire pattern or none

lshift - <CURSOR>

Set selection

lctrl - c

Copy block or pattern (when there is no selection)

lctrl - v

Paste block (replace) or paste pattern (when there is no selection)

lctrl - lshift - v

Paste block (insert) or paste pattern (when there is no selection)

lshift - F2

Transpose block up

lshift - F1

Transpose block down

lshift - F3

Free envelope(s) (depends on block mode)

lctrl - lshift - UP

Move block up one step

lctrl - lshift - LEFT

Move block up one tick

lctrl - lshift - DOWN

Move block down one step

lctrl - lshift - RIGHT

Move block down one tick

lctrl - lshift - a

Quantize block or pattern (when there is no selection)

lctrl - i

Interpolate controller values (current ctl)

Instrument

Key Sequence

Description

lalt - i

Open Instrument pulldown menu

lctrl - TAB

Toggle pattern / instrument views

F1

KeyJazz octave up

F2

KeyJazz octave down

lshift - s

Enter default velocity (focus widget)

lctrl - [

Select previous instrument

lctrl - ]

Select next instrument

lshift - f

Enter instrument nr (focus widget)

lctrl - F12

Toggle keyjazz mode

lctrl - x a

Select keyjazz instrument from current step and toggle edit mode

TrigSeq

General

Key Sequence

Description

a

Show context menu

f

Fold / unfold tracks

t

Show track setup dialog

e

Show euclidean rhythm dialog

RCTRL

Toggle MIDI live recording

u

Undo / Redo

Track

Key Sequence

Description

lshift - BACKSPACE

Clear track

BACKSPACE

Clear track trigs+repeats

lalt - BACKSPACE

Clear track microtime

lctrl - BACKSPACE

Clear track args+repeats

r

Reverse track trigs

j

Randomize track trigs

lctrl - j

Randomize repeats

lshift - j

Randomize arg1 (velocity)

lshift - k

Load arg2 identity (0, 1, 2, ..)

o

Rotate track left

p

Rotate track right

INSERT

Insert step

DELETE

Delete step

lshift - PAGEUP

Increment length

lshift - PAGEDOWN

Decrement length

s

Solo track

d

Mute track

lctrl - l

Focus track length widget

PAGEUP

Inc track length

PAGEDOWN

Dec track length

lctrl - h

Focus swing amount widget

lctrl - t

Focus note length widget

lshift - x

Cut to track clipboard

lshift - c

Copy to track clipboard

lshift - v

Paste track clipboard

lctrl - lshift - v

Paste track clipboard to all patterns

Pattern

Key Sequence

Description

lctrl - lshift - BACKSPACE

Clear pattern

lshift - r

Reverse pattern

lshift - o

Rotate pattern left

lshift - p

Rotate pattern right

lshift - INSERT

Insert step on all tracks

lshift - DELETE

Delete step on all tracks

lctrl - w

Cut pattern to clipboard

lctrl - c

Copy pattern to clipboard

lctrl - v

Paste pattern clipboard

lctrl - r

Clone pattern

lctrl - lshift - r

Clone pattern (sub)

Step

Key Sequence

Description

LEFT

Move cursor left

RIGHT

Move cursor right

UP

Move cursor up

DOWN

Move cursor down

lshift - HOME

Move cursor to first track

lshift - END

Move cursor to last track

lctrl - LEFT

Move step left

lctrl - RIGHT

Move step right

lctrl - UP

Move step up

lctrl - DOWN

Move step down

SPACE

Toggle trig

lctrl - SPACE

Toggle repeat

RETURN

Play step (all tracks)

w

Play track trigger

lshift - w

Play step (current track, and even if track is muted)

x

Cut step to clipboard

c

Copy step to clipboard

v

Paste step clipboard

1

Set step arg1 (velocity index) to 0

2

Set step arg1 (velocity index) to 1

3

Set step arg1 (velocity index) to 2

4

Set step arg1 (velocity index) to 3

lctrl - x RIGHT

Increment step arg2 (e.g. note duration) by 1

lctrl - x UP

Increment step arg2 (e.g. note duration) by 4

lctrl - x LEFT

Decrement step arg2 (e.g. note duration) by 1

lctrl - x DOWN

Decrement step arg2 (e.g. note duration) by 4

lshift - LEFT

Microtime-shift step to the left

lshift - RIGHT

Microtime-shift step to the right

h

Toggle microtime limit (full step or 1/4 step)

TrackSetup

Key Sequence

Description

ESCAPE

Close dialog

a

Focus arg3

c

Focus close button

d

Focus tick duration

f

Focus-cycle forced-output widgets

j

Focus-cycle jitter widgets

r

Focus-cycle repeat widgets

s

Focus microshift

t

Focus-cycle transform widgets

v

Focus-cycle velocity 0..3 widgets

Note Hold down a modifier key (lctrl, lshift, lalt, ..) in case the currently focused widget has already consumed the key event.

Demo Videos

This video shows the creation of a very simple track: https://vimeo.com/218650191

A demonstration of the CtlMorph node (Moog Sub37 parameter blending): https://vimeo.com/219268566

A demonstration of the Prophet 12 specific virtual program change, temporary parameter update, and patch morphing features: https://vimeo.com/219669148

A demonstration of the Prophet 12 editor multi-edit feature: https://vimeo.com/220633861

A demonstration of the "AudioTool" wav slicer and SXT (Reason NNXT) sample patch generator ("alt" drum slicing): https://vimeo.com/222076715

A demonstration of the "AudioTool" wav slicer and SXT (Reason NNXT) sample patch generator (multisampled Osc): https://vimeo.com/222076984

A demonstration of the "AudioTool" autolooper. This one uses some slightly more difficult material (FM4 patch with 3x unison, i.e. a lot of phasing): https://vimeo.com/222077307

A demonstration of the "AudioTool" autolooper. This one uses some rather difficult material with chorus and delay FX (in stereo): https://vimeo.com/222077607

A demonstration of the "AudioTool" SampleChain and Kit generator and uploader for the Elektron Analog Rytm drum computer: https://vimeo.com/222077897

A demonstration of the "AudioTool" VariChain and Kit generator and uploader for the Elektron Analog Rytm drum computer. The resulting "varichain" sample is about half the size of the "samplechain" version: https://vimeo.com/222078031

A demonstration of the cascaded arranger clip state recording feature: https://vimeo.com/263346576

License

This software is available “free as in beer” and is likely to become “free as in speech” (open source) in the future.

It is currently not permitted to redistribute this software, though.

Downloads

GNU | Linux

A Linux port exists and will be released in the near future.