MuLab & MUX VST 7.4.6

[sl23]

Front panels that are smaller than the window are now centered within that window.
As a result of that, when you drag the window border of a window with a small front panel then this does not automatically resize the front panel anymore cause that would give unexpected results.
In such case you can still resize the front panel via its property panel. (double-click or right-click the front panel background)
And to have more control over the window background which becomes visible in such case, each front panel now has 2 extra color preferences "Filler Color 1" and "Filler Color 2".
That way even a small front panel in a wider window (due to the top controls) will still look fine.

I thought you intended to solve the issue?

[imstre]

Thank you very much for the update!
wonderful!

[MuTools]

I suggest you rework the background picture.
It was never intended that a background picture would have a different size than the front panel.

Or maybe you simply need to update the size of your front panel to the size of your pic. One thing is sure: It was never intended that a front panel background picture would have a different size than the front panel itself. That's an unsupported case.

[sl23]

OK fair enough, that has never been stated though. If it's in the docs, don't bother pointing it out, I never check them!

[pquenin]

"Logging now is always active" : does this one slow the application and degrade the performance ?

[MuTools]

No, it should not make a noticable difference. Logging is only done in the UI thread so it should not affect audio performance at all. The importance of logging being always active has to do with possible crashes: When a crash occurs now there will be more info about what happened before the crash so hopefully i will be able to better analyze the context. I tried to avoid logging to be always active but it's the only way i see to get more pre-crash info. I think MuLab is quite stable but imstre reported some rare crashes and i want to find those bugs. And even when those are fixed, you never know beforehand if there still is some rare crash bug here or there that happens only occasionally. So when it happens, the info must be saved. Goal is to make MuLab as stable as possible.

And to be very clear: The logged info is non-personal, it's only tech info about the interactions with MuLab. And nothing is transmitted over the net. In case there is an error the log file will be in your MuLab folder, like before. It's a text file so you can check it.

There is one case that can't be logged yet and that's when a crash occurs that cannot be catched by MuLab. In such case the OS will report the crash and on Windows the crash info will be available via the Event Viewer, on Mac click the report button and copy-paste the tech details.

[MuTools]

New M7.3.16 available in http://www.mutools.com/galaxa/mulab

What's new:

• Projects, MUX presets and MuClips can now have some basic creator info.
• When there are multiple edit fields in a panel, the Tab key now steps thru these fields.
• Fixed an issue wrt double-clicking modules in the deep modular area.
• And other micro improvements.

How to install:

First make sure you already have installed the complete M7.3 package.

Then:

Windows: Put the new .exe and .id files into the M7.3 installation folder.
MacOS: Put the new .app file into the M7.3 installation folder.

The respective MUX Modular VST update coming soon.

[MuTools]

Projects, MUX presets and MuClips can now have some basic creator info.

For projects: Project menu -> at the end of the menu = "Show Creator Info"
For MUX patches, racks and MuClips (=sequence parts): Context menu -> Presets -> "Show Creator Info"

[sl23]

Thanks

[imstre]

Thank you very much !

[sl23]

I suggest you rework the background picture.

What is the minimum size required before the picture is stretched to fit the window?

[MuTools]

If you're using a background pic, it is *always* sized to fit the front panel's size, which can be set via the front panel property panel = right-click/double-click the very front panel background.

[sl23]

Yes I understand that, but what if a picture is smaller than the minimum size of the toolbar width?
There is obviously a minimum width due to this restriction.
Is there a minimum height too? Loading a new MuX modular and clicking it's front panel button shows there doesn't appear to be a minimum height.
So deduced from this I would imagine there is a minimum width requirement for a picture. If it's narrower than this specific width, then it will be stretched to fit the minimum width of a front panel, yes?

Hence my question...
What is the minimum size for a picture?

[MuTools]

Same answer. Note that the front panel now is independent from the top control bar (of which the size may vary with the app version), so the front panel can have any size, also a smaller size. If in still doubt, just experiment a bit with resizing the front panel and you'll see how it reacts.

[sl23]

No need, I get the same result...
It stretches the picture to fit, I really do not want the hassle of trying to figure out my layout, having to edit the picture to suit and then trying to ensure it's the correct aspect ratio afterwards.

In fact, you've made things worse, because now you have to try and plan every detail of a front panel that has a picture relative to the layout. Now you have to ensure your picture is the correct size to fit all your layout devices on. If you decide to later add/remove a few components from the front panel, you now have to re-edit your graphic to suit. You are also restricted with the graphics you use or the layout you choose as the aspect ratio is critical!

I will reiterate, this is a very bad idea, and the only way this will work is if you allow resizing of pictures exactly as if you would a Group Frame. Is this a difficult thing to achieve?
This would also allow users to design hi-res images that MuLab would scale down to fit. Whereas it can, as is my case at present, cause a lot of problems trying to get everything the correct size.

Please consider allowing this, it's not that I'm being picky and trying to convince you my way is better for the sake of it. There really is no better way. If you choose not to change it, please return it to how it was, as now it's far worse and causes more issues than it solves.

Thank you