MuLab 10

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

MuTools wrote: Sat Jun 07, 2025 7:04 pm Right-click the envelope editor -> Set Value Grid.
Is it possible to add a preference to set the default value grid? I use it a lot. It would be nice to be able to set it once.

Thanks.

Post

Quick thinking: I think this value grid depends too much on which type of value the envelope is for.
Note that once you set it for an envelope it's preserved of course, also after reloading the project/preset.

Post

But it just asks for the number of steps. It's really just about how granular you want to get regardless of the type of envelope value. If it snaps to a grid than that saves time. I find it really easy to unintentionally change the value of a point when creating or moving it.
You do not have the required permissions to view the files attached to this post.

Post

What i mean: For certain values a grid of 10 or 100 is more suited, for key-related values a grid of 12 is more suited, etc.

Quick tip: If you only want to change the time of a point, use the time field in the property panel below. Similar for value.

Quick tip 2: If you change the value grid often, add a shortcut key to that function.

Post

Yes, I understand your point. I generally use the same grid value for most of my automation. Often a lot of it is volume automation. Having the points snap to a grid is a lot of faster than having to manually adjust the values. I was doing that, along with copying and pasting values, before I discovered the grid.

Anyway, I can live with the way it is currently. Maybe this is of no interest to anyone else.

Cheers.
d.

Post

why's there's so much place reserved for notes and not for controller data?
can i put 2 or more lanes on this screen?
(it would help if the (name of the) editor you're actually in is displayed on the actual screen, no?)
2025-06-09 11_51_34-MuLab App _ Vermona Perfoumering-20250606-221759.jpg
You do not have the required permissions to view the files attached to this post.

Post

tiger001 wrote: Mon Jun 09, 2025 9:58 am why's there's so much place reserved for notes and not for controller data?
You can drag the divider line between notes area and controller area to make your preferred balance.

Post

indeed, but i still have so much screen for so little info/intel
if i reserve halve the screen for cont. data, i 'd like to see more controller lanes (at the same time)

Post

tiger001 wrote: Mon Jun 09, 2025 10:48 am indeed, but i still have so much screen for so little info/intel
if i reserve halve the screen for cont. data, i 'd like to see more controller lanes (at the same time)
+1 for this FR

Post

sl23 wrote: Tue May 27, 2025 6:32 pm Uhbik v2 has just been released, but no longer supports VST2, only VST3, and other formats.
This is going to become more and more common. Can we please have multi-VST3 support in M10.
Thank you.
Another bump for this one to be pushed up the priority list pls.

I've lost a few u-he plugins since moving to the CLAP versions and would like to use them in MuLab.

Thanks.

Post

Where do you inconsistency in the GUI?
"Inconsistency" = at one place is done this way, in another place it's done another way.

Or did you mean "inconsistent" related to your next point:
In Bitwig it's called the inspector panel, no matter what you select, a device, a clip, a plugin, it's functions and options are all available there, for everything... you don't always use it but when you need a function you'll find it there.
Well i invite you to be particular!
Please be specific about how you would like to improve certain GUI aspects in MuLab.
Adding screen mockups to illustrate it is even more helpful.
I'm curious about it given your design background.
Not that in contrast to some other DAWs i do prefer to keep a rather minimalistic GUI feel.
Too many GUI components give a bloated feel and distract musical inspiration which happens in the heart and soul, not on screen.
I did a quick mock up/critique of a few specific elements I found at quick glance, will post the image in following post (i don't know how to upload/imbed images mid post)
If you want to discuss this a bit more private, lets talk via email.
Your choice :)
Sure, I'm a bit flakey ATM but am happy to help where/if I can.
I'm sorry but this feedback is too vague for me.
Which drag-drop action is missing or not clear to you?
My thoughts on this were along the lines of everything (i know that's an absurd breadth) but I was thinking more of it as a UX paradigm in it's scope, like as a 'rule' the design would aim for all possible (within reason) ways this function could be implemented, in the same way that SurgeXT is a "right click" everything synth... I can pick at it if you wish, but I didn't specify as you may have other paradigms you're working towards, so it would be fairly redundant.
Please be specific, preferably with screen mockups.
3. Input Consistency
What do you mean with this?
Things like all buttons are consistent, the options cog is laid out consistently (see following post), Drag and drop is sweeping in it's implementation, things like dropping a wav file into the app (i know there's limitations because of it's portable nature, that's just 1 example) if it is limited to internal browser, tighten up the internal browser/expand it's usability and function... I limit this critique because it can be exhaustive, and quiet possibly pointless if you already have answers/alternatives for these ideas.

Anyway, I'll post my mockup/critique and you can see what I'm thinking.

Cheers, D.
You do not have the required permissions to view the files attached to this post.

Post

Round 2...
Figured i'd do what I can with the time I have ATM.

I hope this helps explain the UI consistency issues I mentioned.

Again let me say, this program is amazing, and I'm incredibly impressed... It's much easier to
sit on the sidelines and have opinions, and I hope my insights are clear and not any way taken as rude/offensive... I hope that my outside perspective helps in some way, but I in no way am expecting my insights to be legitimate without the inside knowledge that many things I talk about obviously need... It doesn't escape me that future plans and external factors/programming constraints may very well explain a lot of what I pick at, and I have no expectation of any suggestions aligning with future development, but I do have a very critical eye and have spent a lot of my life working on various design projects (some corporate UI work a while ago too in another life) so I thought I could help with a bit of that.

I know that a LOT more of what goes into UI is the burden of the engineer, and designers can often be very single minded (especially me :hihi: ) so please excuse if I at times seem too anal or difficult in my perspective, but years of hyper criticism in design (and audio production) can make you a little obsessive with the details :ud:

Again, AWESOME app, and from what I've seen of v10 it's SUPER impressive where it's going.
MuLab2.jpg
Cheers, D.

P.S... Email me if you need anything I might help with. :tu:
You do not have the required permissions to view the files attached to this post.

Post

Thank you viceverser!
I've bookmarked your last 2 posts and will surely reread them in detail soon.
It will be after the MuLab 10 release though.
I'll first continue the focus on finalizing the last steps towards release.
Currently working on the M10 promo launch video.
Talk soon on topic.
Thx :tu:

Post Reply

Return to “MuTools”