MIDI-Connection not visible if VST starts first

Hi!

If i start VST i cannot select the midi-connection to “core midi lightkey”.
I had to start Lightkey first - then the Lightkey Midi-Input is selectable.

It’s not a big thing but a little bit irritating.

Is it VST or Lightkey that cause this issue?

Hi! that happens because no device-scan while running, just at starting VSTL.

Ok!
It would be nice if in a future release this scan could be startet when “connections” are open.

Not as adequate:
This software is for live playing and RUN shouldn’t be stopped with a message “new device found, do you want to use this one?”

2 Likes

As long as there is no distinction between a live- and an edit-mode, which was also discussed previous. It is better, the system will be not disturbed when it is running. This includes not checking for new devices, plug-ins, etc after start.

1 Like

I dont know how VSTL uses to collect all divices. But it happens reltivly often that some musicians have not connected their devices during others are checking their midi-instruments or frickling around with midi-networks.
So - for me - it would be easier to rescan the devices and had not to restart the whole VSTL with all the loading processes.
Rescan only the midi-devices would help in my case. Maybe start it with a “Rescan-Button”.
Sure, to rescan the audio connections is not a good idea.

However. It’s not a big thing.

MIDI shouldn’t be a problem, as VL only search for MIDI ports at start and not for MIDI devices. I use 2 MIDI ports. The first is part of the audio card (devices with cable) and the second one is a CME WIDI Master for the BLE devices. It’s the better solution, then using system bluetooth connection. as the port is always available and I can turn on/off the connected devices to save battery. And it is more stable to distance changes.

1 Like