Using Samples in MuSynth

[AndreasD]

Seems i'm still suffering from jet lag from recent travel.
I'm on a Win7 system, so i can't say anything about the Mac version.

[sl23]

@ AndreasD
Thanks for the instruction, I was left and right clicking everywhere and didn't think to try double click :doh:

@ mutools
Now you say it, I realise it actually does what I was suggesting! And I didn't know it was made in the MUX. But I don't know how that works yet. I don't even fully understand MuLab's construction, how things work, or how they interact. Is there some information on this in the docs? Once I got my head round how things interact, it'll help a great deal.

For example, the racks. You place a synth here but say a track is the target? But am I right in thinking the track is a target only if you drag a synth/sample or record direct to it? Are they connected or two seperate things? On hardware, a part, track and rack are all different things is this the same with MuLab? If something is changed in relation to one of these does it affect the others? Maybe I'm not thinking of it the right way, but as I said, I've come from hardware to Muzys then MuLab. Muzys was quite straight forward, but MuLab is different, probably due to being superior by being a modular system?

[pljones]

Tracks are not targets. Tracks are containers for parts (just like in Muzys). They can set the default target for all the parts they contain to any available module. You can change the target for a track by right-clicking the middle section (not the left-hand icon or the right-hand icons) and selecting "Choose Target Module".

[janamdo]

For example, the racks. You place a synth here but say a track is the target? But am I right in thinking the track is a target only if you drag a synth/sample or record direct to it? Are they connected or two seperate things? On hardware, a part, track and rack are all different things is this the same with MuLab? If something is changed in relation to one of these does it affect the others? Maybe I'm not thinking of it the right way, but as I said, I've come from hardware to Muzys then MuLab. Muzys was quite straight forward, but MuLab is different, probably due to being superior by being a modular system?

I thought it was only possible to "target a module"
- There is a trackheader with name track..mute and so on
- There is track
- There is a rack ..loaded with modules for sounds and effects for a track

If you use at the track header the + button : use instrument track..than you get a preconfigured track loeaded with a sound

BUT when you want to make your track with your own choosen sound..than you must apply the "target a module" procedure

But there maybe more to do the "target" feature?

[MuTools]

But I don't know how that works yet. I don't even fully understand MuLab's construction, how things work, or how they interact. Is there some information on this in the docs? Once I got my head round how things interact, it'll help a great deal.

Maybe this helps:

http://www.mutools.com/mulab/docs/overview.html

[sl23]

Perhaps AndreasD's instructions should be added to the Docs?

1) double click the word "No Multisaple"
2)Drag&Drop your sample into the area below the keyboard
3)Right click on the green box that repesent your sample and select "Extend Zone to Entire Keyboard"
4)Right click again and select "Edit Zone Details"
5)Right click in the sample in the "Note Zone" window and select "Edit Properties"
6)Set your root key as required

[MuTools]

The essence of that is all in the docs.
Maybe not in this specific order, but i can't document each and every possible combination of actions as that would result in docs of millions of pages.

[sl23]

I appreciate that but this is a basic instruction for adding a sample and should be instructed as it's not actually that straightforward if you don't know, as I had trouble. The whole point of a manual is to instruct and though you've pointed out some of the functions of the MuSynth there's very little info there. Most parameters are obvious without documenting them but nothing on how to add a sample. Maybe it is covered elsewhere but surely this is the obvious place for finding out how to add it.

Is there someway users could help build the info required for MuLab's Docs? That way it'd spare you the trouble and would provide more info. Even if we could just provide instructions that you could copy and paste into place in the docs?

Obviously you don't want the docs to grow out of proportion so they need to be monitored/moderated but I think the docs are a bit on the slim side. There is definitely a lot of helpful info there though.

The overview helped clear a few things up btw, thanks, somehow when I looked before it didn't help, but that was quite a while ago and before I fully attempted to use MuLab. One question though, what is the difference between a Sequenced Part and an Automated Part? The docs say both are used for filter control, so they can be used for any other parameter, yes? So do they have different functions?

[MuTools]

I agree with your constructive criticism. At the same time i need to use a way to create and maintain the docs and tutorials as efficient as possible.
About this concrete example about adding a sample to a multi-sample: It's a combination of the very standard actions in MuLab, independent from what type of object you're working with:

1) Double-click = Create (if nothing yet there) or Edit (if some object is there)
2) Right-click = Show context menu
3) Drag-drop = Move / Copy / Link / ... objects

It's all about a balance of how much we put in the docs.
The more in there, the more work to maintain it and the slower the further development. But again, i agree with you that basic tasks like your example should be covered somewhere. I try to do that with the youtube tutorials. More such tutorials to come.

[sl23]

I see your point about maintaining docs.
The basic instructions are clear but when looking for one specific thing means scouring the docs for that little bit of info which you said before is there but not in one place. Where would I need to look for this info? That's rhetorical btw. Its just that it detract from the flow. Not quite so important when learning but if this is a typical example of the docs then when in middle of something its a pain if some simple instruction would alleviate the problem.

I understand your concern about not spending too much time with docs, amending them when things change is time consuming. But if things change won't that also make the video tutorials redundant?

It's difficult finding a balance but the point of docs is to provide basic info and it should be easy to find. I don't mean to sound like I'm forcing my opinions on you, just trying give some advice that's all.

[MuTools]

I see your point about maintaining docs.
The basic instructions are clear but when looking for one specific thing means scouring the docs for that little bit of info which you said before is there but not in one place. Where would I need to look for this info? That's rhetorical btw. Its just that it detract from the flow. Not quite so important when learning but if this is a typical example of the docs then when in middle of something its a pain if some simple instruction would alleviate the problem.

I understand your point.

I understand your concern about not spending too much time with docs, amending them when things change is time consuming. But if things change won't that also make the video tutorials redundant?

True. The movies aren't a solution for that prob.

I regard the docs as a 'reference documentation' and the movies as 'manuals'.
The movies are more concrete, the docs are more abstract.
That's how i see it now, but i'm open for improvement, as long as it fits in an efficient time management scheme.

It's difficult finding a balance but the point of docs is to provide basic info and it should be easy to find. I don't mean to sound like I'm forcing my opinions on you, just trying give some advice that's all.

I know, thanks!

[sl23]

No one wants your time spent doing menial tasks is there a way users could add instructions? Perhaps a wiki page would solve this?