I am using VST live in combination with mobile sheets pro and receiving via midi programm changes to switch between hundrets of songs.
Our band is normally playning up to 5 hours.
I recognized that after hours of usage in VST live the setting in the menu “connections” is getting lost and need to be manually refreshed.
Below please find how it was configured by me:
INCORRECT (the entry “MSP-an-VSTPRO” is empty, getting lost somewere / somehow)
This is the setting how it should look normally.
MSP-an-VSTPRO is mapped to VirtualMidiPortViaLoopMidi”.
Please can you help to to assure that VST-Live is not loosing this midi connection setting. Within a Gig it would be not good if I am not anymore able to switch songs in VST live.
Please let me know if you need further detailed information.
As I already wrote above I did not changed anything in the connection menue.
The entry got lost without any changes from my side.
That is perhaps not behaving like other MME devices?
VST Live certainly does not remove conenctions or their assignments deliberately, so something must have been initiated by the user, or external events (like whatever external virtual cabling or similar).
Happy End: I found out that Microsoft Rolled out Midi 2.0 via Update of Windows11. It seems that becuase of a bug the functionality of LoopMidi was blocked.
On my Windows11 computer I saw that a preview-update for Feb.-Windows-Update was available. Normally I do not install pre-view-updates for WIndows. But in this case I decided to install it and this pre-view-updated included a bug-fix fir Midi 2.0 @ Windows 11.
After a restart the virtual midi-interface via Loop-Midi was now shown again :-).
Maybe this information is helpful for other users which also use other tools for virtual midi interfaces via Windows 11.
@musicullum: Thanks for your fast feedback. Your analysis was absolutely correct. The Issue was not caused by VST live. It was caused by Windows 11 and a bug in a windows-update for Midi 2.0.
Wouldn’t it be possible that VST-Live could in the future also support virtual midi interfaces @ Windows 11? Then I could prevent an additional tool and could reduce the complexity of my system. I would assume that multiple user have use-cases were virtual midi-interfaces could be very benefitial.
The February update fixed the device count issue for apps which was preventing them from seeing when a system went from 0 MIDI devices to 1 MIDI device.
Additionally, the MIDI service was being demand-started by other apps and the shell when it shouldn’t have. That fix went out in February as well as I recall.
The loopMIDI issue is order of startup. If the MIDI Service is started after loopMIDI, you are good. If it is started before, you are not.
What is likely happening now is VSTLive is starting up the service on first call (you may have noticed it took longer to start), and loopMIDI was already running before that.
However, if you go into loopMIDI now with the service started, and add ports, they will not appear unless you close the app and restart the service.
Dear Pete, Many thanks for your fast reply.
I am quite happy that my virtual midi connection is not working again.
My impression is that since the preview windows update 02-2026 something is working changed. Before the windows update I tried different scenarios but independently from the ranking application starts at the end I was not able to get my virtual midi connection started. But thanks for your explanation I will try to continue to test different scenarios as you described to assure if and how I maybe can reproduce the issue. My standard setting is that Loop Midi is started automatically after windows start via “autostart”. For me the virtual midi is essential because it synchronizes the sound creation (VST live) and my setlist management (via mobile sheets pro"). Thanks again for your great support!
A preview of the service transport with support for loopMIDI and similar is on our Discord server in the #early-preview-releases channel. It will be in Windows in a few months.
