I've recently become very reinterested in Mu.Lab due to the mux development.
I would like to know if it's possible to modulate VST parameters via modulation sources. If it is, how can you do so?
Mux question (vst modulation)
-
Robert Randolph Robert Randolph https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=7328 - KVRAF
- 2226 posts since 25 May, 2003 from Saint Petersburg, Florida
-
- KVRist
- 268 posts since 8 Nov, 2002
You mean assigning an LFO or envelope to e.g the cuttof of a VST synth?
if yes, i think this is not yet possible (i may be wrong though).
if yes, i think this is not yet possible (i may be wrong though).
-
Robert Randolph Robert Randolph https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=7328
- KVRAF
- Topic Starter
- 2226 posts since 25 May, 2003 from Saint Petersburg, Florida
That is what I mean. Assigning some sort of modulation output to an automatable VST parameter.
I can't figure out how to do it other than some silly midi assigning and routing. Is there a more mux-y way to achieve this?
I can't figure out how to do it other than some silly midi assigning and routing. Is there a more mux-y way to achieve this?
-
- KVRian
- 731 posts since 25 Oct, 2008 from Holland
Can you find out in Mulab, that VST pluginn parameters ( knobs, sliders , etc )
will be showing up ?
I thought that Mulab takes over the parameters from most Vsti
will be showing up ?
I thought that Mulab takes over the parameters from most Vsti
-
- KVRian
- 855 posts since 3 Mar, 2009
There is a straight forward way:
1) Put your VST inside a MUX (e.g. Basic Effect patch - even if it's a VSTi)
2) Open your VST GUI and wiggle the parameter you want to automate
3) The VST has a Mulab top panel. On this select the option menu and select "Drag Last Tweaked Parameter"
4) You get a rectangle that you can move onto a MUX parameter, or an automation track (header). Click when you are over the target and you are done.
If you just want to automate a VST param on an automation track, create your automation track and select the VST parameter from the list that comes up.
Parameter lists from VSTs like Guitar Rig or U-he products can be messy (=hard to identify), which is why i prefer the first method.
[edit] Using MUX LFO's or envelopes to modulate VSTs is not possible. That would require the VST developers to open their synth engins, which is unlikely.
1) Put your VST inside a MUX (e.g. Basic Effect patch - even if it's a VSTi)
2) Open your VST GUI and wiggle the parameter you want to automate
3) The VST has a Mulab top panel. On this select the option menu and select "Drag Last Tweaked Parameter"
4) You get a rectangle that you can move onto a MUX parameter, or an automation track (header). Click when you are over the target and you are done.
If you just want to automate a VST param on an automation track, create your automation track and select the VST parameter from the list that comes up.
Parameter lists from VSTs like Guitar Rig or U-he products can be messy (=hard to identify), which is why i prefer the first method.
[edit] Using MUX LFO's or envelopes to modulate VSTs is not possible. That would require the VST developers to open their synth engins, which is unlikely.
-
Robert Randolph Robert Randolph https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=7328
- KVRAF
- Topic Starter
- 2226 posts since 25 May, 2003 from Saint Petersburg, Florida
This is not correct. Other hosts do this without issue. Renoise can modulate any automatable paramater (VST or AU) by nearly any signal. Usine can do this as well, and I believe bidule can.AndreasD wrote:[edit] Using MUX LFO's or envelopes to modulate VSTs is not possible. That would require the VST developers to open their synth engins, which is unlikely.
I'm very interested in Mu.Lab because of many of the awesome aspects of it, but Renoise has completely changed my way of working in software due to the modularity. As awesome as Mu.Lab is, I don't think I could migrate without that functionality.
FWIW, I have managed to get this to work using a midi loopback and assigning CCs to parameters, but the update speed is not useful for some things. It's also a bit messy to configure and resume a project.
It would be absolutely fantastic if you could assign a modulation output to a VST parameter in the same way you can assign an automation lane to a VST parameter. That would also open up all the other tools available for processing signals and modulating stuff.
-
- KVRian
- 855 posts since 3 Mar, 2009
You learn something every day .... 
Just out of curiosity, how fast could the LFO go in such a setup?
Could i use, for example, Diva oscillators and give every osc a different volume envelope?
Interesting prospects if that would work.
Just out of curiosity, how fast could the LFO go in such a setup?
Could i use, for example, Diva oscillators and give every osc a different volume envelope?
Interesting prospects if that would work.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
I built a synth using SynthEdit that had control oscillators that went from 0.01Hz to 14KHz, so you could use them as "normal" LFOs and for frequency modulation. Admittedly, that's within the SynthEdit environment, but MUX should be able to do things like that, too. Any VST parameter should take adjustment at least once per buffer (i.e. hundreds of times a second), I'd have thought.
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
A new MuLab 4.2.0 test version is available in http://www.mutools.com/mulab/cedar
This new version features the new Parameter Event Generator and MIDI Controller Generator modules which should be answering this topic.
To be complete: What's changed in M4.2.0:
New:
This new version features the new Parameter Event Generator and MIDI Controller Generator modules which should be answering this topic.
To be complete: What's changed in M4.2.0:
New:
- New Parameter Event Generator and MIDI Controller Generator modules.
- Dropping a sample on a multi-sample player (e.g. MultiSampla or the "Sampler" in MuSynth) adds a new full range zone for that sample.
- MUX Play Editor: Module buttons can get a fixed color, fixed to the PE layout, independent from the module color itself.
- Waveforms => Rotate function: Input value is expressed in degrees instead of samples.
- Envelope parts are also user renamable.
- Finetuned the default output for new racks.
- "Basic Effect" preset now includes a simple gain parameter in its Play Editor.
- Increased flexibility when reading unconventional MIDI files.
- Internal optimizations.
- Fixed a possible crash bug when inserting new instrument tracks etc. while the music is playing.
- Fixed: When deleting a rack the [+] rack button in the rack desk stayed at its old position.
- In certain situations, Import Audio File, Import Sample Loop and Import Sampe Sound could use an inappropriate rack.
- Move-drag a module from a preset device into a deep editor not possible anymore. Copy-drag still works though.
-
- KVRian
- 855 posts since 3 Mar, 2009
Wow!
In case you haven't recognized, you've got what you asked for.
While i'm writing this, in the background there an VST Classic Autofilter changing it's frequency driven by an MUX LFO. At full MUX LFO frequency.
Thanks Jo!
In case you haven't recognized, you've got what you asked for.
While i'm writing this, in the background there an VST Classic Autofilter changing it's frequency driven by an MUX LFO. At full MUX LFO frequency.
Thanks Jo!
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
OMGAndreasD wrote:Wow!
In case you haven't recognized, you've got what you asked for.
While i'm writing this, in the background there an VST Classic Autofilter changing it's frequency driven by an MUX LFO. At full MUX LFO frequency.
Thanks Jo!
ABEFLGMOPPRRST 
-
Robert Randolph Robert Randolph https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=7328
- KVRAF
- Topic Starter
- 2226 posts since 25 May, 2003 from Saint Petersburg, Florida
This is great, thank you. I do have a few requests for modulation processors, but I'll make those requests after I buy UL later tonight
Thank you much!
Thank you much!
