MPC 3 -- Let's GO!!

HouseWithoutMouse wrote:

Jean-Marc Liotier wrote:... But the new mute behaviour that cuts the audio immediately instead of just not playing any further note sucks badly for long notes.

Sounds like the same as with the Force. Track mute on e.g. a drum/keygroup/plugin track means muting the audio outputs of the track, and it's even post-fx so I can't even leave a reverb or delay tail to soften the abrupt mute except with audio send effects. If I want a musically useful mute, I have to use a separate MIDI track sending to the sound-generating drum/keygroup/plugin track. So is the same thing coming to MPC now. Use two tracks per track.

The number of Youtube promoters casually explaining that a second track to send MIDI from is a perfectly acceptable workaround for that functional regression suggests Akai knows they hurt traditional MPC users and tries to control the fallout by having them push that message.

I am sad in a way with this update. I stated before in other threads that what I like about the now defunct MPC workflow is that it is not a DAW. But now it is a DAW. Uninspiring.

TT_Lab wrote:I am sad in a way with this update. I stated before in other threads that what I like about the now defunct MPC workflow is that it is not a DAW. But now it is a DAW. Uninspiring.

u dont have to update

might have to keep my live on 2.0 and then get a 2nd mpc to try out 3.0 just in case there is no roll back

main concern is how programs will translate on this new system, cos i have drum programs that i use as the starting point for all beats.


now it has to be strongly implicated that a new flagship x is on the way; and maybe a live 3 next year

Update looks great a welcome change to the original workflow I have been using since the 90's I'm scared to.see how my 12 sequence songs convert tho..

Jean-Marc Liotier wrote:The number of Youtube promoters casually explaining that a second track to send MIDI from is a perfectly acceptable workaround for that functional regression suggests Akai knows they hurt traditional MPC users and tries to control the fallout by having them push that message.

The youtubers are just sales guys and they do anything to sell the product, that's what they're paid for.

But as far as I can see, all that's needed is an option to select whether Mute controls the track's MIDI output, or audio output. Right?

Anyway, I'm an Ableton user, I'm completely used to adding lots of dummy tracks for i/o and utility purposes. Then again, Ableton at least has grouping and folding for track organization.

kaydigi wrote:Hmmm Loop pop’s videos states that MPC Software 3.0 is not slated for 2024.

And of course projects opened on MPC 3 can’t open on MPC 2 software. What a weird release strategy unless, it’s going to be in beta for a while.

maybe they will run the beta this year; then at next winter NAMM they will drop the new flagship with the fully tested 3.0 software.

sounds like a good plan imo

I only came to say YEEEEEEHAW

Okey Kakai, where is my beta firmware. I volunteered to test for free, I give you my valuable time. Why are you looking for free help and artificially delaying it? Next time pay for real testers instead of asking for free help.
KAKAI COME ON!

Has anyone figured out what will happen to drum programs? If you have loads of legacy drum programs it looks like you can still load them but can we still create them to use over multiple projects?

robleighton22 wrote:Apparently track mute is no longer unique per sequence, instead it works globally. I really hope they change that back of have an option to toggle either. I get persistent tracks across all sequences but the track mute workflow was genuinely one of the main efficiencies of using an MPC to draft an arrangement. Deleting notes as a work around is not the same.

Yeah it almost seems like Inmusic believe their armada of YouTubers more than they have knowledge of how their products are being used outside of making simple four bar loops…
Not trying to hate here, lots of improvements, but also a lot of downsides with the overhaul…

Interesting, so.......

no more programs, but 128 tracks that can be assigned.

in V2 there was a maximum of 128 programs but.....
you could arrange these in any combination per track for each song.

my question is does V3 mean that each song must inherit the track assignments from the first song?

or does it mean you can create new assignments for tracks on a per song basis?
(and if so does this mean the 128 track limit is lifted?)

I know 128 programs sounds like a lot, but I like to have many program variations. this always seemed like an artificial limit to me anyway. (e.g. the 4K does not have this limitation).

It would be a good opportunity for AKAI devs to do a Q & A as MPC 3 fundamentally changes one of the core aspects of the MPC philosophy.

jpeg wrote:at next winter NAMM they will drop the new flagship with the fully tested 3.0 software

All you suckas better be listening. Jpeg is calling it NOW! Either kiss da rang now or look like a straight fool come NAMM 2025

Surely this track mute per sequence is a bug or something, why would they change that workflow? It’s how I use the MPC!! But I’m excited and please let’s us choose how we use the 128 tracks!? What if I want 30 audio tracks and 8 internal instruments. Drums midi and then record all my hardware synths straight on to the arranger via audio tracks. 8 is not enough for this new workflow. Yeeeeeeeeeeeeeeeeeeeep. Let’s us max the cpu out with more than 8 plugin instruments running. Just unlock it please. We love you