Bome Network - Virtual Midi Ports - doesn't work

Need about 25 virtual ports and was using loopMidi but often BMT wouldn’t see them so decided to use my Virtual Midi Ports license, see if that would be more reliable but I can’t get any software to respond to any Virtual Midi Port created in Bome Network. They see them, I can route them in BMT, I can select them as the midi port in software but the software does not respond to anything that is supposed to be coming through this virtual port. I then went back into loopMidi, created a port, routed it, selected it, worked fine.

So what am I doing wrong?


Unlike LoopMIDI ports and Bome MIDI Translator, virtual ports Bome Network ports, when created are just end points. You have to route them to get any MIDI to go through them. See this post.

This tripped me up at first also.

Steve Caldwell
Bome Customer Care

Also available for paid consulting services:

So every time I want to route a Virtual Midi Port, I have to go into Midi Router in Bome Network and route them there? Individually, every one? I can’t route them in the graphical Midi Router of BMT?

Edit: Is there any way at all to increase the number of BMT Virtual Ports?

You would create 25 named virtual ports and route each IN to out in the Bome Network MIDI router. This would be a one time setup. They would then behave much like LoopMIDI ports. These are always setup using the Bome Network Interface.

Then in MT Pro you would use your named virtual ports with as many routes as you would like.

We are looking into modifying the GUI for Bome Network MIDI router to make look easier to do it graphically.

I think there is a previous feature request for more virtual ports within Bome MIDI Translator Pro. I don’t have a status whether this is still planned and if so, when it would be available. I’ll check.

Steve Caldwell
Bome Customer Care

Also available for paid consulting services:

If I’m understanding correctly, I’m supposed to route the VMP to itself in the Bome Network Midi Router., is that correct? If so, still can’t get any response.

Yes In to out and it will behave like a pipe.
There are other more advanced routing options but this is what I do mostly. In some cases I add virtual ports and then just route to them as ‘monitoring’ ports.

Sorry Steve, it isn’t working. I routed it in Bome Network Midi Router like you said, then went to BMT to route it how I want and software is not reading it.

What I don’t understand is BMT log shows it as working but the software on the receiving end, nothing.

After doing some searching, came across a thread where I couldn’t get it to work a couple years ago either. Forgot about that :slight_smile:


1 ) Create a virtual Port in this case I call it VM1

  • Select Virtual MIDI ports and the the + sign then give it a name


Click Add

  1. Select the MIDI Router and then the plus sign

Select IN: VM1 Virtual In and OUT: VM1 Virtual Out


Then click Add

3 ) In MT Pro select your input device as your controller and output device a VM1

Either use translators with this input and output device selection or put in a MIDI thru path if not needing translation

In my case I just used a MIDI thru path

  1. In your application set up VM1 as your input.
    You should be getting MIDI.

You should also see this in Bome Network by dragging the green line up from the bottom so Bome Network shows the log.

See the this animation.

In my case I also see the EC4-V1 and EC4-V2 since I’m using Bome Network to route my FaderFox EC4 to both of those output ports.

Steve Caldwell
Bome Customer Care

Also available for paid consulting services:

Looks like it is working now. I don’t understand, that’s not any different than what I tried before. But anyway, thanks for your patience. If I have any more problems, will be back.

One thought: Bome could at least put an option (like a checkbox with explanation) when creating a VMP to create the required routing at the same time. Would save the user and you some frustration. Thanks!

Interesting as I was thinking of the same suggestion. I will pass it along.

Steve Caldwell
Bome Customer Care

Also available for paid consulting services:

Hi there, good idea! So there would be options on the Add Virtual Port page:

Create MIDI Routes:

( ) none
(o) Loopback Port (MIDI Route connects IN to OUT)

And I think also this option would be nice:

( ) Passthrough Port: interconnect IN and OUT of this MIDI device:
    MIDI IN:  EC4     -->
    MIDI OUT: EC4     -->

I think the options are the same, right? If so, I prefer the term Passthrough Port as this would be the most common use. Either that is just a checkbox. Otherwise, what is the difference besides terminology?

(o) Automatically add route for this port MIDI IN to MIDI OUT

No, these would be two different options:
Consider creating the port VM.

The Loopback Port will create this MIDI Route:

The Passthrough to IN/OUT EC4 will create these routes:

Does that make sense?

I also think that Loopback is a more correct term for the first option.
What do you think?

How do I get feedback to the controller? If I return the signal back in the BMT Router, it stops working.

Assuming you want it coming back from the DAW, you create another Virtual Port.

For instance I could name my ports ‘To-Cubase’ and ‘From-Cubase’

I would have the following routes:

IN: To-Cubase → OUT:To-Cubase
IN: From-Cubase → OUT:From Cubase

I name them in this fashion so that I can remember which one to send MIDI to and which one to receive MIDI from.

Essentially Bome MIDI Translator Pro has a total of 9 port pairs (or 18 ports).
Example BMT1 is really 2 ports one for input and one for output. but they are different ports so I don’t have to worry about ‘From’ and ‘To’

You could also set local feedback to your controller in Bome MIDI Translator Pro.

No for setting up direct routing between a controller and A DAW without translation, you can do something like the below:

APC mini mk2 1 is a physical controller and APC-MINIMK2-MT Virtual is a virtual port.

Steve Caldwell
Bome Customer Care

Also available for paid consulting services:

It would be a whole lot easier if you all could just increase the amount of VirtualPorts in BMT.

I tried this before you sent this and it didn’t work. Let me work on it some more.

OK, you might need to restart the DAW so that it sees the newly created port(s). It depends on the DAW whether it automatically recognizes new ports as they are added to the system.

Steve Caldwell
Bome Customer Care

Also available for paid consulting services:

That’s not working. I think because a button in Gig Performer is tied to a certain Midi Port and it doesn’t know to send the feedback out to a different port and there is no way to change that. So I give up. I just want to make music and my life right is mired in technical hell, and kind of unnecessarily. I love BMT Pro, it’s made my musical life easier but this Unlimited Virtual Port thing is useless. I will just go back to the instability of loopMidi, at least then I was making music most of the time, instead of not at all. Sorry, just really frustrated and tired of giving people money for things that don’t work and make things more difficult. I do appreciate you trying to help.

I have GP4 loaded on my system. I’ll see what I can do.

Steve Caldwell
Bome Customer Care

Also available for paid consulting services:

Hi, in GP4 Rig Manager you can associate a different output with the given input device. Then the MIDI feedback will work. This is how Rig Manager was set up.

And how I set up Button 0 with LED feedback (Reverb On/Off)


Note, that I had to restart Gig Performer after setting up these routes before the ports were properly recognized. This is how Bome Network MIDI routing was set up.

This is how Bome MIDI Translator Pro was set up.


Steve Caldwell
Bome Customer Care

Also available for paid consulting services: