Connecting Bome Network Pro on my Workstation (‘Husky’) to Bome Network Pro on my Laptop (‘Atlas’) over Ethernet. Works great. Except … I get a slew of auto-generated MIDI Routes. No clue what they do or if I can get rid of them.
Although I don’t quite understand exactly how these work, this is normal. The “Virtual Ports” create are actually some sort of “management ports” that tie together the connections between the physical ports between the machines. If they are disabled, you will likely see that all desired MIDI messages will not go through. I would leave them checked.
I will discuss with Florian to see if there is a better way to explain them.
A few years ago, I had a discussion with him about these and we were talking about either renaming them so that are less confusing.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
These routes are for the main network virtual ports. For example, if you connect to a remote computer ‘Atlas’, then on your local computer, you will have the local MIDI port ‘Atlas’ that other applications see and use as local MIDI port.
Inside Bome network, there will be two sets of MIDI IN/OUT ports:
Internal: IN ‘From Atlas’ / OUT ‘To Atlas’
These are internal ports representing the network MIDI side. Sending anything to the ‘To Atlas’ port will send it over the network to the remote computer. Conversely, the internal port ‘From Atlas’ will receive everything that the remote computer sends.
Virtual: IN ‘Atlas Virtual In’ / OUT ‘Atlas Virtual Out’
These are the representations of the virtual port on the local computer. Sending MIDI to OUT ‘Atlas Virtual Out’ will end up in applications using the ‘Atlas’ MIDI input port. And vice versa for MIDI messages sent by applications to OUT ‘Atlas’, which will be received in BN by ‘Atlas Virtual In’.
In all Bome applications, the ‘Virtual In’ / ‘Virtual Out’ suffix marks an internal side of an internal port.
Now for the whole path to work from the remote computer to an application using the local ‘Atlas’ port, you need these MIDI routes:
From network IN ‘From Atlas’ → to other application OUT ‘Atlas Virtual Out’
and
From other application IN ‘Atlas Virtual In’ → network OUT ‘To Atlas’
BN allows you to disable these routes if you want to route the MIDI streams in a different way. But as ‘auto routes’, you cannot remove them to remind you that they are the expected routes for these network connections.
The same is true for Direct Remote MIDI Ports.
So if you disable some of these routes and everything’s still working as expected, then probably you don’t use the respective virtual MIDI ports outside of BN.
I see your problem though, with the cluttered up route table. Maybe an option to hide auto-routes will make things nicer?
