BomeBox/MTPro/?BomeNetwork - Routing Options for Development

Apologies in advance for one of my ambling questions - this one should prove to be worse than any previous. Sorry.

 

tl;dr -
Two connections for playing:
USB MIDI Inputs -> Hub -> BomeBox
and
DIN MIDI -> BomeBox DIN
*where BomeBox runs BMT script

Need to be changed for development to:
USB MIDI Inputs -> Hub -> Laptop -> BomeBox
and
DIN MIDI -> Laptop -> BomeBox DIN
*where BomeBox runs no script, routes everything straight through, and script is being edited/tested on the laptop

NOTE: I have a working system which involves moving cables around, but I'm hoping for a more elegant approach which I may be overlooking perhaps using BomeNetwork.

--

I'm sure others have wondered about this, but I couldn't find anything from searching the Forum yet.

I have a BMT script that uses Global Variables to "do things". These variables change based on selecting a Preset which is done via incoming MIDI msg.

Okay: I have a sequencer that when I load a song it sends to CH16 on a specific Port a PgmChg msg which loads the BMT Preset which loads the Global Variable values I use for that song.

Awesome.

But the problem lies in going between BMT on the laptop and BMT on the BomeBox: I can't update the variables once the script is on the Box - or rather, if I can then they are not  part of the script itself and they need to be since reading/writing global variables via sequencer data is cumbersome. (Cute and fun, yet cumbersome)

Right now I do a hardware switch.
In my rig, my sequencer sends out via USB and DIN MIDI. I use both (because: >16 Channels)

For the USB bit, I 'break' the connection between the USB Hub and the BomeBox and connect the hub to the laptop, which handles data IO for the USB MIDI stuff.  Easy peasy.  For the DIN MIDI stuff, I use a UM-ONE going from the sequencer into the laptop, and then into the DIN MIDI on the BomeBox.  Then the BomeBox has no script loaded and just a straight through routing.

So, once I have the script variables determined, I load the script to the Box, reconnect the DIN MIDI from the sequencer to the BomeBox, re-establish the connection from the Hub to the Box.

I'm wondering if there's a more elegant way to handle this, perhaps via BomeNetwork. I'm obviously having a difficult enough time visualising what I've got going on now, so I'm terribly sorry I haven't a clue how to properly ask this question.

I'm not sure how involved I need to be offering data to help me get through this.  I mostly have a system that is variable for inputs, but generally there are 5 data inputs to my system, 4 through USB MIDI and 1 through DIN MIDI. These get distributed to USB MIDI and DIN MIDI destinations, the latter of which are partially through a 2x2 MIDI Interface connected to aforementioned USB Hub, and others receive data from BomeBox DIN Out connected to a Kenton Thru box.

Would a picture help?  LOL
(I think a picture would be more confusing)

I'm a picture sort of guy so it would probably help.

With that said, one of the issues I commonly run into is that when hooked to BomeBox, none of the USB ports are exposed individually to the network.  This means i have to move the USB hub from BomeBox to PC for development and then back.  I'm told that multi port network support is coming soon so that with aliases you should be able to be able to more quickly move from BomeBox to PC and back more easily without having to move the USB attached connections.  

I don't know if I covered all of your issues but I think this will be the most major improvement in development.   

I know that persistent variables are also on the list of requests but not sure where that is on the priorities. I know, however that multiport network is very high on the list and I'm hoping that will be available sometime this summer.

 

Steve Caldwell
Bome Customer Care

---

Also available for paid consulting services: bome@sniz.biz

 

I really thought my simplified english explanation was best with the

USB MIDI Inputs -> Hub -> BomeBox
and
DIN MIDI -> BomeBox DIN
*where BomeBox runs BMT script

Need to be changed for development to:
USB MIDI Inputs -> Hub -> Laptop -> BomeBox
and
DIN MIDI -> Laptop -> BomeBox DIN
*where BomeBox runs no script, routes everything straight through, and script is being edited/tested on the laptop

--

