MuLab 9.0.59 App + Plugin

[humanboeing]

Expanding tracks' size no longer works properly, while using a mouse wheel to enlarge all tracks the view jumps to the tracks on top, and not the track under the cursor, visible with many tracks.

As far as i see the only case where this happens if when the total track height is smaller than the available track space. As soon as the total track height is greater than the available track space then zooming in on a track keeps the same track mouse-centered. All the same as in M8. Right?

Nope, I'm working on a project with 13 tracks, they are maximally squeezed and with 100% gui scale they take about half of the available space (with rack desk visible). I can expand them so that the entire space is filled and even beyond, at this point when I expand it even further the zoom is not on the track under the cursor but jumps to the top.

[humanboeing]

I emptied the project from vsts and personal audio in order to zip it and share it here and the tracks started zooming fine, maybe this helps (fine, that is, as soon as the available track space is filled).

[humanboeing]

Attention: Due to some initial research works on CLAP, there already are some internal changes in the plugin system. If you notice anything odd wrt using VST2 plugins please let me know.

I think this may have some connections to these changes because I can zoom on tracks from demo songs without problems, which are free of plugins.

[Kalamata Kid]

I just purchased the Mulab Plugin.
Can I get and use the M8 Mux with my current key?

BTW I love how to "install Mulab"
From M9 Docs:

Download the MuLab Plugin zip package and unzip it to a new folder.
Then move the resulting folder into your preferred VST plugins folder.
Please make sure that the complete folder path towards the MuLab Plugin folder does not contain any special characters, except for plus, minus (hyphen), underscore, round brackets and square brackets.

MuLab Plugin comes as a self-containing folder.
It does not install anything on your system outside this folder.
You can move the MuLab Plugin folder after you have installed it.
You can even put it on a USB stick and carry your MuLab Plugin with you.
Of course it also depends on the host DAW application if that is also that flexible.

[humanboeing]

New note velocity does not affect new samples dragged into an audio sequence.

[pljones]

Can I get and use the M8 Mux with my current key?

There are legacy downloads on the site. https://www.mutools.com/mulab-plugin-downloads.html near the bottom of the page.

[Kalamata Kid]

So the legacy are free or my M9 key will work?

[humanboeing]

So the legacy are free or my M9 key will work?

I don't think M9 keys work with older Mulab versions but there's no reason to because M9 is vastly superior

[heks]

So the legacy are free or my M9 key will work?

I don't think M9 keys work with older Mulab versions but there's no reason to because M9 is vastly superior

Might be needed if someone hasnt bought the last version (M8) of Mulab and is for instance going from M6 to M9. I wish there was a batch converter/updater.

[MuTools]

Attention: Due to some initial research works on CLAP, there already are some internal changes in the plugin system. If you notice anything odd wrt using VST2 plugins please let me know.

I think this may have some connections to these changes because I can zoom on tracks from demo songs without problems, which are free of plugins.

It's certainly not VST related, but i now can repeat some issue wrt zooming tracks. Taken note to research & fix that. (might be a bit later) Thx for reporting this

[MuTools]

New note velocity does not affect new samples dragged into an audio sequence.

True. But when creating an audio sequence from a dropped sample all slices have max velocity too so that the playback level is the same as the original sample. When newly drawn notes would get another velocity that might be unwanted / unexpected behavior. Or should a new audio sequence from dropped sample also take that New Note Velocity preference into account? If yes dropped samples will by default play softer than the original, which might be unexpected / unwanted. Not sure what the best choice is here. What do you think?

[MuTools]

So the legacy are free

No.

or my M9 key will work?

No.
You need a M8 user key to use M8.
If you have a M9 user key and need an M8 user key to upgrade your pre M8 projects / presets, request it via an email to

[MuTools]

I wish there was a batch converter/updater.

There is: See MULAB menu -> Tools -> Upgrade ...

[humanboeing]

New note velocity does not affect new samples dragged into an audio sequence.

True. But when creating an audio sequence from a dropped sample all slices have max velocity too so that the playback level is the same as the original sample. When newly drawn notes would get another velocity that might be unwanted / unexpected behavior. Or should a new audio sequence from dropped sample also take that New Note Velocity preference into account? If yes dropped samples will by default play softer than the original, which might be unexpected / unwanted. Not sure what the best choice is here. What do you think?

I didn't consider these specific use cases, I think it's fine as is, maybe other users might have better ideas.

[robert_p]

When newly drawn notes would get another velocity that might be unwanted / unexpected behavior. (...) Not sure what the best choice is here. What do you think?

Good point, my vote is to leave it as it is.

P.S. The MuLab's time stretching algorithm (audio sequence) is absolutely phenomenal - I compared it with Studio One (considered by some as "good"), but MuLab takes it to completely new level in terms of sound quality.