MU.LAB 3.1 test

[jpumphandle]

I like it you play the guitare solo on you're keyboard or is it composed with the mouse in the editor?

Just a bunch of midi licks put together from other midi files and tuned to 3 chords.

[Simon Posford]

Ok thanks for the info!

[MuTools]

The MU.LAB 3.1.3 test version is available in http://www.mutools.com/mulab/chestnut

What's changed:

• New: Audio To Note Gate module
• Tuned: Waveform display now shows the library name of the waveform (if any)
• Tuned: Waveform display now also features a drop down list
• Tuned: Waveform display supports subfolders within the waveform library folders
• Tuned: On opening/pasting waveforms, MU.LAB now uses a hi-quality resampler so to match the internal waveform size, instead of truncating/padding the loaded/pasted waveform
• Tuned: "Select Previous/Next Preset" shortcuts now also work for VST plugins
• Tuned: Finetuned audio recording setup panels
• Tuned: Audio Recorder: Replaced the "Level Threshold" by a global preference, so recorder setup panel is simplified
• Tuned: Event Monitor: Channel value now between 1..16 (was 0..15)
• Tuned: MIDI Input Focusses panel has 2 labels above the columns
• Tuned: Event Graph Editor: sometimes Parameters 1..16 are available when they were redundant
• Tuned: Event Graph Editor: When drawing a velocity line, then if there is a selection, only the selected events are affected
• Tuned: Optimized drawing of modular connections
• Tuned: When recording a new track, MU.LAB FREE/XT also give a proper alert if the newly recorded track(s) are outside the play limit
• Tuned: Shortcut list: Removed some redundant items
• Fixed: Sometimes the focus box was drawn improperly
• Fixed: Event Monitor showed blank pages
• Fixed: When Sampla editor was open and you deleted that sample, there was a graphical issue
• Fixed: In certain situations there was a little imperfection in the working of the ADSR
• Fixed: Sometimes an audio part was created even for silent audio recordings
• Fixed: On Open MuSession, the file ist showed all types of files

A full package install is required!

To use your current settings, copy your current Mulab/User folder to the new Mulab/User folder.

[Trancit]

The MU.LAB 3.1.3 test version is available in http://www.mutools.com/mulab/chestnut

What's changed:

[*]Tuned: Event Graph Editor: When drawing a velocity line, then if there is a selection, only the selected events are affected

That was for me

Thx very much...

Trancit

[pljones]

• New: Audio To Note Gate module

Cool! I was going to ask for something like this... actually, no, I was going to ask for an audio level tracker (i.e. Audio to Control with 0dBFS being +1 and -48dB (or whatever the current floor is) being 0) but this is good, too!

[MuTools]

I was going to ask for something like this... actually, no, I was going to ask for an audio level tracker (i.e. Audio to Control with 0dBFS being +1 and -48dB (or whatever the current floor is) being 0) but this is good, too!

I've thought about that, but there were technical difficulties. And i also reasoned that when you connect an ADSR to the gate out, you almost get the same practical result, even more parameterizable.

[pljones]

I was going to ask for something like this... actually, no, I was going to ask for an audio level tracker (i.e. Audio to Control with 0dBFS being +1 and -48dB (or whatever the current floor is) being 0) but this is good, too!

I've thought about that, but there were technical difficulties. And i also reasoned that when you connect an ADSR to the gate out, you almost get the same practical result, even more parameterizable.

True... I was thinking "crude vocoder", where the audio signal directly modulates some parameter on another sound or effect...

Is there an existing "Control to MIDI" module? That would be handy.

[MuTools]

Is there an existing "Control to MIDI" module?

How do you mean?

[pljones]

The ADSR envelope outputs a Control signal. Having control over Event Output would be nice (e.g. for an external unit). The "Control to MIDI" module would determine the MIDI Event type to create and what the Control affected (e.g. CC7 between 64 and 100).

[MuTools]

Dont want to be a nitpicker but just for the sake of definition, the green conections are called 'modulations', and lets preserve the word 'control' for MIDI controllers.

Besides that, i have this question: modulation signals are constantly changing, so at what resolution should the MIDI controller be sent out?

[robenestobenz]

Dont want to be a nitpicker but just for the sake of definition, the green conections are called 'modulations', and lets preserve the word 'control' for MIDI controllers.

Besides that, i have this question: modulation signals are constantly changing, so at what resolution should the MIDI controller be sent out?

