uhh, i think this caused me a gray hair or two.
and im only 22. lol.
until yesterday i was using mulab 2 test c. i liked it and i was using it to make my first song that used multisampla. it had loads of vocal cuts and drum samples and everything. so yesterday, i decided to download the offical mulab 2 free (ver 2.02) and try to finish the song in it.
after donwloading and setting up the vsts and all, i open my song and...
bad surprise.
the loops and everything played perfectly but all the vocal samples were pitched down. alot! to make things worse i accidentaly (by habit) chose to save the project at exit and when i tried to open it in mulab test c, i couldnt because 'it was made in a newer version of mulab'.
after falling off the chair i tried to solve the problem. made a new project in mulab 2 free, and loaded a vocal sample into multisampla but this time it sounded pitched UP alot. and to make things worse, after a few tests i discovered that if i move the sample from, for example C2 to C3 it sounds alot higher (an octave higher i guess but im not sure coz on C2 its already too damn high). it never happened before. and it shouldnt.
but i figured the whole multisampla philosophy was maybe changed after the test c version so i tried to load a drum sample to make things clear. and it worked like a charm. normal pitch, and no pitch changes along the keyboard.
so i guess something is wrong with my vocal samples?
but they used to be ok.
if someone has any idea how to fix this, and i hope jo will, here are the samples so u can play with them and maybe find a solution:
http://rapidshare.com/files/158931204/m ... s.zip.html
or
http://www.megaupload.com/?d=GXOIKXFM
tamaravoc is the vocal sample
airy tom is the drum sample
multisampla troubles
-
- Hun #3
- 4265 posts since 25 Mar, 2002 from A quaint little village just south of Hamburg, Germany
morning tomica -
I think I had the exact same problem with drumsamples until I discovered a dialogue called "Sample properties" - doubleclick a blue Multisampla zone so the pop up editor appears. Righ-click on the sample name- go to "edit properties" and set "Root Key" to "No Key".
Weirdly, some samples come with root keys and some don't. Maybe it's encoded in them by the people who created them?
I find myself turning off "Root Key" 1000x more often than I assign a particular note to a sample.
Ah, finally a post where I can say,
Hope this helps!
Marco
edit: just saw the zip -no time but will check it out later.
I think I had the exact same problem with drumsamples until I discovered a dialogue called "Sample properties" - doubleclick a blue Multisampla zone so the pop up editor appears. Righ-click on the sample name- go to "edit properties" and set "Root Key" to "No Key".
Weirdly, some samples come with root keys and some don't. Maybe it's encoded in them by the people who created them?
I find myself turning off "Root Key" 1000x more often than I assign a particular note to a sample.
Ah, finally a post where I can say,
Hope this helps!
Marco
edit: just saw the zip -no time but will check it out later.
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Indeed there have been a change in the sample pitch management from Test D on.
Ok, here is how it works:
When a sample has a root key, that will be taken into account in the MultiSampla. So moving a zone up or down will affect the pitch of the samples in the zone because the root key is fixed.
When a sample has no root key, the MultiSampla will use the middle key of the zone as the root key.
In Test C samples could not yet have an explicit root key and so the root key was always defined by the middle key in the zone.
So to 'upgrade' your session, i suggest to turn off the root key for all your vocal samples, and then they should have the same pitch as before again.
Please note that Test C was still a test version and so it was per definition not yet a stable production version.
Sorry for the inconvenience anyway.
NB: Updated the online docs about this.
Ok, here is how it works:
When a sample has a root key, that will be taken into account in the MultiSampla. So moving a zone up or down will affect the pitch of the samples in the zone because the root key is fixed.
When a sample has no root key, the MultiSampla will use the middle key of the zone as the root key.
In Test C samples could not yet have an explicit root key and so the root key was always defined by the middle key in the zone.
So to 'upgrade' your session, i suggest to turn off the root key for all your vocal samples, and then they should have the same pitch as before again.
Please note that Test C was still a test version and so it was per definition not yet a stable production version.
Sorry for the inconvenience anyway.
NB: Updated the online docs about this.
Last edited by MuTools on Thu Oct 30, 2008 9:14 am, edited 1 time in total.
-
- KVRist
- 124 posts since 24 Oct, 2005
It's the same here...
edit: you write much more faster than me
edit: you write much more faster than me
Last edited by frollo9386 on Thu Oct 30, 2008 9:23 am, edited 1 time in total.
-
- KVRist
- Topic Starter
- 106 posts since 24 Jun, 2008
hahaa
it helped marco!
problem solved, thank you so much.
still, i prefer the previous default settings.
now i have to select the no root key option for over 30 samples. and its not an option thats just a click away or something. i counted, its 6 clicks away.
mutools, i think we need the option to switch off the root key for the whole multisample if we want to.
it helped marco!
problem solved, thank you so much.
still, i prefer the previous default settings.
now i have to select the no root key option for over 30 samples. and its not an option thats just a click away or something. i counted, its 6 clicks away.
mutools, i think we need the option to switch off the root key for the whole multisample if we want to.
-
- KVRist
- 124 posts since 24 Oct, 2005
thank bonteburg...
but i can't find that dialog box you're talking about
can you please explain again how to open that dialog box (you're not talking about tha note zone editor, right?)
but i can't find that dialog box you're talking about
can you please explain again how to open that dialog box (you're not talking about tha note zone editor, right?)
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Note that this issue is only because there was a change between test c and the release version.
The quickest way to update your test c-made session is to go to the main Edit menu -> Sample Manager. There you have all samples together and you can quickly access the context menu of each sample via the little button at the right or by right-clicking the sample name.
Note that in the current MU.LAB a sample's root key is set to "No Key" by default.
Only if you drop a bunch of samples on the MultiSampla, MU.LAB will propose to use any key names in the sample name as the root key.
The quickest way to update your test c-made session is to go to the main Edit menu -> Sample Manager. There you have all samples together and you can quickly access the context menu of each sample via the little button at the right or by right-clicking the sample name.
Note that in the current MU.LAB a sample's root key is set to "No Key" by default.
Only if you drop a bunch of samples on the MultiSampla, MU.LAB will propose to use any key names in the sample name as the root key.