MuLab 10.0.85

[MuTools]

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

MuLab Plugin M10.0.47 beta is available on https://www.mutools.com/mulab/plugin/la ... /beta.html

What's changed:

• Sequence Editor: When multiple notes are selected then changing the start of one of the selected notes also changes the start of the other selected notes, possibly with optional choice: Absolute - Relative - This One Only - Cancel.
• Click-hold module in rack slot and simply release it without moving caused an unexpected UX. Fixed.
• Module Slot -> Embed Parameters: When there are many parameters they were all layed out pure horizontally possibly causing an extreme wide editor. Fixed by arranging them both horizontally and vertically.
• Modular Area: Drag-Drop module into some rack slot or module slot, then undo that action, cables were not restored. Fixed.
• Window context menu now also includes "Full Screen". (for resizable windows)
• Note Key Mapper: The view position of the input and output keyboards are now memorized. The output keyboard position even is memorized per key.
• Note Key Mapper: The highlighted key and the input + output keyboard positions are now saved data so the editor will look the same after reloading a project / preset.
• Other small improvements.

[Teksonik]

The next MuLab 10.0.47 update will have such option. In the current MuLab 10.0.46 there already are some other options and if you're on a 1920x1080 screen you can already use "Size FHD 1920x1080". But the next M10.0.47 will have an explicit "Full Screen" option too.

Ahhh thank you, that's perfect as I am on 1920x1080 so now MuLab displays over the taskbar as desired.

I did make an error earlier. I got my version numbers mixed up. I meant to ask if there is a demo version of the Beta 10.0.47 but I wrote 10.0.46 by mistake.

I just thought it would be nice to test the Beta since at some point it will be the latest release.

[MuTools]

To avoid confusion: At the moment you asked M10.0.46 indeed was the latest version.
M10.0.47 only is available since a little hour

[pljones]

If you chose "no" on that question then the screen rectangle of the project window is recorded.
If that Note Mapper window is not inside the project window screen rectangle then it won't be visible in the video. Does that clarify it?

Yes - I thought it meant it would record all the MuLab windows.

The next M10.0.47 update will also memorize the view position of the input and output keyboards, and the highlighted key and both these view positions will be saved data.

Thanks.

[Calum]

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

What's changed:

• Window context menu now also includes "Full Screen". (for resizable windows)

On a Mac, the new "Full Screen" option causes the MuLab window to drop below the Desktop window by the same amount of pixels as taken up by the height of the Mac Menu Bar:

Screen Shot 2025-04-03 at 14.49.14.png

The majority of Mac apps open in full screen mode by "sitting on top" of the Mac Menu Bar and Dock but the only way to open MuLab in full screen mode on a Mac is to hide the Menu Bar and Dock before launching MuLab.

Of course, if Apple could learn to be consistent and allow a shortcut to hide the Menu Bar as it does the Dock then this would be a simple solution but at the moment you have to dive into the system preferences to make this change before and after using MuLab and that's not convenient. If it was an easy fix to allow MuLab to open "on top" of the MenuBar/Dock I guess that would have been implemented already, so perhaps it would be neater just to drop the new "Full Screen" option from the Mac version (or make it behave like the Maximise button) - just a thought.

My current workaround is to use a Keyboard Shortcut to run an AppleScript in Automator to hide/show the Dock and Menu Bar (set up and tested in Ventura but should work on more recent MacOS). Goes without saying (but I will say it anyway), try this at your own risk!:

• Open Automator (/Applications/Automator.app).
• Click "New Document" and choose "Quick Action".
• At the top, set: Workflow receives: "no input" in: "any application"
• In the Actions panel, search for "Run AppleScript" and drag it into the workflow.
• Paste the following script into the Run AppleScript box:

Code: Select all

tell application "System Events"
	if autohide of dock preferences then
		set autohide of dock preferences to false
	else
		set autohide of dock preferences to true
	end if
end tell
tell application "System Events"
	if autohide menu bar of dock preferences then
		set autohide menu bar of dock preferences to false
	else
		set autohide menu bar of dock preferences to true
	end if
end tell

Screen Shot 2025-04-03 at 14.56.28.png

• Click File > Save, name it something like "Toggle Dock and Menu Bar", and save it.
• Assign a Keyboard Shortcut by opening System Settings > Keyboard > Keyboard Shortcuts.
• Select "Services" from the left panel.
• Scroll down to the "General" section, find "Toggle Dock and Menu Bar", and double click "none" at the right to "Add Shortcut".
• Press your preferred shortcut (eg, ⌃⌥⌘D for Control + Option + Command + D).

