MuTools

sl23 · Post by **sl23** » Sun Jun 03, 2012 12:47 pm

I'm trying to use some samples I created from my old hardware - Korg EA1,ER1 and Roland MC909. I saved these in .wav and was surprised how easy it is to add these into MuLab's devices. Great work Jo

However, when I use a sample in MuSampla it sounds exactly as it should. But when I add it to the MuSynth, it sounds totally lo-fi/distorted and is really quiet. All I did was open new session add MuSynth to rack and add sample to Osc1.

I also tried adding a sample to the Sampler part of MuSynth and can't get a sound out of it. It took a bit of figuring out how to even add the sample but I can see why it's like that.

I'd just like a sampler that works like Rolands do, add a sample play + edit, simple. Why is it not so simple here? The way I see it, opening a fresh MuSynth should be a default patch which you edit to get what you want. Adding a sample shouldn't be such a problem. Nothing should need changing/editing just to get it to sound how it does in MuSampla. In fact MuSampla would be ok if it had some sound shaping controls.

Despite that it does actually produce a great sound from the sample, very dirty and lo-fi so whatever it's doing is still good but I'd like the original sound too if it's possible.

Can you please tell me if there's something I'm doing wrong?

Thanks

EDIT: tried turning off all modules except osc1 but still not getting the original sound. Is there a a max length for the samples used for osc's?

Couldn't find anything in the Docs that could help with this.

This is only my second real go at learning how to use MuLab but I'm very impressed by it, and after learning a few things from the docs I'm even more impressed. I can see how much you've put into it.

May I make a slight criticism though, you may not agree, but the abbreviations for the parameters aren't very clear in my opinion. Could just be me though! For example XPS and FTN didn't have a clue what these were til I looked at the docs. Wouldn't Pch and Fin be better? It's not just these either many parameters have strange abbreviations. Perhaps it is just me?

AndreasD · Post by **AndreasD** » Sun Jun 03, 2012 3:15 pm

When placing your sample into Musynth's sample player, did you activate the sample player (green button) and routed it correctly (press the brown "SP" buttons in the filters or amplifier module)?
The sample player in Musynth is exactly the same as MuSampla, so it should work.

If your sample is a single waveform you should get a perfect result by simply drag&drop your wav file onto the oscillator waveform. I have sampled some of my HW synth as well with good results.

[edit] I just placed a real (longer) sample into the osc. Something that contains dozens of cycles. It will play at very high pitch and very quiet.
This is because osc require a "single cycle". With a, say 50 cycle, osc "waveform" this will sound 50 times higher in pitch that a single cycle wave. You probably hear the samples amplitude envelope stronger than the actual wave. Hence an odd sound.

sl23 · Post by **sl23** » Sun Jun 03, 2012 3:41 pm

Hi, yes I activated it by the green button and set the routing after reading the docs. But your explanation makes sense, though shouldn't it work as the MuSampla does? If I use a single cycle I'll lose the attack and any modulations from the original sample, thus losing the characteristics of the sound that made it the whole point of sampling my HW. It's ok if you just want the basic sound and you know how to recreate all those modulations etc but apart from being unnecessarily time consuming I don't have a clue as I'm still quite a novice at music.

AndreasD · Post by **AndreasD** » Mon Jun 04, 2012 4:44 am

From your reply i presume that you use a real, longer sample, not a cyclic waveform. In this case the sample player is the correct way to go.

So, do you get the sound you want when using the sample player in Musynth?
It does work exactly like Musampla.
Drag the sample into it, edit the sample properties (right click on the sample) to set the root key and activate/route the sample player so that its active and you hear the sample.

sl23 · Post by **sl23** » Mon Jun 04, 2012 9:31 am

I did try but couldn't get it to sound. I don't know how to use the Sample Player it took ages to figure how to get a sample into it! How do I set it to simply play over the whole key range?

Is there any way of layering samples, or having several loaded to play different ones over a key ranges? For eample I have samples of different keys that although isn't perfect, I'd like to set them all over specified keyranges so they work as though one sound over the full range. I don't know how to explain better sorry! Hopefully you understand.

Thanks for your help, I'm finding it a bit frustrating as I can't seem to just get on with making music like I could on Hardware. I could pick up any synth and start using it but software is so vast in comparison and has completely different ways of working it's confusing the hell out of me. I can't quite get how the signal routing works, that's the best I can describe it but not exactly what I mean.

