MPC 3 -- Let's GO!!

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 .

organic wrote:

KaoticShock wrote:Has anyone heard anything about updates to the keygroup engine?

Good question. I see 8 velocity layers for drum programs. Does it apply to keygroup programs also? Mpc tutor said some about a robins and velocity update. Would be nice if we could build instruments with robins and velocity on one channel, to make it easy to use on different songs. If the ”change track view” would remain on screen without holding down a button, you could have keyswitches for different articulations and still be able to use the pitch and mod wheels.

eLuSiVeMiTe wrote:

jalex wrote:do we have a confirmation that we can downgrade back to 2.15 or whatever if we don't like it ?

There's a downgrade button. Been flirting back and forth trying to make my projects suitable to convert to 3.0

tbh long as programs are still recognised by 3.0 its all good; people are saying programs are now locked to a track, that will suffice.

as there is no real extra benefit of having a program that can be assigned to multiple tracks; aside maybe when editing the program and having those updates represented on multiple track; and also saving memory.

As presumaby each track that uses the same program will require a duplicate instance of that program; but as now that we have disk streaming presumably that will read from disk instead of being loaded into RAM, but having multiple instances of a program in RAM would be problematic.

I have drum programs filled with drum loops and one shots that I would like carried across into the 3.0 world, I also want my projects to open without issue in the new world.

Presumably if u save a project in 3.0 then downgrade to 2.x its a wrap for ur projects; so may need to save 2.x projects that get opened and edited in 3.0 under a seperate name while experimentation takes place.

Akai have been doing a great job developing the MPC platform; and this 3.0 will be revolutionary step just like the first mpc touch was a revolutionary step in changing the interface/workflow.

I was happy to move from mpc studio into the touch screen world, and am happy to move from 2.x to 3.0; people are always complaining about change, and always complaining about trivial bug fixes and trivial features, but akai are offering so much value for free its suprising people are not more appreciative.

As some people were always acting as if this would be a paid upgrade; some were even promoting the idea of a montly subscription, but alas all have been proven wrong.

got it jpeg. thanx.
your impressions are encouraging!
I AM hoping for the best and can't wait to get the download, but I was a little scared that it's gonna mess up my old projects that i didn't render/finish, with the whole new track/programs merging schema.
now for onto the long wait...

jpeg wrote:As presumaby each track that uses the same program will require a duplicate instance of that program; but as now that we have disk streaming presumably that will read from disk instead of being loaded into RAM, but having multiple instances of a program in RAM would be problematic.

Duplicating a program has no additional bearing on ram as you don’t duplicate the samples, only the program settings and parameters. 100 duplicate programs will pretty much use the same ram as the one original program

Also disk streaming is by default only for audio tracks, there’s too many performance issues when using it to play back lots of little samples within a program. You can manually set all those individual one shot samples to be streamed but it will likely crash your mpc when it starts trying to disk stream 100s of samples simultaneously during a performance

So, how stable is the beta? Should I sign up ?

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 .

Are you getting earlier than early access ?

The Akai video made it seem like there were more options for midi learn , but it went by so fast.

Hoping they allow midi learn in sample edit mode for qlinks.. they do in the desktop software

MPC-Tutor wrote:Also disk streaming is by default only for audio tracks, there’s too many performance issues when using it to play back lots of little samples within a program. You can manually set all those individual one shot samples to be streamed but it will likely crash your mpc when it starts trying to disk stream 100s of samples simultaneously during a performance

Well... Other software samplers like Halion or Kontakt use some sort of disk streaming heavily cached by RAM.

(Just saying, I'm totally happy with how MPC handles samples, with the amount of RAM and looking forward to see disk streaming for audio tracks)

Seems AKAI MPC 3 is going to have the old 'track mute' functionality as an option according to this guy ...

https://www.youtube.com/watch?v=PBENuWx ... asY&t=1208

mikobuntu wrote:Seems AKAI MPC 3 is going to have the old 'track mute' functionality as an option according to this guy ...

https://www.youtube.com/watch?v=PBENuWx ... asY&t=1208

Good to know , hopefully clip programs are just missing also.

mikobuntu wrote:Seems AKAI MPC 3 is going to have the old 'track mute' functionality as an option according to this guy ...

https://www.youtube.com/watch?v=PBENuWx ... asY&t=1208

They had better bring it back. I get that some poeple want audio muting like a mixer but most people don't want instant cutout of audio.

What should "track mute" mute? When tracks and programs were separate, vs when a program is a part of a track. Should "track mute" mute what used to be called track, or should it mute what used to be called program.

HouseWithoutMouse wrote:What should "track mute" mute? When tracks and programs were separate, vs when a program is a part of a track. Should "track mute" mute what used to be called track, or should it mute what used to be called program.

I don't see the confusion.
If you are generating music, you want to stop subsequent events or notes following the mute from being generated.
If you have audio, you want to silence the audio.

Registered for beta, looking forward to try it out!
First look the UI seems to be much less needlessly convoluted and more direct, that was my biggest issue with the newer MPCs.
Kept the Live2 just in case such an update would ever come up. Hope it will be worth the wait.

LivePsy wrote:I don't see the confusion.
If you are generating music, you want to stop subsequent events or notes following the mute from being generated.
If you have audio, you want to silence the audio.

Which exact buttons do you press in the two different cases in MPC3? What button do you press when you want to stop MIDI event generation, and what button do you press when you want to silence audio? I'm particularly interested in how to "MIDI mute" in the Force. I've only been able to find a mute button which immediately silences audio. I don't want that, I want to interrupt MIDI event generation and then re-enable it, like I can do to a MIDI track. But if the track happens to have an embedded keygroup, drum or plugin program, how does one MIDI-mute without audio-muting.

HouseWithoutMouse wrote:

LivePsy wrote:I don't see the confusion.
If you are generating music, you want to stop subsequent events or notes following the mute from being generated.
If you have audio, you want to silence the audio.

Which exact buttons do you press in the two different cases in MPC3? What button do you press when you want to stop MIDI event generation, and what button do you press when you want to silence audio? I'm particularly interested in how to "MIDI mute" in the Force. I've only been able to find a mute button which immediately silences audio. I don't want that, I want to interrupt MIDI event generation and then re-enable it, like I can do to a MIDI track. But if the track happens to have an embedded keygroup, drum or plugin program, how does one MIDI-mute without audio-muting.

The early videos say that currently both plugin and audio muting is instant, but plugin muting might be improved to mute next midi event in the future. You're right, it makes no sense to cut off the audio of a plugin track.