The event configurator is used at almost every module of the Polimod.

See the  all the virtual polimod tutorials.

The event configurator is used in most modules. It is used to select a message, which will presumably be sent to the module’s output. Think of it as a word selector: it select what the module will tell the other modules.

An event-message is composed by many numbers. With the event configurator, it is possible to select each of these individual numbers.

Pre-configured events

While you hold the event configurator, some matrix buttons appear blue, and some other appear magenta. The blue buttons are used to select pre-configured events (for easier use). By tapping these blue buttons, different types of events are configured for you. The most used is the first one, named note trigger. The note trigger events are those whose first number is 1.

The last blue button, named manual, lets you manually configure each of the four numbers of the event.

About events

The effect that an event-message has over a module depends on the numbers that it contains. The most important number is the first one (also named num[0], or head); this one determines the function type of the event. Function types are such as clock beat, trigger note, change rate, etc. It is analogous to the first nibble of the MIDI header byte. The other numbers usually give more details about that action. For example, if the event is of note type, the following numbers may determine the note number (pitch, or timbre), channel, velocity, etc.

Knowing the role of each number depending on the header can be a bit tricky to remember. This is why pre-configured events may be useful: if you select a clock event, the following numbers will be renamed as cycle and micro step accordingly. This makes it easier to choose an event. Try different things! If you were strongly expecting something to happen, but it doesn’t, it could mean that you have a feature request, specially once you become well acquainted with Polimod.There is a known bug where a pre-configured event gets a header that doesn’t correspond. I haven’t figured out yet what causes this.There is a known bug where a pre-configured event gets a header that doesn’t correspond. I haven’t figured out yet what causes this.There is a known bug where a pre-configured event gets a header that doesn’t correspond. I haven’t figured out yet what causes this.There is a known bug where a pre-configured event gets a header that doesn’t correspond. I haven’t figured out yet what causes this.