I have a Novation Launchkey mk3 49 midi controller hooked up to a windows 10 machine running the trial version of the virtualhere server, and a hyper-v windows 10 instance that's running the client, and can see all the shared devices, but the Launchkey shows as an audio device (little speaker icon) and when I say "use this device" it gets shared, the client OS shows an active "LKMK3 MIDI" entry in the "sound, video, and game controllers" section of Device Manager, but applications like FLStudio or Nanohost don't see any midi devices.
When I try this with an Akai MPK mini, the client shows that device as a normal USB device (using the star icon) but again if I choose "use this device", it shows up in the device manager, but applications don't list it as an available midi device.
.
Did you install the launchkey drivers inside the VM where the virtualhere client is running? https://downloads.novationmusic.com/novation/launchkey-mk3/launchkey-49…
I did not, but even without…
I did not, but even without the novation drivers, it should work as a "standard midi keyboard" (you just can't program it). Also, the MPK mini should work without any drivers but doesn't seem to.
.
Ok well how about you try it with their drivers first. Seems pretty simple to test...
You'd think, but you can't…
You'd think, but you can't install them in Hyper-V. Their installer craps out because it thinks it's not in Windows 10 (so had to file a bug with them over that). So let's ignore the Novation: "my Akai MPK mini doesn't work. It does not have special drivers, its just a standard plug and play midi device".
.
Im not sure, I dont think it will work via virtualhere.
dang =(
dang =(