MuLab 9.0.59 App + Plugin
-
- KVRist
- 118 posts since 20 Feb, 2013
I would, as a Mac user, also like to help to make the beta better. But of course I'm waiting patiently and respecting the hard work of Jo, which does not allow to present a Mac version now.
-
- KVRist
- 41 posts since 19 Sep, 2021
mutools wrote: Sat Jan 08, 2022 9:57 am MuLab 9 Plugin for Windows pre-beta is getting close so you will soon be able to check it out and see if all these pro points are still true, and maybe even better.
-
- KVRAF
- Topic Starter
- 13854 posts since 24 Jun, 2008 from Europe
M9.0.16 is available.
Including MuLab 9 Plugin.
@Beta test users: Please download & install the complete new M9.0.16 zip package and use the new user key provided.
See the change log for what's new in M9.0.16 and for brief info on M9 Plugin.
All for Windows only for now, for practical reasons.
Apologies to Mac users who are eager to also test & play MuLab 9.
Including MuLab 9 Plugin.
@Beta test users: Please download & install the complete new M9.0.16 zip package and use the new user key provided.
See the change log for what's new in M9.0.16 and for brief info on M9 Plugin.
All for Windows only for now, for practical reasons.
Apologies to Mac users who are eager to also test & play MuLab 9.
-
- KVRist
- 97 posts since 1 Feb, 2021
9.0.16 is working here on both Bitwig 4.1.2 and Reaper 6.45. I would characterize CPU usage as very low, though I'm not exactly loading up the DAWs: 2 tracks played simultaneously, each with a different Mu synth and one different Mu effect.
I know reporting bugs is more useful than 'works well' so I'll get back to trying to break it.
I know reporting bugs is more useful than 'works well' so I'll get back to trying to break it.
-
- KVRAF
- 7411 posts since 8 Feb, 2003 from London, UK
At this point I can probably start to spend some time playing... err, I mean testing.
I've a very large MUX-based project that "idle" uses quite a bit of CPU, so it'll be a good comparison on the front. It'll also test loading MUX 8.x patches into MuLab 9.0.x - so I'll have to make sure I'm keeping the test project separate from the working one.
I've a very large MUX-based project that "idle" uses quite a bit of CPU, so it'll be a good comparison on the front. It'll also test loading MUX 8.x patches into MuLab 9.0.x - so I'll have to make sure I'm keeping the test project separate from the working one.
-
- KVRAF
- Topic Starter
- 13854 posts since 24 Jun, 2008 from Europe
Did you receive the M9 beta email?HarmonicD wrote: Tue Jan 11, 2022 7:03 am hey Jo!
I can't find the old mail
I've sent a new mail, please send me the new beta
-
- KVRAF
- Topic Starter
- 13854 posts since 24 Jun, 2008 from Europe
It's quite straightforward: MuLab 9 Plugin looks the same as MuLab 9 App.wibem wrote: Tue Jan 11, 2022 11:23 am Can anybody post some screenshots or a video to see how Mulab 9 is doing as a plugin? Can't wait to see it in action.
-
- KVRist
- 118 posts since 20 Feb, 2013
Ah, thanks. But how does it interact with the DAW, in which it is used as a plugin? I can't really imagine it. E.g Mulab can have a lot of instruments playing together. How does the output get into the outside DAW? Just as one audio signal on one channel ? Are they playing in sync? What about Midi signals? Is Mulab as Vst sending midi data? How about the exchange of data between the inner and outer DAW? Does it work with drag'n drop or doesn't it work at all?
Last edited by wibem on Tue Jan 11, 2022 12:43 pm, edited 1 time in total.
-
- KVRian
- 1125 posts since 30 Oct, 2013 from Scarborough
Trying out mulab9 plugin 64bit in Bitwig Studio 4.0.7
First impression - looking and sounding great! No problems loading, editing and playing presets via the preset front panel.
The 'show modular area button on the front panel opens up the modular area in a new window, but a second press of the button does not close the new window (just an observation - can close the window in the usual way)
If I then click the 'show front panel' in this new window the front panel is displayed in that window, and disappears from the original window. If I go back to the original window and slightly resize it the front panel reappears there, and disappears from the new window. (again not a problem - but unexpected)
The browser panel: If I click on a preset in the library I can preview the sound if I immediately press a key on my midi keyboard, but it cuts off after about 1 second. No sound after that unless I click a different preset - with the same result. Also I cannot get any further sound out of that instance except by clicking a different preset and again immediately trying a midi key. Dragging the preset onto the front panel loads it - but still no sound from that instance.
Tried same in Tracktion Waveform 10 - the preview does not cut off after 1 second here, but still loading a preset this way does not return the focus to the mux front panel - so no sound except via the browser preview.
Again in cubase 7.5 (I know its old - but I am NOT upgrading to any later version) similar result as with Tracktion Waveform - no sound for the loaded patch after once using the browser to load.
UPDATE: If I go into the 'project modular area' and then click on the main module, i.e. the one into which the VST MIDI Input cable is attached, the patch will then sound as normal - until I go back to the browser when the same issue will start again. Note that the module may appear highlighted, but still need to click on something else first and then the main module to re-highlight it before any sound happens.
First impression - looking and sounding great! No problems loading, editing and playing presets via the preset front panel.
The 'show modular area button on the front panel opens up the modular area in a new window, but a second press of the button does not close the new window (just an observation - can close the window in the usual way)
If I then click the 'show front panel' in this new window the front panel is displayed in that window, and disappears from the original window. If I go back to the original window and slightly resize it the front panel reappears there, and disappears from the new window. (again not a problem - but unexpected)
The browser panel: If I click on a preset in the library I can preview the sound if I immediately press a key on my midi keyboard, but it cuts off after about 1 second. No sound after that unless I click a different preset - with the same result. Also I cannot get any further sound out of that instance except by clicking a different preset and again immediately trying a midi key. Dragging the preset onto the front panel loads it - but still no sound from that instance.
Tried same in Tracktion Waveform 10 - the preview does not cut off after 1 second here, but still loading a preset this way does not return the focus to the mux front panel - so no sound except via the browser preview.
Again in cubase 7.5 (I know its old - but I am NOT upgrading to any later version) similar result as with Tracktion Waveform - no sound for the loaded patch after once using the browser to load.
UPDATE: If I go into the 'project modular area' and then click on the main module, i.e. the one into which the VST MIDI Input cable is attached, the patch will then sound as normal - until I go back to the browser when the same issue will start again. Note that the module may appear highlighted, but still need to click on something else first and then the main module to re-highlight it before any sound happens.
https://rjsemper.wixsite.com/website
One Synth Challenge - https://sites.google.com/site/kvrosc/about
One Synth Challenge - https://sites.google.com/site/kvrosc/about
-
- KVRist
- 141 posts since 18 Apr, 2021
-
- KVRAF
- 7411 posts since 8 Feb, 2003 from London, UK
Did you ever use MUX? Using the Modular view?wibem wrote: Tue Jan 11, 2022 12:42 pm Ah, thanks. But how does it interact with the DAW, in which it is used as a plugin? I can't really imagine it. E.g Mulab can have a lot of instruments playing together. How does the output get into the outside DAW? Just as one audio signal on one channel ? Are they playing in sync? What about Midi signals? Is Mulab as Vst sending midi data? How about the exchange of data between the inner and outer DAW? Does it work with drag'n drop or doesn't it work at all?
Did you ever use MuLab? Using the Modular view?
Well, if you ignore the "not modular" view of Mux and MuLab in version 8, you'll see that the Modular view is... the same, right?
So you plug that modular view into your host as a VST. One of the modules is a composer module with "sync" options to the host. In the same way you need to have hardware audio/MIDI ins/outs for the Standalone MuLab, you need to have plugin audio/MIDI ins/outs for the VST MuLab. And that's about it.
-
- KVRist
- 141 posts since 18 Apr, 2021
First of all, Jo, thank you so much for creating this awesome software and for keeping the workflow of Mux! I loveeee it and it looks great!
Few things that I notice on the first use (let me know if I'm just missing something) :
1. The parameters in the main parent window are not controlable / automatable from Reaper(?)
2. Automation doesn't seem to work (using Reaper as a host).
3. Undo option for duplicating modules (currently I don't see undo state after duplicating modules)
4. Copying modules with ability to keep the routings to the copied modules will be sweet. (possible already?)
5. "New Mux from selection" this option should be from drop down list when right clicking on a selected module and not just in an empty area (imho it will be more intuative, because this is what I first tried)
6. In the list panel, it will be nice if we could "tick" what we want to see, so we could see more folders at the same time, like folders: VST synths, VST effects, MUX Presets (as folders that can fully collapse), for a quicker workflow.
Best regards
Few things that I notice on the first use (let me know if I'm just missing something) :
1. The parameters in the main parent window are not controlable / automatable from Reaper(?)
2. Automation doesn't seem to work (using Reaper as a host).
3. Undo option for duplicating modules (currently I don't see undo state after duplicating modules)
4. Copying modules with ability to keep the routings to the copied modules will be sweet. (possible already?)
5. "New Mux from selection" this option should be from drop down list when right clicking on a selected module and not just in an empty area (imho it will be more intuative, because this is what I first tried)
6. In the list panel, it will be nice if we could "tick" what we want to see, so we could see more folders at the same time, like folders: VST synths, VST effects, MUX Presets (as folders that can fully collapse), for a quicker workflow.
Best regards