I've recently purchased a MD-BT01 device with the intention of using in unsupported configurations. Namely PC and Android environments. Given MD-BT01 conforms to standards - getting the device to work within Windows 10 is possible.
Not all software - in fact, hardly any - can "talk to" bluetooth MIDI devices. Hopefully, over time, packages will integrate support. For now, you need to build a "bridge" between the MD-BT01 device and standard MIDI drivers which are recognized by software packages. Luckily, there are choices here and I will present what worked for me.
First step: Pair the MD-BT01 with Windows 10
This may be obvious, but your PC requires a bluetooth transceiver (transmitter/receiver) in order to communicate with the MD-BT01. Not all PCs have a bluetooth transceiver and not all have the level/version of bluetooth support required. Under windows, if I hit the "windows" key then type "bluetooth", I will see an option "Bluetooth and other device settings" which I can click on. After this application loads, choose the "+" (plus) sign for "Add Bluetooth or other device". From the next menu, choose "Bluetooth" which should be the first option. The system will search for the MD-BT01. Make sure the MD-BT01 has been plugged into your keyboard/MIDI device properly so it will be able to be discovered. Once found, select "MD-BT01". Your "Bluetooth & other devices" settings panel should show MD-BT01 as "connected" under "Other devices".
Second step: Create a bridge from the MD-BT01 to your PC
Under normal conditions, even though the MD-BT01 is paired, there is no software which will be able to "see" (utilize) the MD-BT01. Currently, the best bridge application/driver for bluetooth MIDI devices is an app you can download from the Microsoft store called "MIDIberry" from NEWBODYFRESHER http://newbodyfresher.linclip.com/ . I downloaded my version from the Microsoft Store. After downloading, load the app and select the MD-BT01 as the "input" device. The "output" device will be another virtual MIDI cable you will later download.
Third Step: install and create a virtual MIDI cable between MIDIberry and a virtual MIDI port (loopMIDI)
This is the same place I downloaded my version from. I was able to successfully transmit, through Bluetooth, from my Yamaha Montage to the Ctrlr software and wrote a Lua script to display MIDI activity including SysEx messages.
There may be some limitations I have not yet run into yet. But for general/intended use, stringing these applications and drivers together seems to get the job done.
Note: in order to achieve 2-way communication (above only works one way) - you need to create a second "loopMIDI" device for the other direction and use "WindBerry" for the other direction. MIDIBerry will handle the data in one direction and WindBerry will handle data in the other direction. I have been able to get JM Tools (Performance Editor) to work on Montage -- but not fully. Enough for JM Tools to recognize the firmware level of Montage and fact that it is connected. I believe there may be either latency issues or buffer overflows which causes the rest of JM Tools to fail using this method. The method is sufficient for "light" use such as using the keyboard to transmit notes to a DAW or other "slow" work.
I have an HP ProBook laptop which ran windows 7. I have an MD BT01 which I could connect by Bluetooth, but could not use Protools first with, due to lack of MIDI connectivity. I read your post and downloaded MIDIBerry after upgrading to Windows 10. Now the MD BT01 is detected but won't pair with my PC. I have been through all the BT troubleshooting, checking services are running, checking drivers are up to date etc. But I still keep getting the message "try connecting your device again". This is frustrating as I can't get past stage 1 of your instructions @Jason. Others seem to have been able to make this work. Do you have any ideas what I can try?
When your MD-BT01 is powered, there will be a LEDs illuminated. The MD-BT01 has an illuminated LED red-and-green. Make sure the LED is illuminated indicating the MD-BT01 is receiving power. If the device is not powered - windows will not discover it.
Also, if you have any other Bluetooth devices (earphone/headphone, speakers, keyboard, mouse, etc) - you can try pairing those with Windows and just make sure Bluetooth, in general, is working apart from the MD-BT01.
Getting the MD-BT01 to pair with windows is often not the issue - it's usually dealing with the lack of end-to-end software support for bluetooth MIDI in Windows after pairing is completed.
Thanks Jack. I have followed all troubleshooting steps I can think of, reinstalled all drivers from HP and still can't pair with the MDBT01. Bluetooth service is running. I can connect to my Bluetooth speaker, no problem. I have downloaded the Bluetooth LE explorer App, and the data says Connected=TRUE, however when I try and pair I get a pairing error. I have MIDI Loop and MIDIBerry waiting, but just can't get past stage 1 to get the thing to pair. I have updated to the latest software on the MDBT01 using the Yamaha App from my iPhone. Do you have any other ideas, as I have run out. Thanks in advance.
"It works for me on a PC" is not very helpful to you. Unfortunately, supporting PCs is more difficult than apple because PCs have so many variants (different BIOS, different hardware implementations, different underlying driver tweaks, different possibly conflicting software provided by manufacturer). It's not possible for me to replicate your results - so your best bet may be follow up with HP and explore that route. There are likely support forums where perhaps others can pool results that share your hardware and also more 1on1 support from specialists outside of a forum.
Right now the problem is more fundamental than necessarily a "Yamaha problem" since the pairing step is primarily a hardware level handshake that your PC and its drivers are primarily responsible for.
I'm sure you've done this already, but make sure your BIOS is updated. This may have been what you meant when you said you've updated all drivers - although the BIOS is not a driver as it doesn't involve an operating system. Your HP should have some facility to check for BIOS and other non-driver updates (ME engine firmware update, etc).
Also, Windows Update may cover any bluetooth stack updates. I'm also sure you already have this included in your process - maybe under "etc".
As my suggestions become less and less helpful - this is a good indication that perhaps barking up the HP tree may be more helpful.