MPC midi info for confused souls.

Understanding midi control on MPC

There are 3 sections to how you can control midi to your mpc by simply programming your controller

Section 1, transport control
Transport controls are limited to channel 1. your external controller must be on channel 1 and settings midi > control must be enabled

Section 2, drum control
To control drums your controller must be on or capable of sending to channel 9. the drums play at middle c on your keyboard. or wherever they are mapped too sometimes its up or down and octave. Settings > midi > track must be enabled.

Section 3, key control
your keybed should be on channel 7 internally mpc expects your keyboard to be here. this also requires you to have settings > midi > track enabled.

Now for those of you wondering what "global" is for, it's for *global transport controls* controls that carry across through out all menus. interface controls. qlinks etc. enable settings > midi > global and map your controller to channel 1 and set your cc to the according qlink.

You don't need to hack anything or do any crazy work. just understand that the unit expects 3 simultaneous channels to control it and the according prismatic input flag must be enabled (global, control, and or track). You can map literally anything you want. it's always been there.

It works this way because thats how the mpk61 interfaces with the mpc. The mpk drum pads even have sysex lighting like the mpc itself when connected. Nobody ever questioned "why does it work with that plastic pos but not my favorite keyboard?" because you need to map the keyboard channel and ccs *on the external keyboard*.

The keyboard conforms to the mpc's desires not the other way around. Again nice n simple, transports channel 1, drums channel 9, keys channel 7. Try it. Go try rn with your rolland korg or moog.

Here is a list of midi notes and cc's for the Generation 1 modern MPC



.xmm Midi Mapping...
"Target control" is the "dec" value from the list above. Remember to set channels if you're going to go the .xmm route. Here is the apc-key midi mapping. Notice there's a target control, a channel etc? Mapping_control is from 1-4 and controls the type, note, cc, absolute etc.


Please andy write this crap in the mpc-bible once you poke at it a bunch.

there are mapping_control ="5" in your list

Thanks for the post Ultros, I've read it about 5 times now.

Ultros wrote:Understanding midi control on MPC.

Ultros wrote:Understanding midi control on MPC.

Code: Select all    name             dec hex
----------------------------------
    MPC_ENCODER_TURN 100 0x64
         MPC_QLINK_1 16  0x10


Where do you have the list from? Or rather, do you think you can get a list for gen2?

I have a MIDI controller that has something akin to a touch strip. It would be awsome to use the scene fader capability on a gen1 device. MPCe could be possible as well.

@masi :

Zangetsu and I mapped it together while we created the force midi library for MPC.

I would need hands on a modern mpc with ssh to make you a list.

I bet i can make the mpce stuff work on a gen1 with an apc mini, or apc key. albeit not well since they are on/off only not velocity sensitive.

Neodymium wrote:Thanks for the post Ultros, I've read it about 5 times now.

No problem dude lol i wrote this just cus i knew you wanted to know. my explaination in the other thread was kinda crumby.

I hope you get it going, if you have any trouble just message me.

I got my goofy little akai mpk mini play doing start and stop and record with the drum pads on one layer and drums on the other. I was sure i showed it off before but maybe not.

great post, thanks mate.

Excellent post.

So do you need SSH access to modify these files on gen1? On gen2 you don't need SSH access? Is that right?

wavejockey wrote:there are mapping_control ="5" in your list

Mapping_control

1 Toggle Button
2 Momentary Button
3 Fixed Button
4 Note
5 Abs CC
6 Rel CC Offset
7 Rel CC's Complement

I’ve tried th.xmm method as described but I can’t get it to work using the target control dec numbers from the list, e.g. the next seq function in ultros’s list has a target control dec value of 42 that does not work , but if you set the target control dec value to 101 it does work as expected . Is there something else that needs doing to make it follow ultros’s list I wonder?
Because if there was a similar list for the gen2 units all the extra buttons could maybe be mapped. And I’m guessing the force’s grid could too . As it already is in the latest Hakai release albeit only to the launchpad pro mk3.

Wul wrote:I’ve tried th.xmm method as described but I can’t get it to work using the target control dec numbers from the list, e.g. the next seq function in ultros’s list has a target control dec value of 42 that does not work , but if you set the target control dec value to 101 it does work as expected .

This is in line with this document:
https://github.com/TheKikGen/MPC-LiveXp ... ode-how-to

It also lists the first Q-Link as 24. Which matches the .xmm I got after exporting from the MPC Desktop software (version 2.x).

Masi wrote:

Wul wrote:I’ve tried th.xmm method as described but I can’t get it to work using the target control dec numbers from the list, e.g. the next seq function in ultros’s list has a target control dec value of 42 that does not work , but if you set the target control dec value to 101 it does work as expected .

This is in line with this document:
https://github.com/TheKikGen/MPC-LiveXp ... ode-how-to

It also lists the first Q-Link as 24. Which matches the .xmm I got after exporting from the MPC Desktop software (version 2.x).

Agreed , I have been using that method for years. I can confirm that list at the end works, however that list is not the same as ultros listed here
viewtopic.php?f=48&t=220325&view=unread#unread
That list is the midi info what each button on a Mpc x sends to the operating system via the private Mpc midi port .
Also contrary to what is states in the link that it doesn’t work on the force , I can confirm that it does albeit with a very much reduced control items , all the looper controls do though , you can actually record to the looper without going to the looper page, very useful.

Here is a documented .xmm from kikgens github detailing most of the items.



Here is his more detailed explaination on creating .xmm

https://github.com/TheKikGen/MPC-LiveXp ... ode-how-to

Ultros wrote:Here is a documented .xmm from kikgens github detailing most of the items.

Thank you.

But I don't know why my .xmm is not working on the MPC. For now I have only mapped Q-Links becaus this is my main interest. Should I try other targets?

I have enabled SSH on my MPC One running OS 3.7. I put the fileinto "/storage/MPC Documents/Midi Learn" and did a reboot. This didn't do the trick. Should I put it somewhere else? AFAICS you never mentioned the folder.

Then I modified "/media/az01-internal/Settings/MPC/MPC.setting" as document by KikGens. But that still didn't do the trick.