MuTools

MuTools · Post by **MuTools** » Sun Mar 13, 2011 3:08 pm

MU.LAB 3.2.14 has been pre-released.

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

Full Package:

OSX: http://www.mutools.com/mulab/mulab-3-2-14-osx.zip
Win: http://www.mutools.com/mulab/mulab-3-2-14-win.zip

Application Patch:

http://www.mutools.com/mulab/patch

Although this new version has been tested, it might need some more testing in all kinds of setups and situations. If you encounter anything odd, please let me know!

MuTools · Post by **MuTools** » Sun Mar 13, 2011 3:25 pm

Some more info about the finetuned MIDI controller mapping:

When you map a MIDI controller to a parameter (module/parameter context function), this will now work in all cases, both for MIDI input as for sequenced controller events.

This has been requested many times, sorry it took so long before implementing this. Initially this was planned for M4, but now it's here in M3 already.

Also the confusion between the global session controller map and the module controller map should have been gone now. These two different controller maps still exist, but everything is more separated and cleared out.

The 'Session MIDI Input Controller Map' (main EDIT menu) is only about MIDI Input, not about sequenced controllers. It's a performance feature.

The 'MIDI Controller Map' for each module is active all the time, i.e. also applied on sequenced controller events.

Hope everything is clear and works smooth now and will further increase your musical workflow!

Simon Posford · Post by **Simon Posford** » Tue Mar 15, 2011 1:08 pm

Applyed the patch no issue for now.
By the way congrats for :
More smooth level meters.
It's awesome more accuracy than Ableton Live !

robenestobenz · Post by **robenestobenz** » Tue Mar 15, 2011 2:51 pm

I'll check this when I get home, it already sounds much clearer.

pljones · Post by **pljones** » Tue Mar 15, 2011 6:43 pm

A little OT but brought up by playing with the patch... I'm not sure if this a "dumb question" or a "feature request". Why doesn't the rack target have "bypass rack entry N" options as MIDI targets? I can see how to use MIDI to mute the mixer strip, just not bypass rack entries, which would be really handy.

Another question: if I have Ctrl#22 set up as a mapping on a module (Kjaerhus Classic Limiter), controlling a parameter (Level) and adjust the value, should the module's UI be updated to track the parameter change?
-edit-Oh, it's working now. I needed to go into the UI and back out again.-/edit-

MuTools · Post by **MuTools** » Wed Mar 16, 2011 12:54 pm

pljones wrote:A little OT but brought up by playing with the patch... I'm not sure if this a "dumb question" or a "feature request". Why doesn't the rack target have "bypass rack entry N" options as MIDI targets? I can see how to use MIDI to mute the mixer strip, just not bypass rack entries, which would be really handy.

I'm not sure what you mean here, can you please elaborate.

Another question: if I have Ctrl#22 set up as a mapping on a module (Kjaerhus Classic Limiter), controlling a parameter (Level) and adjust the value, should the module's UI be updated to track the parameter change?
-edit-Oh, it's working now. I needed to go into the UI and back out again.-/edit-

Isn't that a Kjaerhus Classic Limiter issue. Normally when you change a VST parameter (directly or via a mapped MIDI CC) the VST editor should redraw the parameter knob. I check with Dune demo, all fine there.

pljones · Post by **pljones** » Wed Mar 16, 2011 8:07 pm

mutools wrote:
pljones wrote:A little OT but brought up by playing with the patch... I'm not sure if this a "dumb question" or a "feature request". Why doesn't the rack target have "bypass rack entry N" options as MIDI targets? I can see how to use MIDI to mute the mixer strip, just not bypass rack entries, which would be really handy.
I'm not sure what you mean here, can you please elaborate.

When you right-click a rack-slot, there's "Toggle Process OFF|ON". I wanted this to be available in the parameter list for the Rack itself - i.e. "bypass rack entry (1-6)" - so that it could be controlled through a MIDI mapping.

