Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar
By Antonym Fri Mar 30, 2007 5:13 pm
amazing. this was basically built for drum programming. i never really understood why it was 6, rather than 8 (half of 16) but it works out for the main drums perfectly, especially if you're doing velocity/qlink layer switching

kick, snare, hat, cym, misc, misc

6 is enough for your basic kit. i add additional percussion now in other tracks.
excellent control over individual notes, both by leaning and by the "edit" option.

my one suggestion for this otherwise perfectly coded page is this: aftertouch velocity for manually inserted notes.

right now, if you hit record and then hit a pad, in the upper right hand screen, you see your velocity. however, this only changes based on the first scan of your hit, not "aftertouch." say you hit your pad at 50 vels but want it closer to 70--it'd be really nice if you could AFTERTOUCH it to 70 by giving it more pressure, kind of turning your pressure sensor into a qlink kind of thing, "pushing" it closer to the value you want.

By deranger Fri Mar 30, 2007 8:38 pm
Good idea, I fully support aftertouch->event velocity. A nice shortcut!
User avatar

By rinseout Fri Mar 30, 2007 10:53 pm
Wow nice idea, do you think its possible? Didnt know the pads support aftertouch, on the other hand they know how hard they are pressed since it works with note repeat, but are there aftertouch features i missed?
User avatar

By Antonym Fri Mar 30, 2007 11:49 pm
the nature of the sensors is that they WOULD support aftertouch - to see it visually, go to the PAD screen where you set sensitivity. with full level off on a working pad, press and watch the bar go up and down. now imagine that was a number between 1 and 127 and well...

i've wanted to see the pads assigneable in slider mode for a long time. imagine playing the filter/resonance with 2 pads.

By Mindzeye Sat Mar 31, 2007 9:25 am
this is great, but for me as Im new to this (grid edit) its a different approach. I usually do all drum tracks on different tracks so unless Im missing something my drums need to be on the same track...at least most of them...right?
User avatar

By M02 Sat Mar 31, 2007 12:05 pm
Its up to you man.

Having them all on the same track in grid edit is really handy because its all infront of you visually, and its really quick to edit everything cause you don't have to skip around tracks.

Though at the same time, if you work with track mutes alot its harder. And it also limits the ability to apply different swing for each seperate track.

So you just gotta work out what works for you.
User avatar

By Antonym Sat Mar 31, 2007 3:36 pm
Though at the same time, if you work with track mutes alot its harder. And it also limits the ability to apply different swing for each seperate track.


definitely issues from someone coming from a multi-track drum world. solution for both -

1 - instead of track mutes, use QLINK LEVEL, or instead, just dont program X pad when you don't want it to play. i never use track mutes because it seems unneccessary when i could just do it myself in grid edit by simply not programming something to play at x time.

2 - swing for "each track" can be applied on an on-pad basis. for instance, if you have hats on A10 and 11, just select those two pads to swing at X%. it will only effect those two.

also, qlink swing makes this easy because the qlink position ONLY EFFECTS what you are currently recording. so if you record your kick and snare pattern at 50% swing, you can then just bump up the qlink a little bit and have 55% swing ONLY EFFECTING THE HAT.

i tell you it's flawless....highly recommended from me to make the plunge and stop multitracking your drums in the mpc. "that's so OS 2.01!" being able to see everything right in front of you is CRUCIAL.
User avatar

By Antonym Sat Mar 31, 2007 3:42 pm
Mindzeye wrote:this is great, but for me as Im new to this (grid edit) its a different approach. I usually do all drum tracks on different tracks so unless Im missing something my drums need to be on the same track...at least most of them...right?


yes, the vast majority of em. for the most part i do all of 1 type of drum on 1 track (accoustic main) and then say a more percussion heavy program on another (program of shakes and other weirder percussion).

I usually do all drum tracks on different tracks


i used to do that as well. i did that for all of edge city (an album i made almost a year ago). the difference to me now is that i am able to make better groove patterns more quickly and conveniently from "within the same box" without so much track switching, track renaming, etc.

By MK25toLife Sat Mar 31, 2007 3:55 pm
If you recorded all your drums in one track how would you recommend tracking it out into a DAW? What is the easiest way to copy and paste the different drum sounds into a new track in the grid edit mode?
User avatar

By Antonym Sat Mar 31, 2007 4:11 pm
If you recorded all your drums in one track how would you recommend tracking it out into a DAW? What is the easiest way to copy and paste the different drum sounds into a new track in the grid edit mode?


1 - track it out via assigneable outs and by LEVEL muting pads you don't want recorded in MIXER mode. couldn't be easier. especially with 6 outputs and 6 pad grid mode - oh wow, this is just falling together so nicely.

2 - by doing it in step edit mode. there's really no real point to "copy and paste diff drum sounds into a new track in grid mode" because in grid mode, each PAD can be used as its own track.
User avatar

By Antonym Sat Mar 31, 2007 5:06 pm
i just emailed jj about my next plans for a Grid Finger.

By Mindzeye Sat Mar 31, 2007 11:50 pm
i tell you it's flawless....highly recommended from me to make the plunge and stop multitracking your drums in the mpc. "that's so OS 2.01!" being able to see everything right in front of you is CRUCIAL.[/quote]


I guess with all these options being new and fresh to me I think Im really missing out...