Screen Shot 2025-04-03 at 16.38.01.png

• To use the Shortcut, make sure you are in the Finder, press ⌃⌥⌘D to hide the Dock/Menu Bar before opening MuLab and use the same shortcut in the Finder to show the Dock/Menu Bar after closing MuLab.

[MuTools]

This new Full Screen function is simple and easy:
It puts the window at point 0,0 and resizes it to the size of the screen it is on.
Works fine on Windows. And the simplicity made it possible to quickly add this.

However, indeed, MacOS makes it difficult again
As it was not planned to invest a lot of dev time in this function from the next M10.0.48 on the "Full Screen" context function will be Windows only for now.

Thanks Calum for reporting this Mac issue.

[Calum]

I fully understand and I wasn’t expecting a Mac fix at this stage in MuLab’s development. I’m sure my workaround will continue to serve me well, at least until Apple decides to break something else!

[4u610h346]

Maybe I am doing something wrong?

-Add audio track
-Import stereo audio file, to new audio track
-Enter audio editor mode (internal), for imported audio
-Select stereo section of audio
-Use the "Create new sample from selection" option
-Name file
-Create new audio track
-drag new sample, from internal browser, to new audio track

So, the issue is that the sample gets altered. Example, choppy at latter half of the sample and or added echo/reverb.
The sample previews fine, from the browser; but once placed in a track its suddenly different.

I can delete it from the new audio track and the browser. Use the "Create new sample from selection" option again, and it often results in the same outcome. If I render the added sampler to a audio file, the alteration is still there. Moving the selection locators doesn't seem to help. Neither does enabling/disabling "Snap to zero crossing".

Maybe I am missing some subtle thing; but I also have the same issue in v9.

v10 32bit on Wine

Can anyone replicate this behavior?

[MuTools]

I doublechecked these steps and the new sample plays as expected here.

What do you mean with "the sample gets altered"?

Can you make a screen video-with-sound demonstrating this issue?

[ortseam]

Hello!

Found a bug (very easy to reproduce ).
Just open a new Composer
- add a new Rack
- try to add a Mixer_Strip into it's slot
... and ooops! immediate crash.

Check this video, please

Thank you for being so attentive to my reported issues! Have a nice day!

[ortseam]

... and one more question (please watch the attached video):

If I insert some Plugin with a sidechain input into a Rack_Module and create an additional Audio_Input wired to it in Rack Modular_Area, then each move of this Plugin from one slot to another results in automatic creation of a new Audio_Input while a previous wire connection gets lost. Was it meant to behave this way? I find it a bit inconvenient since you can't simply reorder the FX chain from Rack front panel without loosing a sidechain wiring. Moreover even after you remove a multiinput plugin all created inputs still remain as a useless garbage.

I'd so much appreciate if you let me know your point on that. Thank you!

[MuTools]

Hello!

Found a bug (very easy to reproduce ).
Just open a new Composer
- add a new Rack
- try to add a Mixer_Strip into it's slot
... and ooops! immediate crash.

Thx for reporting this!
Will be fixed in the next update.

[4u610h346]

Here you go, Jo. Tested on a different machine (track ball device), sorry for the jumpy pointer.
-> https://filebin.net/zr0874pclwgiuh4z
Noticed this on a client's remix/remaster reqest @ 44100 (old track). But this time it just played the file faster. However, I was able to recreate the previous issue, by using MuLab's provided stick sample.

[Michael L]

the only way to open MuLab in full screen mode on a Mac is to hide the Menu Bar and Dock before launching MuLab.

Do you mean the System Preferences to automatically hide and show the menu bar and dock? That's my default so MuLab is full screen but I can show them on top.

[ortseam]

Hello!

Excuse me for inventing more and more weird tasks for the new v10 Rack module, but that's the way the testing is, isn't it?

Another strange things take place when attempting to insert a Module_Slot into a Rack_Slot. Check up the video please (it's hard to describe a bit but easy to see).
v9 with it's former Plugin_Slot had no issues with this and the one could make a permanent multichannel Rack structure not affected by the plugins inserted. I'm missing it in v10 so I tried to find some way and stumbled accidentally upon the above issue.

By the way (please forgive my impudence): will it be so hard to make Rack_Slot channel number configurable (as it is for Module_Slot (former v9 Plugin_Slot). It might cause a question with Rack_Mixer_Strip (about how to manage level and pan settings for mulichannel audio stream), but on the other hand it might give the user much more flexibility and overall multichannel module tracing clarity.

Thank you so much. Sorry for possibly crazy ideas