Everything is all divided, why did they design the software that way?
You make a drumkit program, a bass, a piano. Then you goto sequence 1 and set up the tracks like, t1.drums, t2.bass, t3.piano. Record a sequence for a verse, then goto sequence 2 to do the hook.... and it's empty! So the trick is, you copy that first seq to the second, delete all the events, and use that like a template for all the others.
But then what if you decide to change the t3.piano to be t3.flute? Now you have to go to each seq/track3 and manually change the program for each. It should be that the tracks are the same all across the board, and the sequences are just patterns using the tracks. Then if you make a change to a track, it is updated everywhere.
But wait, there's more... so now you realize that your piano is way louder than everything and you need to turn it down a bit. No prob, just lower the level for the track right? Nope, goto every single pad for all four banks, and manually lower the level.
This sucks because I used to use pure software, and I love the feel of hardware, the fast response, the lil flashing lights. It's like an instrument, and feels better than staring into a monitor and moving a mouse with latency. But this just isn't working.
So I'm wondering, why? I keep trying to change how I use the MPC to fit it to what was intended so that it works smoothly. Before I was trying to treat it like a complete multitrack audio/midi recorder, but the polyphony issues would dropout my vox. So I tried treating it just as a drum/keys midi sequencer, and now I see it's way too much work because pads, tracks, and sequences are all separated. What am I supposed to use this thing for then?
You make a drumkit program, a bass, a piano. Then you goto sequence 1 and set up the tracks like, t1.drums, t2.bass, t3.piano. Record a sequence for a verse, then goto sequence 2 to do the hook.... and it's empty! So the trick is, you copy that first seq to the second, delete all the events, and use that like a template for all the others.
But then what if you decide to change the t3.piano to be t3.flute? Now you have to go to each seq/track3 and manually change the program for each. It should be that the tracks are the same all across the board, and the sequences are just patterns using the tracks. Then if you make a change to a track, it is updated everywhere.
But wait, there's more... so now you realize that your piano is way louder than everything and you need to turn it down a bit. No prob, just lower the level for the track right? Nope, goto every single pad for all four banks, and manually lower the level.
This sucks because I used to use pure software, and I love the feel of hardware, the fast response, the lil flashing lights. It's like an instrument, and feels better than staring into a monitor and moving a mouse with latency. But this just isn't working.
So I'm wondering, why? I keep trying to change how I use the MPC to fit it to what was intended so that it works smoothly. Before I was trying to treat it like a complete multitrack audio/midi recorder, but the polyphony issues would dropout my vox. So I tried treating it just as a drum/keys midi sequencer, and now I see it's way too much work because pads, tracks, and sequences are all separated. What am I supposed to use this thing for then?



