MuLab 10

[4u610h346]

Which UI aspects in MuLab 10 are distractive for you, and thus less good than earlier MuLab versions?

I wouldn't go so far as to say, "less good". But, I'm glad you are earnestly seeking input.

Also, I am a picky user. That is why MuLab is home. For example, when I am on Linux, I use Evilwm and a Terminal for my Desktop. After booting into the graphical session, I have used only 24 to 50 Mb of system memory. My initial "proclivities" would not be appropriate for MuLab. But there is a modest DIY essence to some of MuLab; and it isn't ridiculous with graphical audio jacks on the back of a rack stack. I love it.

I'd like to build and Iron out a few tracks, before I think I'd trust too much input as completely constructive (from me). That way I can think about the rational and benefit towards MuLab; and not just me. Since you are looking for "useful" input, I'll be thinking about it as I grind. I'm currently working on other projects, that are not my own (nor my own gear/software of choice).

New MuLab is Better! After my time away, it seems just as performant (compared to much earlier versions). It is busier (UI); as can be expected, since I came from v4.5. My preference for the older version(s), so far, is out of adaptation (not much needed). Once sifted out, we'll see if I can provide the goods.

I'm hoping I can generate some creative ideas, for you. But I certainly don't want to over season the stew.

[4u610h346]

Hey Jo, ignore this if the layered layout idea was just stupid. Ignore it even more, if you haven't read that input yet. I take back not logging on often enough to converse about it. It seems important enough, to make the effort. I would gladly take correction, if I am wrong.

I just couldn't bare leaving the idea of tabbed selection. It just really bothered me. Of course, I have no perfect idea; but maybe a better one.

I think the tabbed idea suggested too much change, not that you got that out of it. I was thinking about the toggle, to switch back between Mux and Composer. Since in the larger idea, I'm talking about alternative composers, the existing toggle seems appropriate.

So the opened item/module windows, whatever the mixture be, could be snap shot to a layout. Maybe positions fine tuned afterwards, but the initial locations as exemplary. Honestly, i wouldn't care if it always just looked like open windows over Mux. But I image a composer backing would just look cleaner. So, you could switch between the layouts, and then always at anytime toggle back to the Mux. I'm just wondering if the snap shots would be best placed in the minimize bar. That is still somewhat akin to the tabbed idea; but making it clear that it isn't a tabbed interface, like a web browser (yuk).

If no snap shot exists, and no composer, the toggle just closes and re-opens the windows as they were.

I hope I haven't underestimated what MuLab can already do. If this already exists, I'm may just video myself with a face palm, so everyone can enjoy that instead.

[TorresBob88]

I think the UI is just fine. In the general aesthetic sense. I've attempted to try other DAWS for years, and this is the first one that I felt "comfortable" with. That immediately looks like fun to learn and use, where almost any other DAW that I've tried or looked at looks more like a chore.

So I can see how the fun "toy" look, would be unusual to people who are used to the industry
standard of switches and levers and menu's all over everything. But its also what makes MuLab unique. Every other DAW does that, MuLab is the only thing that offers an alternative to it.

[TorresBob88]

When I'm tinkering around in a MuDrum, and I'm in the pad window, sometimes I'll hit the "save" button, but I'm actually trying to save the entire MuDrum, but I'm concentrating on the sound and it slips my mind what window I'm selected in. So now it will give me the option to either, "Keep as is" or "rename this Mux Modular", but I dont actually want to do either of these things, I just hit the wrong button.

But there is no cancel option, I'll have to go into Task manager and kill MuLab to cancel the action.
I would add a cancel option there in Mu 10.

[4u610h346]

I would add a cancel option there in Mu 10.

What happens if you press the Escape key?

[TorresBob88]

What happens if you press the Escape key?

That doesn't work.
Although interestingly, in my attempt to test that, it doesn't always do that.
If the pad is "un-named", in the title bar window, its just blank, it doesn't bring up the "rename" dialogue.

So its a specific situation.
But backing out of it should be selectable in the pop up window IMO.

I dont use shortcuts at all.
I need everything ether visual, or by ear.

[mfkne]

ARA Implementation would be VERY appreciated.

[TorresBob88]

ARA Implementation would be VERY appreciated.