But alas: I am also a visual person.
usually that vision resides in my head - or on hundreds of slips of paper, backs of bills, post it notes, envelopes, etc.  LOL  To attempt to translate to another human is a daunting task indeed!

Okay, let\'s try this...attached is a current layout in a not-pretty drawn way. Sorry. Just a rough quick sketch.

The solid lines that parallel a dashed line indicate Development Mode.
The dashed lines indicate connections made for Play Mode.
The two places this occurs is between the Pyramid OUT DIN A either thru the UM-One + Laptop to BomeBox DIN IN (Development) vs Pyramid OUT DIN A right to BomeBox DIN IN, or the USB Hub to the BomeBox which a physical connection is swapped at [Panel] - Development Mode is USB into the Laptop or Play Mode is a short USB A to USB B cable making the connection straight thru at the [Panel].
The DIN loop that includes the UM-One is completely replaced (no UM-One at all). That is, the connection from the Pyramid Sequencer OUT DIN A is a MIDI Cable to the BomeBox DIN IN for Play Mode, but goes to a UM-One and to the Laptop for Development Mode.  The OUT for the UM-One goes to the BomeBox DIN In and the BomeBox is no longer running a script and just routes DIN IN to DIN OUT. (DIN OUT goes to the Kenton Thru to the rack synths)
The USB connection change between Play and Development Modes happens at that rectangle marked \"Panel\" (which is actually a panel at the back of a rack case where most of this equipment is mounted, or sits upon).  In Development Mode, a USB cable is connected from the Hub connection to the Laptop. In Play Mode, there is a loop USB Cable that replaces the connection to the computer and routes it into the BomeBox.  (Picture a rack mount knockout panel for Neutrik D-Type connectors, one with a USB B and one with a USB A.  This is where the hardware connection is switched between Development and Play Modes)
The USB portion of the show is completely cut out of the BomeBox loop when in Development Mode.

I\'m including an image of the back panel where I swap the USB connections figuring that might help visualise. It\'s currently set up for Development Mode, so the white USB Cable is going from the USB B connection there to the laptop running BMT.  In Play Mode I have a short USB A to USB B cable that just loops between those two connections.

 

Note: Incidentally, all external connections to the rack case are facilitated by a sort of \'data patch bay\' which includes connections for synths audio in to the rackmount mixer, out from the mixer outputs, and all the data connections to the DMX box, the Rample, the Minitaur, Pyramid, P12, etc.  (Because: I\'m weird that way)

For shorts and goggles I\'m including that bit there - it makes the connections all available to me. This is \'dining room mode\' for the rig, so no Prophet 12 nor DMX and monitoring via headphones rather than the Audio Out.
And yes: I love Emu products. The later Proteus models arent as resilient (XL1 & Planet Earth), but I have yet to crash an Orbit (and those are #2 & #3 - my #1 was purchased when they were brand new).

So, even if the USB devices are not discoverable if they\'re connected to the BomeBox, is there (and I\'m asking this because I\'m terribly confused on BomeNetwork even though I was using it for awhile - i still didn\'t understand what I was doing but it just worked and I didn\'t question it) a way to perhaps re-route the connections at the BomeBox, transfer the incoming data via WiFi to the laptop, then send the data back after processing to the BomeBox?

That is, keep it in Play Mode.
As the data comes IN to the BomeBox either via DIN or USB route that via WiFi to the laptop running Bome Network, and then using Bome Network route that data back for distribution?  I would find it easier to just swap a Translator on the BomeBox rather than change physical connections.

I\'m sure this issue is well out of the scope of free support of BomeNetwork, BomeBox, and MIDI Translator Pro. I guess I\'m offering this as an exciting brain teaser!  LOL  Then again, you know you only have to mention a few things and I can figure out a bit on my own.

Youd think if I can get this far, and with everything I have already created in my Translators I should be able to figure it out on my own. Sorry.

Oh, Just was reading the info/response on the query about USB Hosts. My 2x2 interface is actually an iConnectivity with an available USB Host connection, but honestly my brain gets really fried when I start thinking in too many variables. I've never used that feature so it hurts my head to think about it but...should I? Hrmmm