I'm completely new to midi and am trying to get the blueboard foot controller to control basic functions in auria. I successfully followed instructions on another thread to toggle mute, but really need some simple commands to record/play/stop/re-record, so that I can punch in parts and overdub, etc using the foot controller exclusively.
I've given a shot at trying to figure this out, but I clearly have a long way to go. Any help is greatly appreciated. Thanks! Jon
From memory, Auria will respond to MIDI start/stop commands, so assuming the BlueBoard is setup in controller mode with the buttons mapped to controllers 0 to 3 (the default I think), these rules in the Stream Byter would do it: (button A = start, button B = continue and button C = stop)
# BB to start/cont/stop B1-F = XX +B B0 00 7F = FA B0 01 7F = FB B0 02 7F = FC
The record button would be HUI controllable, so you have to use similar rules to the mute technique you have already found. I don't know the HUI incantation for that. I'd need to hookup up a HUI and reverse engineer it like I did for mute/solo. I can do this some time over the next few days and update this thread.
In the meantime, try out the rules above and see if they work at all and let me know. If they don't I can kill two birds with one stone and figure those out also when I embark on the reverse engineering task.
There is on online guide to the Stream Byter here which would get you started. The built-in guide in the app is the definitive definition of the Stream Byter capabilities+syntax. Loads of posts on the board here with tips 'n' tricks and if there is something specific you would like to do, please feel free to create a thread here for it.
OK, I managed to setup to monitor the HUI stuff for the transport buttons. Here is how to map the switches to Auria functions. You use the same technique/setup that you have already employed for mute.
I am going to number the transport buttons (these numbers are used in the rules) in Auria as follows:
1. << 2. >> 3. stop 4. play 5. rec
The blueboard only has 4 buttons so I am going to live without '>>' and map button 1 to <<, 2 to play, 4 to stop and 4 to record. Here are the rules:
# BlueBoard>Auria Transport X1-F = XX +B B0 = 90 00 7F +C # ping B0 00-03 7F = XX 0F 0E +C +D50 # preamble B0 00 7F = XX 2F 41 +C +D50 # b1 = << dn B0 00 00 = XX 2F 01 +C +D70 # b1 = << up B0 01 7F = XX 2F 44 +C +D50 # b2 = play dn B0 01 00 = XX 2F 04 +C +D70 # b2 = play up B0 02 7F = XX 2F 43 +C +D50 # b2 = stop dn B0 02 00 = XX 2F 03 +C +D70 # b2 = stop up B0 03 7F = XX 2F 45 +C +D50 # b2 = rec dn B0 03 00 = XX 2F 05 +C +D70 # b2 = rec up B0 00-0E = XX +B # block BlueBoard
The numbers in bold/red correspond to that first list of commands, so if you prefer a different order or set then those are the ones you modify. You need a pair of rules (button down and button up) for each button.
NB the rules above are not compatible with the mute rules. If you want to use the mute rules and transport rules in one scene let me know how you want the BlueBoard buttons mapped and I will produce a combined (non conflicting) set.
No need since the BlueBoard shows up as a separate virtual port so you would see both the BlueBoard and Scarlett in MidiBridge. You are probably best leaving the green line between BlueBoard and MidiBridge and selecting MidiBridge as the 'Remote' MIDI input in Auria.
Unfortunately the subgroups in Auria are located differently depending upon the number of audio tracks, so it is next to impossible with simple event tranformations like the Stream Byter which has no concept of state. More info here
Post by freddytwonotes on Jan 7, 2015 14:46:29 GMT
Thank you again for the transport script, however, I was not able to get the bb buttons to work on unlatch, so the command sends when depressed and the bb button lights but when the button is pressed a second time, the command is not sent. The mute script works useing both latch and unlatch to on/off the mute. What is stopping this from functioning.
I wanted to alter your script to use the play button for both start and stop. Also, This config would be best served by utilizing the four cue points in Auria and useing two buttons for last and next cue point if this is possible.
(a=prev cue, b=next cue, c=(on=play, off=stop), c=rec) Workflow could be much improved with this.
Also, do you plan to add conditional statements to this module.