MuLab 9.2.22 (CLAP plugin support)

[robert_p]

When clicking on one of these buttons, it would be more efficient for workflow if all locations would appear in the browser list. negating the need for the 'Where' box

Yes, it would be more efficient - currently we need two clicks AND a precise mouse-move to go to the second box (where).

[robert_p]

Where do you get the label for Mux Instruments?

Here:
---

Inst_and_fx.jpg

[sl23]

Tbh, that second mouse click and precision would still be required to click the location in the Browser field! But... At least you wouldn't need to click just to see the locations as they would automatically be shown in the Browser upon clicking a 'What' Button.

Essentially, if desired, you could remove the What and Where fields and rename Which, to Search. This would look neater and give a less hobbyist feel to it. Though, I know some users may like it how it is, cough Michael, cough cough!

[sl23]

What is that screenshot? My browser doesn't have those buttons! I'm talking of the Browser that sits to the Right or Left of the screen.

Also, I would say those are 'Where' Locations. Making buttons for everything at this time is perhaps too time consuming? Trying to consider everyone here. Maybe for now just the main What functions?

EDIT: I see now, you're talking about the browser when clicking a rack slot, yes? Different browser, but maybe this could extend to that too? Perhaps it's possible to make them use the exact same code? Is that possible or easier?

[sl23]

One other thing that would really help navigating long lists is if the Parent folder could be a different colour. This would be helpful if it were a global option btw, so all menu Parents had a different colour.
Would that be possible Please?

[robert_p]

Yes, it's a rack slot browser. I like the tree structure which can also be shown in normal browser (all files), however I'd prefer some folders to be hidden - maybe this could be filtered by using the buttons
---

Browser.jpg

---
P.S. "Where" box can be useful, example: What - Sequences, Where - This project

[sl23]

I understand the Where box is useful, some may prefer it, I am just suggesting it may be better, easier, maybe more productive to remove that and just show ALL those options from the Where box in the actual Browser field. That way you can instantly see where you want to go after clicking a What Button. And if Parent folders can be coloured, it would make the whole navigation easier to see at a glance. If colouring Parent folders is accepted, could we have a couple of options here please. I would suggest two or maybe three levels deep for colouring.

So the What would be Sequences, but as a [SQ] button, clicking it would show a list in the Browser field:
> This Project
> Project Folder
> Factory Library
> User Library
> Desktop
> Browse for Folder
> Favourites

This list could be either browsable, may be harder to code for though, or it could be like a file manager that opens that directory as it would currently do. I feel this would make for a faster workflow, don't you think? And maybe Michael might agree!

This removes the need for the What and Where fields, though it may disgruntle some other users, but I'm just sounding out what others think to gauge it's usage. I personally think, and I believe it's the whole ethos of MuLab, it's better to reduce clicks and searching at every opportunity and this approach does that. Soon as you click a What button, as in the above example, the Browser instantly shows the Where location, from there you can see straight away without having to click the Where field and select.

If this approach is implemented, there would need to be a 'Back' button to go up/back to the Parent folder.

[robert_p]

Ok, I need to go for lunch - I can't think clearly

[sl23]

Haha I haven't had breakfast yet! Think it's time now!

[Michael L]

maybe Michael might agree! it's better to reduce clicks and searching at every opportunity

It is quite interesting to see the different ways people use the Browsers!
But I am not interested in reducing mouse clicks.
Mouse clicks are like tiny steps on decision-making pathways.
When paced correctly, they help users make more efficient decisions.
OTOH, if too many decisions are grouped together in one step (e.g. What & Where), you need more mental bandwidth and time to decode all the options.

[robert_p]

I see your point Michael, but some users may make decisions even before creating a new project. Example:
I want my project to have a MIDI-programable drumkit, bass synth, percussion loop, two arp-synths, synth pad, lead and polysynth/keys, Two FX buses (reverb and delay) and a channel strip for each track + master bus. How do I do it quickly?

[Michael L]

How do I do it quickly?

Option A: set up a template with the FX buses and channel strips; put your synths in the same Category & use 'select next and drop again;' audition drumkits and loops using Preview Monitor.

[robert_p]

That's what I do (more or less) The difference is that I use Studio One's browser where I have access to my saved MUXes
---

List.jpg

[MuTools]

The "What + Where + Which" way to fill the browser list will be kept for now.

About the preset button labels: I propose that you can label them yourself, apart from the preset name. So you can use very short labels (even only a couple of chars) or longer ones.
If no explicit label is given the button will simply show the preset name.

I've also changed the way plugins are listed by enabling the "Where" field for plugins so that it can indicate a plugin category. So, for example, if you group all your EQ plugins into a "EQ" category you can then also add a browser preset button that says "EQ Plugins".

Here is an update preview how the browser may look:

[sl23]

Ok sounds good. Looking forward to trying it out!
Does it mean we can create buttons from the categories shown in the What field though? That was my reason for requesting this.