MuLab 10.0.85

[MuTools]

why is the wet/dry balance of Chaoszilator expressed in ms and not in percentage or plain numbers?

In fact you could check the reason yourself: Open the modular area, doubleclick the relevant meta-parameter to see what's it mapped to. Indeed it's mapped to a delay time. That's unexpected indeed, don't know why the person who created that preset did it that way. Looks like a design bug, will fix that.

[tiger001]

thx for this/these

why aren't all the audio stream overviews loaded upon start when the audio stream is not into (the initial) view ?
now when i scroll to the top (or bottom) of my project, i have to wait (again) for the audio overview to built
-it would be nicer if all audio overview(s) are loaded upon startup

samples are not cleared from the manage audio/sample objects in project (ram) if i used a (multi) sampler and later deleted that track and rack

2025-06-22 08_49_44-Browser.jpg

if i add an (audio) track after i engage S (solo), then that track is played/output anyway
lets say i solo track 2 - then i add track 3 and put it into record arm (+ monitoring) ; i can now hear 2 tracks, even with solo engaged on (only) 1 track
even stranger ; when i engage solo on track 2, the mute button on track 3 dimply lits ! (but not it's solo button)
this -last 'error'- seems to happen after when i engage Solo again (turn off/on again)
i think this is tied to the original output (master/submix) this was set to because when i change the output to master (originally when i created the track it was set to (a) submix) this behaves more or less as the rest of the tracks

when i disengage the rack (with the green button next to the minus sign in the rack) i still hear the track - only when i mute the track i cannot hear the sound(s) anymore - is this wanted/normal behavior ?
there's some "bleed" ; i don't see any vu meters moving but i definitely hear the sound of the track

[tiger001]

it would be nice if you select a track, you 'jump' to the
accompanying rack in the mixer - now i 'always' have to scroll down (to the mixer) and scroll left or right in the mixer to find the right rack

Do you have Project menu -> Auto MIDI Input Focus enabled?

yes

but i don''t see/understand what auto midi focus has to do with the relation between a track and a rack and it's view/place on the monitor screen

[MuTools]

it would be nice if you select a track, you 'jump' to the
accompanying rack in the mixer - now i 'always' have to scroll down (to the mixer) and scroll left or right in the mixer to find the right rack

In fact it works fine here.
Pls post a screen video of what you encounter.

[MuTools]

samples are not cleared from the manage audio/sample objects in project (ram) if i used a (multi) sampler and later deleted that track and rack

I don't get it.
If you only later delete something, then samples should not be deleted beforehand, right?

[tiger001]

samples are not cleared from the manage audio/sample objects in project (ram) if i used a (multi) sampler and later deleted that track and rack

I don't get it.
If you only later delete something, then samples should not be deleted beforehand, right?

correct, the samples should (only) be deleted when you clear it from the project but they are not, they are still in the project , even when/after i cleared the object / sample player and managed audio/samples clearance

[tiger001]

it would be nice if you select a track, you 'jump' to the
accompanying rack in the mixer - now i 'always' have to scroll down (to the mixer) and scroll left or right in the mixer to find the right rack

In fact it works fine here.
Pls post a screen video of what you encounter.

yes, you are correct
probably user error ; focus on somewhere/something else

[MuTools]

correct, the samples should (only) be deleted when you clear it from the project but they are not, they are still in the project , even when/after i cleared the object / sample player and managed audio/samples clearance

I still don't get it.
Please make a super simple project with some factory samples, and send me that MuProject file together with your step by step instructions to repeat the issue you see.

[tiger001]

done, check yr mail

[MuTools]

Thx Tiger, you're right, you catched a prey
Bug will be fixed in the next update.

[MuTools]

MuLab App M10.0.71 beta is available on https://www.mutools.com/mulab/app/lates ... /beta.html

MuLab Plugin M10.0.71 beta for Windows 64 bit is available on https://www.mutools.com/mulab/plugin/la ... /beta.html

What's changed:

• Windows: Virtual MIDI Keyboard key strokes now are *always* processed, even when a plugin takes keyboard focus. Only exception is when a MuLab popup menu or alert is open, so that you can use keys to quickly select a menu item / alert button.
• Virtual MIDI Keyboard now properly cuts notes when changing focused module while a key is down.
• Virtual MIDI Keyboard: Improved layout now with explicit octave buttons.
• Modular Area: Parent Modular Area button also supports right-click -> Open In New Window.
• When appending a new track via a shortcut key, now the new track is immediately scrolled into view.
• After just having deleted a rack with a multi-sampler and immediately afterwards doing Manage Audio Files/Samples -> Deleted Unuseds, some unused (multi-)samples were not deleted. Fixed.
• Other small improvements.

[liquidsound]

My Virtual Keyboard issue is GONE!

Thank you!

[MuTools]

All MuLab 10 beta versions (App, Plugin, MacOS, Windows, 32 bit, 64 bit) have been updated to the latest M10.0.72:

MuLab 10 App: https://www.mutools.com/mulab/app/lates ... /beta.html

MuLab 10 Plugin: https://www.mutools.com/mulab/plugin/la ... /beta.html

FYI: Only a tiny little technical change between M10.0.71 and M10.0.72.

Step by step progressing towards release.

[tiger001]

https://www.mutools.com/mulab/app/lates ... /beta.html

still points to 10.67

[MuTools]

Please first try a refresh of your browser cache.