how to setup a multimbral VSTi in Mulab?

[janamdo]

I do want to connect Mulab with a another program and using a loopback driver

conditions for this are .....
--------------------------------------
The VSTi must listen to all 16 channels of the "Internal Midi" loopback driver and it must respond to midi program selection messages on each channel.

The device description must contain a collection of sounds with program change numbers assigned. Make sure the soundbank is set to the right "Method of Bank Selection" . Check the MIDI documentation of the VSTi.

HN2 will automatically assign the channels and sounds for you. Nothing to care about once the description is done.

If the sounds are on fixed midi channels, assign those to each sound. You can skip the program selection in that case.
.
------------------------------------------------------------------------------
Ok is this possible in Mulab?

[pljones]

1) Insert the multitimbral VSTi into a rack.
2) Best to turn on manual MIDI Input focus for this to avoid confusion (under Edit).
3) For clarity, rename Rack 1 back to Rack 1 and Track 1 to Track 1. Maybe rename the module, if it'll help you.
4) Under the Edit menu, select "Edit MIDI Input Focuses",
5) For each incoming channel you want to map, set the target module and target channel.
(You could have multiple target modules, mapping say ch1/ch2 to one, ch3-ch5 to ch1-3 on a second; you need this flexibility even though for a straight "I want ch1-16 to map to module X ch1-16 it takes a bit of time.)

[janamdo]

Thanks!
I trying to setup a composingprogram working with Mulab
It uses only the VSti sounds and the midiresult can be imported in Mulab ofcourse.
I do use also Project5 as DAW (together with Mulab), but it seems that it there rather complicated to get the right setup, because to get a multitimbral setup there differs from Mulab.

So i try now first if i get the composingprogram working in Mulab
It is also a good exercise to setup now the Vsti Catanya arpeggiator with a loopbackdriver too.

There is tutorial for setting up a multitimbral Vsti and now with your explanation it is complete clear i think.
I don't know if in the coming new version of Mulab there is a Midi recorder for recording midi output from a Vsti ?
If not than you must use still a loopbackdriver.
I did not asked Jo of Mulab about this if it is included in the new version a midi recorder to record a Vsti midi output ?

[janamdo]

Well i managed to connect the hypercanvas edirol Vssti as multitimbral synth as exercise with the method of pljones !
Compare this with the video from mutools to setup a multitimbral Vsti
The session modulair area does not show anything about that i have setup a multitimbral VSti
Perhaps a sound allocation monitor should be handy to see what sound is connected with what midichannel?

[janamdo]

i copied only over the session file from the working multitimbral setup to a another computer with a different operatingsystem (from win 7 to win xp)

Now the midichannels are working, but there is no right sound allocation ?
Is this information stored in the session file? or must i do something else?

---------------------------------------------------------------------
I am working now with a General Midi soundmodule
Is there no Bank ( soundbank) -> initialize General Midi in Mulab ?
-------------------------------------------------------------------

The same problem occur also with other VST soundmodule banks ...i think? when i reopen the session file

[MuTools]

Now the midichannels are working, but there is no right sound allocation ? Is this information stored in the session file? or must i do something else?

Which information do you mean?

Is there no Bank ( soundbank) -> initialize General Midi in Mulab ?

No, there is no specific "GM Init" function.
IIRC it's a sysex string. Sysex is not yet supported.

I did not asked Jo of Mulab about this if it is included in the new version a midi recorder to record a Vsti midi output ?

Assuming you're asking it now: At this very point in the dev cycle it's not yet in M4. It may be postponed to 4.x, not 100% decided yet.

[janamdo]

These are the conditions..for the composer to work with Mulab and vsti soundmodule
I do want to connect Mulab with a another program and using a loopback driver

conditions for this are .....
--------------------------------------
The VSTi must listen to all 16 channels of the "Internal Midi" loopback driver and it must respond to midi program selection messages on each channel.

The device description must contain a collection of sounds with program change numbers assigned. Make sure the soundbank is set to the right "Method of Bank Selection" . Check the MIDI documentation of the VSTi.

HN2 will automatically assign the channels and sounds for you. Nothing to care about once the description is done.

If the sounds are on fixed midi channels, assign those to each sound. You can skip the program selection in that case.
.
-------------------------------------------------- ----------------------------



Assuming you're asking it now: At this very point in the dev cycle it's not yet in M4. It may be postponed to 4.x, not 100% decided yet.[/quote]
Yes i never asked for this...but now i become a loopbackspecialst

How about to setup the 16 Midi In to Mulab for the loopbackdriver from the composer?

[janamdo]

i repeat the question about how to setup a Multitimbral vsti soundmodule
Answered by pljones : again thanks

Now i need the loopbackdriver to connect to Mulab for 16 midichannels but how?
There are only 8 ports
Stand 1 port for 16 midichannels then? ..as i encountered in the composerprogram ( fantastic program but the trouble is to get a decent sound from it )that is the whole issue of this thrread for me

[MuTools]

Pljones gave a good answer.
So which question is still open?

[janamdo]

Pljones gave a good answer.
So which question is still open?

He explaines too how to setup a loopbackdriver?

[MuTools]

The instructions for how to setup a loopback driver should be included with such driver. For MuLab it's just like any other MIDI port, so you got to activate them via EDIT menu -> MIDI Setup.

Also note that a MIDI port is not the same as a MIDI channel.
Each port has 16 channels.

[janamdo]

Thanks..
In Mulab a multi timbral vsti must act as a soundmodule for 16 midi channels
A composer connected with a loopbackdriver use this soundmodule

I try to set this up in Mulab ..so i can use the instructions from PLjones and set the loopbackdriver on port1..all 16 midichannels are routed than to the composer

It is now only the question if the conditions for the composer are satisfied, , because it must listen to Mulab's Vsti soundmodule to get a device setup and a Gm-init function

I did a test with a obsolete VST( i think )and it did not work, so i must use now a modern Vsti General Midi soundmodule like bandstand or others?

[MuTools]

I think all looks right: Composer program -> MIDI loopback -> MuLab.
In MuLab use the MIDI Input Focusses to dispatch all 16 channels to your MT VSTI. Note that MuLab does not (yet) support the GM Init function though.
Besides that GM Init function things should work. What exactly does not work?

[janamdo]

Note that MuLab does not (yet) support the GM Init function though.
Besides that GM Init function things should work. What exactly does not work?

If the composer cannot make a GM Init Call to the Vsti multitibral General Midi SoundModule ( like Bandstand ) in Mulab , than there is no General Midi sound allocation for the Composer

The composer accompaniment( band instruments ) are based on General Midi sounds.
So when i start the band on the composer they will play the wrong sounds in Mulab

So Mulab must support than the feature that the composer can make a Device set up( connected with a loopbackdriver) with the GM Init Call function
I must make/save this device setup in the composer


-------------------------------------------------------
Look at the start of this topic : conditions
------------------------------------------------------

[MuTools]

So if i understand well, then the only thing missing is the gm init support, right?