I’m hoping to set up a sampler preset in which multiple samples are played, but each is triggered only when a specific midi key is pressed. For instance…C1 would fire one sample, Db1 would fire another, D1 yet another… so on and so forth.
NP setting up multiple sampler modules and having them respond to start on MIDI keys, kinda clueless how to set that logic up so only one key out of 128 fires each one alone.
you can use my MTTR module
Thank you so much for responding. I found MTTR on this forum, installed it and gave it a try, but it seems i am unaware on how to get the MTTR to respond to my midi keyboard. I actually made a YouTube video about the problem i’m having. Would be endlessly appreciative if you could give me some advise:
I tried adding the MIDI module b/c i could not get the MTTR to respond to the keyboard without it, either.
see also here about this use case:
Thank you for responding.
I’ll cover three things (1) what i’m trying to accomplish in the long run, (2) the problem i’m having so far and (3) what i believe is the input signal each SAM module I need to set.
I want to crate a patch that triggers multiple samples to play through when the single midi note assigned to each SAM is depressed. In most instances, there will be a total of eight or less of these MIDI key/sample pairs. In one or two presents there will be up to 16 individual samples that will need to be individually triggered.
I was going to use the MTTR modules to do this decoding. For example purposes lets say that the first MTTR has trigger A thru H assigned to midi notes 24 thru 32. Each MTTR channel would have its own SAM module to trigger, so the eight SAM modules would be patched to respond to Trig A: SAM: Gate 1 thru Trig H: SAM: Gate 8 respectfully.
If on my midi keyboard i depress the key midi note C1 (note number 24), the SAM patched to MTTR Channel A via the Trig A: SAM: Gate 1 connection plays through. If i then press midi note D1 (note number 26), then the SAM module patched to respond to Trig C: SAM: Gate 3 begins to play it’s own stored sample over that, etc etc al the way through to every MTTR/SAM module set in the patch.
If a given preset requires more than 8 samples to be available, then i would use multiple MTTR modules, all assigned to separate midi keys with no repeats. So if i had to add a second MTTR to what i described before the second MTTR would have it’s channels A-H set to decode MIDI notes 33-41
I understand that if my patch requires more than one page on the SSP that BUS modules would be required on each page to route similar signals to each page.
For instance, if I’ve set MTTR channel A to midi to 24 ( which i am under the impression means C1 on a midi keyboard), when I press the C1 key on my midi keyboard, I am not seeing a gate signal passing out of MTTR channel A, which leads me to believe i don’t know the proper way to route the MTTR to my midi keyboard connected to the center USB input on the SSP.
So the first problem i am having is how do i get the MTTR linked to the MIDI keyboard coming from the keyboard connected to USB? It is confusing to me how to make that connection? It is confusing to me because the MTTR doesn’t have input variables listed. Is it a MIDI channel problem?
The first SAM is set to receive Trig A: SAM: Gate 1
The second SAM is set to receive Trig B: SAM: Gate 1
Possibly my problem is i don’t understand what the difference is between the Gate 1 thru 8 outputs.
Thank you so much for your time and attention to this
I already replied to you email…
you press LS+RS to together whilst on the MTTR module.
this then brings up a new ‘window’ where you can select midi device - basically press DEVICE button, then turn the midi in encoder.
by default its omni (aka ALL) channels, but you can select a specific channel if you want.
(If you look at my SSP video, you’ll see me doing this for midi learn… its the same process)
why is it done this way?
because the SSP has no concept of a midi connection.
this means each MIDI module is (note) monophonic, so if MTTR were to use cv, you would also need to wire up 8x MIDI modules to 8 x v/oct inputs and 8x gate inputs.
… and also deal with the complication of routing via a BUS due to the 8 → 1 issue.
so yeah, that makes zero sense to me 
for sure, I could make my modules do as MIDI does which is use to the FIRST midi device.
but I wanted to support multiple usb midi devices, which the MIDI module does not. so instead I wanted to have midi device selection.
note: whilst this might appear ‘confusing’ at first, its the same on ALL of my modules, and is also how midi learn works (on my modules), so once you know it, it ‘just works’ ™
sorry, what gate outputs?
MTTR outputs trigs not gates… (iirc).
the idea is then to use one shot samples…
there is not particular reason I chose trigs rather than gates, other than the fact when I created MTTR I needed trigs as I was using for a drum sequencer. hence the name of the module.
I could do a gate variant, I guess.
The MTTR have commands called Trig (A-H):MODULE NAME: GATE (1-8), that’s why i referred to them as 'gates". I understand they are only triggers.
Thank you for you help on the LS+RS…i’ll try it out.
Quick question…I assume you meant watch a video on your youtube channel? Which specific SSP video do i need to watch for the midi learn? The only one i can find that address this involve the XMX and your TRAX plugin. Could you post a link here? Thanks.
Trig (A-H):MODULE NAME: GATE (1-8)
yeah, so the input to ‘MODULE NAME’ is gate.
but often trigs can be used in places of gate, ,assuming the length of the gate is not relevant.
e.g one shot samples, or an env if you are not interested in sustain element.
i do think there’s a issue with the MTTR module;
i can use trig A/C/E/G but not B/D/F/H
this reads almost like a DNA sequence 
yes, the corresponding MIDI notes are received ; they show up in the MTMO but don’t trig sh*t
could you confirm?