Automatic Sample Assignement on Load?

m:t:c wrote:http://www7a.biglobe.ne.jp/~mpc1000/os2xl/gpe_inst_sample.htm

ye, this is not really a solution or a workaround. Kinda strange that an auto-assign feature is not part of the AKAI or JJOS, I reckon it's not something complicated to implement.

If I recall correctly off of the top of my head your numbering should start around 24 or 26 or somthing like that. I have it all figured out and written down somewhere but I'm not at home right now. The only drawback to this method is that all the (drum) samples have to share a common name. It cant be like Kick24, Snare25, etc. So with drum sounds you just gotta hear to know what they are.

It looks like if you set your first samples "original" key value to C-1 you should be able to start from 1 or 2 in numbering the rest of your samples. (sometimes MIDI starts at 0).

In this day and age I wonder how many people build really in depth multisamples with the MPC? The work flow could probably be re-tooled, although I'm not sure autoloading is all that interesting.

One "workaround" would be to join all your samples into one file on the computer (or play them back and sample them as one file), load that one file and use NDC. I actually find this faster and easier, so maybe work ahead is a better word. But I'm of the mindset that having a million one shot samples is a flow killer in general.

Um, this may be crazy and way out.... but why can't Jauly just create a program to hold the 40 samples manually? This program can be reloaded over and over into new projects, right?

So you do the hard work once.