heh now i can control my MPC with voice commands...

MIDI NOTE TO BUTTON
STANDARD LAYOUT

PLAY START
PLAY
STOP
OVERDUB
REC
BAR >>
<< BAR
STEP >
STEP <
CURSOR UP
CURSOR DOWN
CURSOR RIGT
CURSOR LEFT
SLIDER
LOAD
SAVE
TRACK MIXER
RECORD
TRIM
PROGRAM
PAD MIXER
MIDI/SYNC
OTHER
EFFECT
SEQ EDIT
STEP EDIT
GRID
SONG
TRACK-01
TRACK-02
TRACK-03
TRACK-04
TRACK-05
TRACK-06
TRACK-07
TRACK-08
TRACK-09
TRACK-10
TRACK-11
TRACK-12
TRACK-13
TRACK-14
TRACK-15
TRACK-16
TRK-01 MUTE
TRK-02 MUTE
TRK-03 MUTE
TRK-04 MUTE
TRK-05 MUTE
TRK-06 MUTE
TRK-07 MUTE
TRK-08 MUTE
TRK-09 MUTE
TRK-10 MUTE
TRK-11 MUTE
TRK-12 MUTE
TRK-13 MUTE
TRK-14 MUTE
TRK-15 MUTE
TRK-16 MUTE
TRK-01 SOLO
TRK-02 SOLO
TRK-03 SOLO
TRK-04 SOLO
TRK-05 SOLO
TRK-06 SOLO
TRK-07 SOLO
TRK-08 SOLO
TRK-09 SOLO
TRK-10 SOLO
TRK-11 SOLO
TRK-12 SOLO
TRK-13 SOLO
TRK-14 SOLO
TRK-15 SOLO
TRK-16 SOLO
MAIN
WINDOW
UNDO
SHIFT
TEMPO/REPET
MODE
NUMERIC
ERASE
FULL LEVEL
LEVELS
NEXT SEQ
TRACK MUTE
BANK A
BANK B
BANK C
BANK D
F1
F2
F3
F4
F5
F6
AFTER1
AFTER2
AFTER3
AFTER4
NUMERIC 0
NUMERIC 1
NUMERIC 2
NUMERIC 3
NUMERIC 4
NUMERIC 5
NUMERIC 6
NUMERIC 7
NUMERIC 8
NUMERIC 9
NUMERIC +
NUMERIC -
NUM.ENTER
DATA +
DATA -
LOOPING REC











* AFTER 3 and AFTER 4 (100, 101) only for MPC2500

voice = "pattern mode"
becomes:
note 0 on/off (enters grid mode)
note 1 on ........................ note 1 off (holds shift for a time)
................note 2 on/off (triggers F1)
= enter grid pattern mode.

i think this is doable with Glovepie. the scripting is very easy.

sally, i figured out how to do this. it is simple to do, so yes, no problem.

subscribe

nym, when you do this, you gotta have a command that starts the app listening, like the firesay plugin for chrome/ff requires you to say "browser" then it starts listening for your commands...........


you should do something like "JJOS" > "whatever command"

so you have to say "JJOS" for it to start working. although not sure how you'd do it for a live situation.

that's cool!
good work

cyrus i imagine this wouldn't be much good for live use. too noisy, etc, maybe even if you are wearing a headset. i do like your idea of an initiator, though and i will look into it. especially for numeric values.

Nym wrote:cyrus i imagine this wouldn't be much good for live use. too noisy, etc, maybe even if you are wearing a headset. i do like your idea of an initiator, though and i will look into it. especially for numeric values.

true about the live stuff.

Yeah, for entering in values i could see like "JJOS - Open Main - Select BPM - Enter 1 - 2 - 3" = Goes to Main screen and it enters 123 bpm

seems like you're gonna end up with some common language - reserved words as initiators. JJOS,Open,Select,Enter (to that effect).

The main problem i see is how do you know where the cursor is to get complex commands like "Select BPM". I guess thats definately prob still too early and maybe too complex, not sure..........

yeaaah now you're thinking about the process involved.

i'm envisioning most of these actions to be single phrase operators. instead of saying each step you can just rattle off the command and glovepie will spit out the appropriate midi notes to do the deed.

also, you were smart to include the "main" command in your string. many of these actions will have the main command first to standardize the position of the cursor (very important, since cursor position is determined by cardinal increments (up, down, right, left))

i still haven't moved much on this other than building the standardized button layout (acronym time, SBL from here on out) because i've been busy building a precision incubation station for making tempeh, yogurt, pickles, etc, but this weekend i am finally installing win7 64 on a spare hard drive as a test run for my daw OS.

Voice commands?

How about a new OS for the MPC4000, that will make you some money...

Develop for a market if you want to get paid, like JJ, JD and Rohan.

clint246clint wrote:Voice commands?

How about a new OS for the MPC4000, that will make you some money...

Develop for a market if you want to get paid, like JJ, JD and Rohan.

**** a mpc4000. Develop for the beat thang and get some bling instead.

Nym wrote:i think we should come up with a standardized button mode layout...
there are 0-127 midi notes and X number of controllable mpc functions via jjos2xl BUTTON mode
if we map those out, we could share key combinations and "macros" to send to our mpc to automate certain tasks. we spoke of this before but i really think it's time to move on it.
the standardization is the tricky part, as we all have kind of used button mode in our own ways so far
but i would totally reconfigure my setup if it meant that the community would give me new functionality.

I really like the idea of standardizing this and creating macros...they can even be triggered by a computer keyboard or maybe a damn cellphone if we get the implementation right. No reason to stay confined to voice control.

Have a couple questions...are you sending the midi straight out of GlovePie? I've done some work with Autohotkey to automate windows tasks with midi and the implementation is very good.

Either way...I'd like to be a part of this project. JJ is creating some serious creative possibilities and I think we've got some great opportunities to take advantage of.

glad you're interested. i did a lot with this today.

standardization is important. my original plan was to use glovepie only. as it turns out it's a lot harder to write/test complicated macros in glovepie, so instead, i'm using glovepie to trigger .mid files in Piz Midi Looper VST within Reaper.

basically if we use the standard layout, we can just trade .mid files that contain midi info which we can feed to our MPCs using any method we wish.

i haven't used autohotkey, but i should give it a test. glovepie's midi scripting capabilities are clunky at best, but they get the job done.

Nym wrote:i haven't used autohotkey, but i should give it a test. glovepie's midi scripting capabilities are clunky at best, but they get the job done.

yea man give it a shot...i've written a whole midi application in autohotkey. hit me up if you need any help getting up to speed on ahk or working with midi in it.

for the macros you'd basically be sending one midi message then instructing the application to sleep for 10 ms or something then send the next correct?

glovepie just runs idly til conditions are met (voice, key combination, mouse movement, whatever you want) in which case it reacts (by doing voice, key combination, mouse movement, whatever you want)