MU.LAB 3.1 test

[MuTools]

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.

Oh, but it doesn't work like that.

The Minimum Recording Level only defines whether a recording is valid or not. If the whole recording stays below that Minimum Recording Level, then MU.LAB automatically disregards the recording. By default this is -48 dB, but it's a global preference which eventually can be overwritten.

[robenestobenz]

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.

Oh, but it doesn't work like that.

The Minimum Recording Level only defines whether a recording is valid or not. If the whole recording stays below that Minimum Recording Level, then MU.LAB automatically disregards the recording. By default this is -48 dB, but it's a global preference which eventually can be overwritten.

Ha, I had wondered at points when I didn't quite get what I expected. Good to know.

Is punch-in/out on the wishlist?

[MuTools]

If i read about your workflow, then i don't understand why audio rec punch in/out is so important.

If you make an audio recording, and you got some silence in the first part of the recording, then that's not a big problem, is it?

Eventually: Split the recorded audio part + delete the front silent part.

Please note i'm not saying that punch in/out is not something we want, but i'm always trying to do first things first i.e. the most important things first. And i don't see a big problem here. Or am i missing something.

[robenestobenz]

If i read about your workflow, then i don't understand why audio rec punch in/out is so important.

If you make an audio recording, and you got some silence in the first part of the recording, then that's not a big problem, is it?

Eventually: Split the recorded audio part + delete the front silent part.

Please note i'm not saying that punch in/out is not something we want, but i'm always trying to do first things first i.e. the most important things first. And i don't see a big problem here. Or am i missing something.

Well, it comes into play if you record quite a lot of takes, or sometimes have a great take with a bunch of ass in the middle that you'd like to dub over (as I do, because my playing stinks). Here, having to repeatedly snip the leading audio, sometimes the trailing audio too is quite annoying. I'd like not to do it, but if I leave trailing bits Mutools begins to stack tracks, which then leads to unmusical, maintenance type tasks anyway.

I don't expect it to be top of your priority list, Mulab's clearly foremost a MIDI host at the moment (and I don't mean that in a bad way, it's just there is a greater density of features on the MIDI/sequencing side of things), and I get the impression I'm much more reliant on audio than many of the users, at least here on KVR. Just wanted to know if it was on the holy wishlist.

[MuTools]

It's good to read about your workflow. Yes, sure i understand your points.

Added a note on the 'the holy wishlist'

[pljones]

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

I don't like to keep your life too simple..!

I think your ideas on this will be much easier to use - I was letting my "lazy programmer" side show...

[MuTools]

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

To update your MU.LAB 3.1.3, simply replace the current MU.LAB application file with this new application file.

What's changed:

• Tuned: Finetuned the Audio Compressor and Audio To Note Gate algorithms, resulting in a more prompt reaction time for fast attacks
• Tuned: When creating a new module in a modular editor, the module list now uses sub-groups instead of dividers
• Tuned: When resampling an audio file, a progress bar now appears
• Tuned: When having multiple audio recorders in a session, the main audio recording setup panel uses neatly aligned buttons now
• Fixed: When recording audio and Auto Normalize was off, audio file was recorded but no audio part was created
• Fixed: Bug in the audio file writer, only appeared in special cases
• Fixed: When changing presets in MuSynth, Mux, Synthia, etc. the rack slot/rack/track name was not refreshed

Normally this is the last test version before release, please be critical and report any issues. Thanks!

[MuTools]

To MU.LAB skin designers:

For detailed info on how to upgrade a MU.LAB 3.0 skin to MU.LAB 3.1 see http://www.mutools.com/mulab/chestnut/H ... ulab31.txt

[pljones]

(edit - this was 3.1.3)

OK, just tried the "zero input" test again and it didn't record. The "level too low" or whatever it says message appeared and disappeared before I could really read it. It probably should require user acknowledgement because it's probably an unintended condition.

I've just tried editing a Wav from a previous session in audacity. Just as audacity launches, the MU.LAB Wave editor gets "External Edit Mode" written across the display... Unfortunately, when I exit audacity (without saving), the message it still there. And won't go away (for that audio file).

[pljones]

(edit - let's try the right version...)

[Taron]

LooxHiQ skin causes a problem with the modular interface. Currently selected nodes won't display their connections. Other skins work fine.

[Simon Posford]

Thx for these infos jo i haven't noticed the new record.png

[paulhart]

When I start with your demo tracks (fine!) and "double-click" within each rack instrument to look at the settings, some come up with the name in the selection box, some don't. In 'Dream of the Piano#6,' Synthia (Double Bass) showed up, but Multisampla (Drumset)(Stand-In Piano), Stereo Echo, and MuVerb do not.
In Distant Moon#3, Sampla (Simpli) does, MultiSample (Stand-In Piano) does.
In MuJass Walking By#2, MuSynth (RealBass) does. You get the idea. It is uneven regarding which item, when clicked on will show the instrument that it is currently playing, initially. Once I go through the selection, it sticks, but in this case, I want to see what you are using, and clicking on the selection has the potential of inadvertently changing it, particularly as a "noobie" trying to understand how it works. I had commented on this earlier, but it might have gotten lost in the shuffle
Other wise, looks to be a fine upgrade.
Paul

[MuTools]

OK, just tried the "zero input" test again and it didn't record.

Can you please recall the context.

I don't rememeber what this "zero input" test is about.

The "level too low" or whatever it says message appeared and disappeared before I could really read it. It probably should require user acknowledgement because it's probably an unintended condition.

Do others agree? Should the "Recording Too Silent" message stay there until clicked?

I've just tried editing a Wav from a previous session in audacity. Just as audacity launches, the MU.LAB Wave editor gets "External Edit Mode" written across the display...

Automatically?

Was the audio file already loaded in MU.LAB?

Is this repeatable? What's the exact procedure?

Unfortunately, when I exit audacity (without saving), the message it still there. And won't go away (for that audio file).

In any case you can control the "external edit mode" status via the audio file's context menu -> Start/Stop Editing.

[MuTools]

LooxHiQ skin causes a problem with the modular interface. Currently selected nodes won't display their connections. Other skins work fine.

I see. Will be finetuned. Thanks!