MuLab 9.0.59 App + Plugin
-
- KVRian
- 1056 posts since 17 Jan, 2005 from London
Hello Jo! I've been keeping an occasional eye open about your beta program, but I'm unclear what the state of play is for macOS users. Is a beta available yet, and if so, will it work with macOS 12.01 Monterey?
Bitwig 6.0 beta 12 + Akai MIDIMix + Launchpad X + MF Twister
ExpressiveE Osmose Keyboard + Universal Audio Apollo Twin X
Mac Mini M1 16GB/4TB + macOS 26.2 Tahoe
ExpressiveE Osmose Keyboard + Universal Audio Apollo Twin X
Mac Mini M1 16GB/4TB + macOS 26.2 Tahoe
-
- KVRist
- 149 posts since 31 Mar, 2017 from New Caledonia
A thing I noticed: The tempo in the main app and the tempo in the "project modular area" have a sort of parent-child relation.
Changing tempo in the main window only affect current composer in the project, changing tempo in the "project modular area" (top left corner) affect the composer in a relative way.
ex: tempo set at 120 in "project modular area" and 160 in the composer, when you move the composer tempo, the one in the "project modular area stay at 120. Moving the tempo in the "project modular" area also move the tempo of the composer in relative percent. This is not a bug for me, as I think this could be useful when Mulab will be used as VST, to have it synced with the host and still having it's own composer tempo. I notice this for those who want to use tempo-related modules in the "project modular area". A step sequencer in this case will follow the modular area tempo, not the composer tempo.
Changing tempo in the main window only affect current composer in the project, changing tempo in the "project modular area" (top left corner) affect the composer in a relative way.
ex: tempo set at 120 in "project modular area" and 160 in the composer, when you move the composer tempo, the one in the "project modular area stay at 120. Moving the tempo in the "project modular" area also move the tempo of the composer in relative percent. This is not a bug for me, as I think this could be useful when Mulab will be used as VST, to have it synced with the host and still having it's own composer tempo. I notice this for those who want to use tempo-related modules in the "project modular area". A step sequencer in this case will follow the modular area tempo, not the composer tempo.
-
- KVRist
- 434 posts since 17 Nov, 2020
I'm not sure if this is intentional or not but tracks without a target module cannot be coloured.
-
- KVRAF
- Topic Starter
- 13852 posts since 24 Jun, 2008 from Europe
A track indeed is colored by its target module.
What's the purpose of a track without target module?
What's the purpose of a track without target module?
-
- KVRAF
- Topic Starter
- 13852 posts since 24 Jun, 2008 from Europe
Not yet available, but getting closer. May be in about a week.carlca wrote: Thu Dec 09, 2021 8:07 pm Hello Jo! I've been keeping an occasional eye open about your beta program, but I'm unclear what the state of play is for macOS users. Is a beta available yet, and if so, will it work with macOS 12.01 Monterey?
-
- KVRAF
- Topic Starter
- 13852 posts since 24 Jun, 2008 from Europe
That's indeed how it works.skarabee wrote: Thu Dec 09, 2021 11:36 pm A thing I noticed: The tempo in the main app and the tempo in the "project modular area" have a sort of parent-child relation.
Changing tempo in the main window only affect current composer in the project, changing tempo in the "project modular area" (top left corner) affect the composer in a relative way.
ex: tempo set at 120 in "project modular area" and 160 in the composer, when you move the composer tempo, the one in the "project modular area stay at 120. Moving the tempo in the "project modular" area also move the tempo of the composer in relative percent.
Exactlythis could be useful when Mulab will be used as VST, to have it synced with the host and still having it's own composer tempo.
When the step sequencer is inside a composer, it will sync to that composer, which syncs to its master tempo.I notice this for those who want to use tempo-related modules in the "project modular area". A step sequencer in this case will follow the modular area tempo, not the composer tempo.
-
- KVRAF
- Topic Starter
- 13852 posts since 24 Jun, 2008 from Europe
-
- KVRist
- 434 posts since 17 Nov, 2020
M9.0.6 - 4p lowpass, multimode and chebyshev filters are not displayed properly in provided frequency spectrum.
-
- KVRist
- 434 posts since 17 Nov, 2020
That bar which appears after hiding a device is a fantastic idea, I'm already loving it
-
- KVRist
- 434 posts since 17 Nov, 2020
Ah it already was a feature! Completely missed it, nevermind.
-
- KVRAF
- Topic Starter
- 13852 posts since 24 Jun, 2008 from Europe
A new bug caused by fixing a previous bughumanboeing wrote: Fri Dec 10, 2021 6:19 pm M9.0.6 - 4p lowpass, multimode and chebyshev filters are not displayed properly in provided frequency spectrum.
Fixed in M9.0.8 which is available now.
Thanks for reporting this
-
- KVRer
- 8 posts since 11 Dec, 2021
How to get mutools mulab 9 version?Is it already available on your web site ?
-
- KVRist
- 434 posts since 17 Nov, 2020
Mulab 9 is in pre-beta test stage an is available for registered Mulab users, if you are one you can send a request to infodesk@mutools.comMutoolsuser wrote: Sat Dec 11, 2021 3:46 am How to get mutools mulab 9 version?Is it already available on your web site ?
-
- KVRist
- 434 posts since 17 Nov, 2020
Feedback in factory preset "phased delay" does not work.
-
- KVRist
- 434 posts since 17 Nov, 2020
Actually most echo presets with feedback sound off compared to Mux 8, there is some feedback issue.