How is it supposed to work if you haven’t even specified the MIDI port where the track will send the command? Into the void? Or is it preventing you from choosing? The MIDI port menu won’t open?
hi @kraimor , as @sergeantt67 mentioned, an OUT destination is needed to be set (regardless of speaking about any kind of tracks in VST Live). Always keep your eyes on IN and OUT port settings to be sure signal goes in from and coming out to wanted ports
I’ve made the screenshots on my Macbook at home (without the interface). But it makes no difference. It’s the same behaviour like with connected interface.
On the working track I see a amplitude/peak on the track meter when the signal is sent. On thr other track not.
For testing and checking, it is always a good idea to use virtual midi “cables” and Devices/Midi Monitor.
Set your tracks’ output to Virtual MIDI Out 3 (for instance), and the Midi Monitor input to Virtual MIDI In 3 (matching the sending port number). Then you can see what is sent from the track. The exact same data will be sent to your device when you select that as track output instead.
Just to keep everybody here in the loop: VST Live does in fact not send the controller data in question. Checked with Virtual MIDI on multiple machines..
And, as you might have noticed: I moved this discussion to a new topic.
As Michael @Spork pointed out, the Song Channel of the song with the non-working MIDI track wasn’t connected to the Main Out. The MIDI engine, however, depends on such a connection.
In every other respect, the song in question worked perfectly as audio was sent out in groups to a real world mixing desk, leaving the Main Out unused.