M4 Test

[Nielzie]

I have a tiny little last-minute request for change in M4.

Could the "MuTools -> "Factory" menu be folded out by default so the Instrument and Effects are straight availabe, same as in "Vst" menu?

I noticed it becomes a little tedious to have to click it open everytime I want to add a factory Instrument/Effect Device or preset.

The "User" menu may stay closed by default


Ohh and another one for a later version: it would be nice if the key that's been played on my midi keyboard would light up on the Piano Roll, to have a visual response to what I'm playing.

[MuTools]

Can you please give me a ultra detailed step by step how i can repeat it with M4.0.107 starting from a clean factory New.Musession. Sorry to ask, thanks in advance!

It's simple - create a new musession, import any audio file to any rack, press 'play entire file' and the sound will stop after the locator at Bar 1 in the default arranger.

Move any of the locators anywhere at all and the problem is fixed until the next session.

The MIDI-forget issue is pretty much a non issue IMO - wouldn't even have mentioned it if it hadnt been for the snazzy new startup dialogue. If it stays in MULAB forever I wouldn't be fussed.

Finally found it

Fixed in the next version.

[MuTools]

I have a tiny little last-minute request for change in M4.
Could the "MuTools -> "Factory" menu be folded out by default so the Instrument and Effects are straight availabe, same as in "Vst" menu?

You could increase the UseUnfoldedContextMenus preference, cfr http://www.mutools.com/mulab/docs/preferences.html

Ohh and another one for a later version: it would be nice if the key that's been played on my midi keyboard would light up on the Piano Roll, to have a visual response to what I'm playing.

It's on the wishlist.

[Trancit]

Jo,

is there a technical reason, why many modules are not available in the poly synth like the delay/echo modules???

Of course, some modules don't make any sense in the polysynth, but some would be helpful...

[MuTools]

Yes, only modules that can do polyphonics are available, cfr http://www.mutools.com/mulab/docs/polysynth.html

[Nielzie]

I have a tiny little last-minute request for change in M4.
Could the "MuTools -> "Factory" menu be folded out by default so the Instrument and Effects are straight availabe, same as in "Vst" menu?

You could increase the UseUnfoldedContextMenus preference, cfr http://www.mutools.com/mulab/docs/preferences.html

Ok I'll have a look at that, thanks.

Another feature request for a next version:
Being able to choose slider instead of knob, for MUX parameter GUI objects

[Bonteburg]

I recorded a MIDI sequence to find that a MIDI part wasn't created. The second try turned out to be more successful but the implications are quite startling ('that awesome one of a kind performance - lost forever').

I can't figure out what kind of user error it would have been - I could hear my synth (mda DX10 throughout) the recording, Event recording was enabled, I could hear the count-in and while I'm not sure if I had the track highlighted the first time round (is this even necessary anymore?), I did try record MIDI with no such preparations and it worked the second time.

Maybe I just plain didn't hit record but then I wouldn't have hear the count-in.

OSX 10.6.8

Edit: Interestingly, on closing the project, MU.LAB crashed. Crash Report is on it's way Jo!

[MuTools]

Maybe you accidently pressed [Esc] = Cancel after the recording when the name dialog is up?

About the crash: Is this repeatable? Maybe when using the same plugin(s)?

[Bonteburg]

I have a theory that it may have been me cancelling the recording because I got within a few pixels of doing it just now.

User error then... BUT - how about getting rid of the option altogether? It's odd now I think about it - if you don't like your recording you could simply delete it. Doing away with of the cancel option (presented to you before it even is a recording no less!) would greatly reduce the risk of undoable mistakes with no extra effort on part of the user imho.

What is everyone thinkig?


Edit: Yes Jo, you beat me to it. That may have been it (see above)

[MuTools]

I have a theory that it may have been me cancelling the recording because I got within a few pixels of doing it just now.

User error then... BUT - how about getting rid of the option altogether? It's odd now I think about it - if you don't like your recording you could simply delete it. Doing away with of the cancel option (presented to you before it even is a recording no less!) would greatly reduce the risk of undoable mistakes with no extra effort on part of the user imho.
What is everyone thinkig?

The good thing about that dialog is that you can give a name or cancel all at the same time, otherwise there are extra steps. So maybe this little dialog is more a worklow speed gain than a brake.

But also curious for other opinions.

[Bonteburg]

How about 'cancel' generates 'unnamed part01', 'unnamed part02' etc? Come to think of it - is there still 'turn auto-naming on/off'?

I agree the name-or-trash policy speeds things up but at a certain risk.

But yeah, it's more a personal preference I guess.

[Bonteburg]

I'll also try crashing MULAB with other synths than DX10.

[MuTools]

How about 'cancel' generates 'unnamed part01', 'unnamed part02' etc?

The 'cancel' options cancels the whole recording! Not only the naming.
That's why it's a speed up. Imagine you do a take, but it's not a good one -> [Esc] + [*] and there you are recording a new take

[Bonteburg]

No I meant to suggest it as a feature!

[MuTools]

I agree the name-or-trash policy speeds things up but at a certain risk.

The return key is much bigger and corresponds to OK