Mulab for live work - some tips

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

There seems to be some interest about how to setup Mulab/MUX for live use.
I'm starting a new thread with some tips and thoughts about this subject.

Mind you, I have not performed live on stage! So all requirements here come from watching others :)

I am discussing a setup with one or more keyboards or anything that can send notes to Mulab. There is nothing to trigger a sound or a sequence in Mulab other than notes, so we have to use notes. Usually created by external controllers, but the Mulab keyboard/computer keyboard will work as well.

What I understand from live performances is that things should be the same every performance and the setup is supposed to be a fixed one. And things have to stay fixed, whatever happens.
Therefore some setup in Mulab is necessary.
Mulab works with 'focused' modules. Meaning whatever is focused at one moment is going to receive incoming events. One mouse click can change focus and something entirely different is making sound. Quite a frightful thought when performing.

So things have to be fixed. In the Session menu there is the entry "Edit Midi Input Tragets".
Here we assign what controller controls what device.
Note that even you have many external controller, Mulab combines them all as one device. Therefore we use midi channels to separate the external controller.
Set each of your controllers to output on a different midi channel.

I setup racks in Mulab and named them after the controller that will play that rack.
In the "Edit Midi Input Tragets" list setup the midi channels of your controllers to the required rack.
Live Play.jpg
To test the setup, load an instrument in each of your racks and check that each controller is playing the correct rack.


Now how to setup instruments, loops, audio, etc. to be played.

The easy case is to play a VST instrument. Just load it into the required rack and play. You will probably use different patches during your set. Copy all necessary patches in one specific folder. To change patches use the "Next Patch" arrow next to the patch name, or have the folder open in the browser and drag&drop the next patch in your rack.


To play loops and longer audio parts, there is a bit of MUX setup to do.
Live MUX.jpg
In the above MUX I assume that a lot of different items will be triggered from one device.
So first the incoming notes will be devided for their different tasks. The range is set with the Note Key/Vel Filter module.
In the example I set one octave for each of the different playback setups.


1) Playing longer audio parts:
These are the red modules.
The incoming C1 octave will be further broken down to single notes using the Drum Note Processor.
Each note can trigger a different audio part. So you have 12 audio parts under your control.
I use MuPads and not MuSampla for each of the audio parts.
The idea is to trigger audio compared to play it as long as you hold a note. MuPads have an infinite release time and can therefore play any long audio until the part ends. MuSampla's release is 40sec which is not long enough. Mind you that once a MuPad is triggered, it will play till the end! If you rather hold the notes during playback, use MuSampla instead.
Note that all the audio files need to fit into RAM! There is no way to trigger streamed audio in Mulab (unless you replace MuSampla with streaming samplers).

2) Playing loops:
These are the blue modules.
Again you can setup up to 12 loops to be triggered independently.
Here I use Musampla and trigger it from a sequence player that contains only one note. From my experience I always retrigger loops and not loop them. This ensures timing stability over time.
The sequence should have one note only, with the exact length of the loop. The sequence should be looped, so add a loop end at the end of the note. You can switch off the Auto Transpose in the sequence player.
In the MuSampla the loop should NOT be looped. Set amplitude release time very short. Check if the sample is played at the correct pitch. You can Edit Property of the sample and set the key to the note you use in the sequence player.

3) Playing sequences:
If you want to use ready made sequences, like in MuClips, look at the green modules.
Again I limit the keys for this sound. The sequence is triggered and feeds the instrument. I imported a MuClip, which is why a rack is created that holds the instrument.
You can play different keys and the sequence will transpose as you know it from MuClips. That means you must set your key range to something appropriate for your songs.



Mind you that the timing of all those triggers will come entirely from your playing. Mulab does not support things like "trigger at the beginning of the next bar" or similar.

I hope this is a bit helpful.
You do not have the required permissions to view the files attached to this post.

Post

This is very helpful Andreas. Thanks!

I was having some trouble with my MUX. For the loops I was trying to loop them in the sampler and was unable to stop the loop by hitting the same note again. Your MUX fixes that. It also helps me learn a bit more about the MUX modules. The only thing I found was that my loops played at the incorrect pitch. To fix that I placed a note ranger between the sequence module and the musampla. There may be a more elegant way to do this.

Thanks again.

Post

Thank you AndreasD for that explanation, its very fascinating and helpful
Beauty is only skin deep,
Ugliness, however, goes right the way through

Post

mgiambro wrote:This is very helpful Andreas. Thanks!
The only thing I found was that my loops played at the incorrect pitch. To fix that I placed a note ranger between the sequence module and the musampla. There may be a more elegant way to do this.
To adjust the pitch, try a Note Modifier module and transpose as necessary.
Again, there is the right click on the sample, Edit Properties and you set the root key accordingly.

Post

