I still don’t quite understand this take on it. The “MPC core” is the ability to assign more than one track to the same program? That’s pretty much the thing they took away, isn’t it. It’s like that one feature was elevated to become the most powerful feature of the MPC. Clearly it was for some, and I feel for them, but even it it were the MPC core, there’s a workaround by using midi tracks so I’m still not sure why it’s such a big deal.
The MPC is so much more than this one-to-many relationship between tracks and programs. They’ve kept and enhanced a lot of those other things.
But they’re not trying to be more of a daw in a box than they always were (since the current-gen MPC line was introduced). How are the new features making it more of a DAW? I still don’t understand this. To be clear, I’m not trying to be disagreeable or ignorant (there’s a change I am unintentionally the latter), I’m genuinely trying to understand why the removal of the 1:n track:program feature suddenly broke the MPC core.
The point is exactly what you said - that you use the arranger either in a process of turning a loop into a longer structure (the “beats” way), or by leveraging the sequences feature the way you’ve always done it and only using the arranger once you’re done with arranging the song (the “song mode” way).
There’s absolutely no way. Zero chance of that happening. That would indeed kill the core of the MPC in irreplaceable ways!
I agree with this, it would be nice with a visual way of adding another sequence to the cursor/timeline point of the current arrangement to extend it. Perhaps it’ll become more useful in future updates as it’s a little barebones at the moment.
They should also make it easy to drag, copy or erase midi boxes of say 4 bars of midi data. Hopefully they’ll add ways to make it as smooth as possible over the course of the next few updates. After all, they haven’t even releases the first version of it yet.
Yeah, this is what I’d consider a bug and I have a feeling it’ll be fixed. They already acknowledged the other problem with muting the audio/program part rather than the midi/track data. I’m sure those two problems are connected here.
I’m not sure I follow the premise that they’re aiming to become a daw in a box. At least not more than they’ve always been. I mean, it is a DAW, so is 2.x. But it’s a hardware-first experience and none of that is changing with the 3.0 update.