Ableton // multiple devices // Bome Network

BoeseFuchs

2020-08-09 18:40:03

Hi everyone,

I'm new to the whole BomeBox universe so far but - even though I'm struggling a bit right now - let me say that I already love the almost endless capabilities! We're a Female Fronted Metal Duo from Berlin, Germany, playing every instrument on our own on stage, using Ableton Live for that and the BomeBox has been the solution I was looking for regarding all the functions, etc.

I would say I'm pretty firm with technical stuff, including network protocols, standard MIDI functionality, etc. and I've gone through the manual AND the YouTube tutorials but I'm still feeling like I'm missing information and I just can't get it figured out on my own, so really hope you're able to help me, feeling a bit dumb here :-/

So, regarding the problem:

We currrently have two BomeBoxes running, named BomeBox SLY and BomeBox VALY, a third one will be added in future. BBSLY is directly connected to an unmanaged 16 Port PoE Switch, via Cat 7. BBVALY gets its power from the PoE Out of BBSLY. I already properly installed them and did the basic configurations done, like password, firmware update, pairing etc. BBVALY works as Ethernet Master; BBSLY, Mac Pro and all other devices in our network are slaves. BBVALY, BBSLY and Mac Pro are paired.

When accessing each boxes Web Config, all devices pop up in MIDI Port section, so they're plugged in correctly, I assume. I've already bought & installed unlimited MIDI Ports Add-On, as well as MIDI Translator Pro (for future stuff). But well, that's where the problems begin: I don't know where and how to properly configure the MIDI Routing, so that:

I'm aware of the MIDI Routing function in web config and already tried:

But when switching to Ableton, only both of the network streams (SLYBome Net and ValyBome Net) are chooseable as MIDI Ports. Already learned that this is because current firmware only supports one Ethernet stream, correct? So I thought, okay, let's switch to Bome Network Tool and just make a new virtual midi port, named Launchkey for example. And indeed, this one pops up in Ableton then...but still can't get a MIDI signal from the Launchkey in. Besides, do I need to choose the Launchkey in MIDI routing or the USB Launchkey (Alias)? Also noticed that you have MIDI routing options in the Network Tool as well...and that confused me..I just don't know where to make the correct settings for that since there are multiple options (web config, network tool or should I use Translator Pro?)

I know that this is a beginner question, really feeling stupid here but yeah.. Help please :-(


Attachments:

Signalchain_MIDI_BomeBox.pdf
IMG_6682.pdf

Steve-Bome Forum Moderator

2020-08-09 20:41:03

Hi,

Thanks for the detailed description on what you have and what you want to do!  In a nutshell as I understand it, you want to be able to see all 11 attached devices from Both Bomeboxes from Ableton Live on your Mac as separate ports instead of 1 or two MIDI streams (BBSLY and BBVALY). 

Unfortunately, creating multiple virtual ports on your Mac, will not completely solve this since the network connection still only supports only 1 stream between any 2 devices. Although you can add additional virtual ports with unlimited virtual ports, you will need to route them to/from an existing real port so what you will end up getting is a copy of one of the existing stream.  The feature that is being developed right now, however should solve this on a later version of Bome Network Pro and BomeBox firmware.

 

In the meantime, you have 2 choices.

1) Put MT Pro projects on your BomeBoxes that translate from each device yet on a different MIDI channel and then use the MIDI channel number in Ableton Live to differenate them in the existing stream.  This solution, however will not help if you are using MIDI Remote Scripts in Ableton Live (that expects, for instance MIDI CH 1 on a different port for each attache Launchpad).

2) I have developed a workaround as shown in the attached picture.  What I do is from the sending device, I encode the existing MIDI Stream into a SysEX message and add routing information within that message. Then I decode that information and using different preset configurations, decode and  route to a different port on the receiving end.  I can create new virtual MIDI ports for that so that ultimately Ableton Live can see them independently and use the native MIDI channel of each device.  Basically it is a stream multiplexer using MT Pro.

What I haven't tested, is how Ableton Live handles SysEx messages that are bound for only a specific device as I do not encode/decode existing SysEx Messages. So I'm not 100% sure how Ableton Live will handle the initial device handshake if using Sytem Exclusive mesages.

 

I'm hoping that I don't need to implement my solution on a wide scale as I believe native multi-port stream support should be coming soon. I'm happy to share my rudimentry "netsend.bmtp" and "netrcv.bmtp" project files if you want to give it a go. In fact I think I recently posted them for another user.

 

 

Steve Caldwell
Bome Customer Care


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

 

 


Attachments:

multi-port-sysex.PNG

BoeseFuchs

2020-08-10 12:17:57

Hi Steve,

thank you so much for your quick answer! I don't want it but I think solution two is the way to go. Is there any manual or tutorial for the whole SysEx topic? That's completely new to me, never used that before. 

Would also be very happy about your rudimentary project files!

Thanks in advance

Valy

Steve-Bome Forum Moderator

2020-08-10 15:27:57

Hi,

The post with the links to the MT Pro files is here.

The actual file links are below:

Net-Sysex-Rcv-2018-10-03a.bmtp

Net-Sysex-Send-2018-10-03a.bmtp

As mentioned, they are far from a complete solution for your situation. They are simply samples on how it can be done but there would be quite a bit of work and testing for your specific solution.

  1. Example for one way communication only.
  2. Example for 2 MIDI ports only
  3. Example does not encode-decode SysEx to different ports

Again, hoping the Bome releases the new multi-port solution soon.

System Exclusive is part of the MIDI specification, however for the most part it is up to the manufacture (in this case the user) to define the exact format needed for a specific situation. The Key is, it always starts with 0xF0 and ends with 0xF7.

 

 

Steve Caldwell
Bome Customer Care


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