By
Riggs
Fri Oct 12, 2012 5:03 am
Ok, I'm a little late on this one but I thought I would contrib anyway.
A track can...
- only use one program
- record midi data
- mute its midi data
- can run an external midi instrument by sending midi data over one channel
Here's an example… Let's say you have a program for some drums, a program with some sweet bass and a program with random samples. If you want to use those 3 programs in your sequence, you'll need 3 tracks. One for each program.
Another example… I've got a program with some drums and a real synth that I want to drive with the 500. In this case, I'll need two tracks. One for the program and one for synth. The drum track records midi for the drum program and the synth track records midi for the synth.
The track mute on the 500 can't be recorded. So for me, it only serves one function. When I'm working on a song, I'll record just about every part or instrument on its own track on a single sequence. Then I'll copy that sequence a few times and mute certain tracks in each to make the different sections of my song.
I ALWAYS go back and forth about how many tracks to use and how many programs to use. I want to have the program in the track only contain the instruments on that track so I don't get confused. That is hardly ever realistic on the MPC though. I've even tried using only one program but each pad gets it own track. That didn't work out either.
Usually what I do is make the whole thing on one track in overdub mode and if I need to split things out, I'll move the pad events I want out to other tracks.
Anyway, good luck. I've been doing this for a little while now and I still don't have the one single magic workflow. Each song is different.