MuTools

MuTools · Post by **MuTools** » Sat Feb 13, 2010 4:31 pm

You can create a multisample out of a sliced sample via the context menu in the Audio Lab: "Create MultiSample Using Locators"

Bonteburg · Post by **Bonteburg** » Sat Feb 13, 2010 4:50 pm

Maybe we could have a "create x evenly spaced locators". MU.LAB wouldn't have to do any loop detection at all.

MuTools · Post by **MuTools** » Sat Feb 13, 2010 4:55 pm

Chance is rather low that such evenly spaced locators would properly match the drum slices, imho.

Jazz Franco · Post by **Jazz Franco** » Sat Feb 13, 2010 5:34 pm

mutools wrote:You can create a multisample out of a sliced sample via the context menu in the Audio Lab: "Create MultiSample Using Locators"

hmm
I only see 'create sample from selection'
Maybe looking in the wrong place?

MuTools · Post by **MuTools** » Sat Feb 13, 2010 5:36 pm

Then you're editing an Audio File.

This is not the same as a Sample.

The "Create Multisample..." function is only there when editing a Sample. (don't know why out of the head now, will check tomorrow <-> going offline now)

Jazz Franco · Post by **Jazz Franco** » Sat Feb 13, 2010 5:49 pm

mutools wrote:Then you're editing an Audio File.

This is not the same as a Sample.

The "Create Multisample..." function is only there when editing a Sample. (don't know why out of the head now, will check tomorrow <-> going offline now)

Found it now. It's not in the audio editor, but in the Sampla sample view, actually.

fceramic · Post by **fceramic** » Sat Feb 13, 2010 5:53 pm

Could I please join the beta of M3? Maybe it works better for me?

pljones · Post by **pljones** » Sat Feb 13, 2010 6:23 pm

fridtjof wrote:Could I please join the beta of M3? Maybe it works better for me?

I'm sure you mean "Maybe the way I use MU.LAB will find errors no one else has found, making the final product even better".

fceramic · Post by **fceramic** » Sat Feb 13, 2010 6:42 pm

My setup will be M3's ultimate test! Muahahaha!!

MuTools · Post by **MuTools** » Sat Feb 13, 2010 7:03 pm

Feel free to test MU.LAB 3: http://www.mutools.com/mulab/azalea

If you did not yet install MU.LAB 3, simply go for the full package, i.e. ignore the mulab-...-patch.zip

Note that this version does not yet include the note-off strategy change. A new test version will be distributed soon in this same webfolder. Watch this forum topic.

If you encounter any bugs or difficulties, please report here or mail me, thanks!

jpumphandle · Post by **jpumphandle** » Sat Feb 13, 2010 8:43 pm

Noticed a few things in 3.20 ...

In the List Editor, when deleting the top item, the next item is not automatically highlighted for editing as in the past. This forces an extra mouse click or down arrow to get to the next item.

When saving a session, it does not appear to save the zoom settings. When loading the session again, the zoom is back to the default.

bpblog · Post by **bpblog** » Sat Feb 13, 2010 9:21 pm

here's the vocoder research report. as i suspected, external vocoding does work properly in mulab. it was just me having a dumb moment.

but i've figured it out now. vocoder plugins like mda Talkbox and TAL-Vocoder don't show multiple audio inputs in the MPA, but they do need two inputs, one for the carrier and one for the modulator. to make this work, route your voice or whatever to one rack, and a synth of some kind to another rack. pan one rack hard left and the other one hard right. load mda Talkbox in a third rack. now make that rack the audio output for the first two racks.

KONNICHIWA ROBOTO!

MuTools · Post by **MuTools** » Sat Feb 13, 2010 11:07 pm

jpumphandle wrote:In the List Editor, when deleting the top item, the next item is not automatically highlighted for editing as in the past. This forces an extra mouse click or down arrow to get to the next item.

The list editor behaviour indeed has changed a bit here and there.

It now works more in the same way of other editors.

Previously, the highlighted cursor and the selection were two separate things. Now it's the same i.e. the highlighting is the selection.

In the piano roll, when you delete a note, then the next note is also not selected. Well in the list editor it's the same.

Question is: Why would you like to have the next event selected when you delete an event?

If you want to delete multiple events at once, then select them all and press [Delete] a single time.

OK?

When saving a session, it does not appear to save the zoom settings. When loading the session again, the zoom is back to the default.

Improved in the next version.

Bonteburg · Post by **Bonteburg** » Sat Feb 13, 2010 11:14 pm

mutools wrote:Chance is rather low that such evenly spaced locators would properly match the drum slices, imho.

not if you (the user) makes sure that it's actually a 2, 4, etc. bar loop. That's what I meant, it would make things easier for MU.LAB because it'd be the user's responsibility to feed it properly trimmed raw material to begin with (as will be the case 99 per cent of the time when doing mixdowns).

NBV · Post by **NBV** » Sat Feb 13, 2010 11:33 pm

I am currently working on a non-commercial album for the http://www.rpmchallenge.com and my purpose is to test M3 in a "real"
musical production context.

The first tracks of the project were created using Mu.Lab 2.7. Today I was opening them in M3 and saving the M3 versions, and here are some comments after performing that task.

1. Good thing: does not quit automatically when an error occurs while scanning VST plugins.

2. Minor detail: when audio driver is changed from the audio setup dialog, composer view automatically zooms out completely.

3. When a saved session is re-opened, it is automatically zoomed out.

4. Vertical zoom-in in composer view is very limited.

5. good thing: muted tracks turn grey.

6. Multi-out plugins in the MPA adds for more flexibility on the side of the user. Good choice.

Regards.

MuTools

KVR Audio

M3 Tests