MU.LAB 3.1 test

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

sorohanro wrote:
mutools wrote:
sorohanro wrote:How do I turn off the auto quantize ?
I know I knew it some time ago but I forgot :(
Right-click th 'Record Events' button.
Brilliant !!!
not very obvious but brilliant.
About (not) being obvious: It falls in the 'right-click the relevant object' guide which is one of the main GUI guidelines in MU.LAB.

Post

fridtjof wrote:Ok I've been using Live 8 for rewire for a while but im getting sick of all the crashes, causing Record to crash as well and making OSX freeze.

I tried open Record in Mulab and all I get is a error message in Record saying the audio engine is not responding and then it crashes. Then Mulab crashes too when I try to exit.

I tried finding any documentation covering multichannel Rewire in Mulab and cant find anything. All I found was a basic tutorial basically saying "click on Reason and you're good to go".

Could you please send me a link to the document explaining how to Rewire multiple channels?
It's the same as using multi-out VSTs.

It has been answered already here on the forum.

But i'll also make a dedicated tutorial for it.

Post

Thanks!

Post

mutools wrote: It will be 12 keys as it is now. I had this idea for a long time, thought a lot about it and am happy it's finally there. If you need more sounds, then simply use more than 1 drumkit. If you want to use e.g. 43 drumsounds, then use 4 such drumkits.

12 (a dozen) is a nice number of sounds for a drumkit and the advantage of not having to know where the sounds are on the keyboard (it always work thanks to the octaving thing) is too good!!
Good to read that your are satisfied with the result
Perhaps you can make a spin off from the 12 tone keysplitter and make a extra 16 tone keysplitter what is free assignable
Why not ?(it is a idea)

Post

mutools wrote: Thing is: It's not easy to make it easy :D

(especially when wanting to offer deep functionality at the same time)
Wel when a new user of MUlab makes a point of this that he find it troublesome with starting recording midi events and audio than you must this take very serious!

Plugin you keyboard and play !! and record ..easy

Indeed when the new user of Mulab opens now a "new session"file than he sees 4 empty tracks.
He has no idea what these tracks are

Therefore MUlab must open with a new .. "new session"file with 4 native instrument tracks (take the Musynth) and 1 audio tracks ready for recording

Than there is no complaint anymore ..you must satisfy your customers :wink:
Last edited by janamdo on Sun May 02, 2010 8:16 pm, edited 1 time in total.

Post

janamdo wrote:Good to read that your are satisfied with the result
Perhaps you can make a spin off from the 12 tone keysplitter and make a extra 16 tone keysplitter what is free assignable
Why not ?(it is a idea)
There is a multi key-/velocity-zone splitter on the wishlist.

Post

janamdo wrote:
mutools wrote:
janamdo wrote:i told this more ..it must be easy, because it must be simple at first sight The principle is : from easy to difficult
I agree 100% !

Thing is: It's not easy to make it easy :D

(especially when wanting to offer deep functionality at the same time)
Wel when a new userof MUlab makes a point of this that find it troublesome with starting recording VstI and audio than you must this take very serious!
I do.

But i don't see the point.

Record MIDI = simple: Hit record.

Record simple audio = simple: Hit record. (ensure record audio button is enabled).

Record multi-track audio = a bit more complex to setup but inevitable. it's the nature of multi-track recording.
Therefore MUlab must open a "new session" with 4 native instrument tracks (take the Musynth) and 1 audio tracks ready for recording
This is a conceptual topic for M4.

I'll startup/join the M4 talks lateron, as messaged before.

Post

Jake Jackson wrote:2. There are too many areas, accessed by going to different areas of the interface, to go to do simple things: To do the most basic thing, play and record a vst or audio file, the user must go to:

A. The rack at the bottom to select the vst.
B. The rack to the left to select it as the source of the recorded sound.
C. The Edit menu to select Recording options and select the source of the recording. (Shouldn't this be automatic when you arm the track?)
D. Possibly go back to the Edit menu to select Edit midi input focuses. (Shouldn't this be automatic when one arms the track? If not, what does arming the track do?)
E. Go back to the Edit menu to select the "Modular area." Once in that area, things can get confusing--what must be added as a source? Think of a new user, here: some of the options include the vsti's that may have already been loaded into a track. Does one have to add these again as modules? If not, why are they listed there?

3. Some of the most necessary areas are hidden, as though there was an intention to make recording difficult: I can't imagine anyone finding the Modular area without reading the manual. (It's on the Edit menu, for one thing. True in the old version, too.)
Let me elaborate a bit more to avoid confusion:

I just don't understand what you mean with all these steps.

As said before, i think it's quite simple:

If you want to record a VSTi, then just hit record.

I don't know what you mean with clicking here and clicking there to set it up.
Maybe i'm missing something?

Post

mutools wrote:
Jake Jackson wrote:2. There are too many areas, accessed by going to different areas of the interface, to go to do simple things: To do the most basic thing, play and record a vst or audio file, the user must go to:

A. The rack at the bottom to select the vst.
B. The rack to the left to select it as the source of the recorded sound.
C. The Edit menu to select Recording options and select the source of the recording. (Shouldn't this be automatic when you arm the track?)
D. Possibly go back to the Edit menu to select Edit midi input focuses. (Shouldn't this be automatic when one arms the track? If not, what does arming the track do?)
E. Go back to the Edit menu to select the "Modular area." Once in that area, things can get confusing--what must be added as a source? Think of a new user, here: some of the options include the vsti's that may have already been loaded into a track. Does one have to add these again as modules? If not, why are they listed there?

3. Some of the most necessary areas are hidden, as though there was an intention to make recording difficult: I can't imagine anyone finding the Modular area without reading the manual. (It's on the Edit menu, for one thing. True in the old version, too.)
Let me elaborate a bit more to avoid confusion:

I just don't understand what you mean with all these steps.

As said before, i think it's quite simple:

If you want to record a VSTi, then just hit record.

I don't know what you mean with clicking here and clicking there to set it up.
Maybe i'm missing something?

To avoid these things ....

Therefore MUlab must open a "new session" with 4 native instrument tracks (take the Musynth) and 1 audio tracks ready for recording

Post

One more little Note Key Splitter drumtest... ;)
drumSynth03.MuSession

I know it's kinda off-topic now... but why not.

Post

mutools wrote:
Jake Jackson wrote:1. The old way of selecting what kind of track is recorded is gone--there's no choice of a sequencer or an audio track. (What happened to that? How do you select what kind of track is being created?)
Huh? There never was such difference in MU.LAB.
Umm, you had to define the type of track you wanted--either a note event sequencer track or an audio track, into which one loaded audio.

mutools wrote:How to record a VSTi?

Simple:

1) Plugin the VSTi
2) Hit record
Hmmmm. I was trying to record using Drumaxx, and it doesn't work. I've now recorded using a piano, and suddenly it does work. However, one must first click on "Record audio." Not sure a new user would be able to see this step.

Post

Taron wrote:One more little Note Key Splitter drumtest... ;)
drumSynth03.MuSession

I know it's kinda off-topic now... but why not.
At least it is now possible to make a decent drumtrack with the aid of the notesplitter
A big leap forwards seems to me
Nice piece of music to show the drums and again something to learn from
:)

Post

Jake Jackson wrote:Umm, you had to define the type of track you wanted--either a note event sequencer track or an audio track, into which one loaded audio.
Tracks have never had types. Tracks are containers for Parts. Parts are Sequence or Audio. Still are. If you draw one, it prompts - now including whether you want to re-use an existing one or create a new Audio or Sequence part. You don't need to do this to record anything. Just hit record (by default, set to MIDI only, so you need to have a focussed instrument to hear anything).

Post

Hehe, thanks, janamdo! Now you should check out this one... I made a wild sound with the note key splitter! It's got quite some potential...
(although it inspires a few new requests!)

drumSynth04.MuSession

Post

Taron wrote:One more little Note Key Splitter drumtest... ;)
drumSynth03.MuSession

I know it's kinda off-topic now... but why not.
Music is never off-topic!! ;) :tu:

Post Reply

Return to “MuTools”