Maybe it is just me, I created a bug for that, but if anyone else can confirm or disagree: VCV current under Windows 11, 25H2. KBKB5074105 introduced the new Windows MIDI stack. Everything else works (DAW, Midi Dash etc.) - only VCV sees some Midi devices, but does not react on them. Any kind soul here running VCV standalone + KBKB5074105 can confirm this? Note: this is a template I have been running for almost a year and which worked flawlessly…
The new Midi stack landed on my Win11 machine day before yesterday and it’s working just fine with VCV, including the new multi-client. (At least #d CHEM is working great).
I installed the SDK and used the config tool and set it to run the service at startup.
There are a few devices known to have issues. These are often resolved by uninstalling the device’s custom driver. DO NOT use the Korg device uninstaller–it messes up the Midi device registry, and you’ll need to run one of the SDK tools to repair it.
No device is working: SL MKIII, Arturia Keystep, OXI, my HW Synths. They all are visible to VCV and can be selected as Device in Midi to CV, but none of them registers any MIDI event. They all work in Gig Performer, Bitwig, Reaper. Just not on VCV. I did not use the Korg uninstaller, since I don’t have any Korg stuff.
I would just try to uninstall VCV and reinstall it,
but make a backup of the downloaded library and the presets and patches etc. before uninstalling,
maybe this can cure it
There shouldn’t be any need to uninstall or reinstall rack. It can’t hurt anything, but it’s likely a waste of time. I seriously doubt the rack installation does anything with midi.
For some Midi devices you may need to unplug or power them off, reboot windows, then reattach/power them on, all before running any Midi software. Only one cycle of this should be needed.
For some devices, and existing patches, you may need to manually reconnect the device in whatever midi module you’re using to connect.
One may have the new midi driver installed, but the windows feature not yet enabled. It is a rolling release of the feature enablement over the coming month, so not everyone gets it at once. There is a tool you can download that tells you if you have the driver, and if the feature is enabled.
1 Like
Also, there is a known issue with loopbe if you’ve been using that. A fix is in the works, but then with the new service and the SDK tools, you don’t need it anymore because virtual cables are a feature of the new service.
1 Like
Oh, that’s cool, finally.
Interestingly, I had to delete mostly all MIDI devices in Hardware Manager, restart and then it worked. Let’s see… Not using loopbe, but LoopMidi and MidiRTP…
1 Like
MIDIRTP will also become obsolete, too - there’s a new network MIDI implementation in the works, now that network MIDI 2.0 standard was defined.
Sure, once MS gets it all sorted for full backwards compatibility. I will surely not migrate to a MIDI 2 only environment, with all the hardware that has MIDI 1 baked in, although I would wish for smooth controller encoding, instead of 127 steps only…