Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar
By TheUnfuckwithable Fri Aug 19, 2011 7:06 pm
hey guys,

i just did a quick test to see what´s possible with the midi to button feature and i must say i am impressed :shock:

for now i have my mpc cursor controlled by 4, 5, 6, 8 (numpad) and my dec and inc buttons by , and 0 (again on the numpad). i can now navigate ergonomically thru the mpc with my left hand.

even the cheapest keyboard feels way more solid than those crappy mpc buttons and data encoder!

would post a short vid if you guys are interested...

EDIT: the only downside is that you obviously have to use your computer as "translator". as mine is running virtually 24/7 that´s no big deal for me.

you can even go further and connect a usb numpad for example to have a dedicated mpc controller. you can then print your own stickers for the keys that show the function assigned to it. :D
Last edited by TheUnfuckwithable on Fri Aug 19, 2011 7:13 pm, edited 2 times in total.
User avatar
By TheUnfuckwithable Sat Aug 20, 2011 12:54 pm
just a short vid i did to show you that it´s possible 8)

http://www.youtube.com/watch?v=tooGSd1ck2U

of course i'm interested! how are you translating your keystrokes to midi?


i use bome´s midi translator pro. very flexible and versatile application. i´ve also tried various other apps including vmpk and midi-ox, but afaik midi translator pro is the only one that let´s you assign virtually any key (e.g. the cursor keys) to a midi command (note oon, note off, etc.).

i think i am going to write a little tutorial on how to set it all up and put taht on my website.

EDIT: what´s special about bome´s midi translator pro is the fact that it doesn´t need to be focused to translate keystrokes to midi data. it just minimizes to the tray bar. this way i can have reaper open and still navigate thru the mpc with my keyboard. of course you need to keep your mind on two things when working with MTP and an audio app at the same time:

1. you´ll have to have at least two independent midi outputs on your interface if you want to use MTP and send midi data to another device. example: out A could then be used by MTP (important: disable out A in your audio app!) while out B sends midi data to a rack synth.

2. ideally, the keystrokes assigned in MTP should not be used in your audio app. otherwise you would trigger actions in your DAW while navigating thru your MPC.