MuLab 9.0.59 App + Plugin

[MuTools]

Bug: Loading image files (png, bmp), for front design is broken in v9

Apologies for the delay on the reply on this.
You're right, and it will be fixed in the next update.

[cpssounds]

Ah, alright, thank you! Guess that helps, looking for CC number not the actual midi controllers name... great

[cpssounds]

Thanks, I figured it that out, what you replied

Ok, so current status:

Midi Controllers (BCR2000 and x-touch mini) are correctly configured (set to cc, all ccs are numbered, rotation knobs are set to relative 3, push button to cc and toggle).

Controller Mapping directly in Reaper works flawlessly, with Samplitude I still have problems, vst paramter slipping back to zero, but no mulab topic.
I'll focus on Reaper now, to learn how to midi map mulab 9 plugin.

In mulab 9 plugin composer window I created a fx chain, in the upper row the "MP" knobs, I was able to map them via the midi learn from reaper context menue once, than it didn't worked again.
But I guess there must be another way too.
But, then how to map inside of mulab 9 plugin a vst parameter to an "MP" knob?
Or, is it possible to bypass the "MP" knobs and directly map a VST parameter to the midi hardware controller.

Also I know exactly the CC numbers of every midi hardware controller knob, but in the source drop down menue the corresponding numer I choose wasn't working.
Is there like a midi learn function in mulab 9 plugin?

So my question is, how to map a hardware controller knob to a VST parameter inside of mulab 9 plugin module composer and (maybe the same way) in an fx rack inside composer?

So, does anyone can maybe provide like a step by step tutorial for getting midi controller mapped inside mulab 9 plugin to control prameters in a loaded vst inside mulab plugin?

There is no information (as far as I know) outside, that was providing such informations in detail and mulab 9 standalone app works I guess a little different, concerning mapping or setting up a hardware controller, as like in mulab 9 plugin.
Most informations out there reffer to older versions of mulab.

The option of using mulab 9 plugin as a vst container and creating fx chains and controlling them via a midi hardware controller was the main reason of buyiong it, now I feel like standing in the rain, alone at midnight on a street and really dont know where to go.
I'm trying for days now.

Many thanks

[robert_p]

(...)

When you open your VST plugin within the MuLab and touch/move any of it's parameters you'll see the corresponding parameter at the top of the plugin window:

Plugin_Parameter.jpg

You can drag it and drop to your MP Macro knob or map it directly by right-clicking on it.

Also see "Focused VST Parameter Control":
https://www.mutools.com/info/M9/docs/mu ... ugins.html

"At the top of each VST editor, at the right of the Open/Save and Options buttons, there is a parameter knob that reflects the last tweaked VST parameter. Whenever you tweak a VST parameter that focused parameter control switches to that last tweaked parameter. This focused parameter control is a handy bridge between any VST parameter and the MuTools user interface. For example you can easily drag-drop the name of that focused parameter control onto the [+] track button to create an automation track, or to insert a point for that parameter value into an automation envelope editor, etc. You can also right-click the focused parameter control for handy functions like Copy As Parameter Event, Copy As Envelope Point, Map MIDI Controller, etc. It can also be used to monitor the value of VST parameters for VST's that don't show this in their own editor. It can also be used to copy-paste VST parameter values even in VST editors that don't support such functionality. Etc."

[cpssounds]

Oh, man, thank YOU, that was the missing link!!! Drag and drop works perfectly!!!
Now it works

Many many thanks!!!

For that other stuff you mentioned, I have to dive further into, but this as for starters helps alot...

Best

[robert_p]

Oh, man, thank YOU, that was the missing link!!!
Now it works

Many many thanks!!!

Best

Have a good fun and don't forget to spread the word about this amazing plugin.

[cpssounds]

Already did and doing! Thanks

[robert_p]

Would it be possible for them to reproduce this case with demo version of MuLab plugin?

Yes.

Or maybe you'll be able to provide them with the full version of your software for compatibility testing purpose?

Sure, they can contact me via

Unify has been updated to ver.1.9.1 with new "host sync option" - that fixed my problems with synchronizing the transport in "stop" mode. Everything works great now, thanks again for providing your app to Unify developer. Both applications are fully compatible now!

[Jason_ZA]

Awesome news that Unify is now fully compatible with MuTools. Thanks @robert_p and @mutools for arranging/implementing this!

[MuTools]

MuLab App 9.0.56 is available in https://www.mutools.com/mulab/app/latest-binary

MuLab Plugin 9.0.56 is available in https://www.mutools.com/mulab/plugin/latest-binary

What's changed:

• Upon opening the Color Picker, the Saturation and Luminance sliders could be in an unexpected state. Fixed.
• MuLab Plugin: Start playing the host will now also start playing the Live Matrix if that's the composer section that you're focused on. (ie. last mouse click)
• Sample -> Save As -> Save as ogg file created a wrong ogg file with only a small loop. Fixed.
• MUX Front Panels: Picture background did not work anymore. Fixed.
• Envelope engine: In specific and rather exceptional cases envelopes were not rendered right. Fixed.
• When GUI Scale was not 100% then clicking connections in the modular area did not properly work, there was an offset. Fixed.

This M9.0.56 update is for Windows. The respective Mac update will follow soonish.

This M9.0.56 update also includes further code base developments towards an extended plugin system. This should not yet make any practical difference wrt the supported VST 2 plugins, but under the hood the extended plugin system is growing. If you would notice any issues with using VST 2 plugins, issues that were not there in M9.0.55, please let me know! Thx.

[robert_p]

[*]MuLab Plugin: Start playing the host will now also start playing the Live Matrix if that's the composer section that you're focused on. (ie. last mouse click)

Thank you!

[syntonica]

This M9.0.56 update also includes further code base developments towards an extended plugin system.

[xbitz]

hi, I've wrapped a Parameter Event Generator into MUX modular instance and it is still able to modify its original target (even after MUX duplications from multiple MUX instances) but its target can't be changed anymore and shows an empty list

so seems a Parameter Event Generator can't see out from a MUX modular instance but would be nice if it would able to do it ... otherwise dunno how I would create reusable components, so not sure if it's a bug or something but works strangely at this moment so reported it (MUX 9.037 64bit)

[MuTools]

Indeed a Parameter Event Generator can't see outside its parent.
I understand you want to make reusable blocks and in that contaxt, as a draft thought, i would convert it to MIDI CC as that's module independent, and only convert it back to a concrete module parameter in the target context.

[MuTools]

MuLab App 9.0.57 is available in https://www.mutools.com/mulab/app/latest-binary

MuLab Plugin 9.0.57 is available in https://www.mutools.com/mulab/plugin/latest-binary

This update fixes a recent new bug in the plugin system that caused an error alert upon quit when using multiple instances of the same plugin.

This M9.0.57 update is for Windows. The respective Mac update will follow soonish.