MuTools racks and tracks...

[DHR53]

Having done a bunch of reading of the docs and working with MuLab lately I'm still scratching my head on the racks and tracks strategy... So how does everyone one else approach this? Do you create a track w/instrument or audio set up initially... or create tracks and later define them... Or, create racks and then drag to tracks??? I'm trying to get a strategy for my default template but I thought I might see what everyone else does in this matter.

As I just started testing with audio, I was also wondering what the diferences are between the 3 sample options... i.e. import sample sound, audio file and sample loop... I tried sample loop and see it splits the file into a rex loop I guess? On that, once it is split up how do I adjust the slices on that... as it's a sequence and doesn't bring up the audio editor?

Also, I'm using the Mac version so I guess the video isn't working on that yet. Anything else missing from 4.1 on the Mac version.

Thanks to everyone for tips!

[janamdo]

Having done a bunch of reading of the docs and working with MuLab lately I'm still scratching my head on the racks and tracks strategy... So how does everyone one else approach this? Do you create a track w/instrument or audio set up initially... or create tracks and later define them... Or, create racks and then drag to tracks??? I'm trying to get a strategy for my default template but I thought I might see what everyone else does in this matter.

Yeah, it seems that MUlab has more ways to do something, to get the same result ...You must follow a workflow what get the desired result for you.

You can first get a template session, if it's it working than you don't have to bother about how defining it.

A good question i think, because i am wondering also this.. perhaps Jo from MULAB can give a right answer?
Probably he will answer that it can be solved on different ways

[AndreasD]

About importing audio:
- import audio file loads the audio file and places it on a track
- import sample sound puts the audio into a Musampla
- import sample loop does the recycle thing with sequence and multi sample created.

Very clear, no overlap, clean distinction between the cases.

What is the strategy for creating racks and track?

Usually you want to achieve something.
Say you have an audio file you want to hear in your composition. In this case I would cleary start with the audio track and decide from there which rack could play it.
If composing is the task, I usually start with an instrument and live playing, which eventually gets recorded. This means I start with a rack.

Actually, don't worry about theory, just finish the job on hand. Things will become natural very soon.

[DHR53]

I guess I feel like if I create a blank track, I should be able to right click and make that either an instrument or audio track? Maybe that's what I'm looking for. As I create instrument tracks and audio tracks initially, but like to leave a few blank tracks which later would be converted to whatever I might need... I just don't create racks at all except for FX busses.

[janamdo]

OK, you want to start with a empty screen.
Mulab starts up with 4 tracks now and you cannot see if they are for a instrument or audiotrack at once.

Perhaps a idea to start only with a + button for adding a instrument or audio file and futher is Mulab empty ( is this possible? )
On this way the user can also build up his own workflow from the ground
There is no confusion more..all starts from zero.

[> DiGiT <]

just figure it out once and save a template or somebody make a session with nothing in it for this guy

[AndreasD]

I admit that at the beginning the total freedom between tracks and racks can be a bit disconserting. Especially as in Mulab, as Jo pointed out, the racks are 'master' and the tracks have to follow. This is different to all DAWs i know. But soon you will find this concept quite liberating. That's one of the reasons why i'm a Mulab convert. To me the e.g. Cubase concept of midi and instrument tracks each with its own mixer is confusing. Mulab boils it down to a track and a rack. For me the better approach.

janamdo's idea of an empty session is possible:
In a new session, right click in an empty part of the track header and select "delete unused tracks".
Delete all racks but keep the Master rack.

Save this as Template named "New".

Whenever you start a new session, this empty one will come up.

Now you can add tracks. If you create audio or instrument tracks the required racks are created as well.

[janamdo]

janamdo's idea of an empty session is possible:
In a new session, right click in an empty part of the track header and select "delete unused tracks".
Delete all racks but keep the Master rack.

Save this as Template named "New".

Whenever you start a new session, this empty one will come up.

Now you can add tracks. If you create audio or instrument tracks the required racks are created as well.

Yes, thanks AndreasD, perhaps a idea to include also a empty template in the template builtin list for Mulab (there is a template menu entrance )
Than there is only a master rack to be seen when you open the composingscreen.

Perhaps Mulab has also to give more attention to the + knob and make this more outstanding..

[AndreasD]

hey you beat me DiGiT

Here is the empty session: http://dl.dropbox.com/u/62409608/Empty.MuSession

[pljones]

Parts are the real masters, for me...

Tracks are containers for parts that route them to racks. For sequence parts, the events need turning into sounds, so you route them to a rack with an instrument in (or out the door via MIDI). For automation parts, you route them to a parameter. For audio parts, you route them at whatever effects (in a rack) you want. (Subject to me getting MULAB4.1 installed, this may be slightly out of date!) The part is what's "important", that defines the "what". The track defines "when" (i.e. on the timeline) and "where to". And the rack defines "how" you want the signal treated (if you get that far).

[liquidsound]

Parts are the real masters, for me...

Tracks are containers for parts that route them to racks. For sequence parts, the events need turning into sounds, so you route them to a rack with an instrument in (or out the door via MIDI). For automation parts, you route them to a parameter. For audio parts, you route them at whatever effects (in a rack) you want. (Subject to me getting MULAB4.1 installed, this may be slightly out of date!) The part is what's "important", that defines the "what". The track defines "when" (i.e. on the timeline) and "where to". And the rack defines "how" you want the signal treated (if you get that far).

Great explanation!
Just one more if you can: A track shows either a Rack or a VST. What's happening it there then, where is the real difference in the flow?

[MuTools]

Tracks are simply the same as the tracks on a score: There you write the melodies and rhytms etc.

Tracks themselves don't make sound.
So that's why you can tell a track to play module X or Y.
Any track can play any module!

There is no such explicit thing as an instrument track or audio track.
That's only implicitly defined by what type of module the track plays.
If a track plays an instrument, it's an instrument track.
But if you then drop a pure effect rack on the track, then we can call it an audio track.

I'm amazed this is so confusing. It's so simple. No?

[pljones]

A track shows either a Rack or a VST.

...or any other target module. There's nothing special going on. A rack is something you can target. It's a module that's a container for modules (eh, are they modules, still?). You could target a MUX directly, if you had one lying around. Or, well, any module. Name the module, the track targeting it gets that name (by default; again, this all changed and I don't remember the latest... maybe...)

(Hm, racks contain modules. MUX contains modules. A rack's a bit more limited, though...)

[liquidsound]

A track shows either a Rack or a VST.

...or any other target module. There's nothing special going on. A rack is something you can target. It's a module that's a container for modules (eh, are they modules, still?). You could target a MUX directly, if you had one lying around. Or, well, any module. Name the module, the track targeting it gets that name (by default; again, this all changed and I don't remember the latest... maybe...)

(Hm, racks contain modules. MUX contains modules. A rack's a bit more limited, though...)

What I was referring to is that if I have a Track with a Rack or a VST it seems to be the same thing. The same path. Is there a difference? Are there different hidden options based on these two specific way of using the track ?

[liquidsound]

I'm amazed this is so confusing. It's so simple. No?

Simple YES but not clear cut, especially for a new user I think... ( I'm still in M3 mode)