Working with Data

The modules in the “Data” menu play the unique role of providing mechanisms for controlling other modules. Some of them, like the MIDI sequencer, send MIDI data - note on and off messages; others, like the Controller Mapper, send data to change module parameters over time. Control data can be pointed to any module using module Automation IDs, which are uniquely created for each module in your project.

Control data is an integral part of the workflow for creating patches that are performable via hardware or automation, and MSDP provides a large variety of control mechanisms to fit a variety of needs. Learning to master them all is a key part of mastering the program.

The Module Automation Identifier

A new module ID A generated module ID

Each module, upon creation, has a unique random Automation ID assigned to it. Control modules access these IDs to target them for control. IDs ought to be unique, but duplicating them will allow modules to send duplicate control data to multiple locations.

Creating a custom module ID

IDs can be changed at any time by clicking on the text box that displays the name, and typing in a new value.

Accessing Modules by their ID

Creating a custom module ID

Every control module is different, but they each need to access a destination ID. Most often the Destination ID is entered as parameter 2. Look for a text field that displays: “Type Module ID (or Name) Here”. This can be seen in the example above, which contains the Destination ID text field in the center of the module, immediately below the Sequencer Window.

Typically, Automation IDs work like audio channel addresses, in that as soon as the ID matches one that of the destination module, data can immediately be sent from the control module to the destination module.

Creating a custom module ID

In the image above, the exact same sequencer is now pointing to the A+2 synthesizer next to it. Notice that the A+2’s Automation ID is “A+2 877” - This was auto-generated when the module was loaded.

By copy/pasting the ID from the A+2 Synthesizer into the text field of parameter 2 for the Sequencer, the sequencer can now communicate with the synthesizer. Notice that the text field in the middle of the Sequencer module now says “A+2 877” - it matches the A+2’s automation ID.

Creating a custom module ID

With the Destination ID entered, the MIDI Sequencer now has control over the A+2 synthesizer. When the sequence progresses, the notes are sent to the A+2 module to be performed.