Tips for quickly making keygroup programs

I shoulda mentioned this one earlier. Haha, we have to discover features the way that chickens discover food: hunt and peck.

Altopiano, as far as I can tell, there are no options with this feature. You mention a good one -- keep the original name and put a new prefix (as well as numeric suffix).

The one that I want, just on the off chance that Numark is listening, is to be able to set the starting number to something other than 000. If you have already batch-renamed a bunch of snares and stored them you might have SNARE-000 to SNARE-020. Now you load up some new ones and want to name them and save them in the same directory. They should be SNARE-021 to SNARE-040, but unfortunately you can only number from 0...

-illiac

I still have two questions about keygroups, anyone know the answers?

1) sometimes when I am setting spans, the notes are displayed as numbers (0 - 127) and at other times as pitches (E4, C1, etc.) I want the friggin' number form so that I can use the keypad to enter values and see what I'm doing. For example, the original key of a sample is C3. So what's the keypad value for A2, the note that's three semitones below it? I can't remember. But if they gave me the C3 as a number, I could just subtract three from it and key it in. Anyway, does anyone know how to control whether the notes are displayed as pitches or numbers and what causes it to change?

2) is there any way to create a program where the original key of the doggoned sample is the pitch that it is assigned to in the program? In other words, if I have samples of C2, C3, and C4, I want to simply add them to a program (say a drum program) and have them end up on C2 and C3 and C4 (the pads for these notes). Seems obvious, no? That way, if I converted the drum program to a keygroup I would be halfway home. Instead, the doggoned thing assigns samples to the pads in GM order or some useless thing In the case of a keygroup program, it maps every sample over the entire 128 note range, grr.

If they made it easier to create keygroups for this thing, it would roll all over the Fantom and other samplers in most ways. The cross fading, layering, bit depth, the overall sound of the thing is great. But what a pain the butt to make a keygroup program, SHEESH.

-illiac

Have we ever resolved all of the questions in this old post? I'm doing alot of kg's this week and I'd like to learn from the old posts. One of the things I picked up (that I'm sure many probably already know but I'll put it up just in case), is that when setting a kg span on the drum machine itself, it matters where your cursor is. You can position it over both the note and the octave number (Say F1), and turning the knob will keep you on F's going from F1, F2, F3 etc...

Or you can position the cursor just the F (using shift/Cursor) to change the note chromatically. (F1, F#1, G1,G#1, ... C2, C#2 etc...)

1. If you hit (soft key) span twice you can switch the way you view the key span Numbers, or Alfa.

2. create a drum template with all the pitch assignments assigned in chronological order


3.ssl are you speaking of positioning the cursor on the actual low and hi in the keyspan window, so that when play the notes on the keybord it reads the midi note assingmnets vs using the jogg shuttle.

I'm speaking of using the jog shuttle.

popa1 wrote:2. create a drum template with all the pitch assignments assigned in chronological order

I don't understand how this accomplishes what I had in mind. My problem is that a sample file (say, .wav) can store information about its pitch, but the MPC does not use this information when assigning the sample to a program. I wish that, by default, the sample would be assigned to a keygroup with a span of just one pitch, where that pitch is the pitch of the sample itself, as indicated by the sample file. That way you could just slosh a bunch of samples into a keygroup and end up with most of the keygroup assignments more-or-less ready to go.

Or did I misunderstand what you meant?

-illiac