Setting up a route to a remote software process

I’m setting up a basic MIDI route from Bome MIDI Translator Pro on host ‘Husky’, through Bome Network Pro, to a software process (OBS = Open Broadcaster Studio) on another host ‘Atlas’.

=== Irrelevant Backstory

I was previously sending this MIDI traffic out Husky to a port on my BomeBox, which routed it out a USB MIDI port to a MIDI Hub over USB to a SevillaSoft MIDI-MIDI bridge (which lets two USB hosts connect to each other when both have USB-A) into Atlas, where it was split by MIDI channel into four software MIDI streams, one going to OBS. Needlessly complex when I could just connect directly over Ether to Atlas.

=== END Irrelevant Backstory

So I set up a virtual MIDI Port [BN OBS] in Bome Network Pro both on Husky and on Atlas.

I go to set up a route in Bome Network Pro on Husky. On the [Add Route] page, I think I want the Route:

  • [IN: BN OBS Virtual In] => [OUT: Atlas: BN OBS Virtual Out].

However, I get these two choices …

BN OBS Add Route_Screenshot 2025-05-18 151215

… a choice between:

  • [OUT: Atlas: BN OBS Virtual] and
  • [OUT: Atlas: BN OBS Virtual Virtual Out]

as targets. I’m pretty confused …

  • What are these two OUT choices?
  • What is Virtual Virtual??

EDIT: I tried each in turn:

  • [OUT: Atlas: BN OBS Virtual] works. Not sure what this entry is.
  • [OUT: Atlas: BN OBS Virtual Virtual Out] does not work.

Related question: When I move this .BMTP project from PC workstation Husky to my BomeBox ‘RBB’ (Rig BomeBox), will RBB be able to output to the Bome Network Pro virtual port on Atlas [OUT: Atlas: BN OBS Virtual]??

OK, yes this is somewhat confusing.

As explained by Florian earlier.

“BN OBS” would be the port exposed over the network.
“BN OBS Virtual” would be the associated port exposed to the local computer.
My guess is you are using Remote Direct MIDI as well and it’s local port might be exposed as “BN OBS Virtual Virtual”. (part of the auto routing explained earlier).

If you are doing your own routing without Remote Direct MIDI, then you should probably turn it off on those ports.

For instance is you expose “BN OBS” as a remote direct MIDI port it will be exposed on the other system as “BN OBS Virtual” ( for the network connection) and the local connection would be “BN OBS Virtual Virtual”.

As Florian put it, perhaps the automatic routing should have an option to hide these connections to avoid confusion. They often confuse me as well.

Steve Caldwell
Bome Customer Care


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

Got it!

… and …

When I move this .BMTP project from PC workstation Husky to my BomeBox ‘RBB’ (Rig BomeBox), will RBB be able to output to the Bome Network Pro virtual port on Atlas [OUT: Atlas: BN OBS Virtual] ??

Great question! I think you will need to either

Target both machines for output from your main output port “RBB” and the route RBB Virtual on your machines to BN OBS.

or

Use Remote Direct MIDI to access the physical device connected to your BomeBox from both computers.

As you know, BomeBox does not have user creatable virtual ports and cannot use remote Direct MIDI from a different host, (yet)

I think I’d need to play with it a bit to figure it out.

You always ask the hard questions :wink:

Steve Caldwell
Bome Customer Care


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

I didn’t know OBS supported MIDI except maybe if you are running some sort of MIDI plugin.

There’s a dedicated MIDI plugin (several, maybe) for OBS. However, those have been superseded for my needs by the recently-added MIDI capability built into the [Advanced Scene Switcher] plugin to OBS. I fire scene changes from a Novation Launchpad MINI Mk3 (‘LMM3’).

I also have connections to software processes on a laptop for:

  • Nestdrop - a visualizer that I overlay over some live camera scenes in OBS or use it full-screen occasionally (with sprites fired off the LMM3).

  • Surge XT - for ‘way out’ sounds (my ‘real-world’ sounds are mostly handled by a Turbo VL70-m).

  • Cantabile - for other soft-synth VSTs such as SWAM, EVI-NER, Respiro, Suonopuro plugins, Kontakt, …

My goal (getting close) is to have any software process run on any host in the studio, and have any hardware device connected to any host.

Sounds like a good tool!

A good goal. Aliases should help immensely here.

Steve Caldwell
Bome Customer Care


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