MuLab 9.0.59 App + Plugin

[wibem1]

Here is the console log, when trying to open Mulab vst in Reaper.

[MuTools]

Thanks for the console log.
Gentle request: Next time you send such log please provide it as plain unformatted text. Putting it in a zip is ok, but plain text please. Thanks.

About the M9 Plugin issue: Are you sure you have installed the complete M9 plugin package in a fresh new sub-folder in Library/Audio/Plug-Ins/VST? Thus for example into Library/Audio/Plug-Ins/VST/MuTools/MuLab 9 Plugin

After having extracted the complete M9 zip package into that folder it should contain the 2 .vst files (M9 Synth and M9 Effect) and a sub-folder named "App" and a sub-folder named "User", and the quarantine remover files. Right?

[wibem1]

Indeed, I hadn't installed the whole plugin folder, just the plugins. After putting the whole Mulab vst folder into the vst-folder, it works. Thanks. But it is a restricted demo-version. Can I get a M9 key as a M8 user (MUX and Mulab) , who had upgraded to M8 with a free upgrade to M9.

[MuTools]

Indeed, I hadn't installed the whole plugin folder, just the plugins. After putting the whole Mulab vst folder into the vst-folder, it works.

But it is a restricted demo-version. Can I get a M9 key as a M8 user (MUX and Mulab) , who had upgraded to M8 with a free upgrade to M9.

Please see the email with beta info, it contains a beta test user key.
If you can't find it anymore email your request to mutools' infodesk.

[wibem1]

No, the user key in my email was only for the Mulab standalone. There was no beta test user key for the vst in my email.

[carlca]

No, the user key in my email was only for the Mulab standalone. There was no beta test user key for the vst in my email.

I have the same problem. If I try to activate using the v9 code, I get this message...

Screenshot 2022-02-11 at 13.40.43.png

[MuTools]

Maybe i did not yet include a MuLab 9 Plugin beta test user key to Mac users as M9 Plugin for Mac was not yet available at that time.

For the M9 Plugin beta test user key email MuTools' Infodesk.

[carlca]

For the M9 Plugin beta test user key email MuTools' Infodesk.

Email incoming

[carlca]

For the M9 Plugin beta test user key email MuTools' Infodesk.

Email incoming

All sorted now. Thanks Jo

[MuTools]

Curious for your thoughts & feelings on M9 Plugin.

[wibem1]

I ty to send midi data from the M9 plugin to the host (Reaper) , but it doesn't work (at least as I expect it). Reaper doesn't receive any midi events.
For that I use the modul vst midi output like in the screenshot. What am I doing wrong?

[wibem]

I'm quite impressed by the Mulab plugin, but it's a bit confusing that it works quite differently than the Mulab standalone. Because the composer is just a module, there is no access to the internal browser inside the composer. To work properly with the composer you often have to switch from composer view to the module view, which is a bit complicated, because you have three windows on the desktop. One for the daw, one for the composer view and one for the module view.

[MuTools]

I ty to send midi data from the M9 plugin to the host (Reaper) , but it doesn't work (at least as I expect it). Reaper doesn't receive any midi events.
For that I use the modul vst midi output like in the screenshot. What am I doing wrong?

Check with a Event Monitor that the events are indeed streaming to the event output. Then if you're sure about that i think you might have to check how the event stream continues in Reaper but that's a Reaper question.

[MuTools]

I'm quite impressed by the Mulab plugin, but it's a bit confusing that it works quite differently than the Mulab standalone.

I think there is little difference between MuLab App and MuLab Plugin.

Because the composer is just a module, there is no access to the internal browser inside the composer.

The browser is part of the project, not of the composer. The composer is just a module, like an oscillator or a filter. That's the same in MuLab App and MuLab Plugin.

To work properly with the composer you often have to switch from composer view to the module view, which is a bit complicated, because you have three windows on the desktop. One for the daw, one for the composer view and one for the module view.

You don't "have to" use the modular view. You only need it if you want it.
Question: Could it be that you have inserted a composer module manually into a new project? Did you make it the project's "Main Module" ? Right-click the composer -> Set As Main Module.

Indicating a "Main Module" is important because it defines the kind of project you want to use: A composer, a synth, an effect, ... (hybrid options possible, but lets keep it simple for now)
It is the Main Module that will be embedded into the project editor window. That's all the same in MuLab App and MuLab Plugin.

[carlca]

Curious for your thoughts & feelings on M9 Plugin.

I'm having great fun using the Step Sequencer device within the plugin device to drive Bitwig instruments. It's so easy to duplicate a track to achieve parallel sequences. I also appreciate the fact that the plugin encourages you to explore the build in synth sounds within MuLab. There is so much to explore, but I love the fact that the workflow feel fits so well with Bitwig.