Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
By dtaa pla muk Wed Jul 27, 2011 4:17 pm
ok folks, this is the currentstandard midi note > button layout
this is the foundation for meta control.

setting up your midi > button mode (please see this page: http://www7a.biglobe.ne.jp/~mpc1000/os2xl/button.htm) will allow us to share macros to automate certain time consuming tasks and/or control our MPCs with voice via glovepie and windows 7.

i built this list by entering the BUTTON assignment page in jjos2xl and entering the actions/buttons EXACTLY AS LISTED for ease of setup. if any future actions are added, i will recommend that jj add them at the very end, where we still have 10 extra spaces for added functionality.

thanks for your help.
nym

000 - PLAY START
001 - PLAY
002 - STOP
003 - OVERDUB
004 - REC
005 - BAR >>
006 - << BAR
007 - STEP >
008 - STEP <
009 - CURSOR UP
010 - CURSOR DOWN
011 - CURSOR RIGT
012 - CURSOR LEFT
013 - SLIDER
014 - LOAD
015 - SAVE
016 - TRACK MIXER
017 - RECORD
018 - TRIM
019 - PROGRAM
020 - PAD MIXER
021 - MIDI/SYNC
022 - OTHER
023 - EFFECT
024 - SEQ EDIT
025 - STEP EDIT
026 - GRID
027 - SONG
028 - TRACK-01
029 - TRACK-02
030 - TRACK-03
031 - TRACK-04
032 - TRACK-05
033 - TRACK-06
034 - TRACK-07
035 - TRACK-08
036 - TRACK-09
037 - TRACK-10
038 - TRACK-11
039 - TRACK-12
040 - TRACK-13
041 - TRACK-14
042 - TRACK-15
043 - TRACK-16
044 - TRK-01 MUTE
045 - TRK-02 MUTE
046 - TRK-03 MUTE
047 - TRK-04 MUTE
048 - TRK-05 MUTE
049 - TRK-06 MUTE
050 - TRK-07 MUTE
051 - TRK-08 MUTE
052 -TRK-09 MUTE
053 -TRK-10 MUTE
054 - TRK-11 MUTE
055 - TRK-12 MUTE
056 - TRK-13 MUTE
057 - TRK-14 MUTE
058 - TRK-15 MUTE
059 - TRK-16 MUTE
060 - TRK-01 SOLO
061 - TRK-02 SOLO
062 - TRK-03 SOLO
063 - TRK-04 SOLO
064 - TRK-05 SOLO
065 - TRK-06 SOLO
066 - TRK-07 SOLO
067 - TRK-08 SOLO
068 - TRK-09 SOLO
069 - TRK-10 SOLO
070 - TRK-11 SOLO
071 - TRK-12 SOLO
072 - TRK-13 SOLO
073 - TRK-14 SOLO
074 - TRK-15 SOLO
075 - TRK-16 SOLO
076 - MAIN
077 - WINDOW
078 - UNDO
079 - SHIFT
080 - TEMPO/REPET
081 - MODE
082 - NUMERIC
083 - ERASE
084 - FULL LEVEL
085 - LEVELS
086 - NEXT SEQ
087 - TRACK MUTE
088 - BANK A
089 - BANK B
090 - BANK C
091 - BANK D
092 - F1
093 - F2
094 - F3
095 - F4
096 - F5
097 - F6
098 - AFTER1
099 - AFTER2
100 - AFTER3 (MPC2500 ONLY)
101 - AFTER4 (MPC2500 ONLY)
102 - NUMERIC 0
103 - NUMERIC 1
104 - NUMERIC 2
105 - NUMERIC 3
106 - NUMERIC 4
107 - NUMERIC 5
108 - NUMERIC 6
109 - NUMERIC 7
110 - NUMERIC 8
111 - NUMERIC 9
112 - NUMERIC +
113 - NUMERIC -
114 - NUM.ENTER
115 - DATA +
116 - DATA -
117 - LOOPING REC
118 -
119 -
120 -
121 -
122 -
123 -
124 -
125 -
126 -
127 -
User avatar
By sally Wed Jul 27, 2011 6:05 pm
I hope you have many volunteers to check, as a last resort I'll be closing the list of volunteers. I have a mpc2500.
I have the intention of trying.
thank you very much Nym.
I am at your orders, give me orders Nym !
User avatar
By TYPO Wed Jul 27, 2011 7:30 pm
Nym wrote:ok folks, this is the preliminary standard midi note > button layout
what will eventually be the foundation of what i am codenaming the "jenius meta control project"

mods, a sticky would be much appreciated. i will also try to get this put up on jj's page once i get the ball rollin and some youtube vids made.

setting up your midi > button mode (please see this page: http://www7a.biglobe.ne.jp/~mpc1000/os2xl/button.htm) will allow us to share macros to automate certain time consuming tasks and/or control our MPCs with voice via glovepie and windows 7.

i built this list by entering the BUTTON assignment page in jjos2xl and entering the actions/buttons EXACTLY AS LISTED for ease of setup. if any future actions are added, i will recommend that jj add them at the very end, where we still have 10 extra spaces for added functionality.

NOTE: i need someone with a 2500 to check this. i THINK i entered the mpc2500 specific stuff (after 3, 4) but since i don't own a 2500 i am not certain.
if you have a 2500, please check my work by entering button mode and, click by click, scrolling through the actions...keep count to make sure they line up with mine, and if there are any 2500 actions that i've missed, take note of where they are. we want these controls to work with either the 2500 or the 1000 jjos2xl, so please help with this!

thanks for your help.
nym

000 - PLAY START
001 - PLAY
002 - STOP
003 - OVERDUB
004 - REC
005 - BAR >>
006 - << BAR
007 - STEP >
008 - STEP <
009 - CURSOR UP
010 - CURSOR DOWN
011 - CURSOR RIGT
012 - CURSOR LEFT
013 - SLIDER
014 - LOAD
015 - SAVE
016 - TRACK MIXER
017 - RECORD
018 - TRIM
019 - PROGRAM
020 - PAD MIXER
021 - MIDI/SYNC
022 - OTHER
023 - EFFECT
024 - SEQ EDIT
025 - STEP EDIT
026 - GRID
027 - SONG
028 - TRACK-01
029 - TRACK-02
030 - TRACK-03
031 - TRACK-04
032 - TRACK-05
033 - TRACK-06
034 - TRACK-07
035 - TRACK-08
036 - TRACK-09
037 - TRACK-10
038 - TRACK-11
039 - TRACK-12
040 - TRACK-13
041 - TRACK-14
042 - TRACK-15
043 - TRACK-16
044 - TRK-01 MUTE
045 - TRK-02 MUTE
046 - TRK-03 MUTE
047 - TRK-04 MUTE
048 - TRK-05 MUTE
049 - TRK-06 MUTE
050 - TRK-07 MUTE
051 - TRK-08 MUTE
052 -TRK-09 MUTE
053 -TRK-10 MUTE
054 - TRK-11 MUTE
055 - TRK-12 MUTE
056 - TRK-13 MUTE
057 - TRK-14 MUTE
058 - TRK-15 MUTE
059 - TRK-16 MUTE
060 - TRK-01 SOLO
061 - TRK-02 SOLO
062 - TRK-03 SOLO
063 - TRK-04 SOLO
064 - TRK-05 SOLO
065 - TRK-06 SOLO
066 - TRK-07 SOLO
067 - TRK-08 SOLO
068 - TRK-09 SOLO
069 - TRK-10 SOLO
070 - TRK-11 SOLO
071 - TRK-12 SOLO
072 - TRK-13 SOLO
073 - TRK-14 SOLO
074 - TRK-15 SOLO
075 - TRK-16 SOLO
076 - MAIN
077 - WINDOW
078 - UNDO
079 - SHIFT
080 - TEMPO/REPET
081 - MODE
082 - NUMERIC
083 - ERASE
084 - FULL LEVEL
085 - LEVELS
086 - NEXT SEQ
087 - TRACK MUTE
088 - BANK A
089 - BANK B
090 - BANK C
091 - BANK D
092 - F1
093 - F2
094 - F3
095 - F4
096 - F5
097 - F6
098 - AFTER1
099 - AFTER2
100 - AFTER3 (MPC2500 ONLY)
101 - AFTER4 (MPC2500 ONLY)
102 - NUMERIC 0
103 - NUMERIC 1
104 - NUMERIC 2
105 - NUMERIC 3
106 - NUMERIC 4
107 - NUMERIC 5
108 - NUMERIC 6
109 - NUMERIC 7
110 - NUMERIC 8
111 - NUMERIC 9
112 - NUMERIC +
113 - NUMERIC -
114 - NUM.ENTER
115 - DATA +
116 - DATA -
117 - LOOPING REC
118 -
119 -
120 -
121 -
122 -
123 -
124 -
125 -
126 -
127 -


This is great setup.I hope it can apply to all button users.The only problem I see are hardware users
having to set it to work with all midi settings. Also
NYM do you think it is possible to do the reverse button?Can JJ implement this?Always PEACE TYPO
Last edited by TYPO on Wed Jul 27, 2011 7:52 pm, edited 1 time in total.
By dtaa pla muk Wed Jul 27, 2011 7:48 pm
typo i'm sure it's possible, but as i've pondered it i think it's less necessary than i first thought. using the standardized layout, it will be extremely easy already to create custom commands and macros even without reverse button mode. i'd rather JJ take care of other FRs rather than work on something that is somewhat redundant.

i will personally be able to start solving some FRs that are in my power to handle once we get this set up. amazing that a FR can be handled via feeding a midi file into your MPC!
By dtaa pla muk Wed Jul 27, 2011 10:44 pm
The only problem I see are hardware users having to set it to work with all midi settings


could you clarify please?

i have left the INPUT and CHANNEL option up to users. i think most folks have room for 1 MIDI cable coming from DAW. these days, it makes sense to route all your midi controllers thru your DAW first anyway, and THEN to your MPC
By dtaa pla muk Sun Aug 07, 2011 1:07 am
ok folks i wrote my first macro
this is awesome. the mpc responds to even lightning quick incoming MIDI signals...we're talking instantaneous...
we are officially now able to write some of our own workflow feature requests.
my first macro works in LAYER - it automatically splits the velocity range into 3 bits (for a velocitative drum hit)
it used to take 10 seconds and lots of click/scrolling - now it takes a few milliseconds.
i am now taking requests for feature implementations and ideas...
ready yourself with a means of delivering these macros to your MPCs to streamline your workflow
User avatar
By cyrus Mon Aug 08, 2011 3:05 pm
ok, so this is kind of on topic/off topic. so the mpc can respond to midi messages, but do they have to be external?

Seems like the next step would be some kind of internal control. like automation. like an automation track to go with a performance or being able to record button presses/movements to a midi track. or assigning midi patterns to pads (letting pads trigger sequences-like a trigger sequence parameter in pgm mode), then using those patterns to contain messages, turning those pads into macros..............or turning qlink into macro assignable buttons/sliders. Maybe even a new pgm type, we got drum, inst, arp, then add 'midi pattern' where each pad can trigger a pattern.

just thinking outload here. am i off my rocker?

I think its cool with the voice stuff. but really, i think the awesomeness is in the macros, and creating all kinds of personalized shortcuts.......especially for live performance stuff - imagine if you could auto load your next set and have everything set up exactly how you want with 1 press of a pad. am i right? and, if we continue this thread and all pitch in and create a library of macros. would be sweet.
By dtaa pla muk Mon Aug 08, 2011 3:44 pm
you're NOT off your rocker, you're rocking your rocker
internal control will really be the function that will be most accessible to any person iwth jjos2xl...least setup (voice control requires windows 7, glovepie, pizmidilooper, loopbe virtual midi cable or midi yoke, and a host like reaper, wavosaur, minihost, etc. there's a good bit of intermediate level setup involved.

the macros, however, are dead easy. all that is required is a means of delivery to the mpc. this is easy if you have a daw (i use pizmidilooper, the demo is free and i will explain how it's done later). internal control is more of a pickle.

you could maybe put a midi cable from one out to in 2...but there are problems with that
since note=>BUTTON is a meta control, it is assumed that there is some extra hardware involved...
perhaps once we get a series of macros going for the DAW folks, we can FR a means of internal meta control...
such as "shift pad01" = meta control...

cyrus wrote:ok, so this is kind of on topic/off topic. so the mpc can respond to midi messages, but do they have to be external?

Seems like the next step would be some kind of internal control. like automation. like an automation track to go with a performance or being able to record button presses/movements to a midi track. or assigning midi patterns to pads (letting pads trigger sequences-like a trigger sequence parameter in pgm mode), then using those patterns to contain messages, turning those pads into macros..............or turning qlink into macro assignable buttons/sliders. Maybe even a new pgm type, we got drum, inst, arp, then add 'midi pattern' where each pad can trigger a pattern.

just thinking outload here. am i off my rocker?

I think its cool with the voice stuff. but really, i think the awesomeness is in the macros, and creating all kinds of personalized shortcuts.......especially for live performance stuff - imagine if you could auto load your next set and have everything set up exactly how you want with 1 press of a pad. am i right? and, if we continue this thread and all pitch in and create a library of macros. would be sweet.
By dtaa pla muk Mon Aug 08, 2011 4:29 pm
Image
http://www.thepiz.org/plugins/?p=midiLooper

this is what i'm using to deliver macros to my MPC.
in reaper, you can name midi notes. i used the standard layout to name them. now, you can draw in macros right there on the piano roll. you can then render a midi file and load it in piz midi looper.

in piz midi looper, you can set the macro to play as an unlooped oneshot, unsynced to master tempo, and route the midi output to the in of your mpc. you can select what incoming midi note (from speech, midi controller, or computer keyboard) you want to use to trigger it. this midi note is removed from the stream so it doesn't send an extra unintentional message to your mpc.

you could use this in any daw with decent routing ability
or even in a standalone vst host - free ones exist, i use tobybear minihost
piz midi looper is a really, really good plugin, i hope he continues development
User avatar
By TYPO Tue Aug 09, 2011 4:43 pm
Nym wrote:i've discovered additional/repeated functions in the "CC" part of mid note/cc => button mode
including a means of selecting different pads
i will have to incoporate this into the STANDARD layout


I am interested in what additional/repeated functions in the "CC" you have discovered.Please explain.PEACE TYPO
By dtaa pla muk Tue Aug 09, 2011 5:40 pm
Wouldn't it be possible to feed the MPC it's own midioutput and get the same result? I will try this later


ought to be, but there are some problems in that regard...
if you have to have a pgm dedicated to sending macro commands, you're in trouble because the macros are position dependent...ie, if your macro is my velocity split command, it is necessary that you're in LAYER mode on the pad you intend to layer split. therefor you would be out of luck if you were in your macro pgm.

some thought/experimentation is necessary here.

TYPO, i will get back to you on the added functionality.