I just setup a new Windows 11 Pro PC, installed a host (Gig Performer), some VSTs, and Bome Network. I then connected to my BomeBox, launched Gig Performer, and everything was fine. I then rebooted the machine and now even though Bome Network connects to the BomeBox, no midi ports show up in my host. I installed Reaper just to make sure it wasn’t an issue with the host - no change. Rebooted, disconnected and reconnected the BomeBox from BomeNetwork, rebooted the BomeBox, etc, all with no luck.
I then grabbed a laptop that had Bome Network installed, connected to the BomeBox, and everything worked fine - midi ports showed up in various hosts. So it appears to be something in the windows settings or Bome Network install with the new machine. Anyone have any ideas?
In order to see your remote ports on your BomeBox or another computer, you need to turn them on in Bome Network Pro using Remote Direct MIDI switches.
The below example shows exposing the BomeBox attached ports on my Windows 11 PC. First, I click on FOH (which is one of my BomeBoxes). This is done on my PC using the Bome Network tool.
Then you can see the ports attached to my BomeBox. Turn on the switches to expose them.
You should then be able to see the MIDI ports in GiG Performer (and other applications). I’m showning FOH:BomeBox DIN .
Note that in Windows, only one application can open a given MIDI at a time. If you need to share MIDI ports, you will need to either use Bome Unlimited named MIDI ports or Bome MIDI Translator Pro and then route the oritinal port to additional virtual ports.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Thanks Steve, but unfortunately that wasn’t the problem here (I already had the ports enabled).
If I go into the device manager and find my Bomebox, everything looks fine until I go to the “events” tab, where I see “Device BOMEBUS\BomeMIDI\01 requires further installation.” Attempting to update the driver doesn’t work, reinstalling Bome Network and using the “custom” option and checking the box to remove drivers and reinstall doesn’t work either.
Something in Windows has broken the driver and the old uninstall/reinstall, check for windows updates, etc, isn’t getting me anywhere. As stated earlier, it did work just fine when I first installed, but no more. And of course everything is working fine on other machines, just not this new PC I bought explicitly for FOH duties. Very frustrating.
Any and all suggestions appreciated.
EDIT: still no luck, but I went into the event view and found this:
“Device settings for BOMEBUS\BomeMIDI\01 were not migrated from previous OS installation due to partial or ambiguous device match.
Last Device Instance ID: HDAUDIO\SUBFUNC_01&VEN_8086&DEV_281F&NID_0001&SUBSYS_00000000&REV_1000\5&19917933&0&0002&00000014
Class GUID: {4d36e96c-e325-11ce-bfc1-08002be10318}
Location Path:
Migration Rank: 0xF000FFFFFFFFF132
Present: false
Status: 0xC0000719”
I also tried completely uninstalling all Bome software, rebooting, verifying all was uninstalled, and then reinstalling. Oh, and I made sure to run the installer as admin (which is probably redundant, but figured it was worth a try). All to no luck.
I’m running 1.6.0 (which is the latest). No errors during install. Yes, I have selected the option to force reinstall of MIDI drivers, I’ve tried manually deleting the drivers from device manager and rebooting, and even removing all Bome software from the machine, rebooting, verifying everything was removed, and attempting a fresh install, but the result is always the same - all appears OK, except it doesn’t work, and the device manager shows the device “requires further installation”.
I’ve even tried “update driver” in device manger, and “let me choose the driver”. I’ve tried updating windows too. Somewhere in the machine there is a file, or a registry field that it doesn’t like and it refuses to work. I’ve done numerous internet searches and worked through various lists of solutions, but none of them successful thus far.
I’m happy to report I’ve found a solution. Here is what I had to do:
Under the device manager events tab there is an “events viewer” button. Launch the events viewer and expand it. Digging through the events I noticed there was an error than a net framework package was missing (no error was shown during install or anywhere else). I downloaded and installed that package.
Next I uninstalled the device and selected “remove driver”. Then I uninstalled all Bome software and rebooted. Finally I ran pnputil from the command line (as admin) to insure the bome drivers were uninstalled (they were not), and uninstalled them with pnputil.
Reboot again, and run a fresh install. It now works, HOWEVER, I still see the “device requires further instillation” msg in the device manager. But it works….for now.
I really wish all the software I need ran on Linux. Windows is becoming worse and worse over time. Glad to see Bome supporting a wide range of OS solutions.
Forget that - it stopped working. No reboot, it was working for a while and then it just stopped.
This is obviously a windows issue, but it appears to be driver related, since device manager still says additional installation is required (but refuses to do so).
BTW - I installed Bome Midi Translator Pro just to see what would happen (I own a license and have used it for more than a decade on a studio machine). My BomeBox does NOT appear in the translator - no ports in our out are visible there. I am totally dead in the water at this point. Very disappointing….
Hi,
this seems like a strange driver installation problem. We have not experienced anything like this.
I wonder what had to get migrated if that was a fresh install? This ‘migration’ does happen with some Windows updates, though.
Even stranger is the ‘partial or ambiguous device match’. it sounds as if there was a different device driver which seems to be matching the Bome virtual MIDI ports. The Class GUID is correct (audio devices), but the instance ID path looks suspicious. Vendor Id 8086 is Intel, device ID 281F is probably some kind of on-board HD or HDMI audio device. So an idea would be to disable or remove all other audio device drivers, then reinstall Bome virtual MIDI, and then, one by one, re-enable on-board audio if needed.
This is not a general advice, only as the last resort. Note that there is also the Bome bus driver under system devices.
Another thing to try is the standalone installer from here:
Exit all programs that could be using MIDI (including Bome Network). Then run the stand-alone installer, select ‘Force reinstalling (…)’ during installation. Then reboot to be sure.
I’m sorry we’re as much in the dark as you. The PNP approach is quite advanced already… But as you said, it’s likely to be a problem caused by Windows. Sometimes, it doesn’t get driver installation right, and it caches everything about drivers, so it’s very hard to really get rid of one.
Yes, the problem appeared after Windows updated (I think the machine had been on less than an hour from new). It seems Windows always insists on a few updates after starting a new machine. BTW - I did “re-install” Windows on this machine as well….no change.
Great suggestion on removing other audio devices. It didn’t fix the problem, but did potentially provide some useful data. I disabled and removed the driver for the onboard audio. Note I did not restart as this caused the device to be automatically re-installed. I also uninstalled and removed drivers for Bome. I then ran the Bome installer, and had the device manager window open during this process. As soon as Bome Network launched and found my BomeBox, not only did the BomeBox show up in the device manager, but so did the on board audio. And both had the “device requires additional installation” message.
So it appears there is some sort of conflict with the on board audio. The question is how to remove its driver and disable it such that windows doesn’t try to keep re-installing it. BTW - I tried just disabling it and rebooting, then a fresh Bome install, but got the same result.
Oh, and I did try the stand alone installer as well, no difference.
I really appreciate your help here. Let me know what logs, info, or tests I can provide. The machine is a brand new mini PC with Windows 11 Pro, its only task is to sit in my live rack and handle VST’s for virtual instruments and audio processing via Gig performer. Since we already use Ethernet for control (talking to stage boxes, lighting, etc), the BomeBox is the perfect solution for keyboards and control devices to send midi to this PC. It has worked great on my studio PC and laptop for testing (which have tons of other software and attached devices), but not in this simple dedicated setup. Bizarre.
I disabled the onboard audio in the BIOS and did a clean install. This (once again) gave me short lived success. It even worked after a reboot, but then failed on the next reboot. Even when it did work I still had the “additional installation” message. (The onboard audio did not re-appear, so it is properly disabled)
Clearly Windows is mucking with something on the driver side - but what and how do I kill it? Everything else works flawless. Let me know if there is some trace/dump/log file that would help you find the problem.
BTW - just to make sure it isn’t a Gig Performer problem I have tried with Reaper as well. For that matter, midi ports don’t even show up in Bome Midi Translator Pro. But in the Bome Network window I can see MIDI messages coming in, so the BomeBox is talking to Bome Network - the failure is the virtual ports.
You are not running a SnapDragon installation on your new PC are you? (ARM). Bome Virtual Ports do not work on Windows SnapDragon (although I’ve never seen a SnapDragon MINI PC.)
Is there a service I should be looking to make sure is running? Or a background task? I see Bome Network running (obviously), but I don’t see any background processes that are obviously related to Bome. I do see “Bome Virtual MIDI 2.1.0.44” in my installed programs, but there isn’t a process I can identify that is associated with it. Should there be?
The only services that run would be the Windows Audio Services I believe and of course the application itself (which is not started as a service.
It relys on Audio Endpoint builder and and Remote Procedure Call (RPC)
I guess you could try restarting the Windows Audio Service and see if that helps anything. I belived both Audio and MIDI use this service.)
I think that Windows Audio Service calls the Bome MIDI Driver you mentioned when needed for adding and removing ports. I’m not 100% sure but I have this running on my Working PC as well.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
I think @FlorianBome is sleeping so maybe he will have other ideas when he gets up.
The computer is not running a non-production version of Window is it. I know Microsoft is developing and testing new MIDI drivers but only on unreleased versions. (Canary)
