I try to connect on 2 midichannels the same vsti plugin in Mulab and use a loopbackdriver to route to 2 channels in the composer

Strang enough only one midichannels has a output
A midi port has 16 midi channels so i use one port

The midi input focus is set for a channel 1 and channel 2 in Mulab with target chan 1 and 2
I got the same problem with a Vsti with 4 instruments on 4 midichannels..also one midi channel gets a sound

It seems that there are DAWS who don't have this problem ( reaper shows a multitimbral Vsti with 2 wmidi channels working.

With these settings:

and the rack set up as you'd expect:

Switching MIDI channel on my keyboard triggers the appropriate VST. Note that I have had to specify the "Target Chann" to ensure that the VST gets notes with the right channel number.

With a multi-timbral (multi-channel) VSTi, the only difference would be that the "Target Module" would be the same for each source channel and the "Target Chann" would map that source channel to the desired target channel:


One thing I do notice is the new racks I added route directly to "Audio Output 1" rather than to "MASTER", which was a surprise.

Thanks!
The desired configuration is that i connect the VSti in MUlab with a loopbackdriver to a external composingprogram with 8 channels
So there is no Midi focus neccessary .. 8 midi channels from Mulab straight to 8 channels of the composer

But this seesms to be not working, because i get only one midichannel routed and the other midi channels are ot working
A midi port has 16 midichannels so that's not the problem
Midi focus is not relevant for this type of connection

I checked the MIDI Input Focus table feature and it's working as expected here.
Note that you can monitor your effective MIDI input via MULAB menu -> Help -> Monitor MIDI Input Notes. Does that reveal something?

Wel finally it seems to be working 2 the same monophone VSti in Mulab with a external 8 midi channel composer
Yes handy to use Monitor Midi Input Notes !

Still needed is to be use the midi focus by Edit MIDI Input Focus to put on the 2 Vsti ( target ), otherwise there is only one midi channel to be seen( although the 2 sounds can be heard, but only on racks shows a audio output)

I don't know what Toggle Automatic Midi Focus has to do in this setup ?

I have no physical connections feeding MULAB, everything goes through a loopback driver. MULAB doesn't differentiate.
I don't follow the logic here... but it does lead me to another hint. If you're recording multi-timbral MIDI events onto a single track (i.e. the single track has focus), then you must set the track to "Choose MIDI Channel -> Per Part". Parts default to "Per Event", so that is all that's needed.
As noted above, if you target the composer, I assume you're recording events, not targeting a rack, so you need to ensure the track channel isn't set.

Midi focus in MUlab is handy for chancing a rack when you use a keyboard..so you must foucus your keyboard on a rack

I do not need to focus a keyboard in the composer.. only connecting permanent midi channels, but perhaps if i use a keyboard in the composer

I don't understand. Your english sometimes is hard to understand for me. No offense, just a humble note.



Automatic MIDI Input Focus is explained on this doc page: http://www.mutools.com/mulab/docs/main-menu.html

I must be more careful with language..you are right

So are there any open questions in this topic, or is everything now working as you want?

Ah, I see what I think might be a problem now.

Mark I Suitcase and CP11 Harpsi are both sitting in the same instance of Kontakt, which is sitting in the targeted rack. Having just added Kontakt and the two instruments, playing notes on Ch1 triggers the Mk1 sounds. Unfortunately, playing notes on Ch2 also triggers the Mk1 - so clearly something unexpected is happening. It's not clear what's causing the incoming MIDI messages to have their channel changed. (A session MUX MIDI monitor shows Ch1.)
Last edited by pljones on Wed Apr 25, 2012 5:54 am; edited 1 time in total

Yes, i think for these two the same vsti plugins.(two instances)it is working as i want ( 2 racks in Mulab and 2 tracks in the composer )
Now i have used two the same vsti monophone plugins on different midi channels
Mulab acts as Host( soundmodule) here for a composer with a loopbackdriver

It seems to be good working.

Now the configuration with a multitimbral Vsti again,because the last time i tried this i don't get as i want it with the composer

So there are 2 setups

Using Mulab as a external soundmodule is limited to 16 midi channels for working with a loopbackdriver it seems
I do have some composingsoftware where 32 midi channels are also interesting ( classical music)
To use more than 16 midi channels is better, but it seems impossible by the midi standard ( a midi port has 16 midi channels ) so you must add more ports
I must look at this again , because i do have 8 midi loopbackports to use
Maybe in th ecomposer i can add a second loopbackport and route this to Mulab?

How did you setup the MIDI input focus table in this setup. I assume you use 'focused' channels. It should be 1->1, 2->2 etc.

Yes , this is the case with a multitimbral Vsti sampler what has 4 ports, but only one port can be used

Put the midi focus on rack 1 and rack 2 with the right midi channels doesn't solve this problem?

Found it.
The "Target Chann" in "Edit MIDI Input Focuses" set to "Focus" causes Ch1. If incoming Channel 2 is set to Channel 2 (with target module left as "Target Module"), then you get the expected effect. I'm not clear what "Focus" should mean if target module is "Target Module".

At least that lets you switch rack yet still have multi-timbral but it should be like that by default, I'd have thought (i.e. target module as "Target Module" but channel unchanged).

Kontakt as a VST does not have 4 ports. The issue with channel assignment is not related to the number of ports here.
Last edited by pljones on Wed Apr 25, 2012 6:04 am; edited 2 times in total