Windows 10: problem opening midi device

Hi...I really need some help, I’ve used bome several years ago and it worked fine.

but now after I install the translator , it constantly says that my midi port can’t  be opened(maybe in used). But actually I didn’t open any other software.

the status is always pending(error)

I use rme ucx ,Roland rd800, seaboard rise, Korg kronos and some other devices, even if I disconnected all the cable left only one device, the problem is still here.

thanks..

The only port I can connect is the kronos…

Is it always the same device or is it all MIDI devices? If a specific device, which one?

Are you running on Windows or Mac? Do you have CopperLan installed? I know that CopperLan insists on taking control of all MIDI ports. I had to disable it (and later I uninstalled it). There may be other background applications that do similar things. Do you have any MIDI mapping software installed besides MT Pro (even if you don’t think it is running)?

Could you provide a list of your MIDI enabled applications?

I’m using Windows, don’t have CopperLan(a software?)
I haven’t installed other mapping software yet, just daws and pulgins generally .
I’ve tried closing as many running programs as possible, but still can only open the kronos port now…don’t know why

Other software can use my devices without problem, both daws and some standalone instruments

Hi, Open your Dos Prompt as administrator and then type the following: tasklist > tasklist.txt Then post the file. We can see if there is something running that looks suspicious. Keep in mind that only 1 application can use a given port in Windows at a time, so any DAWs you have running concurrently should be routed through Bome MIDI Translator if you want to use them in both places. The DAW would then use a Virtual Port routed to by MT Pro.

Also, close any browsers you have open. If Chrome is one of them, kill all of the Chrome processes then try to open you MIDI ports using MT Pro. There are some network enabled applications these days that like to open an hold open MIDI ports and they are not gracious about closing them when you are done using them.

If other Apps work OK, try going to %APPDATA%Bome folder and delete any .bmts files there.

Have you restarted your computer and as very first thing before starting anything else, started MIDI Translator Pro?
Which version of MT Pro and of Windows are you using?

I have restarted, I’m using the latest 1.8.2 build853 version.

