MPC 3 -- Let's GO!!

ELSADDIQ wrote:Can someone confirm that List Edit in order to edit at 1/96 resolution is still available?

List edit is still present.

Mixerman wrote:When do the punters actually get to download the Beta?

It's good enough for YT affiliates.. those know sign up for beta understand it may include bugs..

So what's the hold up how much longer?

They're likely using us beta testers as the guinea pigs to make sure it doesn't melt down MPCs before they release it to the public, which would be a PR disaster. There's a reason paying Apple and Windows developers get beta versions of the OS before the public ones are released.. I've seen more than a few over the last 2 decades get pulled and 'fixed' beforehand.. Granted, there is always a 'beta disclaimer' but still, you don't wan't something coming out to the public that's got some system killing bug in it, even an alpha version.

B-Wise wrote:

Cashman wrote:So. New user here getting my head around MPC 2 and Ive just been working on a project/template where I have 10 or more (techno/electro/house) drum programs loaded and all mapped to be the same kind of drums on each pad and tweaked to be track ready. The idea was that id be able to boot up record some drums into a sequence and have a drum loop running that I can lay down my hardware synths over the top.

Currently I can do this and on the main screen switch between all the different drum kits to select one with the right vibe as the loop is playing by just turning a knob with the program box selected.

Is there going to be a way in 3.0 to do the same thing? Looks like with kit per track this is going to get unruly pretty fast.

In 3.0 load all the Programs as their own drum track then you can make a "dummy drum track" meaning it's meant to be empty, then MIDI send it from the track settings to another track. As you press the pads on the dummy track it triggers the pads on whatever track your MIDI sending it to.

This is something you can test out on MPC 2 if you want. Also any track data you recorded will get sent out ad well. So you can record a drum pattern or whatever & in real time switch to other tracks to change the vibe.

To add to the maddness. I thought of this while I was explaining this to someone on another site;

I just thought of the fact that know that there's track Reordering, you can just select one track slot to MIDI send your dummy track & change the drum track positions.

Technically MIDI send doesn't send to a specific drum track, it sends to a track slot, so what type of track is in the slot that what will receive the MIDI send info. That method may be helpful in some cases.

emdog wrote:Has anyone been able to test the audio interface selection in MPC3? Can you choose input/output separately? Can you choose the audio rate?

Anyone ?

LivePsy wrote:
A SMALL KIT MADE FOR EACH TRACK
Why not have a kit just for the kick, and a kit just for the hats? .

when you explode a track in mpc3 you get exactly this. So the resulting kick track only contains the kick, no other samples. Unless they are in a mute group together in which case all the samples in the group get placed together in that track (e.g. closed and open hat)

Pytajnik wrote:

emdog wrote:Has anyone been able to test the audio interface selection in MPC3? Can you choose input/output separately? Can you choose the audio rate?

Anyone ?

The external audio hardware routing is exactly like in mpc2. You can still select up to 32 ins outs on a USB compliant device. You can't change the audio rate

MPC-Tutor wrote:

LivePsy wrote:
A SMALL KIT MADE FOR EACH TRACK
Why not have a kit just for the kick, and a kit just for the hats? .

when you explode a track in mpc3 you get exactly this. So the resulting kick track only contains the kick, no other samples. Unless they are in a mute group together in which case all the samples in the group get placed together in that track (e.g. closed and open hat)

Perfect! That makes a lot of sense. I get that people are used to making programs, but its a sampler right, you make a new collection of sounds every project right

Is there any other way than mute groups to group them? Say a Tom groove, with a floor tom, 2 racks and a snare. You wouldn't want to mute group them as you hit and flam simultaneously 2 at a time.

Neodymium wrote:Is there any other way than mute groups to group them? Say a Tom groove, with a floor tom, 2 racks and a snare. You wouldn't want to mute group them as you hit and flam simultaneously 2 at a time.

No, but I was thinking the same, for example if I have a centre hit snare, an edge hit snare and a rim, I will probably want them on the same track after exploding and I would not want them in a mute group. I'm going to add this as a feature suggestion in a sec...

Just realised one of the limitations of the new track exploding system is where you have a track with 4 insert FX - let's say you explode this to 8 indibidual drum tracks, each of those tracks have their own 4 instances of those original FX = 32 plugin FX instead of 4. CPU significantly increases. The mpc2 system doesn't suffer from this as all exploded tracks just reference the same program.

Possible workaround - if you like to explode tracks, get used to routing your drum tracks to a submix and always apply insert FX on the submix instead. The exploded tracks will continue to output to that submix and use the inserts on that submix. This also ensures your exploded tracks continue to 'behave' with insert FX such as compressors, so the compressor is still acting on the kit as a whole (for example, adding some 'glue' to the entire kit), rather than an individual compressor on each individual pad.

MPC-Tutor wrote:Possible workaround - if you like to explode tracks, get used to routing your drum tracks to a submix and always apply insert FX on the submix instead. The exploded tracks will continue to output to that submix and use the inserts on that submix. This also ensures your exploded tracks continue to 'behave' with insert FX such as compressors, so the compressor is still acting on the kit as a whole (for example, adding some 'glue' to the entire kit), rather than an individual compressor on each individual pad.

Very useful, thanks a lot! I will finally have a reason to use submixes (more often)

MPC-Tutor wrote:Be aware that this might change as I'm sure Akai did not expect so much backlash, and perhaps they can be persuaded to come up with something to accomodate these existing wokflows.

I'd really like to believe that, but surely they know exactly what they're doing here? Pretty much ruining the device for existing users who like MPCs to placate people who just don't like MPCs at base level. But especially the kinds of people who won't bother to figure out the very basics of how it works and then blame the machine. for this. As well as cost cutting on the extra development that'd have been required to turn the Force OS into an actual MPC OS.

I'm kinda going between extremes here - on the one hand I both my Live years ago and I'm happy with the updates it's received, I honestly wasn't expecting 3.0 to even work. But on the other, it's pretty irritating the disregard they're showing for how people have been using these devices for decades, plus I'm not sure I want to be on an old OS in the long term given that I do tend to use the plugin quite a bit.

I wasn't gonna bother, but I guess there's no harm in raising a ticket on all of this even before the beta drops - I don't really share the optimism that it'll make any difference, but I guess it's better than just bitching on here.

"The external audio hardware routing is exactly like in mpc2. You can still select up to 32 ins outs on a USB compliant device. You can't change the audio rate"


So, it's still impossible to use the built-in speakers (Live 2) and the audio card simultaneously... That's unfortunate.

About midi controllers, i used a novation on my mpc one. Sadly i had a lot of crashes when using track mix with the controller. Others reported that too

Is that better on 3?
Any chance we have shareable templates for midi controllers?
I gave it away for now but still use my global template.

Guess theae questions should go dirctly to akai.

Pytajnik wrote:

emdog wrote:Has anyone been able to test the audio interface selection in MPC3? Can you choose input/output separately? Can you choose the audio rate?

Anyone ?

No, you cannot. Though oddly it does recognize my Access Virus TI Darkstar as an audio interface over USB... it now prevents me from using USB Midi for the Virus since the Virus disables audio outputs when this happens