MPC 3.4 Beta 3 - Bug Reports & Feedback Here

Did anyone try out the XY macros? For me they sort of work, but overall I find them unusable because of the UI in a live situation. That's odd, because in the overwiew video by Akai they are touted as a live permormance feature.

Weird interplay between different modes
To make all assigned XY areas work, the mode selector must be one any that has been assigned yet.
That means if you happen to end on a mode with no assignements, the pad does not react at all.
The one exception are quad axis. It is enough that either X or Y is assigned.

That is a bug to me.

No visual clue which areas have assignments
Let's say I have assigned some columns, I want the pad to become striped.
Probably currently not possible, because you can layer all modes. Super nifty, but only for real advances use cases. Actually the only real use case I know of is to layer X and Y quadrant axes.

No visual cluse what macro you are manipulating currently
What is shown is always the name and value of the selected mode.
Which also make some sense if you consider the layering mentioned above. But at least the name for each area should be shown.

The first time I wished something could be more restricted, to make a better UI. Meaning except for quad modes the layering of modes should not be allowed. No

And finally...

You have to go into Q-Link edit mode to get access to them.
To be useful there must be some kind of shortcut.

BTW, funny that there is no mode for a dual XY pad.

MIDI channel selection doesn't work: respond to all MIDI channel even if a specific one is selected on a track

Mpc 37 has anyone noticed project load times are much longer on the beta? Used in a live setting the same projects take twice as long sometimes 10 seconds (bear in mind there are no notes recorded just plug ins and samples to play via the keyboard and a midi keyboard) having to revert back to 2.15 , load times are roughly 2 to 4 seconds which is manageable but 10 seconds is a long time when you need to keep the crowd interested!

PascalJoguet wrote:MIDI channel selection doesn't work: respond to all MIDI channel even if a specific one is selected on a track

Works for me and a USB keyboard plugged into a MPC One.

Did you perhaps confuse MIDI out (visible on the main screen) and the MIDI in (visible on mixer and track settings)?

Cerijames wrote:Mpc 37 has anyone noticed project load times are much longer on the beta?

Is your MPC offline? Akai lists longer project load time when not connected to the Internet in the known bugs.

From my understanding the MPC 3.4 now allows to map the Q Links to external midi controllers. We tried this feature - but our USB midi controller didnt get detected by the MPC. (We tried two different ones, 1x NI Tracktors controller and Novation Remote SL.)

Can you confirm if this would generally work? I.e. mapping the Q Links to a remote midi controller?

Sternenlicht wrote:<font style="vertical-align: inherit;"><font style="vertical-align: inherit;">Según tengo entendido, el MPC 3.4 ahora permite asignar los Q Links a controladores MIDI externos. Probamos esta función, pero el MPC no detectó nuestro controlador MIDI USB (probamos dos diferentes, un controlador NI Tracktors y un Novation Remote SL). ¿ </font></font>

<font style="vertical-align: inherit;"><font style="vertical-align: inherit;">Puedes confirmar si esto funcionaría en general? Es decir, ¿asignar los Q Links a un controlador MIDI remoto?</font></font>

I am deeply sorry to say that midi in v3 is totally broken, I use external controllers and I have had to go back to v2 much to my regret because v3 is great as an idea, but in practice it is less flexible than v2.
If you plan to use controllers with triggers with mutes and etc it will be impossible since in Learn mode the mapping options to controls like pad mute are no longer available since in mpc 2 that belongs to the defunct Programs architecture, and in v3 you can only map to Tracks... they have forgotten to migrate midi options from Programs to the current Track... very sad, at akai there is someone who has a good job and does not deserve it...

I just want to use macro controls to volume automate several tracks at once.

I.e. having multiple percussion tracks, volume on one down, and volume on a 2nd up, or filter them in /out with a macro. Or having a single midi clip pointing to multiple instruments, and only volume transition between the sounds. That would be the main use case.

Actually that what a Q Link can do, but done from a 16 knob controller. (Dont have MPC X)

Sternenlicht wrote:I just want to use macro controls to volume automate several tracks at once.

I.e. having multiple percussion tracks, volume on one down, and volume on a 2nd up, or filter them in /out with a macro. Or having a single midi clip pointing to multiple instruments, and only volume transition between the sounds. That would be the main use case.

Actually that what a Q Link can do, but done from a 16 knob controller. (Dont have MPC X)

I insist on my previous comment, I have returned to v2 because the midi in v3 cannot be configured as it should, I repeat, the midi is broken, I use controllers for the same thing you want to do but directly in the "Midi Learn", in my way of working I don't see any sense in using the qlinks for those functions, do you want it like that? ok.. why do you want to make a (I suppose) definitive mapping in the beta? since you have a controller and you want to get the most out of it, isn't it more sensible to work on your ideas and serious projects in v2 that can be configured for those tasks and reserve the qlinks for other functions? I repeat again, even if you don't use silencers, the root of the problem is the same, that is, the broken midi. If you want use v3 without controllers you will be fine, if you want use midi controllers v3 is not for you, wait to stable and official v3. good luck

I found a video, maybe it will help you.

https://www.youtube.com/watch?v=1kta8FmmhCY?si=i2jEh46eiZqmaRy8

Munko Roughliffe wrote:If you plan to use controllers with triggers with mutes and etc it will be impossible since in Learn mode the mapping options to controls like pad mute are no longer available since in mpc 2 that belongs to the defunct Programs architecture, and in v3 you can only map to Tracks...

When I choose a drum track as source, I can also choose a bank and then a pad. As target I can choose pad mute in the mixer category.

But I may get it all wrong. The whole process of MIDI learning is quite arcane to me.

When I paste copied MIDI events all new notes are C-2.

Sternenlicht wrote:From my understanding the MPC 3.4 now allows to map the Q Links to external midi controllers.

It is probably not possible to do that without some form of hacking.

Masi wrote:

Munko Roughliffe wrote:If you plan to use controllers with triggers with mutes and etc it will be impossible since in Learn mode the mapping options to controls like pad mute are no longer available since in mpc 2 that belongs to the defunct Programs architecture, and in v3 you can only map to Tracks...

When I choose a drum track as source, I can also choose a bank and then a pad. As target I can choose pad mute in the mixer category.

But I may get it all wrong. The whole process of MIDI learning is quite arcane to me.

In 3 Beta?

MPC Live 1

I'm trying to re-create my live performance template that includes over 100 tracks (and multiples of this sequence), lots of plugins, etc. I can barely even add 75 blank drum tracks before I'm topped out on memory. If MPC 3.0 is going to take up this much RAM I'm not going to be able to use it live.

Really bummed but looks like I'll be stuck on MPC 2.9.1 forever and ever and ever and ever....oh well. Still a really great tool. Those fancy plugins are sooo good looking tho!

I’ll be stuck on v2 for the foreseeable future too, but as the midi-note off bug has killed my workflow anyway, both MPCs are just gathering dust.
Back to the DAW software.
May as well sell them.