MPC 3 -- Let's GO!!

dustyslices wrote:just my 0.001 cents:
you buy a device for what it is at purchase time, there is no sticker on the box that promise you future updates (free nor paid) - plugins or additional functionalities are extra. The only thing I expect from them is to provide bugfixes for stuff that doesn't work as it should or as it was advertised.
Having said that, I'd be pissed if for example I didn't liked the 3.x workflow which break my habbits but that is the only way to fix for example a midi bug. In that scenario I'd feel that my mpc was missold to me as it force me to use it in a completely different manner that it was advertised.

Well said

MPC-Tutor wrote:I don’t think there’s any updates to keygroup instruments beyond the advertised 8 layers and the slice motion feature. But I’ll be investigating this in detail soon and will report back. There’s qlink macros though, these are stored in the track and can be quite powerful, but the ‘engine’ is mostly the same as mpc2 (I think).

This is likely the case with many core modes (sample edit, sampler, browsers, song mode etc), Some tweaks but fundamentally the same as mpc2.

Sounds good. Thanks.

In all honesty you guys are over thinking this whole thing.
Let's step back and remember when the 4k first came out people were hating the 4k because it was so different from the previous MPCs.
That quickly changed to people wishing the older MPCs had various features of the 4k.
Much of what JJ originally did with the 1k was mirroring features and workflow from the 4k.
Even the 5k big update was heavily driven by the 4k features.

OS 3.0 while be very "FORCE" driven is greatly based in features that the desktop was already more capable of doing than the standalone.
So with this update a lot things will benefit from it;
- the Force now doesn't seem like a throwaway product
- the standalone MPCs get a very competitive bump
- the MPC Key 37 becomes more appealing to modern users
- Akai can develop and sell the desktop to a wider base of users one the 3.0 shows up

Best take away from it is to try it out and if it doesn't work for you go back to 2.x but the one thing you don't want to do is get caught up in youtubers showing their limited understanding of 3.0.

Also if the MIDI bug is fixed in 3.0 people should stay on Akai about fixing it for 2.x since they are so different and it's been a problem for a long time.

Big Tick wrote:
Yes it works with KG too.
Also with the new Slice Motion feature, you can use that to do round robin without using layers. So you can have drum kits with 8 velocity levels, and as many round robins as you want.

Good looking.

Neurone wrote:I wish Akai would make MPC2 open source while they carry on developing MPC3.

It would have to Benefit InMusic if they offered Open Source.

I havent said much just been reading, but tbh im frickin stoked. i doubt they will skew the work flow of the mpc in a traditional sense. i wouldnt be shocked to find that

im assuming the arranger is optional like in the force. its just for when you get done creating your sequences so you can format a finished song with tactility (if you chose to do it that way). they arent gonns just convert it into a 4x4 force box on us... that would be super cool, but the vintage crowd would flip their wigs lol.

The new system simplifies things for working with the Arranger & mixer. Now you don't have to keep track of what's on each track for each sequence. If you need more programs just load them in new tracks. There's 128 track s slots & I doubt most are using most of them all the the time. Most of tracks go unused, now they're not there unless you create them.

You still use 1 drum track to edit a bunch of samples being triggered on different MIDI tracks. The thing that sucks about this is that, if you move a drum track around later you'll have to reassign all the MIDI tracks getting sent to it because technically your sending tracks to a track slot number, not a specific track name, if that makes sense, but that's real easy to adjust in the track settings window. Having a project template with tracks already made & named is key.

Not all legacy MPC users hate the new system. I had a 1000/2500 since 2005 & I hated the traditional MPC way handling sequences/tracks/programs. It's the reason why I got the RS7000 back in 2014 & later the Pyramid in 2019 & the Force, which is now my main sequencer, in 2021. I used to use the track mute method on the MPC, but most of my tracks would have the same program across sequences.

The thing that sucks about this way is that you make a track edit like sequence data, track name or reorder, you'll have to make sure that you update all other tracks on other sequences. Hated that with a passion!

The Force sequencer is the future as it can be used just like the MPC seq by only playing the clips in the same scene or it can get more advanced by playing clips from different scenes & all that can be recorded into the Arranger live.

Ultros wrote:im assuming the arranger is optional like in the force. its just for when you get done creating your sequences so you can format a finished song with tactility (if you chose to do it that way). they arent gonns just convert it into a 4x4 force box on us... that would be super cool, but the vintage crowd would flip their wigs lol.

Untill they realize it's the better way, but they'll need the clip-matrix to make it work for the best!
They gonna hate that they love it

Big Tick wrote:Yes it works with KG too.
Also with the new Slice Motion feature, you can use that to do round robin without using layers. So you can have drum kits with 8 velocity levels, and as many round robins as you want.

There's already been a working way to have more than 4 velocity layers even before, by placing several keygroups on the same MIDI notes, each keygroup with 4 layers so with 2 keygroups you get 8 layers, and with 3 keygroups you could do 12 layers etc. Previously the real maximum number of samples was 128 x 4 = 512. I've converted a keygroup with 5 note-on layers and 3 note-off layers into an Akai keygroup program, and it was only limited by what I could cram in a total number of 128 keygroups or "Instruments" as it's called inside the XML format. Is the limit higher now, or is it still 128 "Instruments" i.e. keygroups?

I only have a Force and I think it'll take some time before I'll be able to test it.

Has there been any indication of when the public beta begins?

Hi-D-Ho-Man wrote:Has there been any indication of when the public beta begins?

Someone earlier said he signed up for the public beta, so I guess you can go sign up now.

eLuSiVeMiTe wrote:

kja wrote:So a basic question.. But does it load all the prior projects ok if I update? I don't want to lose my current projects I'm working on.. anybody tried it yet?

If you have a single sequence workflow with programs used on multiple tracks it's been crippled unfortunately.
So any project with multiples won't play correctly. Any duplicates get made midi tracks.

Feels like the worst of the mpc combined with the worst of the force.
At least on the force we had midi clips playing from the same program.

Really needs a new name. No longer an mpc

This is what I feared. 3.0 might not be for me.

Hi-D-Ho-Man wrote:Has there been any indication of when the public beta begins?

I've seen people in the wild who say they have it but I'm not sure if they are insiders or not. You can sign up now but not many people have it yet.

For the few that were wondering like me... In healthy music's latest stream, he shows the Clip Matrix Icon in the menu screen. He moves it to put the arranger there.

When he goes to the arranger , his screen shows the Clip and List button on top like the Akai screen shot does.





You have to skip to the 15 minute mark to see it. Be warned it's a producer/YouTube personality video , I know it triggers some people on here.

https://www.youtube.com/watch?v=hrX97dwnMVc&t. couldn't get the embed to work

I already started filing bugs against the things that I need. No need to wait for the Public Beta to tell them that they need to store the track mute's in each sequence.