How to show/select detailed target-information of a track/part

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

Post

topic not really new, but I still have some difficulties:

e.g.:
- create a rack, with a multi-layer vst plugin (e.g. eastwest, free edition)
- select e.g. two layered instruments (each instrument has its own settings, like envelope attack)
- create a seq. manually, play --> both instr. sounds, ok.
- open seq., click at velocitiy track (left) -> you can see all available presets, (midi-) controllers, content ... but no plugin specific parameters.

do the same, but creating the seq. by recording midi keyboard events, change some parameters (like attack for 1st instr), and e.g. the mod wheel.
--> now you get two parts on two tracks, 1st part with key events as usual, incl. mod wheel events,
but also an add. track with the attack parameter events
--> fine, also playback is as expected.
--> now in the separate parameter track seq. all parameters of the plugin are visible and selectable.

questions:
1) why are the parameters are not visible in the first case, why do I have to record at least one parameter event ?
2) the target of the parameter track is the vst plugin, ok. But it is not visible that (only) one instr. (layer) is targeted. Information about that must be hidden somewhere in the seq. itsself.
When trying to target a seq. manually to a layer, I failed (plugin in the rack is selectable, but no further sub-selection for layer is visible).
3) In which cases does mulab create multi-tracks during recording ? Sometimes parameter events during records are simply ignored (even if changed), and key events are recorded only. (Same track active).
Everything should be made as simple as possible, but not simpler!

Post

The answer is quite simple:

To make the plugin parameters visible in a sequence, you have set the target for this track or only for this sequence by rightclicking "Choose target module"...(by default the whole rack is on target and in this case, MULAB cannot know, which plugin in the rack you want to automate, so you have to specify this)

It is sometimes a little confusing with the autonaming racks in MULAB...As long as you haven't renamed a rack already and you insert a module in a rack, the whole rack and the matching track gets the name of this module automatically, but the target of this track is still the whole rack...
Follow the next steps:

In the next menu, click in the line of the rack your plugin is inserted in on the rightmost rack icon (with a little arrow, pointing to the right) to "open" the rack (in this list)...this is where you can choose the plugin...after choosing this as the target, you can access the parameters from the controller lane


As you recorded the sequence, your changes in the plugin has been recorded as parameter modulation, which you have recorded in the second sequence because this one was automatically routed to the plugin directly and so you were able to access the parameters of this instrument out of this sequence...

Two sequences because your main sequence for the midi data was routed to the whole rack, the parameter changes are only for the plugin, so MULAB made two sequences, because you are able to route sequences to different targets on one track...

Hope this was not too confusing :-)

Trancit

Post

I've taken to renaming the racks back to something other than the plugin name. Makes it a lot easier to follow what's going on.

Post

Trancit wrote:The answer is quite simple:

To make the plugin parameters visible in a sequence, you have set the target for this track ...

Hope this was not too confusing :-)

Trancit
Thanks a lot, yes, it's logical!

Seems that multi-layer plugins have different behaviour,
e.g.
- for eastwest all parameters are visible in the sequence parameter list,
but only layer one is affected by the parameters,
- a multi-string plugin shows all recorded parameters (in the content section)
for each layer (where parameters has been changed during recording),
but here the parameter section itsself is empty. :-o
Everything should be made as simple as possible, but not simpler!

Post Reply

Return to “MUTOOLS”