what happened/what did i do to my ports in this screenshot?

I had a recording session and for some reason I couldn't figure out why my edrum port (BMT3) was sending MIDI to my keyboard port (BMT4)

The picture should explain it all, but what's going on here? Why are the ports all mixed up?


Attachments:
![](upload://7LYD3zLdMbFf0IMXnWjBEE2bgZV.png)

Oh my gosh. I've never seen this behavior before. Could you please post or send me your project file and I will have a look. What version of Bome MIDI Translator Pro are you running? You are on Windows 10, right?

 

Steve Caldwell
Bome Customer Care


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

 

 

Hi Steve,

I\'ve attached my project file

What version of Bome MIDI Translator Pro are you running?

I am not sure but my about says 1.8.3 build 892

You are on Windows 10, right?

Yes


Attachments:
1599937366087_Jonnys-Maschine.bmtp

Hi, I recommend you go to 1.8.4 build 962 which is the latest. This will also de-install and re-install your Bome Virtual Ports. Are you running any other virtual port software besides MT Pro? (loopMIDI? loopBE?)

 

As far as your project file, I recommend that you select All of your used ports at the project level and then select just the ports you want to use at the preset level (which will override the project level defaults). Any port checked at the project level will always stay opened. If you only check them at the preset or translator levels, they only attempt to open or close the port upon use. At least this is the way I understand it.

Also, instead of using the Bome Virtual Port aliases, I suggest you use your own aliases and then point them to the correct virtual port. In some cases you are opening the Auto Alias (Bome Virtual Port x) which points the the real port name (Bome MIDI Translator x Virtual Port). The auto aliases were put in place some time back for compatibility with older versions of MT Pro. I'm not saying you can't use them, however try to be consistent in their use. I never use them since it restricts the portability of the application.

In a nutshell though, it appears you did nothing wrong and somehow the Windows drivers got confused. It is likely that some things got moved around on your MIDI ports which confused the MIDI drivers. Usually re-installing MT Pro also fixes the MIDI Port virtual drivers.

 

Steve Caldwell
Bome Customer Care


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

 

 

Are you running any other virtual port software besides MT Pro?

No not on this laptop, Bome is the sole traffic warden between apps and devices.

I'll reinstall and update you.

 

Thanks!

Hi Steve,

The installation seems to have realigned the ports.

Now about Alias's, won't that mean I'll have to reassign all the ports in my presets and so on? Will a name change mean I have to go into my DAW and select the MIDI IO again?

Also with this update I had a strange thing where my routing had my edrums sending midi to all BMT ports until I activated a specific preset in which the midi device was being used. Is that a new feature where no translation = send midi to all BMT ports?

Now about Alias\'s, won\'t that mean I\'ll have to reassign all the ports in my presets and so on?

SJC> Yes but this should be a one time thing.

Will a name change mean I have to go into my DAW and select the MIDI IO again?

SJC> No they should still see the ports with the names as they do now. Aliases only effect what MT Pro understands as the devices.

 

Also with this update I had a strange thing where my routing had my edrums sending midi to all BMT ports until I activated a specific preset in which the midi device was being used. Is that a new feature where no translation = send midi to all BMT ports?

SJC> If you don\'t set any default ports at the project level, there is nothing to override at the preset level if not defined at the preset or translator level, output will go nowhere and input will not be recognized.

However if you set the default ports at the project level that means you expect input from and to every port you have defined so you should go to the preset level and assign any ports you want used for the presets there. Then if you want to override a preset level as well, you can do that at the translator level.

See the tutorial on managing inputs and outputs here.

The way I do it is to check all ports I want to use within the project at the project level, then I organize my devices by preset and override project defaults there. Occasionally I override both project and preset at the translator level but I try not to do it too often because if things change, there are more translators to change than presets.

 

Steve Caldwell
Bome Customer Care


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

 

Hi Steve,

I appreciate your comment, no one I know uses Bome (but a lot of people recognise it in the studio) so it’s helpful to hear how someone else uses it.

I watched the Alias tutorial too and noticed the routing featured there, I think I’m just about getting it.

Glad to help!