MPC 3 old projects

Monotremata wrote:

MPC-Tutor wrote:Loaded up a fairly complex 2.x project without too much drama, but it was well structured (e.g. same track order throughout and consistent program assignment per track) so not sure how it deals with some of these crazy muddled up messes that some people like to make

Have to accept it's going to use MIDI tracks + routing to deal with programs used on multiple tracks

So far I'm also finding mpc2 kits and programs don't need any tweaking.

Same here, so far so good, just learning the way around and where things have moved too.
I always did my projects in a 1:1 layout across the sequences as well, so my Song bounce was ready to go.
Still getting used to the Digital Performer way of working with the multiple MIDI tracks to one program, not too bad though.

For the most part, its still the same MPC, new coat of paint, its not like they reinvented anything in here.

I would for guys to test out a project that not so neat.

The multiple MIDI track to 1 drum took some time for me to get used to on the Force but once you get into the groove you'll be flying.

Also here some alternative ways of dealing with it, each has their pros/cons;
You can copy the same drum program to each track & only have the samples that you want on that track or just one sample per program. You just won't be able to play all sound to together, but you won't have to deal with MIDI tracks.

Another way is to have a drum program with, all the samples after you done most of program editing & copy this to all the tracks you want but only play & record the sample(s) that you want on that track. If you make new edits they won't match up with the other copies, but you'll be able to jam with all the samples, record some pattern, then track out the other samples to their dedicated tracks.

So with all this routing using multiple MIDI tracks via MIDI send, what workflow would you use if you need to export individual track stems, because all those MIDI tracks will produce no audio in an exploded mixdown?

I'm trying to understand the advantages of them using MIDI tracks in this situation, rather than the method they use when exploding an existing drum track which makes multiple drum tracks each containing a single drum pad and the corresponding MIDI data for just that pad

(except for mute groups, where each track contains all the sounds in the same mute group, that way you get all the open/closed hats together in a single track.)

B-Wise wrote:The multiple MIDI track to 1 drum took some time for me to get used to on the Force but once you get into the groove you'll be flying.

Also here some alternative ways of dealing with it, each has their pros/cons;
You can copy the same drum program to each track & only have the samples that you want on that track or just one sample per program. You just won't be able to play all sound to together, but you won't have to deal with MIDI tracks.

Another way is to have a drum program with, all the samples after you done most of program editing & copy this to all the tracks you want but only play & record the sample(s) that you want on that track. If you make new edits they won't match up with the other copies, but you'll be able to jam with all the samples, record some pattern, then track out the other samples to their dedicated tracks.

MPC-Tutor wrote:So with all this routing using multiple MIDI tracks via MIDI send, what workflow would you use if you need to export individual track stems, because all those MIDI tracks will produce no audio in an exploded mixdown?

I'm trying to understand the advantages of them using MIDI tracks in this situation, rather than the method they use when exploding an existing drum track which makes multiple drum tracks each containing a single drum pad and the corresponding MIDI data for just that pad

(except for mute groups, where each track contains all the sounds in the same mute group, that way you get all the open/closed hats together in a single track.)

B-Wise wrote:The multiple MIDI track to 1 drum took some time for me to get used to on the Force but once you get into the groove you'll be flying.

Also here some alternative ways of dealing with it, each has their pros/cons;
You can copy the same drum program to each track & only have the samples that you want on that track or just one sample per program. You just won't be able to play all sound to together, but you won't have to deal with MIDI tracks.

Another way is to have a drum program with, all the samples after you done most of program editing & copy this to all the tracks you want but only play & record the sample(s) that you want on that track. If you make new edits they won't match up with the other copies, but you'll be able to jam with all the samples, record some pattern, then track out the other samples to their dedicated tracks.

If it's individual stems that you want to keep separated than just make a drum tracks for each or put them all in one drum track & trigger them there or from multiple MIDI tracks.

This seems like a situation where you're going have to decide how you want to work. I was just giving suggestions on working with the lack of a Drum-Program pool. I as you may know the Force doesn't have track explode, so I never considered that situation. Hopefully Akai something planned.

Off topic, but how long will you wait before starting the new MPC Bible, because it seems like the direction they'll with is gonna be heavily based on the beta testers feedback, so it'll need some time to stabilize?