MPC Thread : MPC Live - MPC X - MPC One (Part 2)

Does the MPC download all your Splice samples or can you pick and choose which samples and packs you want to add to the box?

I have gigs of Splice samples and it sounds like a nightmare to try to add them to the MPC.

Thanks!

Splice sync over wifi is all or nothing unless I’m missing something.

Watched that Bolo video nearly to the end, if I have misconceptions about 3.0 it wasn’t doing much to dispel them.

“It’s the same, just the colours are different”, then in the next breath says that the current per sequence muting is gone. “But it only takes five minutes to go in and delete parts in the arranger” - yeah, and that makes a huge difference when you’re in the creative flow stage of just trying a bunch of stuff out, combinations of drums and chops, etc. Few other examples throughout the video, also interesting the kinds of stuff he and his audience are talking about as wish list items - not much there that I’d personally think I’d need in an MPC, also Fruity Loops and Beatmaker 3 wouldn’t necessarily be my big reference points.

The thing is that it’s obvious that there will be big changes to the way the device works, so I don’t know why anyone would pretend otherwise - this was a lot of the initial selling point. Problem at the moment is that it’s really easy to understand what’s going away and how this will be a negative if you want to keep using the MPC like an MPC, you just have to start with the basic fact that it’s going from independent programs to locked down “drum tracks” and think it through from there, but it’s much more difficult to get any kind of grasp why this is supposed to be as good or better.

Actually the one thing from the hour that really jumped out at me was the bit when he said the current arranger “ain’t it”. This really needs to deliver given the carnage that’s obviously coming for the existing MPC process - not sure I’d be expecting the public beta to drop any time soon tbh.

Because it will sell more MPC’s to new customers that are put off by the current OS.

Any long time MPC users they lose in the switch will be completely eclipsed by a flood of new customers.

Welcome to the real world Neo. Your eyes hurt because yada yada…

1 Like

Based on what? The Force flop? :grin: :fishing_pole_and_fish:

1 Like

Based on dozens of people in this thread alone that are looking forward to the 3.0 possibilities vs what I count as fewer people who think the sky is falling.

There is a Force thread where your opinion can be discussed further. It’s very clear to me that the bean counters at inmusic want to sell more units and more software. Dumbing down and making the OS more generic will sell more units.

I can’t wait and the only bad part will be all the begging posts in the beta forum from the dinosaurs trying to hold on to the past. ‘But me programs, me programs!’ I do feel sorry for y’all kinda like when the internet killed bicycle couriers.

There will never be another masterpiece such as…

And all your MPC’s is deadz now. Pour one out for your homies. Then tell your homies to chill because no one will force them to upgrade. Crazy.

Meanwhile some 13 year old will get a One+ with 3.0 for Christmas, have it mastered by Easter, and be placed by summer break while everyone is still reminiscing on their MPC60, which we can all still buy if we really want that workflow and that sound.

But maybe a whole new forum post will be made, ‘MPC 2 OG Fam’ or something.

6 Likes

Please don’t tell me you actually watched for an hour on regular speed? Had to watch that crap at 2x speed & still only got halfway.

You can still load up a bunch of Drum tracks & test stuff out. The muting per track is still gonna be there. Whatever your missing will have to be worked around.

Or don’t upgrade, MPC2 is still a 7 year old OS which makes it a middle age adult in MPC years. I would just hope & request that Akai still make bug fixes for 2.0.

Or wait for the official OS to drop & see what Akai does with the Feedback to give the OS a proper assessment before you make a decision. That’s kinda why they did this long ass beta testing approach. They shouldn’t have never released the version without the mutes or at least made it more clear to the YouTubers that it would still be there. Tefty was the only one that mentioned this earlier on. Most didn’t get that message & it caused all hell to break lose.

2 Likes

It flopped so bad that it’s being used as the model of MPC3 & it still in stores 5 years later. Interesting assignment.

It’s also interesting that more MPC users are unknowingly asking for more Force features like in Bolo’s livestream he was saying “there should have some way to store the MIDI I’m blocks to make using the arranger better.” Basically asking for Force style clips which would then lead to users wanting the Force clip-matrix. What a flop.

Yeah, this is it. Not a big deal to opt out here, just quite frustrating that they seemingly think their least important customers are people who use the MPC right now because they like MPCs.

Oh yeah for sure. Definitely everyone who’s been slating the MPC for years is going to be rapturously into it once 3.0 drops, especially the ones who just couldn’t get past having to keep track of what’s where in their patterns. Which is a unique issue in the MPC and not just a fundamental part of making music. You’re absolutely right, there will be no complaints from anyone other than old hasbeens trying to cling on to the past. This is 100%, without a doubt, definitely what is going to happen.

1 Like

Gotta say if there was one thing on my wish list you nailed it, I really like Mpc3 and I’d love a clip matrix page kinda like ideas mode on maschine where you could just highlight what you need and hit a send to arrangement button…

1 Like

I’d sample this with mpc 3.0

1 Like

On the version of Force I have the midi isn’t stored in a “block” or “clip” in the arranger. Did this change in an update?

These are the end of days, I predict Mpc 3.0 will be released on November 5th. :smiling_imp:

1 Like

