Yeah, now that I’m really exploring it and setting up a template… It seems like the whole protocol/design is a bit convoluted.
As you say Martin, there are no MIDI sends for the instrument track.
The other inconsistency is the ‘Channel Editor’ window. You can only access the Audio Channel Editor window and not the MIDI Channel Editor window…
And in the example of say HalionSE, and utilizing all 16 slots… It’s sort of weird to have one instrument track, and then 15 MIDI channels but then there’s this strange differential of functionality whereby the MIDI channels are straight up MIDI, and the Instrument Track is this weird MIDI/Audio cross,.
It would almost make more sense to just have 16 separate HalionSEs loaded in as Instrument Tracks.
Especially because, as @st10ss pointed, there’s a lack of smart integration functionality between the 15 MIDI tracks compared to the one main instrument track.
This is kind of silly no?
Instrument Tracks should just be fully self-contained if they are to be multi-timbral.
But I guess the way they’ve done the whole protocol is a hack, because the VSTi instruments 16 slots are really just one instrument receiving multiple MIDI channels in which it can have multiple-outputs - but - adding multiple outputs doesn’t translate to the program ‘multiple instruments’ so there’s no way for the DAW to know there’s 16 instruments because multiple outputs doesn’t necessarily mean multiple instruments.
It’s kind of annoying though,
it’s left me indecisive on setting up my mother of a templates template.
it’s annoying having that one first channel be different than all the rest.