Percussa MIDI MPE Support Details + Module Group #1 List

via the Percussa Kickstarter campaign:

"The past couple of days we worked on a proposal for how the MIDI MPE Support will work in the Percussa SSP. Besides that we also came up with a list of modules for Module Group #1 (= Stretch goal #2). You can find all details below! We're pretty excited about this :-)

We are almost at the first stretch goal, MIDI MPE Support, so please SHARE our update on facebook, twitter, instagram and any other social media channels you use to help us spread the word: EVERYONE wins when more people back the project, because the more stretch goals we reach the more software modules all backers receive. MOAR MODULES!

MIDI MPE IMPLEMENTATION PROPOSAL v1

Quick reminder of how MPE works: an MPE controller (such as a Linnstrument or ROLI Seaboard) sends each note on a seperate MIDI channel. MIDI Channel #1 is a global channel which is used for sending global expression data. So the remaining channels 2-16 are used for notes.

Here is what I suggest for the MIDI MPE Support to be implemented on the Percussa SSP: we make 2 modules, MPE channel and MPE global. You can find the explanation of how the modules work below.



1) The MPE channel module can generate a control (modulation) signal based on the MPE data that is received. The module can be set to only listen to a specific MPE channel (= note).

So if a note is received on channel 5, along with its expression data, the user can use the encoders to “mix” together the data from the note however (s)he wants. If (s)he just wants to use the pitch of the note to generate a pitch signal that can be sent to an LFO, (s)he just turns up the “pitch” encoder to 1.00. If (s)he also wants to use the “glide” data along with pitch, (s)he can turn up the “glide” encoder to 0.50 for example, or whatever value (s)he wants.

Using the +CH and -CH buttons the user can change which channel the MPE channel module is listening to.

When the user is happy with the signal generated it can then be routed to whatever modules the user wants to route to, using the routing system in the synth engine.

The user can create as many of these MPE channel modules as (s)he wants. You can even have multiple modules listening to the same channel, but using the incoming data differently to generate an output (modulation) signal.

This way the MPE data can be used for driving synth voices (traditional use) but it can also be used to control modules in unusual ways.



2) The MPE global module lets you similarly generate modulation signals using incoming MPE data on channel 1. For example, XY data or Slider 1/2/3 or pedal data can be used to generate signals.

The user can have multiple of these modules, potentially using the same data differently to generate different modulation signals which again can be routed to whatever (s)he wants to route to.

MODULE GROUP #1 PROPOSAL v1 (STRETCH GOAL #2)

advanced modules (2)

sampler module with time stretching: allows you to load a WAV file and play it back looped or one shot, with the ability to change the sample’s pitch or length without affecting the other.
granular processor: an advanced granular processer module with support for different kinds of windows, with control over the spread of the grains, grain length, grain speed, grain pitch, offset, etc.
simple modules (3)

simple delay: a simple delay line to delay signals, mostly useful for signals that are used as control (modulation) signals.
bit crusher: a module to reduce the resolution of signals, for example from 32 bit to 8 bit.
physical modeling membrane: allows you to feed a signal trough a membrane implemented using physical modeling."

via the Percussa Kickstarter campaign: