MuLab 9.1.27 [released]

[MuTools]

This isn't concerning the FP at all, it's global. Go to MULAB menu and select an APP theme via GUI. change it to whatever, save it. Then go to GUI again and change the Buttons theme. Now change your APP theme, the Buttons theme is different to the APP theme and mine looks very odd! lol

The global button setup (User/Settings/AppGlobalButtonSet.MuButtonSet) is separate from the global color setup (User/Settings/LooksSetup.Xml).

Imho, ALL of the colours should be a part of the central theme if it's a global colour.

I understand this is a reasonable feature request. I can't give priority to this FR now though, maybe later, sorry.

[MuTools]

Ok, so here's a full screen screenshot showing the colours of the FP buttons not changing after having set the colours in the Tab Frame properties window, right next to the Tab Frame. Notice the buttons haven't changed colour.

I doublechecked it here and the tab frame buttons do follow the respective front panel button type definition. I can't see why it doesn't look like that on your screenshot. Best to save it as a MUX preset and send me the MUX preset file.

Also, note that the transport bar buttons haven't changed with the theme change.
Image 001.png

I don't see what you mean.

Same screenshot but after I changed the theme via MULAB/GUI/Colors/APP
Image 002.png
See how the buttons are set for one theme only and never change when changing global themes?

I don't see what you mean.
Please note that the global colors are separate from the front panel colors, as explained before.

Can you also see what I mean about the Osc waveform in the screenshots? It has a Waveform display with arrow buttons and a cog wheel button for selecting a wave and adjusting preferences.
Would be great to have this for Sample Players too on the FP!

The sampler section does have a sample selector with similar previous/next buttons.
But as the sampler section also contains other mandatory fields it cannot get smaller, as explained before.

[sl23]

I understand this is a reasonable feature request. I can't give priority to this FR now though, maybe later, sorry.

No, that's fine. Like I said before, this is low priority stuff, minor issues compared to what's being done at present. But thank you for taking time to understand the issues and accepting it needs resolving, even if it may be quite some time, I completely understand.

[MuTools]

- When changes the size via drag&drop the corners and frames of a textlabel, a big "X" appears instead of the label

I see, that's because there is no specific background color for the text label yet, but i'll fix that case by using a default color. Thx for reporting this.

Just an Idea:
It would be great if there were something like an eventgenerator which is able to "hear" of a button-state from the front-panel and is also possible to change the state from the mux (something like the Note-Event-Pad but with releation to the new Button-Controls)

I already had some wild ideas in such direction too, but it's not yet for short term, though i'm working into that direction. Thing is that by making the front panel system more uniform (ie. giving up the special code for MuDrum, MuSynth, MuSampla and MultiSampla) it already clears some of the path for that kind of future evolutions. For me that was one of the big reasons to dump these 'special devices', together with the reason that making them standard MUXes also brings a lot of extra flexibility to the user, eg MuDrum presets can now be fully customized, each drum pad can have a different editor, eg kick = sampler based, snare = virtual analog, etc.

[MuTools]

EDIT: I've just noticed what's happening. The expected behaviour is that by switching the module ON/OFF using it's power button changes the colour of the text i.e. the modules name.
But what's actually happening is that when you click the module, NOT the power button on it, the module responds to the click by changing colour.
Any chance it can work as expected please?

The module editor button is just a push button that, when clicked, opens the module editor. So it uses the standard push button color defintion.

EDIT 2: Forgot to mention, about Sample Player, I understand it has other adjustable parameters, but so does the OSC and MFO, yet these waveform displays can be added to FP easily. If it's something you'd rather not do, that's fine, I just thought it would be a great addition to quickly change a sample via FP. Deeper editing can be done by clicking the module/button via FP, as is currently done with the OSC and MFO.

You can't have a sample selector without having the start-loop-end displays, they're too essentially related, imho.

[sl23]

Ok, so here's a full screen screenshot showing the colours of the FP buttons not changing after having set the colours in the Tab Frame properties window, right next to the Tab Frame. Notice the buttons haven't changed colour.

I doublechecked it here and the tab frame buttons do follow the respective front panel button type definition. I can't see why it doesn't look like that on your screenshot. Best to save it as a MUX preset and send me the MUX preset file.

Here's the current preset, it's unfinished so it may be a little messy!

MC-909 v3 - mod3.zip

Also, note that the transport bar buttons haven't changed with the theme change.
Image 001.png

I don't see what you mean.

Here's the current theme:

Image 004.png

Switching the App theme doesn't change the global Buttons theme, they stay the same and have to be edited from scratch every time you change the App theme:

Image 005.png

Same screenshot but after I changed the theme via MULAB/GUI/Colors/APP
Image 002.png
See how the buttons are set for one theme only and never change when changing global themes?

I don't see what you mean.
Please note that the global colors are separate from the front panel colors, as explained before.

Understood, but hopefully you see the issue above. This is a good reason why they should be part of a global theme. As should Knobs and sliders too.

EDIT: I thought it would be better to include these other colour settings within the current MULAB/GUI/Colors window. You could make the window wider and have two columns for the APP tab of colour settings. This way, the window would be the right size and shape for the Button and Knob settings.

One thing that I find really annoying about the theme window is that when it's open, it stops you using MuLab. I don't really get why? You're only changing colours and it can be helpful to open other things like Mux Edit windows to grab colours from, which you can't at present.

Can you also see what I mean about the Osc waveform in the screenshots? It has a Waveform display with arrow buttons and a cog wheel button for selecting a wave and adjusting preferences.
Would be great to have this for Sample Players too on the FP!

The sampler section does have a sample selector with similar previous/next buttons.
But as the sampler section also contains other mandatory fields it cannot get smaller, as explained before.

Ok, from my point of view, I don't understand why not, as you can still open the full Sample Player, just as you do with any FP Oscillator or MFO when deeper editing is required. It's just that having the Sample Waveform and select buttons on the FP is a quick way to browse through or to use the browser to drag n drop them onto the SP. Maybe it's a technical issue? I'll leave it at that.

[sl23]

Minor bug: When editing Knob Colour settings, when switching the columns on the left, it causes the settings to show an extra frame called Extras. This widens the whole settings area, but the window doesn't enlarge with it causing the right hand side to be cut off, including the Options button on the right.

[MuTools]

Here's the current preset, it's unfinished so it may be a little messy!
MC-909 v3 - mod3.zip

You have given specific colors to those tab buttons so they use your specific colors.

[sl23]

The module editor button is just a push button that, when clicked, opens the module editor. So it uses the standard push button color defintion.

Yeah, I figured that out in the end!
I was sort of requesting that the text change colour to suit the button state ON or OFF.

You can't have a sample selector without having the start-loop-end displays, they're too essentially related, imho.

Ok, you only have to say if you think it's a rubbish idea!

[sl23]

Here's the current preset, it's unfinished so it may be a little messy!
MC-909 v3 - mod3.zip

You have given specific colors to those tab buttons so they use your specific colors.

Urm, ok, missed that, sorry!
But thank you

[MuTools]

Minor bug: When editing Knob Colour settings, when switching the columns on the left, it causes the settings to show an extra frame called Extras. This widens the whole settings area, but the window doesn't enlarge with it causing the right hand side to be cut off, including the Options button on the right.

I see. Taken note to fix that. Thx!

[sl23]

Here's the current preset, it's unfinished so it may be a little messy!
MC-909 v3 - mod3.zip

You have given specific colors to those tab buttons so they use your specific colors.

Urm, ok, missed that, sorry!
But thank you

One more thing wrt these buttons, why doesn't the Contour work? The FP has a contour setting but the buttons themselves don't. Shouldn't that show through?

[MuTools]

The buttons do have a contour color, see FP -> Options -> Edit Buttons.

[sl23]

Yes, I know, but I'm saying that when directly editing a buttons colour, there's no contour option (perhaps that'll come later?). But if you specify a Contour colour I think it should show, even if you set a Buttons colour directly. If you set Back Colour to none, then the Contour shows, but setting a Back colour blocks the Contour setting, I don't think it should. Unless you plan to add this setting to each button?

I think that's making the whole colours thing over complicated though. I reckon the best option is to scrap setting a buttons colours directly via it's properties and just increase the number of Tabs in the FP's Button settings, maybe to Ten? This gives plenty of options for everyone. Same for knobs and sliders too.

I have another issue regarding Colours. Copying a Button that has no background colour won't paste that setting to another button. This means I have to set it manually on every button. Could this be added to copy/paste please?

[sl23]

No, keep it as is, I see what you're getting at now, it's just that I never knew about these changes and it made it seem more complex than it need be. Where I'm adjusting an old preset, it makes it a pita to change, especially as when colour is set to None, as it won't copy/paste that to other buttons. There's a lot of buttons here, that's a lot of opening properties windows and manually drag n drop each None colour to every buttons colour setting!

I would suggest, when you can, no rush, to implement the following:
1. Add Contour option to each buttons individual properties.
2. Allow copy and paste of the info when a particular colour setting is None.