映像名称 PID 会话名 会话# 内存使用
========================= ======== ================ =========== ============
System Idle Process 0 Services 0 8 K
System 4 Services 0 14,868 K
smss.exe 536 Services 0 452 K
csrss.exe 724 Services 0 2,276 K
wininit.exe 828 Services 0 1,516 K
csrss.exe 836 Console 1 2,604 K
services.exe 904 Services 0 6,948 K
lsass.exe 912 Services 0 11,224 K
svchost.exe 1020 Services 0 816 K
svchost.exe 168 Services 0 21,224 K
fontdrvhost.exe 472 Services 0 2,368 K
svchost.exe 676 Services 0 9,484 K
svchost.exe 672 Services 0 3,864 K
winlogon.exe 1048 Console 1 47,340 K
fontdrvhost.exe 1104 Console 1 9,924 K
dwm.exe 1176 Console 1 36,160 K
svchost.exe 1272 Services 0 1,108 K
svchost.exe 1324 Services 0 4,452 K
svchost.exe 1332 Services 0 5,248 K
svchost.exe 1340 Services 0 4,508 K
svchost.exe 1380 Services 0 8,752 K
svchost.exe 1460 Services 0 1,832 K
svchost.exe 1524 Services 0 5,356 K
svchost.exe 1564 Services 0 14,460 K
svchost.exe 1716 Services 0 6,484 K
svchost.exe 1724 Services 0 1,672 K
svchost.exe 1748 Services 0 14,732 K
svchost.exe 1828 Services 0 3,632 K
svchost.exe 1944 Services 0 1,692 K
svchost.exe 1952 Services 0 5,876 K
svchost.exe 1964 Services 0 4,196 K
svchost.exe 2072 Services 0 2,056 K
svchost.exe 2128 Services 0 5,112 K
svchost.exe 2156 Services 0 5,372 K
svchost.exe 2164 Services 0 4,492 K
svchost.exe 2504 Services 0 1,436 K
svchost.exe 2536 Services 0 1,292 K
dasHost.exe 2584 Services 0 4,124 K
svchost.exe 2604 Services 0 8,732 K
svchost.exe 2624 Services 0 1,532 K
svchost.exe 2728 Services 0 9,552 K
svchost.exe 2756 Services 0 4,460 K
svchost.exe 2764 Services 0 2,440 K
svchost.exe 2772 Services 0 2,952 K
svchost.exe 3008 Services 0 4,804 K
spoolsv.exe 3068 Services 0 6,820 K
svchost.exe 2840 Services 0 3,052 K
AppleMobileDeviceService. 3528 Services 0 6,416 K
mDNSResponder.exe 3544 Services 0 2,308 K
Everything.exe 3552 Services 0 1,900 K
svchost.exe 3568 Services 0 2,344 K
svchost.exe 3576 Services 0 16,904 K
svchost.exe 3588 Services 0 21,896 K
svchost.exe 3612 Services 0 6,232 K
NvTelemetryContainer.exe 3624 Services 0 3,168 K
svchost.exe 3664 Services 0 5,196 K
svchost.exe 3680 Services 0 2,084 K
svchost.exe 3688 Services 0 3,320 K
svchost.exe 3712 Services 0 11,124 K
LogiRegistryService.exe 3736 Services 0 1,512 K
svchost.exe 3744 Services 0 7,428 K
SecurityHealthService.exe 3760 Services 0 5,064 K
svchost.exe 3808 Services 0 12,124 K
svchost.exe 3816 Services 0 8,940 K
svchost.exe 3824 Services 0 5,440 K
svchost.exe 3832 Services 0 3,828 K
svchost.exe 4120 Services 0 3,784 K
Memory Compression 4264 Services 0 268 K
svchost.exe 4520 Services 0 4,524 K
svchost.exe 4596 Services 0 1,652 K
svchost.exe 4852 Services 0 1,448 K
svchost.exe 5064 Services 0 4,676 K
WmiPrvSE.exe 5420 Services 0 13,128 K
svchost.exe 5704 Services 0 2,704 K
OfficeClickToRun.exe 3080 Services 0 59,576 K
sihost.exe 7340 Console 1 17,216 K
svchost.exe 7372 Console 1 15,288 K
svchost.exe 7412 Console 1 20,756 K
svchost.exe 7484 Services 0 9,816 K
explorer.exe 7776 Console 1 120,936 K
taskhostw.exe 7844 Console 1 15,292 K
ChsIME.exe 8040 Console 1 1,764 K
ShellExperienceHost.exe 8372 Console 1 67,188 K
SearchUI.exe 8532 Console 1 72,880 K
RuntimeBroker.exe 8808 Console 1 43,456 K
svchost.exe 9032 Services 0 6,816 K
RemindersServer.exe 9144 Console 1 7,468 K
SkypeHost.exe 9204 Console 1 41,780 K
svchost.exe 9280 Services 0 11,780 K
SettingSyncHost.exe 9676 Console 1 9,916 K
svchost.exe 10032 Services 0 6,032 K
AppVShNotify.exe 10204 Console 1 2,036 K
svchost.exe 10272 Console 1 19,972 K
svchost.exe 11176 Services 0 2,016 K
svchost.exe 11212 Services 0 1,860 K
svchost.exe 11296 Services 0 17,456 K
MSASCuiL.exe 16740 Console 1 2,268 K
Everything.exe 16876 Console 1 715,476 K
svchost.exe 17100 Services 0 3,744 K
svchost.exe 17124 Services 0 3,248 K
svchost.exe 17152 Services 0 2,184 K
svchost.exe 17276 Services 0 2,176 K
SGDawNodeService.exe 18080 Console 1 9,584 K
OneDrive.exe 17640 Console 1 19,876 K
DiscSoftBusServiceLite.ex 1652 Services 0 3,220 K
svchost.exe 10724 Services 0 3,316 K
SearchIndexer.exe 2424 Services 0 52,420 K
svchost.exe 20340 Services 0 8,660 K
svchost.exe 19784 Services 0 3,268 K
dllhost.exe 4572 Console 1 2,608 K
svchost.exe 18032 Services 0 5,264 K
svchost.exe 12020 Services 0 1,840 K
svchost.exe 12220 Services 0 3,660 K
Taskmgr.exe 4608 Console 1 34,244 K
ApplicationFrameHost.exe 13560 Console 1 12,528 K
SystemSettings.exe 13204 Console 1 23,600 K
NVDisplay.Container.exe 14216 Services 0 5,184 K
NVDisplay.Container.exe 1912 Console 1 27,720 K
svchost.exe 15860 Services 0 1,500 K
WUDFHost.exe 12636 Services 0 2,396 K
Microsoft.Photos.exe 3804 Console 1 190,952 K
LDSvc.exe 1924 Services 0 37,272 K
svchost.exe 18052 Services 0 7,396 K
MIDITranslator.exe 8884 Console 1 78,672 K
svchost.exe 13032 Services 0 7,536 K
audiodg.exe 9068 Services 0 11,788 K
powershell.exe 13084 Console 1 70,104 K
conhost.exe 8528 Console 1 15,212 K
tasklist.exe 2416 Console 1 7,920 K

