Script for sending 2 cc's

Hi somervid111 ,

Yes, you would connect blueboard app to luminair in MidiBridge for the routing. Yes, you would use the +C clone flag

On the blueboard input or luminair output add a Stream Byter (use beaker icon) and paste in rules like this:

# BB/luminair
X1-F = XX +B # block unwanted BB channels
BX 00 = XX 40 +C # clone extra CC

When MidiBridge sees a CC 00 (on channel 1) come in, it will send a CC #64 along with it to luminair. I just choes CC 64 if you want a different CC # then you need to change the bolded value (40) in the rules to whetever luminair is expecting; don't forget these are hex numbers.

Regards, Nic. 

Hi somervid111,

First of all, make sure that CC0 works via MidiBridge by altering the ruleset to put a '#' in front  of the last line, so effectively all it is doing is blocking the duplicate BlueBoard messages on channels 2-16.

If luminair responds to CC0 via MidiBridge then maybe we need to delay the CC64 a touch (don't ask me why). Uncomment that last line (remove the #) and after the +C add +D1000, so your rules should look like:

# BB/luminair
X1-F = XX +B # block unwanted BB channels
BX 00 = XX 40 +C +D1000 # clone extra CC

See how that goes. I do wonder whether luminair is seeing the CC0 from the BlueBoard app as well as MidiBridge (seeing double). I'm not familiar with luminair, but if it can be configured to only listen to particular MIDI inputs, ensure that MidiBridge is enabled and BlueBoard is disabled. If it has no port selection feature does it have the ability to set which channel to react to?

Regards, Nic.

Hi somervid111,

I wonder whether Luminair is seeing conflicted messages from both the BB and MidiBridge.

Could you please let me know whether Luminair has the capability to allow you to select which MIDI port(s) it listens to? This will determine how we approach this; if we can't stop it listening to the BlueBoard virtual source port we will have to do some extra gymnastics.

It has just occurred to me - The blueboard sends out 16 CC messages (one per channel) when you press one of those buttons and furthermore, they are latched so alternate between CC0 ON and CC0 OFF. We will need to handle the latching issue in our rules

What we want to do is:

- have Luminair listen only to MidiBridge
- have Luminair learn CC0 for one action and CC64 for the second action
- trigger our two CCs on BB CC0 on *or* off

However, if you can let me know the answer to the first question, then I can advise how to setup the rules and get Luminair to learn what we want.

Regards, Nic.

Hi somervid111,

OK, if Luminair does not have the facility to listen only to a certain port, then we have to make sure that all the CCs it learns are never sent from the BB directly.

What this means is that you are going to need to teach it to react to CC's 64, 65 etc (for example) and then in MidiBridge we can do the right thing by cloning the BB CCs to any of the new CCs and Luminair should therefore react only to the MidiBridge ones.

Problem is getting it to learn them because you don't want the BB to be connected during the learn process and you need something to trigger the CCs!

Question therefore - does Luminair have a way of setting those CC triggers manually without MIDI learn? That would get around that problem. Otherwise we'll need to use a different hardware controller or an app like Midi Designer just for creating some CCs for Luminair to learn from discretely.

If we can avoid the learn by doing manual trigger configuration then that will definitely be easier.

Let me know how you get on. Once Luminair is setup to respond to CCs 64 etc then I can make up some rules to send multiple Luminair CCs from the BlueBoard triggers in any which way you like.

Regards, Nic.