OS2 ONLY - 14 multisampled instrument programs

EDIT - these programs are OS2 only. they will not work in os1.

http://nymantics.com/instprograms.zip

i got busy.

THIS is what a sampler is all about.

contents include:

yamaha DX7 piano
stylophone
roland stereo strings
roland string stack
roland jp fizz
roland glass pad
roland dance saw
roland choir
roland brassy
roland ancestral
prophet5 PWN
polymoog
the jj synths
arp strings
and an accordian.

Nym, you're the man! Youre too kind.

building inst programs is fun. there is 1 important trick i've learned though.

remember, when you detune a sample, you're going to start hearing the machine's pitching algorithm. ie, if i take a C_1 sample and pitch it all the way up to C_5, you REALLY hear the sound. not necessarily a bad thing, but multisamples let us escape mickey mousing it.

so say i have the following guitar samples:

C_0
C_1
C_2
C_3
C_4

and i want to make a multisampled inst program out of them.
think: how best can we set the note ranges to avoid stretching the sample more than we have to?

here's an example of what NOT to do.

1: low-C_0 high-B_0
2: low-C_1 high-B_1
3: low-C_2 high-B_2
4: low-C_3 high-B_3
5: low-C_4 high-B_4

why? because you're "starting" each sample from its original point and pushing them all up, instead of maximizing on the stretch range.

ie, C_0 stretched + or - 6 sounds better than C_0 stretched + or - 12.

so what do you do? try this:


1: low-G_-1 high-f#_0
2: low-G_1 high-f#_1
3: low-G_2 high-f#_2
4: low-G_3 high-f#_3
5: low-G_4 high-f#_4

understand?

I didnt really get it (not your fault at all) but I just do it the way that MPC Tutor explained in the tutorial. That has worked for me soo far.

Antonym wrote:building inst programs is fun. there is 1 important trick i've learned though.

remember, when you detune a sample, you're going to start hearing the machine's pitching algorithm. ie, if i take a C_1 sample and pitch it all the way up to C_5, you REALLY hear the sound. not necessarily a bad thing, but multisamples let us escape mickey mousing it.

so say i have the following guitar samples:

C_0
C_1
C_2
C_3
C_4

and i want to make a multisampled inst program out of them.
think: how best can we set the note ranges to avoid stretching the sample more than we have to?

here's an example of what NOT to do.

1: low-C_0 high-B_0
2: low-C_1 high-B_1
3: low-C_2 high-B_2
4: low-C_3 high-B_3
5: low-C_4 high-B_4

why? because you're "starting" each sample from its original point and pushing them all up, instead of maximizing on the stretch range.

ie, C_0 stretched + or - 6 sounds better than C_0 stretched + or - 12.

so what do you do? try this:


1: low-G_-1 high-f#_0
2: low-G_1 high-f#_1
3: low-G_2 high-f#_2
4: low-G_3 high-f#_3
5: low-G_4 high-f#_4

understand?

The1. 2. 3 4. 5. you have listed are individual samples? I have to sample 88 keys?

I believe what you are saying is that is you sampled G then you tune it to Fb (f flat) so you DONT get that 16 level off tune sound on each key CORRECT? Tuning down instead of up saves your samples from getting that sped up chipmunk effect that I HATE!

I still thought keygroups were when you sample say Middle C and the MPC take that one note and creates the whole 88 key range.

Exactly how does tutor explain how to use it? Please elaborate.

The1. 2. 3 4. 5. you have listed are individual samples? I have to sample 88 keys?

yes, they're individual samples, no you don't have to sample 88 keys.
multisampling takes 1 sample and ranges it over a series of notes. i sample a C_1 key, specify it as C_1 in TRIM, then set it to play over a range of notes.

I believe what you are saying is that is you sampled G then you tune it to Fb (f flat) so you DONT get that 16 level off tune sound on each key CORRECT? Tuning down instead of up saves your samples from getting that sped up chipmunk effect that I HATE!

actually, i don't tune the sample at all. i just specified the range over which it plays, in this case low-G_-1 high-f#_0.

I still thought keygroups were when you sample say Middle C and the MPC take that one note and creates the whole 88 key range.

you can do that, yes, but you'll end up with a chipmunked sample. basically, instead of ranging it over 88 keys, you can range it over say 12 keys instead. then, over the next 12 keys, you range a different sample. and then a different one. that way you end up with a more realistic patch.

Antonym wrote:

The1. 2. 3 4. 5. you have listed are individual samples? I have to sample 88 keys?

yes, they're individual samples, no you don't have to sample 88 keys.
multisampling takes 1 sample and ranges it over a series of notes. i sample a C_1 key, specify it as C_1 in TRIM, then set it to play over a range of notes.

I believe what you are saying is that is you sampled G then you tune it to Fb (f flat) so you DONT get that 16 level off tune sound on each key CORRECT? Tuning down instead of up saves your samples from getting that sped up chipmunk effect that I HATE!

actually, i don't tune the sample at all. i just specified the range over which it plays, in this case low-G_-1 high-f#_0.

I still thought keygroups were when you sample say Middle C and the MPC take that one note and creates the whole 88 key range.

you can do that, yes, but you'll end up with a chipmunked sample. basically, instead of ranging it over 88 keys, you can range it over say 12 keys instead. then, over the next 12 keys, you range a different sample. and then a different one. that way you end up with a more realistic patch.

Gotcha! one more ? So in order to range the sample you have to hit mode--program. Then what are the rest of the steps?

actually, you don't do it from GPE yet. you do it from the main screen. on the main screen, navigate to the spot right of "pgm" (i guess it should be the name of your pgm) and hit window. this takes you to NPM, new program mode. this is where you change adsr and all that happy stuff. the first screen, sample, is where you do the damn thing.

load jj's example files or some of my pgms to give it a quick browse, it'll help a lot.

Antonym wrote:actually, you don't do it from GPE yet. you do it from the main screen. on the main screen, navigate to the spot right of "pgm" (i guess it should be the name of your pgm) and hit window. this takes you to NPM, new program mode. this is where you change adsr and all that happy stuff. the first screen, sample, is where you do the damn thing.

load jj's example files or some of my pgms to give it a quick browse, it'll help a lot.

can I do it on the 2500?

nope, not until os2 is released for the 2500 in march. this is all os2 stuff we're talking about, i forgot you were on the 2500

To bad i can't check this out on os1

There was an excellent series of articles in sound on sound a couple of years ago, dealing with "The Lost Art of Sampling".

http://www.soundonsound.com/search?sect ... f+sampling

It covers anything you need to know about sampling, it really is fantastic.
I've been using the techniques in there for ages to multisample my monosynth into my S5000 to get a polyphonic synth program and once you've got the hang of it you're unstoppable.

you can do that, yes, but you'll end up with a chipmunked sample. basically, instead of ranging it over 88 keys, you can range it over say 12 keys instead. then, over the next 12 keys, you range a different sample. and then a different one. that way you end up with a more realistic patch.

This is actually the way the pro sound samplers make a realistic sounding synth, without sampling all of the keys seperate. all the old school dudes did it this way to build synths in the 80s and shiz

definitely. 1 sample per note is the ideal, but a pain to assign.

the greatest os2 multisample program of all time would be 64x3 samples, velocitatively layered

are you guys playing these keyboard pgms on mpc pads or midikeyboard? are these working well on pads?

A good rhodes pgm would be niiice