I've just realised the shortcut system is what's intended to handle this... but on trying it, that also didn't let me pick which rack slot I wanted to control, just what command. I couldn't work out a way that, without worrying about what else is going on, I could just hit a button my external controller to toggle processing off/on. (I can mute using the mixer strip but that doesn't save the CPU.)

MuTools · Post by **MuTools** » Wed Mar 16, 2011 10:43 pm

pljones wrote:
mutools wrote:
pljones wrote:A little OT but brought up by playing with the patch... I'm not sure if this a "dumb question" or a "feature request". Why doesn't the rack target have "bypass rack entry N" options as MIDI targets? I can see how to use MIDI to mute the mixer strip, just not bypass rack entries, which would be really handy.
I'm not sure what you mean here, can you please elaborate.
When you right-click a rack-slot, there's "Toggle Process OFF|ON". I wanted this to be available in the parameter list for the Rack itself - i.e. "bypass rack entry (1-6)" - so that it could be controlled through a MIDI mapping.

FYI: The Process On/Off switch is not an automatable parameter. It can't be 'mapped' to a MIDI controller.

I've just realised the shortcut system is what's intended to handle this... but on trying it, that also didn't let me pick which rack slot I wanted to control, just what command. I couldn't work out a way that, without worrying about what else is going on, I could just hit a button my external controller to toggle processing off/on. (I can mute using the mixer strip but that doesn't save the CPU.)

You could indeed make a MIDI shortcut to the "Toggle Process On/Off" function, and that will work when a module editor is open, and also in other case, but you're right that the individual rack slots currently can't take the GUI focus and so in that case the shortcut won't be resolved. Individual GUI focus for the rack slots (so that shortcuts work) is on the wishlist.

pljones · Post by **pljones** » Thu Mar 17, 2011 8:42 am

The thing is, to make it useful, it needs to be automatable. Having to worry about UI focus defeats a lot of the benefit of binding UI controls to a MIDI controller.

Oh... of course, I couldn't do that in the Session map, it would have to be a mapping specific to the rack, as they're plugins...

MuTools · Post by **MuTools** » Thu Mar 17, 2011 9:38 am

pljones wrote:The thing is, to make it useful, it needs to be automatable.

The process on/off switch is not an automatable thing and it's not planned to be because of technical reasons, but also:

If you want the musical effect of sequencing a bypass on/off, then simply use a MUX, setup a bypass scheme, and automate the relevant parameter in there.

If you're concerned about controlling the CPU usage, then i think it should not be your concern as a musician but the concern of MU.LAB i.e. MU.LAB must automatically stop processing plugins that are not used. If you think that's not the case then lets focus on these cases as it must work.

The Kob · Post by **The Kob** » Sat Apr 02, 2011 10:45 am

"The process on/off switch is not an automatable thing and it's not planned to be because of technical reasons, but also:"

shame, this is something i occasionally wish i could do for effects resaons

pljones · Post by **pljones** » Sat Apr 02, 2011 6:53 pm

mutools wrote:If you want the musical effect of sequencing a bypass on/off, then simply use a MUX, setup a bypass scheme, and automate the relevant parameter in there.

I don't call that "simply", really. How much overhead would it be for that scheme to be present in each slot of a rack and have the parameter available to automate? (For those not wanting the overhead, simply don't use the rack.)

MuTools · Post by **MuTools** » Sun Apr 03, 2011 1:23 pm

The Kob wrote:"The process on/off switch is not an automatable thing and it's not planned to be because of technical reasons, but also:"

shame, this is something i occasionally wish i could do for effects resaons

pljones wrote:
mutools wrote:If you want the musical effect of sequencing a bypass on/off, then simply use a MUX, setup a bypass scheme, and automate the relevant parameter in there.
I don't call that "simply", really. How much overhead would it be for that scheme to be present in each slot of a rack and have the parameter available to automate? (For those not wanting the overhead, simply don't use the rack.)

pljones, you're absolutely right, sorry for my 'simple' expression

I understand what you guys want and have added a note on the wishlist.
(That's not the M4 wishlist though, too late to plan this in in M4, sorry)

pljones · Post by **pljones** » Sun Apr 03, 2011 4:20 pm

mutools wrote:I understand what you guys want and have added a note on the wishlist.
(That's not the M4 wishlist though, too late to plan this in in M4, sorry)

Thanks! I can wait. I'll keep on watching to make sure things are simple, too

.

MuTools

KVR Audio

MU.LAB 3.2.14 pre-released