Hello,
Since I have the new midi stack, the BMT port names have changed.
For example what used to be BMT 2 is now changed to **BMT 2 (4)
**
Below is the endpoint properties from Windows Midi Service Console.
Hi, although I have not seen this on my Windows PC with the new stack, it could indeed be a problem within Windows on the way it names MIDI ports. I suggest you try the following:
De-install Bome MIDI Translator Pro . This should delete all of the Bome MIDI Translator Pro virtual ports.
Re-install Bome MIDI Translator Pro. This should re-create the virtual ports with the correct naming.
Let me know if this works for you.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
I have uninstalled and reinstalled Bome Midi Translator Pro, but now I still have, the same problem, with some port unwanted number being incremented, e. BMT4.
Are these the same names that your application reports or do they not have the number within parenthesis?
What version of Windows (and build) are you running?
It might be possible that the MIDI management application reports differently than other MIDI applications.
If other applications are reporting the same then you could try.
Uninstalling Bome MIDI Translator Pro
In Device Manager, deleting the problem MIDI ports (under Sound, video and game controllers)
Reinsallling Bome MIDI Translator Pro
If that doesn’t work, let me know and I will find the Microsoft link for you to report bugs on the new MIDI stack.
Here is the discord link for users reporting bugs in the MIDI stack.
Here is a link to a list of known issues:
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Looking at my system. I see the following for my Bome MIDI Translator Pro virtual ports but there are no-apps that see the numbers in the parenthisis. I think the numbers are just an enumerator to help define a unique MIDI endpoint. If this is not true, tell me what apps are getting messed up.
I’m using a streamDeck with the midi plugin and the app has now an option to use the new native midi stack interface. Its in this case that the ports are exposed with the number ().
When i use the compatibility option WinRT Midi (The WinRT framework, “Windows Runtime”), it works as before.
Not a big deal but I think the developer should know.
That is good to know, thanks! From what I understand, there will be a tool released from Microsoft that will allow you to provide an override to the default Microsoft provided port name. I have not seen the tool yet. In the meantime. the RTMIDI and MME API’s will still be available. I think the main advantage in using the new API is to allow MIDI 2.0 messages to work on the system although right now there are just a handlful of MIDI 2.0 applications and controllers. It looks like Microsoft did a lot to keep old API compatibility.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz