MPC 3.0 Question

Ok…. I’m not sure if this has been asked or addressed so bear with me. In the prior software, once I chopped and created a drum program, I would load that same program across 3 different tracks (drum, snare, hats). For the life of me, I can’t figure how to do that, or if it’s even possible, in this beta update. Please, assist me

Ok I'll take a stab at it...I'm still learning 3.4. It appears Drum Programs on a Global scale is gone. You can load the Same "XPM" Program on multiple tracks but I'm not sure if its Loading multiple Instances of the same Program on separate.

The Best workaround I have is....
If you load a Drum Program on a Track, To avoid using multiple Instances of the Same Program...I just create a New Drum Track, Open the new track's "Program" in The Track Edit feature....Same as Program Edit. Then Pick a pad and load the Samples to your desired Pad...Manually.

Kind of Extensive...but hey lol

Each track is a different program. They can share samples, but they don't share what we would traditionally think of as program settings...

Programs are gone in 3.0. Now it is just a track.

To do what OP wants to do... just duplicate the track... *or* play the chops as wanted, and then explode the track. The main problem with exploding the track though is that if you are on mono, the hits won't choke each other... besides that though, it'll preserve mute groups and other necessities.

In MPC 3, a program is loaded into a track and becomes part of the track, there is no longer a 'program pool' , programs don't exist as a unique project resource, and you cannot freely assign programs to multiple tracks or change the program assigned to a track. This is probably the most discussed issue affecting MPC3 and why many prefer to stay with MPC2.

Some workarounds:

- Record your drums to one track and explode (best option IMO, and will keep pads in the same mute group together on the same exploded track, e.g. open closed hats)
- Duplicate your track so you have three tracks with the same drums
- Use the 'send to' track setting to send MIDI to the master drum track (convoluted)
- Create three new tracks and manually assign your chops to each track accordingly

Just be aware that exploding tracks will also duplicate any track insert FX so I would suggest you first route the track to a submix and apply the FX to that instead. This will also preserve the action of FX across a whole kit, such as compressors. Duplicating tracks has the same issue, but also will duplicate any pad FX. But contrary to what you might have read, duplicating a track does not duplicate the samples, each track just references the same set of samples.

I'm convinced that Programs and Tracks were combined to be conceptually more like Ableton Live.

To have tracks and programs separately, kind of, you can use a MIDI track as a "track track" and route its MIDI events to a "program track" which only serves as a container for the program and its automation.

Appreciate the feedback! Looks like I’m downgrading LOL.

A technical question, regarding the firmware:
Would it be possible (in theory) to have different versions of the firmware located in the memory, where you could decide to load up different firmware version with different projects? This way you could utilize different workflows depending on what you’re working on.

There are many interesting features on the new beta, but this change in the way the programs are handled would be a deal breaker to me on most projects I work on.

Yeah I know only one is usually used… just wondering whether it could be technically possible?
Like, having the internal memory partitioned in a few different sections, so that when you choose one you are only using that part of the memory.

I mean, if techs can program AIs to host podcasts, surely something like this would not be impossible

someone drop that confused Big Lebowski gif

Supraphonic wrote:Yeah I know only one is usually used… just wondering whether it could be technically possible?
Like, having the internal memory partitioned in a few different sections, so that when you choose one you are only using that part of the memory.

I mean, if techs can program AIs to host podcasts, surely something like this would not be impossible

Used MPC Ones start are around $375 USD,

might be option for you to carry a second MPC and have that flashed as the ALT firmware.

kaydigi wrote:
Used MPC Ones start are around $375 USD,

might be option for you to carry a second MPC and have that flashed as the ALT firmware.

That’s what I have been thinking.
I have been also thinking of getting a used Live2 in addition to the X, for the sake of mobility. (The X is a Central piece that is not very easily moveable in my setup). But the Live2 would also have to use the same firmware as the X to be useful..

Meaning that I would have to get a third MPC just for the new firmware. Perhaps a little overkill, but who knows what the future brings?
At present moment not financially possible unfortunately

kaydigi wrote:
Used MPC Ones start are around $375 USD,

might be option for you to carry a second MPC and have that flashed as the ALT firmware.

The Best Advice As Of Yet!

Eventually they are going to stop Support of MPC 2(if they haven't already). So you might as well get use to the New Firmware or you'll be trying to learn it later...Forcefully lol.

I keep a couple of my other MPCs with 2.15 on them but find myself Not using them as much.

JJ used to offer a partitioned OS system, not sure how it worked from a technical POV, but you could switch OS versions at boot up. Akai are unlikely to do this as they'll want everyone moving over to MPC3 rather than trying to support older versions, which is reasonable IMO.

Another option is to keep a copy of both firmwares on a USB stick and re-flash when required.