Linking VST parameter auiomation the way you do that with MIDI CC?
-
- KVRist
- 83 posts since 11 Jul, 2011
Hi!
I would like to find a way to link any parameter of VST-plugin loaded inside a MUX module to the MUX module's own automation parameter (or top-level MULAB-PLUGIN parameter) in the same easy way as we currently use for MIDI CC linking (just from the pop-up menu opened from the last touched parameter field on the top of the VST plugin window). Is there any way like that now? The thing is that for many VST plugins the process of finding the right parameter from a long list in the Parameter Map window is not so simple and obvious. Setting up the automation can be quite a tedious process...
Thanks a lot!
I would like to find a way to link any parameter of VST-plugin loaded inside a MUX module to the MUX module's own automation parameter (or top-level MULAB-PLUGIN parameter) in the same easy way as we currently use for MIDI CC linking (just from the pop-up menu opened from the last touched parameter field on the top of the VST plugin window). Is there any way like that now? The thing is that for many VST plugins the process of finding the right parameter from a long list in the Parameter Map window is not so simple and obvious. Setting up the automation can be quite a tedious process...
Thanks a lot!
- KVRAF
- 13851 posts since 24 Jun, 2008 from Europe
See this doc page: https://www.mutools.com/info/M9/docs/mu ... ugins.html
Briefly: Tweak the parm on the plugin editor, this will switch the focused parameter knob at the top of the plugin editor. (if the top controls are expanded)
Then you can right-click that 'proxy' parameter and do the same as for MuLab's own parameters, as well as drag-drop that parameter to an automation track.
Does this answer your question?
Briefly: Tweak the parm on the plugin editor, this will switch the focused parameter knob at the top of the plugin editor. (if the top controls are expanded)
Then you can right-click that 'proxy' parameter and do the same as for MuLab's own parameters, as well as drag-drop that parameter to an automation track.
Does this answer your question?
- KVRAF
- 13851 posts since 24 Jun, 2008 from Europe
Thanks for your appreciation!
Please also tell others about MuLab via your socials so MuLab gets more known!
Please also tell others about MuLab via your socials so MuLab gets more known!
- KVRAF
- 3139 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Is there any chance you could add the ability to assign a midi knob to the Focused Plugin Parameter Control itself as opposed to the underlying parameter?
In other words whatever you last adjusted is always controlled with the same hardware knob. You move mouse to a vst knob, adjust slightly, then it's usable via a hardware controller assignment. But move the mouse to another vst knob and the same hardware controller is used to adjust that new parameter.
In other words whatever you last adjusted is always controlled with the same hardware knob. You move mouse to a vst knob, adjust slightly, then it's usable via a hardware controller assignment. But move the mouse to another vst knob and the same hardware controller is used to adjust that new parameter.
-
- KVRist
- Topic Starter
- 83 posts since 11 Jul, 2011
I use Mulab Plugin mostly as a mega-handy subhost/router in Reaper. My setup is rather unusual but it gives much possibilities and I always advice your product to people who look for such possibilities. I'm not presented much in socials. The only things I use are Facebook and Telegram. I could re-post your FB news on my page if you like as soon as new ones are coming.
By the way, I think that Mulab is highly underestimated right as a subhost/router. I'll think about posting the description of my work setup with it inside Reaper in Reaper's forum. Maybe that could attract some people looking not for new DAW but just for a flexible playground inside the DAW they're familiar with.
One more possible interesting role of Mulab Plugin is a modular VSTi but, as to my own taste, there are some limitations that make it sound not as perfectly as many (semi)modular competitors. As I can see (dissuade me if I'm wrong) most of the modules (except oscillators, samplers and few others maybe) work at project sample rate and are not antialiased. Even Amp Distortion module isn't oversampled. The same to envelopes and VCA modules. This makes the sound have that "early 2000-th soft synth" character which I personally don't look for and which is an immanent feature of sound engine without oversampling.
Sorry for my criticism. I'm happy using your product and so grateful for it's intensive development! I think, as a playgroung for 3d-party VST-s it's simply the best one on the market. But speaking about popularization of your product among other people I thought it could be useful to share some of my critical thoughts with you.
Thanks!
By the way, I think that Mulab is highly underestimated right as a subhost/router. I'll think about posting the description of my work setup with it inside Reaper in Reaper's forum. Maybe that could attract some people looking not for new DAW but just for a flexible playground inside the DAW they're familiar with.
One more possible interesting role of Mulab Plugin is a modular VSTi but, as to my own taste, there are some limitations that make it sound not as perfectly as many (semi)modular competitors. As I can see (dissuade me if I'm wrong) most of the modules (except oscillators, samplers and few others maybe) work at project sample rate and are not antialiased. Even Amp Distortion module isn't oversampled. The same to envelopes and VCA modules. This makes the sound have that "early 2000-th soft synth" character which I personally don't look for and which is an immanent feature of sound engine without oversampling.
Sorry for my criticism. I'm happy using your product and so grateful for it's intensive development! I think, as a playgroung for 3d-party VST-s it's simply the best one on the market. But speaking about popularization of your product among other people I thought it could be useful to share some of my critical thoughts with you.
Thanks!
- KVRAF
- 13851 posts since 24 Jun, 2008 from Europe
Nice idea. Taken note to take a look at it from tech side. But that will be later, after the reworked rack system is ready.sl23 wrote: Mon Sep 09, 2024 7:24 am Is there any chance you could add the ability to assign a midi knob to the Focused Plugin Parameter Control itself as opposed to the underlying parameter?
In other words whatever you last adjusted is always controlled with the same hardware knob. You move mouse to a vst knob, adjust slightly, then it's usable via a hardware controller assignment. But move the mouse to another vst knob and the same hardware controller is used to adjust that new parameter.
- KVRAF
- 13851 posts since 24 Jun, 2008 from Europe
Thanks!ortseam wrote: Mon Sep 09, 2024 7:42 am I use Mulab Plugin mostly as a mega-handy subhost/router in Reaper. My setup is rather unusual but it gives much possibilities and I always advice your product to people who look for such possibilities.
Yes please.I'm not presented much in socials. The only things I use are Facebook and Telegram. I could re-post your FB news on my page if you like as soon as new ones are coming.
It's essential to pull public attention to MuLab as much as possible.
I don't have a media team and nowadays media attention is extremely vital !!
And lack of media attention is killing !!
Yes! Anything that publicly highlights the goodies of MuLab definitely helps!By the way, I think that Mulab is highly underestimated right as a subhost/router. I'll think about posting the description of my work setup with it inside Reaper in Reaper's forum. Maybe that could attract some people looking not for new DAW but just for a flexible playground inside the DAW they're familiar with.
Thx
I agree adding oversampling options to the modular signal path would be very welcome.As I can see (dissuade me if I'm wrong) most of the modules (except oscillators, samplers and few others maybe) work at project sample rate and are not antialiased. Even Amp Distortion module isn't oversampled. The same to envelopes and VCA modules. This makes the sound have that "early 2000-th soft synth" character which I personally don't look for and which is an immanent feature of sound engine without oversampling.
It's taken into account already in some tech structures under the hood but will need some extra work to get implemented for real.
I always welcome constructive criticism, like you share here.Sorry for my criticism. I'm happy using your product and so grateful for it's intensive development! I think, as a playgroung for 3d-party VST-s it's simply the best one on the market. But speaking about popularization of your product among other people I thought it could be useful to share some of my critical thoughts with you.
Doing my best, within the realistic context of a solo dev, to keep growing MuLab
The more users help to put media attention on MuLab the more i can focus on developing MuLab!
Thanks
- KVRAF
- 3139 posts since 28 Mar, 2008 from a Galaxy S7 far far away
