MuTools

TonyL · Post by **TonyL** » Mon Aug 11, 2008 5:58 pm

I'm trying to work through the johnnypumphandle tutorial on automation. I've added an automation sequence and drawn in the envelope and followed all of the other steps, including setting the controller to pan (lower left). This automation sequence is sent to Rack B as per the tutorial. Of course, audio output from Rack A is set to Rack B.

In rack B I've narrowed down the Stereo width. This is where things seem to go wrong. I double click on the Volume slider, bring up the 'Assign MIDI Controller' box and select Pan control source...then OK. The tutorial says uncheck the Global box but I don't see one.

Anyway, I OK out after setting the parameter to 'Stereo panning' as per tutorial and then play the MIDI sequence that controls the synth in Rack A. Audio plays from Rack A and via Rack B but no panning happens and the pan control in Rack B stays put unless I move it manually, in which case it works.

I've been messing with this for hours now. Any ideas what I'm doing wrong much appreciated.

infectedpimple · Post by **infectedpimple** » Mon Aug 11, 2008 6:25 pm

if this is mu.lab 1 you're having trouble with, make sure your automation sequence part targets the rack's mixer panel (from the "rack plugins" menu), as opposed to the rack itself. speaking of which, i haven't yet tested mu.lab 2, does anyone know, are some of these automation quirks improved any in the new mu?

TonyL · Post by **TonyL** » Mon Aug 11, 2008 6:49 pm

Thanks, I'm using Version 1.1 I just tried targeting the Rack B mixer panel after reading the other automation thread. Still no go. I'm stuck until I can get this sorted.

TonyL · Post by **TonyL** » Mon Aug 11, 2008 7:12 pm

Got it!

As well as the mixer strip issue (it says to target the rack itself in the tutorial)....

It also omits to mention that the part type has to be set to Automate. It justs says *rename* it to Automate, which I did. It also incorrectly says (and shows in a diagram) to select Pan as the controller in the lower sequence matrix. The correct selection is Stereo Panning. My effort now works.

Is this tutorial simply in error or has the implementation of automation changed since it was written ? <rant> Either way, I'm not a happy bunny about the time I had to spend on discovering something really basic. I wonder how many noobs like me have simply given up after a few hours of getting nowhere ? </rant>

Edited....Just to say thanks for your help I.P. and to say that MuLab rocks !

infectedpimple · Post by **infectedpimple** » Mon Aug 11, 2008 8:36 pm

Glad to help, I had similiar troubles early on--what really tripped me up was that you can record an automation sequence by just targeting the rack and fiddling with your cc knob or whatever, but it doesn't do anything when playing back. Like you, it took me a while, going many times over that same tutorial in fact, trying to figure out what the deal was. I guess that tutorial is relatively old now, speaking in terms of software years. Even with that figured out, though, more times than not I still find myself having to spend too much time ironing out various quirkinesses associated with the automation. In general it could be a lot easier to accomplish something as simple as a fade or a pan, and there's certainly a lot of room for it to get stronger in creating more complex automations, but it's still a work in progress and the developer is well aware of the critiques and expectations regarding this aspect of Mu.Lab. I've faith that it'll improve, because there's lots to love about Mu.Lab already, but I guess we just need be patient...

MuTools · Post by **MuTools** » Tue Aug 12, 2008 9:01 am

It's all about the proper target plugin.

If you record the movements of a single rack volume slider, then the resulting sequence-part will automatically target that rack volume slider.

However, if you record the movements of multiple rack volume sliders, then the resulting sequence-part will be set to no target as there are multiple targets in the recording.

Same issue when recording parameters of different plugins in a single take.

This could be confusing, i agree, and it's certainly something which will improve in the future.

Eclectronique · Post by **Eclectronique** » Mon Sep 15, 2008 8:39 am

Hi - I'm a Mu.Lab newbie, [although not a newbie to KVR - I just let my account lapse too long so I made a new sign-in -

]

i'm looking for a new sequencer and am kind of attracted by Mu.Lab - am trying out Mu.lab Free, v. 1.1 and wanted to see how it works with my Oxygen8 v2 k/b.
Where do I find the this automation tutorial you were discussing (Johnnypumphandle?!)? I'll read up on your comments on it too, so I dont get in too much of a mess

.
thanks
Matt

MuTools · Post by **MuTools** » Mon Sep 15, 2008 9:25 am

First of all, let me recommended using MU.LAB 2.0.

Although MU.LAB 2.0 still is in its test phase, it's already well tested and close to PreRelease.

You can download the MU.LAB 2.0 test version from

http://www.mutools.com/downloads.html

The tutorial you're looking for is at:

http://johnnypumphandle.com/johnny/tutor/MuLab.htm