I’ve deleted the backup bmts files…still can’t open ports..

Windows 10 1703

Hi, I don’t see any glaring issues with your task list. Did you delete all .bmts files or just backup files? If just backup files, go ahead and spin them out to a safe place then delete them in your AppData folder. Also try uninstalling and re-installing MT Pro.

As a last ditch effort, you can try going to device manager and look at your Software Devices (anything there that is MIDI) and Sound, video and game controllers (again anything that is MID), and delete them then restart you computer. Windows should regenerate the devices when you reconnect them. You may need to re-install MTPro to get your Bome MIDI Translator Virtual Ports back though. If none of this works, I’ll ask Florian to step in to see if he can assist further.

I deleted all the bots file to try…still same as before
I just have tried deleting some midi devices and retbooted, still can’t open midi port except the virtual port and kronos port

Did you un-install and re-install MT-Pro? Also, are you running your devices through a USB Hub? If so, lets see if anything works with Bypassing the hub.

I uninstall and reinstalled several times…
Some devices are through usb some are not(the rme ucx’s own midi ports are connected through direct usb), but both can’t be opened..

Maybe we should look at one device at a time. Lets start with the RD-800 since it is a simpler device. It appears that the RME UCX is a much more complicated device (audio, OSC and more in one device).

Try connecting it directly and set the driver up for Generic MIDI USB driver as shown on page 53 of the RD-800 user manual. I’ve found on one of my Roland Devices (A-300), I’ve had problems if using the custom driver since the custom driver is not class compliant.

According to the Seaboard Rise, it is class compliant, however so maybe we could start with that with direct USB connection. I’m also going to ask Florian for assistance.

I use a midi cable to connect the rd800 and ucx now….
I also have a studiologic vmk88plus, I think I can try that first…

It doesn’t work, I disconnect all the midi devices letting only vmk88 and the port can’t be opened

Wether through a hub or not(using the kronos’s working straight USB port)

Same as seaboard rise along

I wonder why other apps work fine….only midi Translator can’t use my devices…

OK, I’ve alerted, Florian. I’ll let you know if I can think of anything else to try.

Steve

Thank you Steve！

I am only aware of one single reason why a port shows “pending(error)” in MT Pro: if it is used in a different application. So I still believe that some process is using the MIDI devices.

Unfortunately, there is no easy way (that I know of) to find the process blocking a MIDI device. What you could do: download Process Explorer, restart your computer, then start Process Explorer and use from the Find menu “Find Handle or DLL”, and enter the search term “winmm”. That’ll likely give you more results than processes which actually block the MIDI device, but it’s worth looking through that list, and/or posting it here.

Note that Windows 10 introduced a new MIDI API which might also block the MIDI ports only for applications NOT using the new API. Have you activated Bluetooth? The new BLE-MIDI is also using the new Windows 10 MIDI API.
We will support the new MIDI API in future with MT Pro, but so far there are relatively few applications using it.