What is ARA, so that we can all get prepared for it.

I think dragging and dropping presets would be a super workflow enhancement.
Which we can do, if the Vst is already in, for Vst2.

But I could have sworn that somebody said that some Daws can just load the Vst, FROM the preset. Which makes sense, Fxp's do have an instrument ID code in them. So that I could just browse my presets folder for inspiration, drag it into MuLab, and it loads up the Vst ready to go.

THAT would be magical!

[TorresBob88]

I dont know if its irrelevant to everybody else,
but you know the panel section at the bottom of the instrument lanes,
where you set the volume or velocity of the midi-notes?

Well when I turn some notes down to zero, to silence them, to try variations in a sequence,
I can spend 30 seconds trying to make the pencil-tip grab the turned down note again, to turn it back up.

How do other DAWS handle that?
I was imagining that maybe a long'ish swipe up above it, could grab it?
Or maybe turning it all the way down, leaves a small visible "cap",
at the top of the volume indicator stripe, that can be grabbed.

Or maybe just make the "recognition" area larger,
so that you can just click underneath the bottom line of the panel and be able to grab it.

[Michael L]

ARA Implementation would be VERY appreciated.

What is ARA, so that we can all get prepared for it.

ARA enables compatible sample editors to act like part of the DAW

Melodyne, Izotope RX, AutoTune, SpectraLayers, WaveLab, AutoAlign, VocAlign, Acoustica, Revoice, RePitch and IRCAM ASAP exchange detailed audio data with the DAW: note, chord, tempo, pitch, etc. You can edit clips or tracks across the project, and click to move between editor and DAW views without a 'transfer' process.

This is how it works with Melodyne:
https://helpcenter.celemony.com/M5/doc/ ... awsWithAra

Cubase, ProTools, Reaper, Logic, S1, Waveform use ARA.
Live, Bitwig, FL Studio, Renoise, Reason do not.

Would you use one of those ARA-compatible audio editors in MuLab

[Michael L]

I can spend 30 seconds trying to make the pencil-tip grab the turned down note again

Yeah that’s true
You can drag the Time, Length,Velocity or Length window in the property panel.
It gives fine control; even finer with Cmd+drag.
It’s also a way to move notes between grid lines

[MuTools]

I dont know if its irrelevant to everybody else,
but you know the panel section at the bottom of the instrument lanes,
where you set the volume or velocity of the midi-notes?

Well when I turn some notes down to zero, to silence them, to try variations in a sequence,
I can spend 30 seconds trying to make the pencil-tip grab the turned down note again, to turn it back up.

How do other DAWS handle that?
I was imagining that maybe a long'ish swipe up above it, could grab it?
Or maybe turning it all the way down, leaves a small visible "cap",
at the top of the volume indicator stripe, that can be grabbed.

Or maybe just make the "recognition" area larger,
so that you can just click underneath the bottom line of the panel and be able to grab it.

Even if velocity is 0 there still is a visible clue of that note event.
Indeed not enough to comfortably drag it, but enough to lasso select it and then use the properties panel at the bottom left to increase the velocity numerically.

If you want to silence notes, better to mute them.

[nenneb]

You also may want to use the "Logical Selector":
Equal=note / value2=lower 2.0
will do the job!

Btw @Jo: In this Logical Selector I still miss "time-position WITHIN a BAR" to select all one's or three's ...
Overall time-position seems quite useless to me, as it appears only once in a song ....

[TorresBob88]

If you want to silence notes, better to mute them.

Aha, that had me befuddled in the right click zone for a minute,
but that must be what the "M" button is for.

M.png

Very good. That helps and is actually a better way to do it.
Thanks.

[TorresBob88]

I've noticed that sometimes when I'm testing a new VST3,
just dropping it in from the desktop. And then if I move that VST3,
if I decide that I like and move the location into my proper VST folder,
MuLab will give me an error, "Couldn't create VST3 instance for*"

Its a simple fix, you just have to go into Plugins Manager and delete the reference to it,
and drop it back in. Or rescan it. But I've tried "rescan all known" and it doesn't necessarily catch it without deleting it first.

Its a minor issue, but maybe you could tweak that so that it can automatically update the location,
just to save somebody some minor frustration figuring it out.