I use these kinds of plugs a lot (VSTs though of course, as there's no audio>modulation module in MULAB yet). Well, if it's sending out a CC it would have the usual resolution of 128 discrete levels. If it was sending out non-MIDI modulation, e.g. to a Mulab module, I dunno. Couldn't it just use the same res as Mulab's built-in LFOs / ADSRs etc?

[*]Tuned: Audio Recorder: Replaced the "Level Threshold" by a global preference, so recorder setup panel is simplified

Yow! I use this all the time. At work right now so I can't test, but is there a shortcut to open up the global preferences menu where this option is now located?

[MuTools]

I use these kinds of plugs a lot (VSTs though of course, as there's no audio>modulation module in MULAB yet).

Well now there is the "Audio To Note Gate" module. Hook up an ADSR to that and you have what you want: audio level -> modulation envelope.

Well, if it's sending out a CC it would have the usual resolution of 128 discrete levels. If it was sending out non-MIDI modulation, e.g. to a Mulab module, I dunno. Couldn't it just use the same res as Mulab's built-in LFOs / ADSRs etc?

I thought some more about it, think the question is already answered, thanks.

[*]Tuned: Audio Recorder: Replaced the "Level Threshold" by a global preference, so recorder setup panel is simplified

Yow! I use this all the time. At work right now so I can't test, but is there a shortcut to open up the global preferences menu where this option is now located?

I asked about this twice here on the forum whether it would be ok to replace it by a global preference. No one responded so i finally concluded it was better to simplify the record audio panel.

You say you use it all the time. I don't understand. What's your workflow then? Why do you need this parameter all the time?

[pljones]

I thought some more about it, think the question is already answered, thanks.

Modulations... right, must remember that! Like I said, I'd expect it to be managed by the "Modulation to MIDI" module (that's too many "m"s...). I'd expect to see:

(MIDI Event Channel?)
MIDI Event Type
MIDI Event Value 1? [ ] (enable to modulate value 1, when disabled use Low value)
MIDI Event Value 1 Low value
MIDI Event Value 1 High value
MIDI Event Value 2? [ ] (enable to modulate value 2, when disabled use Low value)
MIDI Event Value 2 Low value
MIDI Event Value 2 High value

Of course, you would only have Value 2 available for certain MIDI Event Types.

Events would be emitted when the Value being modulated changed. So a sweep of the modulator from zero to one would generate 128 events at most.

Oh! Maybe have a "Sample and Hold" facility, too - add a "Wait" parameter so that the minimum time between events can be supplied.

[robenestobenz]

I asked about this twice here on the forum whether it would be ok to replace it by a global preference. No one responded so i finally concluded it was better to simplify the record audio panel.

You say you use it all the time. I don't understand. What's your workflow then? Why do you need this parameter all the time?

Sorry, I must have missed that.

Well, I've got a bunch of instruments I use thru the mic as well as the guitar via DI. They have varying volume levels, and I use them differently in terms of their prominence in songs - hence I change the recording threshold to control when recording kicks in.

It's mainly a substitute for punch-in/out recording really, so that I don't end up with unwanted leading audio to resize.

[MuTools]

Modulations... right, must remember that! Like I said, I'd expect it to be managed by the "Modulation to MIDI" module (that's too many "m"s...). I'd expect to see:

(MIDI Event Channel?)
MIDI Event Type
MIDI Event Value 1? [ ] (enable to modulate value 1, when disabled use Low value)
MIDI Event Value 1 Low value
MIDI Event Value 1 High value
MIDI Event Value 2? [ ] (enable to modulate value 2, when disabled use Low value)
MIDI Event Value 2 Low value
MIDI Event Value 2 High value

Of course, you would only have Value 2 available for certain MIDI Event Types.

I rather think of doing a specific "Modulation To MIDI CC" (MIDI CC, Minimum Value and Maximum Value). That's nice and simple. And without doubt the most used transformation, so it's good it's there out of the box.

Then apart from this we could (at some point in time) also add a generic MIDI event transformer, which could then be hooked up to that if you want.

And/or apart "Modulation To Aftertouch" and "Modulation to Pitchbend" modules, so to have instant modules for that, without the need to build it up.
(A "Modulation To Program" change really doesnt make sense, imho)

Events would be emitted when the Value being modulated changed. So a sweep of the modulator from zero to one would generate 128 events at most.

Yep, but maybe with a limited 'bandwith' of 1 MIDI event per millisecond, so to keep efficiency under control.

Oh! Maybe have a "Sample and Hold" facility, too - add a "Wait" parameter so that the minimum time between events can be supplied.

I would make a separate module for that, say a "Modulation Sample & Hold".

Nice ideas, damn i wish i could program 10x faster. (while staying relaxed feeling good, and enjoying life).

Ok, back to cool, added some notes on the WL.