|
Post by somervid111 on Feb 28, 2016 4:30:10 GMT
I use Blueboard with Luminair lighting app, I need to setup the output of one of my BB pedals to cc00 for master blackout and send another ccXX to Toggle playback off at the same time. Can this be done with the +C flag in a stream byter script? I tried a bunch of scripts using the Stream Byter guide but I'm lost on how to configure midi bridge to do this. Luminair midi output shows up in midibridge so do I connect blueboard input to Luminair output and use stream byter at Blueboard port?
Any help or advice you can give would be greatly appreciated.
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Feb 28, 2016 11:08:54 GMT
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 CCWhen 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.
|
|
|
Post by somervid111 on Mar 1, 2016 19:54:13 GMT
Nic, Thanks for the prompt reply, the script is sending cc64 ok but for some reason Luminair only responds to the cc64 message, The master blackout cc00 is not responding. I checked that without midi bridge running, both cc's perform their function separately within Luminair, I did see the cc00 Master Blackout in Luminair flash the odd time when pressing the BB pedal but it wouldn't operate.
Any ideas?
Thx
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Mar 1, 2016 20:26:04 GMT
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 CCSee 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.
|
|
|
Post by somervid111 on Mar 3, 2016 3:54:59 GMT
Nic, I checked cc00 to Luminair with the line 2 commented and it is odd, Luminair has a midi learn mode and the cc00 message is picked up when learning master blackout function but the function won't operate when patched through midi bridge, yet when you disconnect Luminair from the BB output the cc00 message works fine. I tried delaying cc64 and the delay works but doesn't help cc00.
I also tried to put BB into PC mode and tried using PCs but same type of issue. Luminair does not allow me to pick the input so I assume the BB is coming in via inter app and also through midi bridge. There is a Listen channel setting in Luminair and it is set to listen only to Ch1.
Thx
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Mar 3, 2016 9:57:18 GMT
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.
|
|
|
Post by somervid111 on Mar 3, 2016 13:53:52 GMT
Nic, There is no way to select the listen port on Luminair, I suspect conflicting messages. When I first install the 2cc rule and fire up Luminair the first press of the pedal momentarily activates both functions but then only the cc64 function operates after that and no cc00 message works. I thought I would have to deal with the latched messages as well but the BB appears to do what I want (I.e press cc00 pedal Master Blackout activates and lights stay off until I press again, it is also ok for the cc64 action as well).
If you can figure this one out for me it would probably be handy for other apps with simple midi settings. I do greatly appreciate the support.
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Mar 3, 2016 16:41:56 GMT
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.
|
|
|
Post by somervid111 on Mar 3, 2016 19:40:51 GMT
Ok, I was going through all the settings in Luminair, given the app cost $120 something didn't add up. I went to my network connection settings in Luminair and found that I can scroll down the settings and voila the midi port settings were there! I set it to only listen to midi bridge and installed original 2cc rule you gave me and after restarting Luminair IT WORKED!
it is a poor place to put the port setting, I fully expected it on the midi setting page. I only checked a couple presses so far. I will cross my fingers.
i really appreciate the support, never had such good service even on the expensive software I have! All the best!!
|
|