MuLab 9.0.59 App + Plugin

[plutonia]

M9.0.10 is available.

using latest beta version audio recording and then "convert to audio sequence" as you suggested earlier now works fine!

no odd fade/echo on clips longer than 5 bars

[shorty]

Hi,

I'm trying to send midi data to an external synth. In version 8 it works
(https://www.mutools.com/info/M8/docs/mu ... utput.html), but in the beta I can't drop the project event output on a track.

Did something change with using external gear in version 9? How do I make the connections to external gear?

Thanks in advance

[Jonathan Shepherd]

Sorry if this has been answered but is the note action map going to remain in a separate window or will it be added as a sort of track in the composer or other? Just curious, I'm fine any which way you go.

[MuTools]

I'm trying to send midi data to an external synth. In version 8 it works
(https://www.mutools.com/info/M8/docs/mu ... utput.html), but in the beta I can't drop the project event output on a track.

Did something change with using external gear in version 9? How do I make the connections to external gear?

Good point!
Yes the M9 architecture differs from M8's.
I've taken note, will check this, and will get back on this.
Thanks for questioning this

[MuTools]

Sorry if this has been answered but is the note action map going to remain in a separate window or will it be added as a sort of track in the composer or other? Just curious, I'm fine any which way you go.

Yes the Note Action Map is a separate editor. It will not be possible to send Note Actions to the composer it belongs to.

Note however that it is possible to use a meta composer to sequence the time line note actions of a nested composer. So you can make a full song in composer X and define relevant time line note actions for it (in composer X's Note Action Map), then put composer X inside composer Y and make a track in composer Y that plays the different sections in nested composer X.
And if you want you can even use a composer X1, composer X2 and composer X3 inside composer Y.

[humanboeing]

Little visual bug: when a new point in lfo's wave shape editor is made or deleted, the lfo module does not update the current state, it only does after dragging a point.

[MuTools]

Little visual bug: when a new point in lfo's wave shape editor is made or deleted, the lfo module does not update the current state, it only does after dragging a point.

Will be fixed in M9.0.11.
Thanks

[Jonathan Shepherd]

Doh! Thanks Jo. Sometimes I need a reminder that Mulab is the modular of modulars. Good day-

[humanboeing]

(edit)

Shouldn't the part transpose function in the item properties panel affect all linked parts?

[humanboeing]

Shouldn't the part transpose function in the item properties panel affect all linked parts?

[MuTools]

Shouldn't the part transpose function in the item properties panel affect all linked parts?

You mean that it should affect all parts playing the same sequence?
Then the answer is no. It really is a part parameter, not a sequence parameter.
Which is an advantage as then you can have several 'ghost' parts playing the same sequence but with a different transpose. If you want to transpose all parts playing a certain sequence then transpose the sequence and all parts will play that same transposed sequence.

[carlca]

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?

Not yet available, but getting closer. May be in about a week.

I'm not trying to push you (that's exactly what I'm doing ) but how's it looking for us Mac users?

[MuTools]

Thanks for checking.

Last week i have been busy with an unforeseen challenge: It's about the Envelopes and LFOs, cfr this topic: viewtopic.php?f=79&t=574657

M9.0.10 featured an important improvement regarding the quality of envelopes and LFOs, especially when they have sharp shapes and/or high rates, but it turned out to have a bit too much impact on the CPU consumption to be acceptable. So last week i had a tough time optimizing the performance of the envelopes and LFOs while preserving that improved sound quality. Technically: From the next update on M9 automatically switches to audio rate rendering of envelopes and LFOs where necessary but does more cpu-friendly rendering of envelopes and LFOs where it doesn't affect sound quality. For example a sine wave LFO below say 10 Hz really does not need audio rate rendering, but a sharp exponential decay (eg for pitch/filter modulation) must be sample accurate. That optimized choice is made automatically, transparant to the user. That's all ready now in the next M9.0.11 update. So that took an unforeseen extra week, but the good thing is that we have nicely improved envelopes and LFOs, which is an extra highlight for M9.

Working full speed on reaching the point where also MuLab 9 for Mac and MuLab 9 Plug-In can be shared. Still a handful of items on the todo before that point.

[heks]

Just wondering Jo, is vst3 compatibility planned to be in the first Mulab 9 release or will it be added as a 9.0+ increment after release? Sorry to ask, but from a selfish point of view its my main "want" for Mulab 9
I hope your planning some down time at Christmas Jo, to recharge your "batteries " and I hope you and everyone here has a really good Christmas

[MuTools]

Just wondering Jo, is vst3 compatibility planned to be in the first Mulab 9 release or will it be added as a 9.0+ increment after release? Sorry to ask, but from a selfish point of view its my main "want" for Mulab 9

I'm thinking quite a lot about that Vst3 situation. I understand the need from user point of view, Steinberg has played that well by unnecessarily murdering Vst2. Technically however Vst3 is an ugly monster. And Steinberg also has damaged trust by forcing ( ) devs towards Vst3. So what if they come up with some Vst456 and say all devs Have To Obey to Vst456? That's not compatible with my view on things. So that's why i'm very happy to see this: viewtopic.php?p=8296134#p829613
We, the music software world, really need something like Clap, and i will surely have a deeper look at it. Does this mean i have decided not to do Vst3? No. It's still undecided atm. And the issue is not finding the dev time, the issue is on a higher level, as described above.