The BlueBoard's aux ports always transmit CC values. By default these are 1 and 21 (decimal).
If using a footswitch or pedal do make sure you use the 'calibrate' feature of the BlueBoard app so that it is setup so that when you press down the pedal all the way or switch that this sends the maximum controller value of 127 and 0 for switch up/pedal up.
You will need the hex codes of the notes you want to map from midi note table
Once you have the note(s) you want to map, add rules like this to the Stream Byter as per the rest of this thread:
X1-F = XX +B # block unwanted BB channels B0 01 7F = 90 3C 60 # aux1 on to note C3 at medium volume B0 01 00 = 80 3C 00 # aux1 off to note off B0 15 7F = 90 3E 70 # aux2 on to note D3 loud B0 15 00 = 80 3E 00 # aux2 off to note off
You may need to adjust the rules to select the actual notes you want and set the volume the notes will play at to taste.
I also have some standard drum triggers that are sending 127 and when I hit them they respond by cutoff of the signal gradually. Any way of reversing the signal so that it'll do what I'm doing with the foot switches?
I think I'd need to see what those triggers are sending MIDI-wise to determine how it could be simulated. Might be tricky.
What I suggest you do is download the free 'Midi Monitor' (or the not free but will spit out events Stream Byter style MidiVision) and connect one of the drums to it, strike the trigger and then post the Midi Monitor screen shot of the MIDI events.
It seems to send a barrage of foot controller events from 0 to 127 over time on channel 2 per hit.
The following rules would replicate this over 1 second. Add these rules at the bottom. I assume that you have a modified set of rules for your own setup, so you might need to adjust these to suit, but essentially we are going to issue those controller messages each time we see a note on:
Finally got some time to work on this again. I'm following all of the directions, midi bridge is seeing the foot controllers, I've calibrated them correctly, I've typed the code in and configured the dm1 stuff and I'm still not getting it to register. I thought I was going crazy so I went back and recreated the moment I was able to get sound from the BLUEBOARD pads themselves and they worked. Is there something I could be missing? Has anyone else tried to get the expression signals to translate into notes and got them to work? Help!
I have a BlueBoard and DM1, so if you could please post your current set of rules you have in the Stream Byter and I will make them work.
Note that DM1's virtual MIDI port (I think) can be unreliable. I strongly suggest you route the BlueBoard (left) to MidiBridge (right) in the MidiBridge Interfaces view and not to the DM1 virtual port. In DM1 you tell it to listen to MidiBridge.
Pretty much any app that will honour events coming from MidiBridge or has its own (working) virtual input. Even GarageBand can be made to trigger drum hits from the BlueBoard and that is probably one of the most tricky in terms of its MIDI implementation.
I'm a bit lost with what you have / don't have working. Is it just triggering notes from the aux inputs on the BlueBoard that are causing grief now or is it everything?
Like I said, I have DM1 + BlueBoard, so if you can outline which buttons on the BB you would like mapped to which sounds in DM1 then I can construct a step-by-step recipe for you.
I can get the blueboard PADS themselves to trigger the dm1 kick, like you mentioned. But the aux pedals, while midi bridge recognizes it, does not trigger anything and I realize (I think) it's because I don't know what "note" the kick drum in dm1 is.