MuLab 10.0.85

[MuTools]

It would be nice to be able to configure the startup window for color preference at least.
Not a big deal, but personally, I would like it to be consistent, if I had my way.

The next update uses a bit more consistent coloring on startup. It's still using rolling colors, but the start point is more consistent to the MuTools brand color, which is some kind of blue.

[MuTools]

Somehow most of the VST3-2 have issues with the virtual keyboard on my windows machine:

If I interact (adjusting parameters, changing presets) with instruments such as Pigments, Zebra, Massive-x etc, the Virtual Keyboard loses the input/focus and the only way to get it back to the plugin is to click the plugin's title bar.

Serum 1 and 2 never have this issue... why?

Surface Pro W-10. All and latest MuLab version.

I've taken note about your feedback, for which thanks, and will check this later, assumed during the M10.x life cycle.

[MuTools]

is it because we (always) have the possibility to open a file through a new/different external audio editor that there's 2 references for externally working with audio?

Yes.
But i understand your question.
Will reflect on it.

[liquidsound]

Somehow most of the VST3-2 have issues with the virtual keyboard on my windows machine:

If I interact (adjusting parameters, changing presets) with instruments such as Pigments, Zebra, Massive-x etc, the Virtual Keyboard loses the input/focus and the only way to get it back to the plugin is to click the plugin's title bar.

Serum 1 and 2 never have this issue... why?

Surface Pro W-10. All and latest MuLab version.

I've taken note about your feedback, for which thanks, and will check this later, assumed during the M10.x life cycle.

Thank you Jo.
Btw this problem doesn’t exist with the Mac OS.
Lately I’ve been thinking to get an Apple laptop since my CAD program has been successfully ported to the Mac OS so, if I’m the only one complaining for the above issue, don’t waste your precious time to investigate and fix it.

Let’s move on with your wonderful MuLab progress.

[MuTools]

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

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

What's changed:

• MacOS: After having hidden the Focused Module Keyboard at top, a right-click did not show a context menu anymore to show it again. Fixed.
• Some extra polishing on the startup window.
• Extra log output on Maximize Window.
• Other small improvements.

[dayvyg]

I've had to reconnect the audio cable from some tracks to the master to get audio to play through the master track. Seems fairly random though. I've only had this happen on one project so far.

No, I've been using the beta version of Mulab for a while and the projects affected we're created in version 10.

Is it 1 or more projects?
Please send me the smallest project that repeats this issue.

This just happened on one project. I fixed it at the time be reconnecting the cables. I can't remember which project it was and I haven't had the issue since.

[MuTools]

Ok. I remember that there was such issue in an earlier stage of the M10 beta when importing M8 or M9 projects, cfr what pljones also referred to. I thought it was fixed. Could it be that it's about a single project that originated before M10?
Anyway, lets keep an eye on it and if it happens again pls try to make it repeatable for research. Thx.

[MuTools]

Preview video about MuLab 10's new curves:

[pljones]

Odd, don't see a reason in the code. Next update will log relevant data when doing Maximise so pls email me the complete log file after having repeated that case using the next update.

I've emailed the log. Thanks.

[MuTools]

Thanks for the log. Bug will be fixed in the next update.

[jd88]

Preview video about MuLab 10's new curves:

wow

this will (maybe later!) be so nice for LFO-Curves in Polysynth

[MuTools]

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

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

What's changed:

• Curve property "Edging" renamed to "Sharpness". Also the above video has been updated.
• Oscilloscope maximum Time Range increased to 5 secs. (before it was only 1 sec)
• Bug fix when maximizing a window on a multi-monitor setup where the primary screen is not the first screen.
• Oscillator portamento bug fix.
• Removed some irrelevant menu options from the rack slot context menu.
• Other small improvements.

[dayvyg]

Ok. I remember that there was such issue in an earlier stage of the M10 beta when importing M8 or M9 projects, cfr what pljones also referred to. I thought it was fixed. Could it be that it's about a single project that originated before M10?
Anyway, lets keep an eye on it and if it happens again pls try to make it repeatable for research. Thx.

Yes, I think I was mistaken. I went back and looked at the projects I updated and one of them could have been started before version 10. It's quite possible that is the one I had the issue with. I'll let you know if I run into the problem again.

Thanks.

[tiger001]

if i have a (few) submixes/racks and add a new track, why does the output of that new track goes to my submix and not (default) to my master out (anymore) ?
[edit] probably user error ; when i had my submix rack selected

if i have (lots of) tracks -so my screen is full- and add a new track why is it always out of sight ? -> i always have to scroll down to (be able to) see that new track

a few basic browser basics (up/down/back) in the browser would be convenient, no ?

2025-06-20 19_20_08-MuLab App _ Vermona Perfoumering-20250606-221759.jpg

if i am in the audio sequence editor (window) and i'm browsing -in the browser- for another sample, i cannot add that new sample to a (new) track, i have to exit the audio editor (so see the timeline) to be able to add a new track/sample

it would be nice when you rename a track, the rack belonging to that track is renamed the same / too, no ? The other way (when you rename a rack, the accordingly track is renamed) it works like that already

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

wouldn't it be nice if we had a few more options in the rack right click menu? Like position (all the way) Left, (all the way) Right, position Left from (rack x), position Right to (rack y) etc ?

2025-06-20 22_42_28-.jpg

why is the wet/dry balance (of this stock delay) expressed in ms and not in percentage or plain numbers?

2025-06-20 23_28_56-Chaoszilator Front Panel.jpg

i find it a pity i cannot extend the length of a sliced sample (with the Loop end marker) unless mulab is stopped

[MuTools]

if i have (lots of) tracks -so my screen is full- and add a new track why is it always out of sight ? -> i always have to scroll down to (be able to) see that new track

Streamlined in the next update.

it would be nice when you rename a track, the rack belonging to that track is renamed the same / too, no ? The other way (when you rename a rack, the accordingly track is renamed) it works like that already

The rack, or in fact the track's target module, is the master wrt naming.
But you can rename a track separate from its target module.
That's what rename track does.
If you want track & rack to have the same name, leave the track name empty, then it will automatically be named ike its target module.
If renaming a track also renames the target module, as you suggest, then there is no way anymore to have different names.

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?