Rim from Auria has gotten back to me but the news is mixed. There is no HUI command to select a specific fader group. It is possible to do a HUI disconnect (which tells Auria to select fader group 0) and then use the 'forward' command to move up to the correct group. The problem is that since Auria's track count is variable (and we can't know what this is) we still can't determine exactly which fader group the master fader is in. So, it might be possible to control the master fader if it is agreed exactly how many tracks (and possibly subgroups) there are in all tracks - not really practical I don't think.
What I will do is finish off my rulesets that will allow you to switch between two banks on the BlueBoard:
Bank 1 - Buttons 1-4 = Mute tracks 1-4, Expression pedal = fader 1, External switch = move to bank 2 Bank 2 - Buttons 1-4 = Solo tracks 1-4, Expression pedal = fader 2, External switch = move to bank 1
If you want a different layout than the above just let me know.
Here is something to try (as per last post). Assuming the following:
- MidiBridge Scene Channel is set to 16 (Preferences>Options) - BlueBoard in controller mode, buttons 1-4 set to controllers 000-003 - Footswitch in EXT1, controller 010 (calibrated to send 7F when pressed) - Expression pedal in EXT2, controller 021 (calibrated to send 00 to 7F) - BlueBoard is connected and routed to MidiBridge output port (right) in MidiBridge - Auria has MidiBridge selected as Remote Control (HUI mode) as before.
You will need two separate scenes. I am going to assume you will use scenes 000 and 001 in MidiBridge.
Touch BlueBoard 'beaker', select Stream Byter and paste in the following:
# BlueBoard>Auria, steve, scene 0 X1-F = XX +B # remove BB excess
# EXT1 010 switch to scene 001 B0 0A 7F = CF 01 +C
# Toggle Solo # BUT1-4, CC 000-003 B0 = 90 00 7F +C B0 = XX 0F X2 +C +D50 B0 = XX 2F 43 +C +D50
Save this into scene 001 in Scene Panel.
Now, when you hit the foot switch you should see the Scenes change in MidiBridge's Scene Panel as you do so. Switch over to Auria and see if the buttons mute (or solo) and the footpedal controls fader 1 (or 2). Hit the EXT footswitch and buttons control Solo (or mute) and fader 2 (or 1).
The bolded numbers in the fader rules are what you change to access faders 3-8 (change from 0 to 2,3,4,5,6,7).
I am not blocking the original BlueBoard controller events since there is some overlap between them and the HUI events. I think Auria will ignore them since they are not within a HUI packet, but if it's doing strange things then maybe not.
Had a go with this, the mute and bank switch worked as planned. The volume control didn't function and the solo worked on subgroups 4-8. Before you put any more time into this, I may be having (yet another) slight tweak, depending on tonights rehearsal. Cheers Steve
after giving this some more thought, and a couple more gigs to really define how it would me benefit the most, I think I've come down to this
scene1 blueboard buttons 1-4 : toggle solos* on auria tracks 1-4 ext button 1 : switch scene in midibridge ext button 2(instead of foot controller) : possibly auria mute all, or potentially jamup Pro mute
scene2 blueboard buttons 1-4 : do nothing in auria, just operate patches in jamup Pro ext button 1 : switch scene in midibridge ext button 2(instead of foot controller) : possibly auria mute all, or potentially jamup Pro mute
when toggling solos in Auria, is it possible that the button press turns off all other solos, so I'm effectively selecting just one track to be audible for each button press?
hopefully thats simpler and not much more work for you, I'm aware I've taken up a lot of your time
thanks again Steve
Last Edit: Oct 19, 2014 15:24:24 GMT by steve: clarity enhancement
I've looked into your soloing question (button press solos specific track while un-soloing the others) and the problem here is that solo seems to be a toggle only affair which makes things quite difficult since we need to have if/else logic to do this which the Stream Byter doesn't have. It might be possible with many scenes covering all possibilities but this would be cumbersome and prone to failure, so I am going to have to put this in the 'too hard' basket. Sorry about that - you're going to be forced to press two switches to solo one and unsolo the other.
Mute all is sort of possible but again we're subject to the toggle issue, but since you just want one button to mute/unmute all with no other specific mutes, this is just a case of sending multiple mutes on the tracks on one go. Thus I think this can be done.
Operating patches in JamUp is done by converting the button press events to program changes.
To summarise, I can provide 2 sets of rules for you that almost do what you want, but could you let me know the following:
- which Auria tracks do you need muted/unmuted with the mute all switch? 1-4 (8)? - which program changes do you want sent to JamUp in scene1 for the 4 buttons? 1-4?
I think those are the only things I would need to create the two rulesets for you.
- which Auria tracks do you need muted/unmuted with the mute all switch? 1-4 (8)? Tracks 1-4 would be perfect - which program changes do you want sent to JamUp in scene1 for the 4 buttons? 1-4? Ideal scenario here would be if midibridge ignore buttons 1-4 ao that the buttons were picked up directly via jamup pro. -for this scene, midibridge would just be monitoring the scene change external switch, if thats possible (and makes sense?)
Hi Nic, just to report back, I couldn't get EXT1 to switch scenes. I've assigned the correct CC number in the blueboard app, and its working there, but auria isn't seeing anything. JamUp is working as it should too, cheers
I would say EXT1 isn't sending what we expect. Can you load up the free Midi Monitor and press the EXT1 button and see what is being sent when you press/release. Should hopefully just be a simple change.