MuLab 10.2.29 beta

[MuTools]

MuLab App M10.2.5 beta for Windows 64 bit is available:
https://www.mutools.com/mulab/app/lates ... /beta.html

What's changed:

• Improved VST3 support: When a VST3 processor outputs parameter events, these are now properly forwarded to the VST3's editor, as it should.
  Some VST3s rely on this mecanism for showing level meters etc.
• Support for dropping a VST3 plugin folder on a slot, i.e. a "SomePlugin.vst3" folder which includes the actual .vst3 DLL file aside of other related files. Previously MuLab scanned it as a folder and added the plugin to the database, but did not insert that plugin into the target slot. Now it does.
• Plugin Manager now has explicit "Done" button.
• When moving a sequence clip while there is an Event List Editor for that clip, the displayed event times now are properly updated taking the new clip start time into account.
• Instant typing in a numeric value (added in M10.2.4) has been further optimized: Pressing Enter/Return will instantly accept the typed value without further delay.
• Other small improvements.

[pekbro]

Seems like that parameter thing was a problem with the PSPaudioware stuff. Nice!

[MuTools]

Seems like that parameter thing was a problem with the PSPaudioware stuff. Nice!

So what difference do you notice when using PSPA in M10.2.4 and M10.2.5?

I still encounter the "left output only" issue with PSPA in M10.2.5.

[pekbro]

Seems like that parameter thing was a problem with the PSPaudioware stuff. Nice!

So what difference do you notice when using PSPA in M10.2.4 and M10.2.5?

I still encounter the "left output only" issue with PSPA in M10.2.5.

Yea I get that as well, it’s like it’s stuck in mid/side. Setting width to zero gives 2 even channels. Their plugins that don't mess with the channels or stereo field seem to work as designed. Unfortunately, the bulk of their plugins do that one way or another.

Anyway, the fix changes the meter and visualizer display. Now visible, where they weren’t before. I’d post a before and after, but I don’t have the old version of MuLab anymore. I overwrite with every update without testing heh.

[MuTools]

MuLab App M10.2.6 beta for Windows 64 bit is available:
https://www.mutools.com/mulab/app/lates ... /beta.html

What's changed:

• Upgraded to the latest VST3.8.0 SDK.
• Module info window now includes parameter count.
• Note On Upon Note Off: Parameter events were not properly processed. Fixed.
• Test Sine Generator now has an event input for receiving parameter events, eg. from an automation clip, from a MUX Meta-Parameter, from a source module, ...

[tiger001]

even adding smart snippets (10-15s samples) takes its time
be that as audio sequence, audio stream, sample player
samples are stereo, 24b, 96khz

another note:
generic, loop, playback markers from WaveLab (11) are neatly transferred (as ordinary markers) in audio sequences, pitched samples but not in audio streams
markers are not automatically filled in in the sample player but can be chosen from a drop down list (snap to nearest marker doesn't seems to work when you are already positioned on a marker)
-when browsing with the arrow keys in the loop , the ruler (positioning line) doesn't seem to be updated, you can see the | jump through all the markers in the file but a bit difficult when you don't see a (marker) number nor a ruler in the view but only a | (this works in start/end position box)

adding marked (in WL) samples to a multi sample uses the (generic, loop or playback) markers as slice information and consequently places the different marked in different zones in the multi sampla - this is very neat!
one thing though: if there's markers for start & end that are not sequentially (so e.g. with space between marker 4 and marker 5), that space is used/translated as another slice while it really shouldn't

2026-02-15 12_26_58-FBF010.jpg

i whish i could select more than one track (left most ruler in the composer) so i could scale multiple tracks in 1 go
but whatever key combination i try, i cannot select >1 track (or rack for that matter) - nor lasso them

[tiger001]

another issue(thingy)

why is there a mulab.wave resampled file left in the original folder?
-especially when i had them (the original samples) copied over to the project folder
-especially because these are quite big files

2026-02-15 12_49_38-I__FBF=ENG.jpg

[MuTools]

even adding smart snippets (10-15s samples) takes its time
be that as audio sequence, audio stream, sample player
samples are stereo, 24b, 96khz

Please give a concrete example. Share the sample and add the time it takes to import it on your system.

when browsing with the arrow keys in the loop , the ruler (positioning line) doesn't seem to be updated, you can see the | jump through all the markers in the file but a bit difficult when you don't see a (marker) number nor a ruler in the view but only a | (this works in start/end position box)

I don't understand what you mean.
Please explain this more visually.

[MuTools]

why is there a mulab.wave resampled file left in the original folder?

When streaming an audio file with a different samplerate than the current audio engine's samplerate, MuLab resamples that audio file to a temporary audio file. That's the file you see.

[tiger001]

i agree that you need to resample etc but why is this file present on the original file location AND also in the project folder? (once you bring those files/samples/project self-contained)

that's bloat

[tiger001]

when browsing with the arrow keys in the loop , the ruler (positioning line) doesn't seem to be updated, you can see the | jump through all the markers in the file but a bit difficult when you don't see a (marker) number nor a ruler in the view but only a | (this works in start/end position box)

I don't understand what you mean.
Please explain this more visually.

here you go
you see me browsing start position first, then loop position in the sample player
first the ruler positions itself in the waveform display, second use not

ML10_SamplePlayer_Browse.gif

[MuTools]

In your example the loop is not enabled.
Enable the loop by clicking the loop toggle button at the right side of that loop position field.

[tiger001]

ah yeah!
that works
thanks

[MuTools]

Just to make sure you know: That loop button has different states:

• Loop Off
• Forward Loop
• Backward Loop
• Alternating Loop

[pekbro]

So my midi devices are not working as they used to, is it possible this has anything to do with the new midi services in win 11? Just trying to track the problem down, it's possible that I have not used some of the HW since before the midi services rollout.

Sending the clock out from mulab to the device no longer works for example.
I have verified that the new service is installed and working on this machine,
it was done with no involvement from me no less.

thx