MuLab 10.0.85

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

If you start from a default new rack and don't touch its modular area then the "Before/After" choice should never popup. If that choice pops up it's for a good reason, as demonstrated in that video.

If you think the "Before/After" question comes at unnecessary moments please demonstrate that case using a small example project.

Post

MuTools wrote: Tue Jan 28, 2025 10:07 pm If you start from a default new rack and don't touch its modular area then the "Before/After" choice should never popup.
But it does :roll: Check this video please:
Image

Post

Ohw, i see, it's when clicking the fader triangle at its current location.
That's a little bug indeed which will be fixed in the next update.
Such click should result in no action at all, obviously.
Thx for the video, that helped :tu:

Post

MuTools wrote: Wed Jan 29, 2025 3:16 pm That's a little bug indeed which will be fixed in the next update.
Thank you!
MuTools wrote: Wed Jan 29, 2025 3:16 pm Such click should result in no action at all, obviously.
Yes, there's actually no need in clicking the triangle at it's current location. :)
I faced this behavior when trying to drag the triangle, which I used to do in v9.

Post

Hi Jo, I updated to m10.0.38 and my recent projects do not show any more.
I thought maybe it was the new setting, but it hasn't changed, it's still on 10, but everytime I start MuLab, I get this window:
mulab.png
You do not have the required permissions to view the files attached to this post.

Post

Please launch MuLab, open one of your own projects, then do MuLab menu -> Tools -> Keep Log.
Then quit MuLab and email me both the most recent log in MuLab/User/LogFiles as well as your MuLab/User/Settings/PreferredFilesAndFolders.txt file.

Post

OK will do that tomorrow :tu:

Post

Email sent :tu:

Post

Thx. Lets continue via email.

Post

Thx for the logs.
A bug which will be fixed in the next update.

Post

syntonica wrote: Wed Jan 22, 2025 5:52 pm Edit: I just checked the project in v9. It's fine there, but now I see in v10, it's adding a second Audio Input 2 under the Master.
Found the cause, fixed that bug.
An important bug fix wrt loading MuLab 8 projects in MuLab 10.
Thx for highlighting this issue :tu:

Post

Quick question for Jo - did you perhaps implement the VST3 IPluginCompatibility interface for plugin migration? I see on the first page of this thread in the changelog you mention some migration options that sounds like you spent an awful lot of time (probably) to do yourself, when VST3 provides this capability (and more and more hosts and plugins are starting to support this capability).

Post

EvilDragon wrote: Wed Feb 05, 2025 3:19 pm Quick question for Jo - did you perhaps implement the VST3 IPluginCompatibility interface for plugin migration?
No, not yet.
That's new to me.
Thanks for the pointing to it.
I see on the first page of this thread in the changelog you mention some migration options that sounds like you spent an awful lot of time (probably) to do yourself
Not an awful lot of time.

Post

Well, good then! This is the official method for VST3 migration. The alternative is supporting moduleinfo.json (some plugins choose to use IPluginCompatibility, some choose moduleinfo.json, so realistically a host should support both).

Post

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

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

What's changed:
  • Recent project list was missing the projects saved in the user folder. Fixed.
  • Clicking a rack's fader position indicator, thus at its current position, caused an irrelevant "Insert Before/After" popup. Fixed.
  • Via right-click on rack output display you can also switch the display mode to modulation output, if any.
  • When a MuLab Plugin project modular area has less audio outputs modules than the number of audio outs reported to the host then this could result in audio noise/static in the host. Fixed.
  • Edit Front Panel from inside the main project editor window did not work anymore. Now it will popup a separate window where the MUX Front Panel can be edited. On finished editing, a question pops up whether to optimize the project window size.
  • MuLab App: Right-click project window includes "Optimize Size" which can be used in case the Main Module editor itself is not resizable, eg. when MuLab is used as a synth or effect where the main editor is a MUX Front Panel.
  • MuLab Plugin: Right-click the bottom-right resize control of the main plugin window pops up a context menu with option "Optimize Size".
  • Project menu now includes Copy + Paste.
    These can be used to more easily upgrade a MuLab 9 Plugin instance to a MuLab 10 Plugin instance:
    In M9 Plugin do Copy Project, in the host DAW replace it by M10 Plugin, in M10 Plugin do Paste Project. (Needs MuLab Plugin 9.5.35, link below)
    Also handy to copy-paste between different MuLab Plugin instances in a DAW project, or between MuLab App and MuLab Plugin.
    It simply is a handy shortcut for using a temporary project file. (MuLab/User/Temp/Clipboard.MuProject)
  • Loading MuLab 8 projects could result in a wrong number of IO for the composer module. Fixed.
  • Restyled launch/info window background looks.
  • Other small improvements.
M9.5.35 Plugin

MuLab Plugin 9.5.35 for Windows 64 bit is available here: https://www.mutools.com/mulab/legacy-ve ... 64-dll.zip

MuLab Plugin 9.5.35 for Mac 64 bit is available here: https://www.mutools.com/mulab/legacy-ve ... 64-dll.zip

The only change between M9.5.34 and M9.5.35 is that it also includes the Copy + Paste Project options so to make upgrades from M9 Plugin to M10 Plugin more easy.

Post Reply

Return to “MuTools”