M3 Tests

[bpblog]

MP3: http://www.mutools.com/mulab/examples/V ... 100209.mp3

aha! so you're playing with vocoders instead of working hardly on m3? well, nice going jo, that's all i can say...

I don't think you have to do something special regarding the inputs. It works fine here out of the box using TAL Vocoder in MU.LAB 3

but have you tried using it external mode? for example talking in a mic and playing on an external synth at the same time, so that voice is the carrier, and an external synth is the modulator? i think that TAL-Vocoder has this feature, actually i'm pretty much sure because there's a button on a gui that suggests it: http://i47.tinypic.com/23m6bo2.png

Zipped MuSession: http://www.mutools.com/mulab/examples/V ... 100209.zip
The session needs "TAL-Vocoder.dll".

another strange thing is that i can't open your example session. i tried M3.0.18 with TAL-Vocoder installed.

anyway, i must add that it's quite possible that it's just me who is doing something completely wrong or not understanding how to set these sweet vocoders up in Mulab, and i'm also mega tired now which isn't helping at all. so, i will go in-depth tommorow and try to setup TAL-Vocoder and mda Talkbox in external modes and come back with proper reports.

Yes.... it was a workflow step that I tolerated but never really saw the point of in Mulab.

+1

this will be a sweet improvement.

[gemada]

Question:

When pasting parts or events, the paste position is defined by the snapped mouse position in the editor.

But a popup dialog appears where you can still edit that paste position.

I would like to remove this popup dialog so that pasting immediately occurs at the snapped mouse position.

Then pasting would work exact the same way as e.g. splitting parts, which works fine now.

By removing the popup dialog, we get a more streamlined workflow, i think.

Do you agree?

Hi Jo.
I completely agree

[MuTools]

but have you tried using it external mode? for example talking in a mic and playing on an external synth at the same time, so that voice is the carrier, and an external synth is the modulator? i think that TAL-Vocoder has this feature, actually i'm pretty much sure because there's a button on a gui that suggests it: http://i47.tinypic.com/23m6bo2.png

It works too.

Though i encountered a panning issue. I'm too tired now to research it in depth. To be continued tomorrow.

Zipped MuSession: http://www.mutools.com/mulab/examples/V ... 100209.zip
The session needs "TAL-Vocoder.dll".

another strange thing is that i can't open your example session. i tried M3.0.18 with TAL-Vocoder installed.

Oops, i'm sorry, the session was made with M 3.0.19 which has a little change in the MuSession file format. So i guess you had a "Session made with newer version" alert, right?

I've refreshed the session zip file, now it's 3.0.18 compatible

Here is the link again:
http://www.mutools.com/mulab/examples/V ... 100209.zip

[MuTools]

MU.LAB test 3.0.19 is available in http://www.mutools.com/mulab/azalea

What's changed: http://www.mutools.com/mulab/azalea/mul ... hanges.txt

If you've not yet installed MU.LAB 3.0.16, then it's best to install the full new package. Then if you want to keep your current MU.LAB settings, copy everything in your current Mulab/Settings folder to the new Mulab/Settings folder before using the new MU.LAB.

If you have already installed 3.0.16, then you can simply apply the newest application patch.

[MuTools]

I've updated the examples using the TAL vocoder.

There are 2 examples:

1) Using TAL's built in synth to generate the carrier sound:

Mp3: http://www.mutools.com/mulab/examples/V ... 100209.mp3

MuSession: http://www.mutools.com/mulab/examples/V ... 100209.zip

2) Using the MuSynth to generate the carrier sound:

Mp3: http://www.mutools.com/mulab/examples/V ... 100210.mp3

MuSession: http://www.mutools.com/mulab/examples/V ... 100210.zip

As you can see, it's even possible to do it using racks only, no special routing in the MPA needed.

Cheers!

[Nielzie]

As it looks like M3 is getting pretty stable now, are there any things on the wish list you're planning to implement before M3 will be released as final or will you have a "new feature-stop" until 3.0 is released?

[MuTools]

The latter.

[MuTools]

MU.LAB test 3.0.20 is available as a patch in http://www.mutools.com/mulab/azalea

This patch quick fixes: Drive letters weren't visible in file browser

[toxicoh]

The only feature I'm REALLY missing is the audio editor.

I'm using Audacity on my iMac. It works, but it would be much cooler to do this within MuLab

[sorohanro]

Well, some basic editing features are available also in Mu.Lab, just double click on the sound file in the sequencer and it will bring up the sound editor.

[Jazz Franco]

Played a little with M3 last night, few impressions.
New integrated 'all in one' synth/sampler designs is fantastic! Very handy. And the new presets handling system for both VST and native synth/fx is OK. I'd only propose adding the old-school 'choose files from OS inteface' option to add files to MultiSampla -- in OSX (at least on my machine) drag-n-drop turns to be a little painful, as the zone editor keeps disappearing under the main interface.
Like some other ppl above I also miss the sample editor with some crude autoslice option, as it was in Muzys/CMuzys. Sure, it didn't have all modern bells and whistles, but could be used to create rather cool cracky beats (imo).
Unfortunately, still no support for multi-out plugins Which is a shame, considering the modular possibilities.

[MuTools]

Unfortunately, still no support for multi-out plugins Which is a shame, considering the modular possibilities.

You can use multi-out VSTs, no problem!

But the way to do it has changed compared to M27.

Simplest way to do use multi-out VSTs in M3 is plug the VST into the MPA and there you have all outputs available, you can route them as you want

If you want to integrate a multi-out VST within a rack, then you could plugin a MUX in the rack, then plugin the multi-out VST into the MUX, and then do the submixing within that MUX

Both ways are OK, it depends a bit on what you exactly want to do i think.

[MuTools]

in OSX (at least on my machine) drag-n-drop turns to be a little painful, as the zone editor keeps disappearing under the main interface.

Yes, i noticed it too. Will research this and try to finetune this.

Like some other ppl above I also miss the sample editor with some crude autoslice option, as it was in Muzys/CMuzys. Sure, it didn't have all modern bells and whistles, but could be used to create rather cool cracky beats (imo).

You can slice up a drum loop in the Audio Lab and create a multisample of it. The only difference with muzys is that muzys had a slice-detector, in MU.LAB the locators (still) need to be created manually, but the good thing about that is that chance is higher that they're placed more accurately.

[Jazz Franco]

Unfortunately, still no support for multi-out plugins Which is a shame, considering the modular possibilities.

You can use multi-out VSTs, no problem!

But the way to do it has changed compared to M27.

Simplest way to do use multi-out VSTs in M3 is plug the VST into the MPA and there you have all outputs available, you can route them as you want

If you want to integrate a multi-out VST within a rack, then you could plugin a MUX in the rack, then plugin the multi-out VST into the MUX, and then do the submixing within that MUX

Both ways are OK, it depends a bit on what you exactly want to do i think.

Ah, thanks for clearing that out -- oughta put a word or two in the manual, methinks
One more thing: just noticed, that, when creating a new sequence, there's no prompt for a name anymore.

[Jazz Franco]

can slice up a drum loop in the Audio Lab and create a multisample of it. The only difference with muzys is that muzys had a slice-detector, in MU.LAB the locators (still) need to be created manually, but the good thing about that is that chance is higher that they're placed more accurately.

IIRC, the good thing about Muzys editor was that you could slice up a loop and the slices were then mapped automatically, which was handy.
In case this is already implemented in MuTools -- my apologies, I really just started out (a couple of weeks with 2.7, now straight on to 3:))