MuLab 8.0.66

[MuTools]

NB: About the tempo factor in the step sequencer: It was still there from the core M8 R&D phase. But cfr previous post i think it's better to remove it there.

The Sequence Player module also has a tempo factor, there it is relevant.
Also in the Sequence Player module changing the tempo factor during play could cause stuck notes.
That has been fixed in the next M8.0.51.

[Jimp_music]

Quick Question : Could M8 see Presets for MUX's within the Front end panel?

[MuTools]

At the top of the front panel there are the controls to select, open and save a MUX patch. They're at the right of the power on/off led.

[Jimp_music]

At the top of the front panel there are the controls to select, open and save a MUX patch. They're at the right of the power on/off led.

I meant that in the way that having one bodied mux and it having different parameter presets within the mux in like a small side column/scrollable/navgatable way. Like the small room reverb, large room reverb, garage reverb and big hall reverb basically use the same mux with different settings. Would be convenient if all those different presets of settings were on the panel, the main panel being the basic same one.

In the existing system, yes you can click on the next button to load the next effect but there ja no boundary as in if i keep clicking the button i may well end up in a different effects section that preceedes or succedes.

Having the different settings embedded in the same basic frame will reduce the loading time, repeated loading and will provide easy navigation, ESPECIALLY FOR MUXS WITH SAME MUX PANELS.

[MuTools]

Kind of mini-presets for that specific MUX front panel? Yes i thought about that too already. But then this question: What if you have a dozen of panel presets and then you change that MUX patch/front panel, then there could quickly be a difficult to resolve incompatibility between the existing panel presets and the new panel. How would you solve that?

[Jimp_music]

Change could be both in an existing parameter or in terms or introducing a new one alltogether. I hope from my understing that parameter values are directed toward the source and not to their visualisation/realisations on the front panel.
Besides that, mulab still supports the old instrument panels like Vintage bass rack, Digital bell rack and the newer Basic synth type panels. Even church reverb uses a differnet panel than small room one.

My idea is of one elegant, simple UI for an effect with various on/off buttons and presets to add and variate, which untimatly saves time and rack space.

But then, being flexible is a great option in having various types of UI for users to choose from.

My point is, its easier to naviage something if you know where it will be found on a panel, which requires a basic common framework. It could really save thw effort of diving inside the modular segment and editing each setting one by one. I am sure if you draw a few samples to upgrade existing muxs, the community will be really helpful in coming out with one, solid UI.

[MuTools]

Not sure if i fully understood what you wrote / your technical solution. Anyway, no doubt "MUX panel presets" could be an interesting addition. It is already on the wishlist, but it's a matter of 1) finding a good technical solution, and 2) finding the right time to implement it.

[bibz1st]

If you dont want too many you can set up your own little presets system using the parameter randomizer but with absolute values instead of random ones. Does come with a little extra CPU use but it works.

[MuTools]

Thx for the suggestion bibz1st. Elaborating on this topic: It's not only a matter of saving parameter values, if a front panel includes oscillators also the waveforms must be saved in the panel preset, if it contains samplers, also those sample settings must be saved in the panel preset, etc... And a MUX patch can have nested MUXes and the front panel can point to any modules in any of these nested MUXes so it can get a bit complex, certainly if you would save panel presets for a complex MUX patch, and then change that MUX patch.

[RichardSemper]

Sounds like this could get pretty complicated.
Personally I like the way it is. Often a preset can create quite different sounds and types of sound with just a few tweaks of parameters. This can be saved as a completely new preset - in a location more suited to the different use, eg a sequence vs a pad.
The best way in my opinion is to keep preset names and folders nice and tidy.

[Jimp_music]

Thx for the suggestion bibz1st. Elaborating on this topic: It's not only a matter of saving parameter values, if a front panel includes oscillators also the waveforms must be saved in the panel preset, if it contains samplers, also those sample settings must be saved in the panel preset, etc... And a MUX patch can have nested MUXes and the front panel can point to any modules in any of these nested MUXes so it can get a bit complex, certainly if you would save panel presets for a complex MUX patch, and then change that MUX patch.

Note taken, also thanks B for the suggestion. I was still hoping mulab to have a UI that incorporated easy presets to quicly get a basic sound done, which could be further customised, like in almost every third party synth/effect.

[Deprekat]

Oooooh, just saw the new beta now. Super excited! Since I'm heading for a lot of sample work and field recordings, it'll be very interesting to check it out.

While I'm at it, here are two tiny suggestions I'd like to put forward to be incorporated:
1. A project-wide "MIDI Mappings Overview" that outlines all active MIDI mappings and their parent objects (ie, whether a mapping is defined globally, for a specific rack, for a specific instrument in that rack, etc.). It's easy to lose track of what I'm setting up.
2. An annotation tool for the modular editor. Inspired by spreadsheet software like MS Excel, where you can add a pop-up note to cells to hold some additional information. I'm building some quite technical things in the modular editor and it would be cool to have notes outlining what each element does. Module names just don't cut it sometimes.

[sl23]

Regarding Menu items, is there any chance we could please have another colour option to change the colour of folders separate from any items contained within them?

Thanks

[sl23]

Although I've used Muzys as an example, it's just because it was easier to achieve the goal I wanted to convey. Obviously the colours in the pics are just my preference but if applied you should get free choice as with all other colouring options.

I'd like to have another colour option, which makes things clearer imho, would be to remove the colouring from the track headers, like this:

Image 001.png

...and simply have a border around the selected track. Then just have a colour option for the track name and maybe a second option to change the text colour for the selected track, like this:

Image 001-2.png

This would mean three additional colour options:
1. Track header background
2. Selected track border
3. Selected track text

You could expand on this but I think this would be enough.

Does anyone else like the idea? It's simply easier to read a list of tracks without all the separate tracks graphics making it appear quite so packed. I expect this would help those with poor eyesight too. Perhaps the option to have this or the current, rather than this replace the current, so to please everyone

EDIT: Looking at it again, it may be easier to add option to colour unfocused Racks and just the text for unselected and selected. Without lightening the colour of unselected tracks, or it goes against the point of colouring them. That would solve the "issue."

[sl23]

Btw Jo, THANK YOU for my license key