In a HW workstation, you select a part/track, choose a sound and record away, MIDI is the same as the track and everything is easy to find. I'm not putting down MuLab at all it's great and many things are easy to find but I can't figure out the chain if you get my meaning? Once I do then it'll all fit together and I can get on. I know there's a learning curve involved with any software it's just very confusing at the moment!

EDIT: I think it'd be a good idea to make each oscillator and the sampler selectable between sampler/osc. So you could have 3 osc's or 3 samplers or any combo of both.

Got key range figured out. Should be easier to add sample though took few minutes to do it again.

After reading the docs for devices noticed that it says drag n drop sample onto MuSampla so tried that for the Sampler in MuSynth but didn't work. Opened the key range editor and tried again and it worked this was easier than however I loaded samples previously! Something that basic should be included in the docs surely?

MuTools · Post by **MuTools** » Mon Jun 04, 2012 1:29 pm

sl23 wrote:After reading the docs for devices noticed that it says drag n drop sample onto MuSampla so tried that for the Sampler in MuSynth but didn't work.

The sample player in the MuSynth is a multi-sample player, not a MuSampla or single sample player with a waveform display. That's a difference. When dropping a sample on a sample player, things are pretty clear. When dropping a sample on a multi-sample player, it's not yet clear which key/velocity zone you want to play the sample in. Ok, MuLab could assume 'full range'. I've added that on the WL.

MuTools · Post by **MuTools** » Mon Jun 04, 2012 1:39 pm

sl23 wrote:EDIT: I think it'd be a good idea to make each oscillator and the sampler selectable between sampler/osc. So you could have 3 osc's or 3 samplers or any combo of both.

The more you would make a fixed device 'flexible' the more you'll end up into the MUX itself which has 'ultimate' flexibility.

What i mean: If the MuSynth is not fitting your musical need at some point, then you can use the MUX to build whatever instrument/effect you need

AndreasD · Post by **AndreasD** » Mon Jun 04, 2012 2:01 pm

My bad to say it's a Musampla in Musynth. Apologies!

DHR53 · Post by **DHR53** » Mon Jun 04, 2012 2:07 pm

Speaking of samples... how do I change the trigger note number for each pad in the MuDrum? I was thinking of remapping to midi loops I have.

AndreasD · Post by **AndreasD** » Mon Jun 04, 2012 2:14 pm

As MuDrum is a closed system, you can't.
Alternative 1: Save all pads as patches and reload them into the new positions.
Alternative 2: Change the midi sequences (which i find faster)
Alternative 3: Give me some time and i come back. I need to try something...

DHR53 · Post by **DHR53** » Mon Jun 04, 2012 2:23 pm

Also... I noticed that my template (I created) loaded with a sequence in the drum track plays when I start up MuLab... so it seem that the midi is what "won't start" when I launch the program? Maybe you know that already but I wasn't sure... OSX 10.6.8

Thanks,
DHR

AndreasD · Post by **AndreasD** » Mon Jun 04, 2012 2:39 pm

Here is Alternative 3:

Add the "Mudrum Note Assign" module before the Mudrum.

Click on each "key" and edit the transpose value. The default patch is the original assignment. Values can be from 0 .. 11 (0=C; 11=B)
[edit] I'm talking bulls*t: Edit the transpose so that the incoming note plays the Mudrum pad you want to be played. E.G. if an incoming note is 'B' and it should play the 1st pad, transpose has to be set to -12.

Patch can be found here:https://dl.dropbox.com/u/62409608/MuDru ... Assign.Mux

AndreasD · Post by **AndreasD** » Mon Jun 04, 2012 2:48 pm

@DHR53: For your autoplay when starting Mulab, edit the file User\Settings\MULAB.Txt and add the line: AutoPlay=0

AndreasD · Post by **AndreasD** » Mon Jun 04, 2012 2:56 pm

@sl23: To give you the step-by-step to hear your sample:
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

That's it for a single sample.

DHR53 · Post by **DHR53** » Mon Jun 04, 2012 3:05 pm

Not sure what you mean by that... but MuLab would not start up playing sounds from the midi kybd, since I switched to Snow Leopard... Jo said it was a bug. FYI.

MuTools

KVR Audio

Using Samples in MuSynth