M3 Tests

Official support for: mutools.com
RELATED
PRODUCTS

Post

When I go a bit deeper, it shows 'MultiSample', and when I bring up the zone editor I see the references to kick2.wav, snare.wav, and hh open.wav
(rather like a preset you may have created ?) - but where are those .wav files located ?
The samples were originally in different directory's but I used a nice feature of Mu.Lab where you can embed the samples within in the song. It's a function found from the main menu in Edit - Sample Manager.

Post

cytone wrote:
When I go a bit deeper, it shows 'MultiSample', and when I bring up the zone editor I see the references to kick2.wav, snare.wav, and hh open.wav
(rather like a preset you may have created ?) - but where are those .wav files located ?
The samples were originally in different directory's but I used a nice feature of Mu.Lab where you can embed the samples within in the song. It's a function found from the main menu in Edit - Sample Manager.
Thanks for that !

I had occasionally played a little with Sample Manager - but had not experimented with 'right-click->embed' (or 'embed all', via the Options button). Great stuff.

Learning all the time !!

Les J.

Post

Here's another M3 MuSession. I got to fooling around with the nice little session that cytone posted. Ended up with something entirely different but using just the Mulab synths.

Here's the session download for M3 - called Shiny.

It is truly portable and less than half the size of the end result MP3 or OGG file.
Image

Post

preserving midi channels?

When I import midi files (general midi, ready to play e.g. in the media player),
I think all midi events will be send to channel 1.
I remember earlier discussions, where right behaviour should be:
With track target, the selected target channel is relevant,
but when using part target, the (original) part channel will be preserved.
Is this the way how it is implemented ?
Can I select a midi channel, when using part target (have not found it in the context menu)?
Everything should be made as simple as possible, but not simpler!

Post

jpumphandle wrote:
Here's the session download for M3 - called Shiny.
Awesome job :tu:

Post

1) When importing a MIDI file, the channels are preserved. But the issue is whenever you choose another target module (short: target) for track or part, then the MIDI channel is reset to 1. In the next version, the MIDI channel will be preserved.

2) Yes you can choose a MIDI channel per part but only when the track is not defining the target and when the part already has a target module, i.e. you cannot choose a MIDI channel when a part is set to 'No Target Module'.

Post

simple question:

how can I activate step recording ?
Step recording window is open, but when pushing record button (midi events),
then marker bar is progressing to the right as normal,
but I think only when hitting (and releasing) a key it should progress one time step.
What I'm doing wrong ?
Everything should be made as simple as possible, but not simpler!

Post

http://www.mutools.com/mulab/azalea/docs/recording.html (at the bottom)

You don't need to press the record button, just make sure the window is focussed, which is the case when you pop it up.

Post

mutools wrote:http://www.mutools.com/mulab/azalea/docs/recording.html (at the bottom)

You don't need to press the record button, just make sure the window is focussed, which is the case when you pop it up.
Oh yes, now I understand,
the step recorder window must have the focus,
then it works.

But this means,
- you can't use the virtual midi keyboard for step recording, and
- when clicking in the editor window, to choose a new position,
you have to focus the step recorder window again (to focus this window again).

right ?
Everything should be made as simple as possible, but not simpler!

Post

Eggu wrote:
mutools wrote:http://www.mutools.com/mulab/azalea/docs/recording.html (at the bottom)

You don't need to press the record button, just make sure the window is focussed, which is the case when you pop it up.
Oh yes, now I understand,
the step recorder window must have the focus,
then it works.

But this means,
- you can't use the virtual midi keyboard for step recording, and
That's correct. It's a consequence of how things work. It's a pity they can't be combined of course, but at the same time i do believe the way things work is ok. (i mean: the focus system)

If you want you can create a step sequence using the Sequence Editor of course, so there are ways to create the music :)
- when clicking in the editor window, to choose a new position,
you have to focus the step recorder window again (to focus this window again).right ?
Yes, which is ok, imho.

You could even use the focus to 'pause' the step recorder <-> focus away from it without closing it.

Post

regarding step recorder:

it works fine,
only want to be sure that it works as intended on my system
and that I caught on to the principle.
Everything should be made as simple as possible, but not simpler!

Post

Not a bug, I'm afraid -- but there is one simple usability feature I think would fit deliciously with the new multi-solo aspect of the solo system.

I constantly use the mute/unmute feature where you can toggle the mute status of as many tracks as you want by dragging over the track audio status icons. I reckon it'd be a convenient addition if ctrl+drag allowed you to toggle solo status of tracks in the same way. What do you think?

Post

It's a good idea and there is a note on the whishlist about this. (but there is a 'but' but that's for later)

Post

doc, chapter <sequence functions>:
Percent

For example: Factor = 150%, Reference 0 => Result = 0 + ((70-0)*150%) = 105
For example: Factor = 150%, Reference 40 => Result = 40 + ((70-40)*150%) = 105
last result must be 85, not 105
Everything should be made as simple as possible, but not simpler!

Post

:oops: Thanks!

Post Reply

Return to “MuTools”