Though this tutorial uses MU.LAB 1.1, most of it should still be relevant when using MU.LAB 2.0.

Eclectronique · Post by **Eclectronique** » Mon Sep 15, 2008 9:32 am

Great, thanks for such a speedy reply

Good support is a real luxury.
BTW - i hope it is not inappropriate or already in a thread I havent read, but what is the history M.z.s / Cm*s*c / LUNA, and now Mu.lab?
I used 2 of the former, and got real pleasure and good results out of them..

Sorry if that's awkward or difficult to answer.

*checking out the tutorials now - thanks a lot!*

MuTools · Post by **MuTools** » Mon Sep 15, 2008 10:40 am

Brief answer:

They're all products of the same developer.

Having started with products like I.M.S. for Atari and MBooM for Windows and classic Mac OS, Muzys was developed and became a very usable piece of software which was used in many releases.

CMuzys was a customized version for Computer Music.

After Muzys died a mystic death (an NDA prohibits more info), MUTOOLS is reincarnating the soul of Muzys into MU.LAB.

MU.LAB uses totally new technology which opens a lot of possibilities which were not available in Muzys.

LUNA was a previous name/version of MU.LAB. CMusic is a customized version of LUNA for Computer Music.

History timeline:

.... to 1999 : IMS
1999 to 2000 : MBooM
2000 to 2003 : Muzys, CMuzys
2005 to 2007 : LUNA, CMusic
2007 to .... : MU.LAB

Cheers!

Eclectronique · Post by **Eclectronique** » Mon Sep 15, 2008 11:32 am

After Muzys died a mystic death (an NDA prohibits more info),

I suspected the NDA from the way people were referring to the previous products

. Thanks for taking the time to go over that, I appreciate it, especially as a one-time user of M*z*s and Cmusic!
It's good to know the same brains are behind it.
And to have such quick replies -

I'll delve into v 2 and be sure to come back, it seems you do value and respond to feedback

PS - is there a thread where you deal with the possibility of TimeStretching in Mu.Lab?

MuTools · Post by **MuTools** » Mon Sep 15, 2008 12:18 pm

Eclectronique wrote:Is there a thread where you deal with the possibility of TimeStretching in Mu.Lab?

No, not such thread i know of.

Anyway, "time stretching" is on the whishlist. It may not be time stretching in the traditional word, i'm sure goal is to have "elastic beats" which auto-match the tempo. So that you can just drag and drop a drumloop into the composer and then the drumloop fits the tempo, right?

Eclectronique · Post by **Eclectronique** » Mon Sep 15, 2008 12:31 pm

that would work for me

So long as the analysis element was included for the user, (detect beats, add/remove markers etc), so I can use my homegrown loops not just Acidized ones or REX type files with the infos alread embedded.
I'm using Haxxor for this at the moment, which is a quick (and nice) workaround.

I've been looking for a new budget sequencer for a long time, I've tried so many demos, you wouldn't beleive it.

Here's my checklist for sequencer Must-Haves

- Quick workflow - CHECK!
- Easy on the eye - CHECK!
- Simple audio record - CHECK!
- VST instrument and Effect support - CHECK!
- Automation (external and internal) - CHECK!
- Not too expensive

- CHECK!
- Timestretch - ON THE WISHLIST!

it's looking good for Mu.Lab

MuTools · Post by **MuTools** » Mon Sep 15, 2008 12:58 pm

Note that with MU.LAB 2.0 you can already split up drumloops and play with the individual slices.

You just have to do some manual work, but that also has the advantage you have a lot of control.

Here is how to:

-> Goto File menu -> Add A Sample.
-> Choose a sample (note that each sample ca be previewed, also on the MIDI keyboard).
-> Once loaded, open the sample editor by double-clicking the sample display in Sampla.
-> Right-click in the timebar to add locators, as many as you want.
-> If you're done creating locators, right-click the sample editor background -> Sample -> Create Multisample Using Locators.
-> Now replace the Sampla by a MultiSampla (or just create a new MultiSampla if you want) and choose the new multisample you created in the previous step.

So now each slice is on a separate key and so you can play with the individual slices of your drumloop.

We'll further develop this technology in the future so that (most of) these steps will be automated.

But the good thing is: You can already slice up drumloops in MU.LAB 2.0.

Eclectronique · Post by **Eclectronique** » Tue Sep 16, 2008 7:52 am

But the good thing is: You can already slice up drumloops in MU.LAB 2.0.

Wow - that's Pretty Damn Good!

I'm kind of sold, i just need to do some audio recording to really check out that side of it.
Thanks so much.

btw is there a full feature list for v.2 ? I'm glad you docked the racks window into the arrange pane - tabbing around between windows was getting a bit annoying on v.1
Matt

MuTools

KVR Audio

Noobie automation problems