MuTools

LYTZ · Post by **LYTZ** » Sat Apr 04, 2015 1:56 pm

Hey all,

why isn't it possible to map midi controller messages internally to parameters of musampla, mupad, etc?

When I use Midicontroller generating VST modules in the mux to control parameters of the
internal muDevices nothing happens. Also when I map muDevice parameters
to a Meta-Parameter it doesnt work.

But with other VSTi Instruments and/or VST Effects it *does* works. Is that also a technical limitation?

Thanks,

tL.

MuTools · Post by **MuTools** » Sun Apr 05, 2015 9:55 pm

Pls see this doc page: http://www.mutools.com/info/docs/mux/us ... llers.html

So yes it's possible to map a MIDI controller to eg MuSampla filter cutoff.

LYTZ · Post by **LYTZ** » Mon Apr 06, 2015 12:42 pm

Please re-read.

I know that it is possible to map an *external* midi controller to any muDevice parameter and record that.
It does not work however with midicontroller data that is generatet internally by VSTs like Midishaper, LFO tool, numerology or whatever.

(Also doesnt work when I use Midi to Modulation converter, use a parameter node and all that stuff. Even when I map for example muSamplas Filtercutoff to Metaparameter 1 and try to modulate Metaparameter 1 with some VST generated mididata, nothing happens. )

Like I said, it does work however with any other VST device, *except* the muDevices. This is what I meant.

MuTools · Post by **MuTools** » Mon Apr 06, 2015 2:35 pm

See attached project.

The "LFO Controller" MUX can be replaced by a VST LFO.

LYTZ · Post by **LYTZ** » Mon Apr 06, 2015 4:08 pm

Aah, now I understand. Has to be done directly via the midi controller map, not via midi-learn. Thanks a lot!

LYTZ · Post by **LYTZ** » Mon Apr 06, 2015 4:10 pm

Just another thing. Trying this right now with muSampla. When opening the controller map for muSampla, I dont see anything in the parameter list. (empty?) Where are they?

LYTZ · Post by **LYTZ** » Mon Apr 06, 2015 4:16 pm

I cant get anything in muSampla modulated. Can you please try to replace the basic synth in your example and get anything (no matter what) in muSampla modulated via the LFO?

MuTools · Post by **MuTools** » Mon Apr 06, 2015 4:18 pm

LYTZ wrote:Aah, now I understand. Has to be done directly via the midi controller map, not via midi-learn. Thanks a lot!

Yes indeed. Because via right-click MuLab will automatically select the most relevant module for storing the MIDI mapping, which often is the rack. If you then insert a LFO VST in that rack it misses the mapping.
That's why you need to map it specificly = via the context menu of the specific module.

LYTZ · Post by **LYTZ** » Mon Apr 06, 2015 4:38 pm

Cool. Thats good to know. Now what about muSampla? Why is the parameter list empty? There is another one just for the filter module,
but even there nothing is moving when properly mapped.
Try it, see for yourself..

(Multisampler also no luck, muPad and muDrum are working fine. Also the modules Sample Player and Multisampleplayer are working fine.)

MuTools · Post by **MuTools** » Mon Apr 06, 2015 4:41 pm

Attached updated example project using MuSampla

LYTZ · Post by **LYTZ** » Mon Apr 06, 2015 4:53 pm

Oh man. Okay, now I have ease of mind. That drove me nuts. So everything in muSampla is listed under the Polysynth module.
Just didnt even came to my mind to click that little triangle there.
Thanks a lot. Again.

MuTools

KVR Audio

MuxDevives - No Internal Midi Learn?