Multichannel VST Problem
-
- KVRer
- 4 posts since 15 May, 2009
I'm having a very unpleasant problem with multichannel VSTs.
Say I've made a blank project in Mu.Lab. I set up midi inputs, assign channels to midi tracks and load up a certain multichannel VST. Then, I choose patches for different midi channels in my VST and set Mu.Lab to "Use Automatic Midi Target". All is sweet until you try to switch to another rack. Once I switch, nothing happens, except I hear the instrument assigned to channel 1. Even setting the rack as midi target won't help. I have to choose a rack, then a corresponding midi track and set midi channel anew to make it work as it should... And so every time when I'm switching to another rack.
Also, some other multichannel VSTs won't remember the patches I chose when I open a saved project.
Say I've made a blank project in Mu.Lab. I set up midi inputs, assign channels to midi tracks and load up a certain multichannel VST. Then, I choose patches for different midi channels in my VST and set Mu.Lab to "Use Automatic Midi Target". All is sweet until you try to switch to another rack. Once I switch, nothing happens, except I hear the instrument assigned to channel 1. Even setting the rack as midi target won't help. I have to choose a rack, then a corresponding midi track and set midi channel anew to make it work as it should... And so every time when I'm switching to another rack.
Also, some other multichannel VSTs won't remember the patches I chose when I open a saved project.
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
I'm not sure what you mean.composerx wrote:I'm having a very unpleasant problem with multichannel VSTs.
Say I've made a blank project in Mu.Lab. I set up midi inputs, assign channels to midi tracks and load up a certain multichannel VST. Then, I choose patches for different midi channels in my VST and set Mu.Lab to "Use Automatic Midi Target". All is sweet until you try to switch to another rack. Once I switch, nothing happens, except I hear the instrument assigned to channel 1. Even setting the rack as midi target won't help. I have to choose a rack, then a corresponding midi track and set midi channel anew to make it work as it should... And so every time when I'm switching to another rack.
When you setup some MU.LAB tracks so they target the same multichannel VSTi, and you right-click the tracks to setup the effective MIDI channels on which they have to play that VSTi, then when you click a track or part, the proper target plugin is focussed on the proper MIDI channel.
Of course, if you click a rack containing a multichannel VSTi, then MU.LAB cannot know on which channel you want to play that VSTi. Clicking a rack makes that rack the target for MIDI input, on channel 1. I think this is logical, no?
It's the VST plugin's responsability to load/save its data.Also, some other multichannel VSTs won't remember the patches I chose when I open a saved project.
Which VST plugin(s) are you talking about?
-
- KVRer
- Topic Starter
- 4 posts since 15 May, 2009
Thanks, the save/load problem was solved.mutools wrote:
It's the VST plugin's responsability to load/save its data.
I connect multiple racks to one multichannel VST like this:mutools wrote: I'm not sure what you mean.
When you setup some MU.LAB tracks so they target the same multichannel VSTi, and you right-click the tracks to setup the effective MIDI channels on which they have to play that VSTi, then when you click a track or part, the proper target plugin is focussed on the proper MIDI channel.
Of course, if you click a rack containing a multichannel VSTi, then MU.LAB cannot know on which channel you want to play that VSTi. Clicking a rack makes that rack the target for MIDI input, on channel 1. I think this is logical, no?

But I have to re-assign channel for a midi track (that targets a rack) every time I want to play thru it (it doesn't happen to a 'channel 1' track, though). I have only two multichannel VSTs (namely Hypersonic 2 and Edirol Orchestral) and this thing happens to both of them.
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Question: Why do you need the racks before Orchestral?
What's in these racks? (just asking for my curiosity, it's perfectly ok to do so)
Anyway, if i have two tracks targetting the same rack, but i set track 1 to target channel 1, track 2 to target channel 2, then
when i click track 1 i'm effectively playing rack a, channel 1
when i click track 2 i'm effectively playing rack a, channel 2
I just tested this and it works ok.
So i still don't see the problem, sorry
Note that if you click a rack itself, then midi channel 1 will be used as MU.LAB cannot know that you would want to target another channel. So it's best to click the tracks or parts in this case.
Does this help?
What's in these racks? (just asking for my curiosity, it's perfectly ok to do so)
Anyway, if i have two tracks targetting the same rack, but i set track 1 to target channel 1, track 2 to target channel 2, then
when i click track 1 i'm effectively playing rack a, channel 1
when i click track 2 i'm effectively playing rack a, channel 2
I just tested this and it works ok.
So i still don't see the problem, sorry
Note that if you click a rack itself, then midi channel 1 will be used as MU.LAB cannot know that you would want to target another channel. So it's best to click the tracks or parts in this case.
Does this help?
-
- KVRer
- Topic Starter
- 4 posts since 15 May, 2009
...Well, for some reason I thought thatmutools wrote:Question: Why do you need the racks before Orchestral?
What's in these racks? (just asking for my curiosity, it's perfectly ok to do so)
one rack = one midi track
I was wrong. Modular plugin area and Mu.Lab's interface in general was a bit confusing to me when I first saw it, so I made this mistake.
Thanks a lot! My problem is solved now
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
FYI: It could perfecty make sense to use racks before Orchestral in case you would want to apply some MIDI plugins (arp, chord-mapper, etc...) before the midi events get to Orchestral.
On top of that note that it is not necessary to use racks for that, you could also connect such midi plugs directly in the MPA.
You can see MU.LAB as a flexible music studio where you can play and experiment with connecting the cables between the various modules aka plugins
On top of that note that it is not necessary to use racks for that, you could also connect such midi plugs directly in the MPA.
You can see MU.LAB as a flexible music studio where you can play and experiment with connecting the cables between the various modules aka plugins