Thanks Andreas. I'm not a live player but the bit about midi controllers targeting racks was useful info do me.

Post

mgiambro wrote: I was having some trouble with my MUX. For the loops I was trying to loop them in the sampler and was unable to stop the loop by hitting the same note again.
Make a panic shorcut. It allway usefull in many cases.

I'm using Mulab in live philosophy too, with internal and external synths.

I'm just starting to understand modulare mux.
As oldschool synth player i just made 2 Mux modules who makes life easier

"Midi merge" 2 in 1 out
"Midi split" 1in 2 out

it solves my synth stack problem to mix internal, vsti, an external synths.

Just use "Midi split" (mux module) as destination for a midi channel and connect all you want after.

I'm using midi vst to replace missing midi support.

Like channel mapper or midi program change.

What i really missing is to be able to switch thing on / off with button , single or multiple swich would be nice because we would be able to use pads or other external in easier way.

Post

This is a nice thread. I'm learning a lot!

@Braserox
There are some switching on/off, but you are correct, some things are missing, e.g. a selector.

What you can do:
Live MUX Front.jpg
1) To switch off single notes, use the Drum Note Processor. Open it's editor and you can Mute/Solo single notes by using the M and S of each pad. It's called drum note processor, but works for anything. And each pad shows the name of the connected device. Very nice!
I just learned that there is a Note Key Splitter with the same functionality as the drum note processor just without the front panel.

2) Most modules have on/off switches. You can simply drag&drop any module from the editor to the front panel. On the front panel right click a module, select Edit Looks and activate the On/Off Button.
If you switch off midi modules they will either stop doing what they should do(e.g. transpose) or every input will be routed through the leftmost connection
You do not have the required permissions to view the files attached to this post.

Post

AndreasD wrote:
mgiambro wrote:This is very helpful Andreas. Thanks!
The only thing I found was that my loops played at the incorrect pitch. To fix that I placed a note ranger between the sequence module and the musampla. There may be a more elegant way to do this.
To adjust the pitch, try a Note Modifier module and transpose as necessary.
Again, there is the right click on the sample, Edit Properties and you set the root key accordingly.
Thanks for the tip. Re editing the sample properties - sorry, I missed that in your original description.

@Braserox - Thanks for the tip. I agree about the buttons. That would certainly be useful. As would trigger on next bar start. Maybe it could be suggested to Jo.

Post

I'm following this topic, be it a bit shallowly atm, cause i'm quite concentrated on a couple of other working points atm. But i'll certainly reread relevant posts at relevant time. Thx.

Post

AndreasD wrote: There are some switching on/off, but you are correct...
To switch off single notes, use the Drum Note Processor.
I have your mux file. Drum Note is a nice idea .
But when im speaking about swicht, i mean CC controler switch . I need my notes to play music ;)

CC num , value 0 -127 (for on / off)

Or step switch or selector CC num, multiple values for selecting pcm waves for exemple (on some synths)

Unfortunelly i have a dead Clavia Nord Mudular C2 i was controlling via Midi keyboard controller.
Was very nice to play around with modular system.

Post

Manual of real synths are good basis to understand how synthesizer are working.
Digital rollroyce for ideas for modular systems and ideas for new or missing modules .

http://www.nordkeyboards.com/sites/defa ... 201.4x.pdf
http://www.native-instruments.com/filea ... nglish.pdf

Im thinking about to make a list of G2 modules and how they can be done with Mulab . G2 has a free demo version but there is no VSTi Can be used to make some test . Patch can be saved. Save sound with some external audi tools.
.
What i really miss in Mulab is a better and easier midi support.
Device , Midi in channel, midi out channel should be visible and modifiable on Tracks for live use.
Same in modular with input and output module.

When you are making live stage you are often using more than 1 device to controle sound. Moste time 1 to control the synth (virtual or hardware ) 1 to control sequence or arpage an 1 to control audio FX.

You have thinking to be able to control several instruments with serveral midi devices.

Roughly 3 parts need control at same time

Rythm part
Pad part
Lead part


In creation mode you only need 1 device because you are working step by step.

And if poeple is lazy they need only a mp3 player as music controller.

Post

Suggestion for dev:
The merge device input system is not very good. Instead having more chanel we have to share the 16 midi channel between all devices.

Easy way would be making a copy existing "Midi input channel target " list for each connected midi device

Second thing in Modular we have "session event output" why not add "session event input"

We have both for audio why not for midi ?

Post

mutools wrote:I'm following this topic, be it a bit shallowly atm, cause i'm quite concentrated on a couple of other working points atm. But i'll certainly reread relevant posts at relevant time. Thx.
As regards the 'on next bar start' etc, don't worry about it too much (unless lots of others want it of course). I think if I need to do a dj type set, I'd probably use dedicated software - probably together with mulab for triggering bits here and there.

Post Reply

Return to “MuTools”