Use Alesis Trigger iO with Superior Drummer 2 - Bome Forums Archive 2005

florian

2011-08-02 12:01:50

A user asked this:
Alesis Trigger iO, and superior drummer 2, and there is an incompatibility issue between the two of them.
For variable Hi-Hat sounds, the Trigger iO sends a 0~128 signal separably from the cymbal signal (I couldn't understand how that 0~128 works in therms of MIDI), which indicates the expression of the Hi-Hat cymbal (from fully open to fully closed). The Superior Drummer 2 can only receive 4 separate notes (fully open, fully closed, half open, half closed) for the Hi-Hat cymbal.
My question is, can I use your software to remap both MIDI notes into each of the 4 notes?

Code: Select all

Trigger iO                                        Supperior Drummer
Cymbal               expression
    on                  0~32                         MIDI note A
    on                  32~64                        MIDI note B
    on                  64~96                        MIDI note C
    on                  96~128                       MIDI note D

florian

2011-08-02 12:13:55

This is quite easy with Midi Translator Pro!

This is the straight-forward way:

Code: Select all

Translator 1: Hihat state 1
Options: stop=false
Incoming: MIDI 90 40 pp 
Rules: 
  if pp>32 then exit rules, skip Outgoing Action
Outgoing: MIDI 90 01 7F

Translator 2: Hihat state 2
Options: stop=false
Incoming: MIDI 90 40 pp 
Rules: 
  if pp<=32 then exit rules, skip Outgoing Action
  if pp>64 then exit rules, skip Outgoing Action
Outgoing: MIDI 90 02 7F

Translator 3: Hihat state 3
Options: stop=false
Incoming: MIDI 90 40 pp 
Rules:
  if pp<=64 then exit rules, skip Outgoing Action
  if pp>96 then exit rules, skip Outgoing Action
Outgoing: MIDI 90 03 7F

Translator 4: Hihat state 4
Options: stop=false
Incoming: MIDI 90 40 pp 
Rules:
  if pp<=96 then exit rules, skip Outgoing Action
Outgoing: MIDI 90 04 7F

This will send MIDI notes 01, 02, 03, or 04, depending on the velocity range of the Note sent by the Trigger iO. Replace the Outgoing Note number with what you need!

I assume the Trigger iO note is 0x40 (hexadecimal), i.e. Note 64 (decimal). You can use MIDI Capture in the Incoming action to get the note directly from the Trigger iO. Then replace the third number with the pp local variable.

For every outgoing note, there is one Translator Entry. That makes it easy to understand and to modify. The outgoing velocity is always full velocity. There is no Note Off.

Hope that gives an idea!
Florian

florian

2011-08-02 12:20:27

I guess that the Trigger iO sends different velocity for how hard you play. So if in range 0..32, 32 will be the hardest for that hihat type and 33 will be the lowest for the second hihat type.

If you want that, you can add rules to calculate an outgoing velocity:

Code: Select all

Translator 1: Hihat state 1
Options: stop=false
Incoming: MIDI 90 40 pp
Rules:
  if pp>32 then exit rules, skip Outgoing Action
  qq=pp*4
  if qq<1 then qq=1
  if qq>127 then qq=127
Outgoing: MIDI 90 01 qq 

Translator 2: Hihat state 2
Options: stop=false
Incoming: MIDI 90 40 pp
Rules:
  if pp<=32 then exit rules, skip Outgoing Action
  if pp>64 then exit rules, skip Outgoing Action
  qq=pp-32
  qq=qq*4
  if qq>127 then qq=127
Outgoing: MIDI 90 02 qq 

Translator 3: Hihat state 3
Options: stop=false
Incoming: MIDI 90 40 pp
Rules:
  if pp<=64 then exit rules, skip Outgoing Action
  if pp>96 then exit rules, skip Outgoing Action
  qq=pp-64
  qq=qq*4
  if qq>127 then qq=127
Outgoing: MIDI 90 03 qq 

Translator 4: Hihat state 4
Options: stop=false
Incoming: MIDI 90 40 pp
Rules:
  if pp<=96 then exit rules, skip Outgoing Action
  qq=pp-96
  qq=qq*4
  if qq>127 then qq=127
Outgoing: MIDI 90 04 qq

I guess you see from this example how the velocity can be mapped.
Florian