MU.LAB 3.2 released

[MuTools]

MU.LAB 3.2 has been released and is available via http://www.mutools.com/downloads.html

What's new in MU.LAB 3.2: http://www.mutools.com/mulab-change-log.html

Enjoy Making Music!

[sorohanro]

Cool.

[TheGuysanIdiot]

MUTOOLS Web site

Products page needs to be updated to read 3.2

Still mentions 3.1

(and the "MU.LAB 3.1: Highlights" page etc.)

OZ

[MuTools]

Updated

[MuTools]

A MU.LAB 3.2.3 patch is available in http://www.mutools.com/mulab/patch

What's changed: http://www.mutools.com/mulab-change-log.html

[pljones]

Minor glitch:
I just changed audio driver in 3.2.3 from my Echo ASIO driver to ASIO4ALL. Control Panel then correctly let me edit the ASIO4ALL options. However the (MU.LAB) Inputs and Outputs were still labelled up with the old Echo driver's labels, rather than those from ASIO4ALL. Clicking OK to exit the Audio Setup and going back in sorted it out.

[pljones]

Question:
Should right-click on the target module icon on a track pop up the target module menu or the track menu? At the moment, it's the target module menu. It's a little bit confusing and perhaps unnecessary? (Right-click everywhere else on the track header brings up the same menu. If you set track target to per part, there's then a "dead spot" where no menu appears.)

[MuTools]

Minor glitch:
I just changed audio driver in 3.2.3 from my Echo ASIO driver to ASIO4ALL. Control Panel then correctly let me edit the ASIO4ALL options. However the (MU.LAB) Inputs and Outputs were still labelled up with the old Echo driver's labels, rather than those from ASIO4ALL. Clicking OK to exit the Audio Setup and going back in sorted it out.

Taken note, will check, thanks.

[MuTools]

Question:
Should right-click on the target module icon on a track pop up the target module menu or the track menu? At the moment, it's the target module menu. It's a little bit confusing and perhaps unnecessary? (Right-click everywhere else on the track header brings up the same menu. If you set track target to per part, there's then a "dead spot" where no menu appears.)

Currently it's intended behaviour.

Icon = target menu
Track name = track menu
When no track target, then no target menu, that's consequent, imho.

I'm just talking about the current situation.
Not about possible future developments.

[robenestobenz]

Dunno when this was implemented, but I selected some audio in a part from right-to-left and was this time rewarded with the selection of exactly what I wanted instead of the frustration of having forgotten L-R only yet again! Lovely.

[bpblog]

is anyone else experiencing slowdowns as the project grows?

i can't exactly pinpoint what's going on in my case, but with each of my projects, after creating a few different sequences, a couple of audio files and just a few vst plugins, mulab becomes a bit less responsive. for example, after clicking a sequence, it takes a short (less than a second, but still noticeable) while until the sequence is highlighted. same thing with expanding the racks after they have been clicked, etc. and as the project grows, this delay time seems to grow.

i will investigate this weekend and try to make a more detailed report, but i'm just curious atm if anyone else is getting this kind of behavior in their mu.

[TheGuysanIdiot]

Hi bpblog,

I have not had problems like you yet but that is not to say you are not having problems.

EDIT (I have removed my issue as it was PC specific and solved)

OZ