MPC midi info for confused souls.

Ok so your controller is set to send cc on channel 1 (on the device itself). then you programmed the xmm to recive your chosen cc on channel 1. you make sure the xmm loads. and lastly settings > midi > global is enabled?

Say you had an mpk249* (edit) one of these (https://external-content.duckduckgo.com ... bc8900c35a) and you plugged it into your mpc and you were like wtf the qlinks dont work? its because "global" isnt flagged on input midi.

If it is, there is some other issue. I assure you qlinks worked i have mapped those to the dials on my mpk mini play in the past.

You may have to screw around with it until you find what works. but the channels i mentioned are absolutely crucial. you cant come in on channel ?? for cc and remap it in xmm. it wont listen to it.

Could be different with different roms too. i really dont know. I am on 2.14 still a pretty old rom. I'll try to mess with it myself and see what it took to make those work. I maybe mis-rememebering and the qlinks only went to selected program. I know they work though because I mapped mine to the little dials on my crappy keyboard and realised quickly they would not suffice.

Masi wrote:

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.

What is the path of the midi learn folder?
Asking coz there are two paths to it , I’ve found only one works
The one that works is
/usr/share/Akai/SME0/Midi Learn
Delete all the unwanted .xmm’s from here just have your .xmm and the version file
Make sure your 2 added lines are in the Mpc.settings (after a reboot, coz they get overwritten) , set your controller midi in to control .
That is all .

Edit I always configure my .xmm to channel 16 out of the way to avoid conflicts.
And I’ve never ticked global always control.

Sorry ultros if I’m contradicting you but it’s what I’ve found works flawlessly for the last 3 years on all os versions.

Question for ultros……how would you get you’re target control list respond, way I see it is that list is what the Mpc hardware sends to he hidden midi private port , when I try to make a connection in terminal it’s always busy., as you would expect.

Your global and transports must be on channel 1.

The device expects 1 for global and transport, 7 for keybed and 9 for drums.

Anyone own an mpk mini play? download the software for it and switch your keybed to channel 7, drums to 9 and then program the cc's for the dials using values from my original list (hex values need to be converted to decimal). Skip the xmm step. Plug it in. try it *with* midi > global / track enabled. If that doesnt work switch "keybed and controls" to channel 1 in the editor below and try it again. the keybed will end up toggling menus if its on channel 1.



If your controller is fully programable like this one, you dont need to make a .xmm just program the controller to the channel and note or cc you wish to target. (the actual real note or cc the mpc software uses on the correct channel)

If you program all the drums you can play the drums and keys at the same time with *merge* enabled as well right from the keyboard. Iirc my device supports more than one config, so i can program different channel and note / cc configs for different favorites

I use aplay --dump to get the midi info from my devices btw. if i need to map one blindly. If you want to know every button of your mpc, hook it up in controller mode* and log the midi info and make a list. you will end up with the list i provided.

I have a programmable controller and whatever I send on channel 1 is ignored.

I tried Q-Links targets from Ultros list and the the ones of TheKikGen.
I tried start/stop from both list.

Nothing.

I wonder if it works without .mmc for known devices. At least some of the pre-made files have a <device> section in them.

Wul wrote:The one that works is
/usr/share/Akai/SME0/Midi Learn
Delete all the unwanted .xmm’s from here just have your .xmm and the version file

Um. You have deleted all factory mappings? And to do that you hat to remount / as rw?

Wul wrote:Make sure your 2 added lines are in the Mpc.settings (after a reboot, coz they get overwritten)

MPC.settings is also written when you exit the preferences screen. But when it is read?

I didn't dare to delete the factory mappings. Just adding my file (after remounting / as rw), doing a reboot and changing the lines in MPC.settings didn't help.

Yea do the remount , delete all the files , then do the opposite remount .
Edit the Mpc.settings file , then I make that undeletable , power the unit down , when it’s rebooted you can make the Mpc.settings file deletable again . That always works for me . I do that everytime there is an update .
I delete all the files because, I’ve proved they have a tendency to select them randomly,
And it also stops copies of them being created , as I’ve seen already in this thread.

Wtf now it doesnt even work for me! i wonder where this went wrong. lemme get back to you mr wul, im missing a step here..

Ultros wrote:

Wul wrote:Yea do the remount , delete all the files , then do the opposite remount .
Edit the Mpc.settings file , then I make that undeletable , power the unit down , when it’s rebooted you can make the Mpc.settings file deletable again . That always works for me . I do that everytime there is an update .
I delete all the files because, I’ve proved they have a tendency to select them randomly,
And it also stops copies of them being created , as I’ve seen already in this thread.

Stop trying to make an xmm and map your midi controller itself dude. You keep circling back around to the xmm. its NOT NEEDED. get a mapable controller.. something tells me you are unwilling to relent on some pos controller mapped all wrong.

when i say *map the controller* i dont mean in xmm. i mean go into your controller and set new cc's channels and notes.

You could use a midi filter that goes between input device and mpc and redirects messages to appropriate channels.

The xmm is a last effort after you've configured the controller properly and want even more control.

I use the .xmm method because I use a og korg nano kontrol for the desktop, Mpc one, and more limited on the force. The same buttons, every button and slider, everytime, anywhere. It just works . I also have a lemur template on the iPad using the same .xmm , again it works
Just as a matter of interest I just tried mapping a slider on my Kenton controller to qlink 1 using your list, it was cc16 on channel 1, with it set to track, global and then control , confirmed the Mpc one was recieving the message …….but nope it didn’t respond.

Man it's not even working for me now. I wonder wtf changed. Literally nothing is doing what it should.. maybe i had to map the controller then make an xmm as well. its been so long now. i was sure i did this without hacking and was all surprised by it. i just gotta figure out where i am going wrong. sorry about the retarded thread i guess.

Ultros wrote:Man it's not even working for me now. I wonder wtf changed. Literally nothing is doing what it should.. maybe i had to map the controller then make an xmm as well. its been so long now. i was sure i did this without hacking and was all surprised by it. i just gotta figure out where i am going wrong. sorry about the retarded thread i guess.

Really hope you figure it out. This was looking like a bit too much to bite off for me, but the more I think about it, the more I think that getting it to work will really add to my MPC One, especially with the recent changes they made to make the Q-Links much more flexible and powerful.

Don't think you need to apologies for trying to help.

Ultros wrote:Man it's not even working for me now. I wonder wtf changed. Literally nothing is doing what it should.. maybe i had to map the controller then make an xmm as well. its been so long now. i was sure i did this without hacking and was all surprised by it. i just gotta figure out where i am going wrong. sorry about the retarded thread i guess.

I guess it came in by accident and the same way it was gone again.

No need for excuses, after all it did work for you at some time.