Multisample Instrument Test Single Sample vs Multi

Have just got an mpc1000 upgraded to jjos2 for instrument multi samples.
Have been testing it out recording stuff.

Single samples won't work as a Multisample instrument program because the tune scale adjusts the time of the sample. Why is this important ? ! if one sample is faster than another or has modulation then the sounds will be out of sync. Will not sound correct as a chord poly etc. each program I tested saved to about 512k which is one sample pitch shifted.

Recorded a Multisample with emu emulator x setup then added to Mpc 1000 took a good 15-20mins adding single samples into Mpc. Now when I play a chord the sample lengths are the same.

Just to note mpc sorts samples into alphanumerical order so scrolling through adding each sample is a major task as order goes C#1 D#1 etc then C1 D1 etc. you will have to scroll back and forth. Unless their is an easy option to autoload samples per name ( C1.wav could autoload into C1 key etc).

Emu samples tested at about 1 sec so when added to mpc came out about 10mb per program.


Only solution I can think of is to time stretch a single sample to match each note scale but this would most likely be impossible on mpc, it would have to be tempo synced too.

Unless anyone has any solutions to the singular sample used as a instrument program?

Recording a synth with 100 presets and setting up in mpc 1000 for multisamples would probably take a day?

Arrrrrrrggghhhhhhhhh!!!!!

Found a solution to using single samples for perfect poly use.

Seems to work best with longer samples because loop point adds modulation to end.
Shorter samples will have a higher modulation speed using xfade.
Trial and error I guess.

Add sample to all notes in program.
Select chromatic scale.
Select note on.
Go to mode trim and select loop point.
Now try and find a loop point by holding down pad and adjusting data.
If you hear a click select xfade which helps with re trigger click.

Now try holding 2 pads down to hear if it sounds correct.

Now go back to program and adjust for use.

This is the method used by emu samples most are small 12k up to 100k max.

The loop point creates a continuous note so now poly are Reasonably in phase.

Xfade seems to add different modulation to some samples.
Forward has less modulation but clicks more on lower higher notes.

Always check note repeat for highest and lowest notes clicks can happen
Readjust loop points best seems to be near zero wave form.

You should not use modulated multisamples (or any other sample with any kind of tempo elements to it) - sample without modulation, build the program, then add modulation in your program.

As for auto assign, don't think that's possible, but if you name the samples with the note (C1 or 36 etc) it will at least work out the root note automatically (might be a JJOSXL-only feature?)

The MPC1000 is not ideally suited to multisampling, even with INST programs and JJOS it's very limited in terms of features. You can multisample, but you need to accept the limitations and be prepared to make compromises.

Some resources that might help:

http://www.mpc-samples.com/product.php/ ... ing-bible/

http://www.mpc-samples.com/section.php/ ... tisamples/

MPC-Tutor wrote:As for auto assign, don't think that's possible, but if you name the samples with the note (C1 or 36 etc) it will at least work out the root note automatically (might be a JJOSXL-only feature?)

yeah I don't recall exactly but I think sample has to end with with note name like "sample_C1.wav" and it only works for instrument type of program, maybe on OS2 also

It's here :
http://www7a.biglobe.ne.jp/~mpc1000/os2xl/gpe_inst_sample.htm

Auto set
The sample which finishes with the note number or note name of the sample can perform the above-mentioned setup automatically.
The following is an example in case a note is a sample of D0.
As for all the following samples, a note is recognized as a sample of D0.
Piano26.wav
Piano 26.wav
Piano_26.wav
PianoD0.wav
Pianod0.wav
Piano D0.wav
Piano d0.wav
Piano_D0.wav
Piano_d0.wav

PEAce

oh thx for reminder

Would anyone support dropping some "features" in the OS, to make more room for better implementation of inst/multisampling programs? Perhaps a JJ for this. .

drop for example the grid sequencer, or audio recording, or the effects.. or (?) Add the ability to automatically send out MIDI, record the audio, assign a sensible name, assign to MIDI not or pad. Or something like this. .

It would be nice to bring the MPC up a bit in this area, so I could finally dump the rack sampler.

thoughts?
~Steve

No.. I wouldn't support that.. especially not removing the grid sequencer or even effects..

Anybody using Instrument Programs in 128XL? I'm trying to create some synth programs using a single looped waveform and it seems to only pitch the sample up to a certain point and then the same note is repeated across the remainder of the keys. Could this be a limitation of OS128XL or is there a limit to how far a wav. file can be pitched?

Also to the OP, what OS are you using? It sounds like you are using Drum Programs rather than instrument Programs?

You can only pitch +/- 3 octaves on every OS. Speed up 2x in PC editor or resample and use another slot for higher pitches.

Thank You, good to be informed about that. I've noticed that portamento reacts differently when using multiple samples. It sounds more natural to me with a single waveform.