MuLab & MUX Modular VST 7.3.6 Test: Rescalable GUI

[MuTools]

Hi,

There is a new MuLab 7.3 test version in http://www.mutools.com/galaxa/

How to install: Many graphic files have changed hence a complete package install is necessary, but of course you can copy over your user settings, see this doc page: http://www.mutools.com/info/docs/mulab/ ... ation.html

What's new since M7.2.24:

• The whole GUI now is rescalable up to 200%. See the "GUI Scale" preference.
  A rescalable UI is relevant for users with a view issue and/or on high-res monitors. Also relevant wrt touch-screens.
  Screens are getting bigger and bigger and hence the MuLab UI was getting smaller and smaller on those screens.
  This new feature handles that.
• All tree lists: Improved search behavior:
  * Starts searching from the cursor downwards, eventually looping to the start of the list.
  * [Ctrl]+G searches again for the next match.
  * After 1 sec, typing new characters for the search string will create a new search string.
• Project browser -> Audio Files: Support for selecting multiple files.
• Renaming Tracks, Racks, etc...: The current name is always filled into the edit field, even when it's using the automatic name.
• Fixed a potential sonic bug in the noise generator.
• Moving windows via [Alt]+drag border does not limit the window at the top anymore, the window is freely movable.
• New "Module Slot" module. It's like a single rack slot and can be put on a front panel.

Rescaling the GUI can be done via MULAB menu -> Preferences -> GUI Scale.

All constructive feedback on this M7.3 test version very welcome.
And if you would encounter any bugs, pls let me know the details.

Cheers,

Jo

[runaudio]

Love this brilliantly done

[runaudio]

just need to be able to connect the module slot and if you could add the level compressor front to mux front panel

[MuTools]

About the Module Slot: Right-click the module slot for its context menu, there you'll find a Setup Ins/Outs which allows you set choose how many audio/event ins/outs it must have. Then whatever module is plugged in will be automatically be linked to the available ins/outs of the module slot.

[runaudio]

Thank you

[Taifunk]

Everything works perfectly here ,I love this new release
Thanks Jo

[pljones]

Is it just me or does it seem to start up a lot faster than 7.2.x?

I think the inputs/outputs should either default to the "normal" values for a slot (one audio, one MIDI) or pick up the declared in/outs of the slot content automatically. I'd mildly prefer the visible defaults as being less unsettling (I might want to wire up a configuration before deciding exactly what I want in a slot). If the latter is done, then I don't see the need for being able to configure them (unless I'm missing something?).

The [*] option menu could do with doing something when the slot is empty -- it seems to show the same menu as right-click on the slot when there's content present but does nothing when there's nothing there. The "active LED" on the module is shown as green/active even when the slot is empty, although the LED next to the empty slot is grey. When there's a module present, the LEDs are the same state (i.e. turn the slot inactive, the module goes inactive).

Right-clicking the border around outside the slot itself should get you the same context menu as clicking on the slot module in the modular area, I think -- otherwise, you have to switch what you're looking at.

[runaudio]

Wot would be great if you could switch between samplers like in mudrum but added to the front mux panel

[MuTools]

Is it just me or does it seem to start up a lot faster than 7.2.x?

I don't know, i would not expect much difference, did not compare it, may be something system dependent?

I think the inputs/outputs should either default to the "normal" values for a slot (one audio, one MIDI)

Ok in the next version the Module Slot has an audio + event + modulation input and output by default.

The [*] option menu could do with doing something when the slot is empty -- it seems to show the same menu as right-click on the slot when there's content present but does nothing when there's nothing there.

That options button is about the plugged-in module, not about the module slot itself.
I know it may be a little bit confusing at first, but that's the nature of the module slot, i think things are logically correct.

The "active LED" on the module is shown as green/active even when the slot is empty, although the LED next to the empty slot is grey. When there's a module present, the LEDs are the same state (i.e. turn the slot inactive, the module goes inactive).

Indeed because the module slot itself is active but when there is no module inserted that one cannot be active.

Right-clicking the border around outside the slot itself should get you the same context menu as clicking on the slot module in the modular area, I think -- otherwise, you have to switch what you're looking at.

Same thing: Right-clicking there is about the plugged-in module, not about the module slot itself.

[runaudio]

Load time is faster

[TheoXD]

My prays have been answered, thank you!! Will try it now on surface pro

[pljones]

Right-clicking the border around outside the slot itself should get you the same context menu as clicking on the slot module in the modular area, I think -- otherwise, you have to switch what you're looking at.

Same thing: Right-clicking there is about the plugged-in module, not about the module slot itself.

That's why I differentiate between right-clicking the plugged-in module and the area surrounding it, which is conceptually the slot module. One should have the plugged-in module context menu, the other the slot module context menu. Similarly, if the [*] is the plugged-in module context menu, it should show the same as right-clicking the plugged-in module - even when there isn't one - otherwise it feels inconsistent and confusing.

[MuTools]

That's why I differentiate between right-clicking the plugged-in module and the area surrounding it

That area is not guaranteed to be there. For example when embedded in a front panel the designer can choose to make that area transparent.

One should have the plugged-in module context menu, the other the slot module context menu.

The "Module Slot" is especially for use in the front panel. The front panel user should not see the Module Slot context menu itself, that's only relevant in the modular area. The Module Slot context menu is available via right-click on the Module Slot. I know it's a bit a thin zone, but this is about a special abstract module and it should only be used by modular patch designers hence they work in the modular area and hence Module Slot's context menu is easily available there.

Similarly, if the [*] is the plugged-in module context menu, it should show the same as right-clicking the plugged-in module

It does.

even when there isn't one

Why/how would you want to "Rename" or "Delete" a module that doesn't exist??

otherwise it feels inconsistent and confusing.

The general concept of "container" and "contained" may be a bit abstract sometimes and requests technical insight, but that's due to that general concept, not due to MuLab / MUX, imho.

[dakkra]

Works great for me so far! As always, an absolute joy to use

Dakkra

[AndreasD]

I think the inputs/outputs should either default to the "normal" values for a slot (one audio, one MIDI) or pick up the declared in/outs of the slot content automatically. I'd mildly prefer the visible defaults as being less unsettling (I might want to wire up a configuration before deciding exactly what I want in a slot). If the latter is done, then I don't see the need for being able to configure them (unless I'm missing something?).

Please keep the configuration of in/outputs for the modular slot.
I do a lot of non standard things and this module adds nicely to the user interface for those things.