That clip-matrix was one of things that made me get the Force over the X in 2021. They even have a really cool features called “Capture & Insert” that will take only the currently playing clips on any of the scenes & copy them to 1 scene. Having all you sequences/scenes & clips laid out in front of you really helps, especially if you named your tracks appropriately.

I like to use the top of the matrix for all my main clips & their variations, then make a dummy scene with just blank clips to act as a matrix divider so I can test out seq ideas with all the main clips & copy those to a new scene under that dummy scene as new song. Want a new song, just end the last song with dummy scene & copy clips & or scenes to that new section.

There’s 999 scene per project which makes up for the lack of a song mode like on the MPC. Both have their pros/cons, but the Force is way faster at moving ideas around because of the matrix & the dedicated buttons like copy & delete.

I hope Akai adds the matrix as an option & as 3.0 become popular, more users will see the benefits of it & ask for it… like Bolo.
But more than anything I want both platforms to to get bug fixes & QOL improvements. Why the hell can’t we copy & paste text in 2024? Come on!

1 Like

You would have hear the context of how he was describing it in the video to know he was asking for clips like the Force before you even get to the arranger.

Pretty curious about this … is this not just a more complicated and less direct approach to a problem that the MPC already has a tried and true solution for?

I’m not really sure I get how the Force clip launcher works, I will admit that my impression is that it’s basically Ableton lite. Could easily be way off the mark with that though. Either way, this all sounds like basically trying to bring back functionality that is working perfectly well in 2.0 but is broken in 3.0? What you’re describing in no way sounds quicker or more intuitive than just creating new patterns and changing up the programs / midi / mutes then adding them to a song or bouncing to a DAW. But like I say I don’t know the Force at all, genuinely interested in why you’d prefer that setup.

On the mutes thing, seems most likely to me that the original plan was to have a single mute for a track rather than per sequence and they’re only putting a hack together because of all the pushback they got, like the change follows logically from having locked in “drum tracks”.

I don’t think that’s true is it, using/crossing over the existing Arrangement functionality Akai have is hardly a validation for the Force.

That’s it basically.

Yes, this is about the size of it.

The uniqueness of the MPC non-linear approach has been shown a massive amount of respect and love when its been under threat… I think that’s a good thing.

Hopefully Akai will figure it out and still enable that non-linear approach to be used and fed into the new linear Arrangement section.

It’s going to take a long time to get to the alpha MPC 3.0 though.

And how does it interact with sequences? Is it a thing that you select a sequence then you can launch the tracks within it? Or are sequences and scenes interchangeable? (Edit - sequences not patterns, brain is obviously fried)

It really jumped out at me in the early demos that they all seemed to be trying to do a whole song in a single sequence. If it’s a thing that they’re looking to drop the Force OS on MPC pretty much but without the launcher element that’s maybe even more yikes than I’d been thinking. And if they do bring along a launcher, what are we going to use for scene buttons?

Apple tried to graft a clip launcher onto a linear sequencer a few versions back in Logic and imho it doesn’t work at all, but at least you can just ignore it and go ahead with the bits that do work.

I’d like to see it handled like the live control screen myself, it’s clearly doable as the gui is already embedded in the software, nobody has even mentioned live control in any of the beta vids so I won’t go into details as I’ve already been to much of a loudmouth regarding these things but it’s there and I feel it would be a great addition…

This is something that would need a more detailed video to best show the benefits. The 1st thing to keep in mind is that the clip matrix (CM) is is same the MPC project with 128 seqs & 128 tracks each. The main difference is the Force has 999 scenes. Scene & Seq are different words for the something. Also a seq plays all tracks in the seq. A scene gives each track the option to play or not when the you play the scene. The cool thing is that a track with all it’s clips that was set up not to play, can still have any of it’s played by tapping it on the screen or its clip pad if the pads are in launch mode. They can be in-synced or not which can be really cool or not.

Now here’s the thing they clips can be set to play in legato mode so clips can play on different scenes on the same track can cut each off mid of the clip length whlie staying in sync. Meaning if you want a seq/scene with a track mute you could make 2 copies of the same scene, 1 could have the all the tracks you wanted muted, deleted instead & if all your clips are in Legato mode you can at anytime launch between the 2 or more scenes. If you name your tracks well all your clips will be named after that & make it easy to know what’s going on that seq/scene. A lot of this part is where it’s personal, because since it’s your project you’ll know what’s what & also you can make a dummy track & name a clip for that scene something like intro, verse1, drop…etc.

Force makes this easier with it’'s 64 pads & other buttons, but the MPC could get the screen option for the 8x8 matrix & you’ll have to use the touchscreen which also has launch button on it. better than nothing. They would also need to add the Force Navigation view, so you can have a birds eye view of the whole CM at once, which can also be used to move to other parts of the CM quickly by touch.

The thing is that you can still do what you on the Force but not in the MPC way of doing it. The benefits will be difficult to understand without actually using a device that was built for the CM from the get go. The way the Force is set makes so you need the things your holding on to.
Once again I’ll post these demos of me trying break down what I mean. I’ll make some better version of them, but this is all I got & if you watch it, read the description to know whats going on.

This shows how Force can emulate the MPC sequencer:

This one show How fast you can build scenes & move around the CM:

On mutes, I don’t know if they put it back because of pushback. Like I said, Tefty mentioned early on that Akai said it just wasn’t in those early beta’s, but was still in the system. But who knows…