BrainModular

Hello
I'm using a MPE controller (Exquis), and I'm new to MPE.
As far as I understand, the sent messages (CC, pitchbend etc) from a pad are not linked to a midi channel, and the channel can change from one pressure to another.

Is it possible to control a basic module (i.e. a simple fader) with MPE ? It seems to be no as the midi channel has to be assigned.

Are they "MPE compliant" modules in Usine?
Or what is your strategy to deal with MPE? Maybe I'm completely off track!

There are many different possible ways but pers i often use those two:
If want use a 'single' cc that is accross several mpe midi channels, in a patch drop a midi input module, a midi filter module,
Then could for ex use a pass if changed from out val2 to input of a fader so that "if any cc 74 is received, on any channel' it remotes that fader (defining wich rule on the filter)
Or the other way, if do want polyphonic stuff mapped to different things, have a look at "polyphonic patches" in usine
Where man can link in a way such that each midi channel control each polyphonic patch individual voice.

Thanks for your answer.
I tried to patch according to your advice. Here is a configuration to listen to 3 pads, getting up down movement (CC), left right (pitch bend) and pressure (polyAftertouch) for each one.
What do you think about this logical ? It would become big to control the 40 pads of Exquis, would you think about a better solution ?

Well actually my patch works when a single pad is pressed, but is not able to manage multipad pressure. Any idea ?

I think it can be simplified a bit like this (here just ex for CCS)
then not sure understood, but you shouldn't need to do stuff for 40 pads, you would have your 3x similar patchs (ie one for CC74, one for pressure, one for PB) / or pack them all in a single polysubpatch,
then normally when you press pads on Exquis, it should take care of sending to different channels each time to a free MPE /midi channel.

MPE usually works that way: (ch1 is reserved for global/config stuff, then ch2-16 are poly musical events)
_press any pad ---> datas sent to MPE_chan2
_keep that pad pressed and press a new pad --->new datas are sent to MPE_chan3
then can go up to ch16
_then if you release the first pad, ch2 is marked as free, so next pressed pad can/will use ch2 again, even if not same pad

23fx23 wrote: ↑

07 Oct 2026, 15:18

MPE usually works that way: (ch1 is reserved for global/config stuff, then ch2-16 are poly musical events)
_press any pad ---> datas sent to MPE_chan2
_keep that pad pressed and press a new pad --->new datas are sent to MPE_chan3
then can go up to ch16
_then if you release the first pad, ch2 is marked as free, so next pressed pad can/will use ch2 again, even if not same pad

Hi,
This is why you should discriminate the pad by it's note number, not its channel

use the new midi dispatch MPE module in a polyphonic sub-patch, then filter by note inside this sub-patch to dispatch the midi controllers that are going with that particular note,
then send the data outside the subpatch to the 3 different synth/samplers

I'll try to make a patch soonish

edit : I'm investigating the MPE module, not sure it does the trick... stay tune !

Olivar

In fact it depends what goal comes after,

if that's remoting ie like in other daws an "MPE" synth or patch, you don't really need to be "pad" aware, what matters is that the current/ each poly voice / midi channel got its own datas, so more "voice aware" that could be called maybe
(but yeah indeed if use HH7, could directly use new Poly Voice Dispatcher MPE module probably easier)
but if need to do someting relative to a specific pad, that remain the same/different for that specific pad than any other pad, then yeah that would be different/per note system

for ex got a sensel morph here that remote MPE hardware, and pers i don't do stuff relating to each pad/note, i just ensure each played voice got each own midi channel.
the sensel morph "driver" itself take care of the channels distribution, pretty sure exquis works same way (mean ie a C3 note does not have an "associated" static midi channel, this is dynamycally allocated)

here's 2 solutions for your PADs :
The all midi solution is simpler to use but could send false messages if you hit non assigned pads. (hence the split, that could be replaced by a note number filter)

Hi Olivar
With this patch, when I release a pad it happens that the sound keeps on playing.
Do you have this kind of behavior?

XpiR wrote: ↑

10 Oct 2026, 18:01

Hi Olivar
With this patch, when I release a pad it happens that the sound keeps on playing.
Do you have this kind of behavior?

Hi !
the all-Midi-solution is not very reliable, I'm afraid