MuLab 9.1.27 [released]

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

Post

If you have downloaded that M9.1.12 quick fix for win64 of an hour ago then please redownload it from the link in the next post. It's still the same version nr but there is a slight UI difference about the main menu buttons.

Post

MuLab App 9.1.12 is available in https://www.mutools.com/mulab/app/latest-binary

MuLab Plugin 9.1.12 is available in https://www.mutools.com/mulab/plugin/latest-binary

What's changed since last beta M9.1.11:
  • Quick fix for the reported front panel plugin slot issue.
  • The main menu buttons are also consistently flat by default.

Post

Hi, MuLab Plugin 9.1.12 (Multiple instances within the session) Error 349 constantly logged when closing:
You do not have the required permissions to view the files attached to this post.

Post

The Rack Component has the larger size in ver.9.1.12 which makes it "visually" incompatible with front panels made with ver.9.0.59
---
Rack.jpg
---
And some more "349 Errors" here:
You do not have the required permissions to view the files attached to this post.

Post

About the 349 errors:
I can't repeat it.
Please share a project/preset that causes it.
You can monitor when that error happens by opening the log window via MULAB menu -> Tools -> Show Log
Thx.

Post

mutools wrote: Tue May 30, 2023 10:50 am About the 349 errors:
I can't repeat it.
I tried again and I couldn't repeat it neither - I'll keep you updated as it becomes more specific

Post

Thx to a tip someone sent via email i could find the cause of the "349" error and it will be fixed in the next update. Thx for reporting this :tu:

Post

robert_p wrote: Tue May 30, 2023 6:28 am The Rack Component has the larger size in ver.9.1.12 which makes it "visually" incompatible with front panels made with ver.9.0.59
Indeed the racks have grown in size. And indeed that also affects front panels that contain a rack. But i'm unsure how to solve this automatically. There could be many different front panel cases and it's not straightforward to automatically rearrange a front panel when the size of a contained component has changed.

This same aspect will also be there once it will be possible to include front panels in front panels. Imagine you embed a front panel ("Child") into another front panel ("Parent") and put all kinds of other components around it. Lateron you edit the child front panel on its own and grow its size. Then when you open the parent front panel it might not look right anymore because the child front panel has grown size.

How should that be handled?

Post

mutools wrote: Wed May 31, 2023 8:16 am How should that be handled?
I think backward compatibility is a crucial thing when it comes to any software update. Imagine, how many presets have been created by users since the release of MuLab9 (I’ve got hundreds of them already). The only solution that comes to my mind (if you really need the rack to be larger) is to have 2 types of rack components available: Small (v.9.0.59 style) and Medium (v.9.1.12 style) that could be selected thru “Properties” dialog box. The small one would be loaded with already created front panels by default (i.e. none of the size properties was specified when saving). The Medium one would appear only if the Medium Size was selected during the panel design process, then saved. (This also could be the default selection for all new panels in edit mode).

Post

That's indeed a possible instant solution for the current rack size issue. That idea crossed my mind too. But it's not a solid solution for the more general (future) issue of size changes of embedded front panels or other front panel elements. Hence the general question i posted.

Post

mutools wrote: Wed May 31, 2023 10:13 am But it's not a solid solution for the more general (future) issue of size changes of embedded front panels or other front panel elements.
If the "child panel" was previously saved without specifying the rack size (or other elements) it should appear "Small" (or "legacy") within the parent panel. The parent panel should be able to "read" the properties of the "child" one.

Post

Thinking further loud: Maybe these 2 issues should be considered separately. 1) Add compatibility code for the legacy rack size. 2) Embedded front panels (future feature) that grow size could be placed in a scrollable view that has the original size. It won't look ideal as the new child front panel will be cropped (but scrollable to full extent) but at least the parent front panel stays consistent.

Post

robert_p wrote: Wed May 31, 2023 10:27 am If the "child panel" was previously saved without specifying the rack size (or other elements) it should appear "Small" (or "legacy") within the parent panel. The parent panel should be able to "read" the properties of the "child" one.
We're talking about parallel things. Anyway, i guess the short term solution indeed is to add compatibility code for the current rack size issue. Thx for thinking along.

Post

One more thing to consider: MuLab plugin state is saved with a DAW project file - and the project may not open in the future due to MuLab's updates.

Post

robert_p wrote: Wed May 31, 2023 10:42 am One more thing to consider: MuLab plugin state is saved with a DAW project file - and the project may not open in the future due to MuLab's updates.
MuLab 9 opens older M8 + M9 project file data, no prob at all about updates.
If you have M4-M7 projects/presets these can be upgraded using M8 and thus make them compat with M9. I fully agree that preserving file compatibility is very important.

Post Reply

Return to “MuTools”