Otherwise the MIDI will be blocked by the first program it is run thru, from running to any and all other programs.

The simple fact with MIDI is that every device needs a driver. This should work via BLE as Windows can see and attempt to pair with xkey but fails with yellow refusal/retry message. By the way class compliant means BARE MINIMUM. So that not only do Xkey air NOT connect via Windows BLE, (and I’m not going to buy a Widibud when my Yamaha’s BT01 transmits fine, and windows can see Xkey but not connect just as Xkey attempts fail over android where I recieve the message “bad private key”) but also now barely hold a basic Class Compliant MIDI channel. Todays livestream I demonstrate that using my current cocktail of DAWs the xkey disconnects recurringly from 52:30 thru the end, at least 10 times: Yamaha never seems to write the most stable drivers for their gear, particularly when using software other than their own editors.I have shown time and time again (in my livestreams) that MIDI devices do not work right without a driver. Again my experiences like that are in the PC world, so perhaps their Mac drivers work better, but I wouldn’t bet on it. Because I have found those virtual ports to be less than reliable and tend to disappear on you and the ports stop responding.

But going with external hardware MIDI ports would probably solve that and frankly based on my experiences using Yamaha console’s USB or Network MIDI ports I would suggest going that way anyway. It’s been years since I’ve used a 01V96’s USB MIDI like that and it was on a PC, not a Mac, so I don’t know if there is an option to make it appear as fewer MIDI devices or not. I think the easiest solution might be to forget about plugging in the mixers via USB, pick up a single or dual port USB MIDI interface and plug them in that way.

Well if the 01v has a USB port it must be a 01v96 actually.

Yamaha usb midi driver single client