You’re the only person reporting such a problem, so it should be possible to fix it for you!

I wonder what the latest MIDI related application you installed. Maybe that would be the most likely suspect. It is odd that only BMT is pending and that no other applications are blocked unless they all use the new API.

here’s the process related to winmm (sys32 and syswow64)

I’m not using bluetooth, but I’m using logitech wireless keyboard and mouse…they should not bother midi I thing?

What application are you running with Powershell?

I just opened a powershell window myself I think. normally not there(like now)

The shouldn’t bother anything MIDI. Just out of curiosity, have you ever tried right clicking a port you cannot open and then unchecking “Open” and then re-checking it? This is very odd as I have never seen anyone with this problem yet unless something else MIDI was running and trying to access that port. I’m on the same Bome Build and running Windows 10 1709 OS Build 16299.125.

I just tried…same as before, can’t open…

It’s really odd, I tried the bome translator several years ago and it worked fine. And now my other daws and apps work fine too.

I just find another app can’t open midi port, it’s called midi tools from mountainutilities.eu
It says can’t open midi input device undefined external error like bome does.
Well, this software looks a little bit of obsolete…..

Hi, thanks for trying. We have many thousands of active users, so there must be something on your computer which blocks the MIDI ports. Have you already tried the Process Explorer method above to, hopefully, find the culprit?

Hi Florian, I’ve tried and list the pictures below, you can check them.

I use MIDI Tools and MIDI-OX occasionally. It would be interesting to know if you can open with MIDI-OX.
The software that runs rme ucx may be causing the problem. It has an OSC interface capability and if it is trying to convert OSC to MIDI within it, maybe it is holding some MIDI ports open? Just a thought.

I would be suspicious of TotalMixFx. Try killing it and see if that helps.

I tried, exiting both totalmix and firefaceusb app…still the same, I’ll try midi ox anyway..

I tried MIDI-OX(which I just remembered I’ve used before), yes, it can’t open port too…..
it seems like old and new apis problem? new software like cubase 9 and new vsti standalone apps work fine…

Hi, I just found out if I install the Korg MIDI Driver for Winows 10. I can no longer see my Korg PA900.  To fix, I deinstalled the driver and then went to device manager. My PA900 still showed up and instead of using the Korg Driver, I selected Generic MIDI driver and now it works. The only caveat is Windows 10 sees it as a Generic MIDI device but at least it sees it and recognizes what it sends and receives.

 

that’s a korg problem, their driver requires your korg devices in first 8 position of midi devices list, so use their tool or manually delete some devices and let the korg things be in front of the list will work…

Interesting. I just decided to uninstall and revert my Korg device back to the default Generic Windows MIDI driver.

If you let the korgs in first 8 position, they’ll be fine…
so as my problem is still here…maybe the only solution is to wait until the translator release its new version which use the new API?

I highly doubt that the new API is required. Maybe if you show me the services you have running on your system, we can find out which one is the culprit. I still suspect it has something to do with TotalMixFX or associated services it uses. Maybe we successfully killed the application but there was still a service running. Like maybe and OSC service.

You know what….I finally resolve this damn problem…It’s a windows reg problem(probably the system’s bug)…nothing about the running processes and services
I find the solution here:
https://www.youtube.com/watch?v=cn5VEFoAjVE
It’s weird, the reg just miss a key, once I add the key as the video said and reboot my computer, the problem is gone!

That also solve other problems related to midi port(which I think using old API)
I’ll just post the method here:
open regedit, locate HKEY_LOCAL_MACHINESYSTEMControlSet001ControlClass{4d36e96c-e325-11ce-bfc1-08002be10318}
creat a new multi-sz key ‘UpperFilters’, and value it ‘ksthunk’
That’s all…simple but useful

That is awesome. Thanks for sharing this!

Steve

I already had this 'ksthunk' but my MIDI devices are still in the 'do not exist' status.

Hi, please post a screen shot if you would of the ports that you can see in other applications that cannot be seen by MT Pro.