Has the Volume track any effect ?

[Eggu]

When beeing inside the midi editor you can choose in the lower part the different effect channels (typical velocity, pitch, modulation wheel).

Following questions:

1) If adding/drawing events to the volume track,
I never heard any volume change, any hint ?

2) Is a turtorial available explaining the lot of effect tracks ?
I think the effects listed are a mixture of midi events and mulab specific effects. Good example to link the effect track to a rack or instruments ?
I think there are several ways and variants.

3) While recording you can change the volume slider in a rack.
If storing this events to a separate track (Rack x Mixer Strip)
it works as expected. But if you <merge> it to an existing track,
the volume does not change during replaying
(obviously, if you have the <rack itsself> as target,
these volume events are not routed to the mixer strip).
Might be logical, but not so easy to forecast which effect will work
on separate tracks only and which in merge mode too.

[pljones]

I'll dive in and try to offer some help.

"Volume" is a MIDI Continuous Controller (CC#7). You need it routed to something that's going to respond to CC#7.

If you want to control the rack level, you can select the mixer strip as a target (either for a specific part or a whole track). When you do that, you'll find - in addition to Controllers - a section under Presets called Parameters. Within this is "Gain", which is the gain slider. Thats what you want to automate.

MIDI Continuous Controllers are nothing to do with MU.LAB itself -- you need to consult the documentation of whatever you're routing them to. MU.LAB uses Parameters -- but you can map CC's to Parameters, I think (I get confused around that area...).

If you merge parameters for one target into a sequence for a different target, you're not going to get sane results. Don't do it

Maybe someone else can add more.

[MuTools]

but you can map CC's to Parameters, I think (I get confused around that area...).

In MU.LAB 2, you can indeed map MIDI CC to the parameters of plugins in the MPA, that's including the Racks and their mixerstrips.

But note that this mapping only applies to MIDI CC's which come at MIDI input.
So it's not used to map any MIDI CC's from sequences.
If you want to sequence a parameter, just sequence the parameter itself.

[Eggu]

Thank you for your hints,
I think there is still a broad field of different topics around automation
and a tutorial focusing on this would be helpful.

[pljones]

but you can map CC's to Parameters, I think (I get confused around that area...).

In MU.LAB 2, you can indeed map MIDI CC to the parameters of plugins in the MPA, that's including the Racks and their mixerstrips.
But note that this mapping only applies to MIDI CC's which come at MIDI input.
So it's not used to map any MIDI CC's from sequences.
If you want to sequence a parameter, just sequence the parameter itself.

Isn't that confusing then? If I've mapped a CC and am playing live, it'll have an effect. But if I record that live performance, the captured CC information is disregarded when I play back the sequence? Or is the mapping traced through and the parameter movement recorded?

[MuTools]

Or is the mapping traced through and the parameter movement recorded?

Yes indeed.

[pljones]

Yes indeed.

What about VSTs that are responding directly to the MIDI CCs? (He says, clutching at straws.)

[theorize]

LOL @ "clutching at strawsf" dude that reminds me of some x-chic i had that would walk around at parties passing out straws like they were lollipops, then everyone gets up the next day complaining about cut up gums and shit.all I could do was laugh to myself.

my guess would be that the vsti translates the cc's to the parameter and since your recording "events" then you would be also as a side effect be recording the parameter modulations.