Post your questions, opinions and reviews of the MPC1000. This forum is for discussion of the OFFICIAL Akai OS (2.1). If you wish to discuss the JJ OS, please use the dedicated JJ OS forum
By trustsound Wed Apr 06, 2011 5:45 am
I think I've watched every tutorial on how to do this..

MPC SETTINGS =
my mpc is set on sync 1 a
my track type is set on midi, the midi: is set on 1a

Pro Tools 8 Settings with mbox 2 pro

midi studio setup :
mpc 1000 is set on input port : digidesign mbox 2 pro midi
mpc 1000 is set on output port : digidesign mbox 2 pro midi

midi beat clock : enabled / mpc1000 checked


now, I make a midi track

and for the I/O settings for the MIDI INPUT SELECTOR I pick MPC 1000 > All channels

and for MIDI OUTPUT SELECTOR I pick MPC 1000 > channel 1

As soon as I play a key, things kind of go haywire, the volume goes fully up and stays there, in the mpc if i go to see the bars by pressing mode+pad15, its like its getting random steps filled in, without pressing anything..

what I'm trying to do is use my keyboard to play sounds or data into the mpc, but my keyboard doesn't have midi, so I'm trying to go through pro tools to do it, the keyboard makes no difference at the time because even with it off it still does this even when i hit buttons on the mpc..

I'm missing something.. Any clues?

I use this exact configuration for my keyboard and it works perfectly, pro tools sends the midi information back to the keyboard and the keyboard plays..

I cant get the mpc to do this..

I would blame the cords but I just bought them, and I've never actually used the mpc or the mbox 2 pro for midi, so I'm guessing it's something I'm doing wrong..?

I do this in hopes to get my pro tools to send midi information to my mpc,

ANY TIPS ON A SOLUTION WOULD BE MUCH APPRECIATED!!
Last edited by trustsound on Wed Apr 06, 2011 6:38 am, edited 1 time in total.
User avatar
By krush777 Wed Apr 06, 2011 6:04 am
trustsound wrote:I think I've watched every tutorial on how to do this..

MPC SETTINGS =
my mpc is set on sync 1 a
my track type is set on midi, the midi: is set on 1a

Pro Tools 8 Settings with mbox 2 pro

midi studio setup :
mpc 1000 is set on input port : digidesign mbox 2 pro midi
mpc 1000 is set on output port : digidesign mbox 2 pro midi

midi beat clock : enabled / mpc1000 checked


now, I make a midi track

and for the I/O settings for the MIDI INPUT SELECTOR I pick MPC 1000 > All channels

and for MIDI OUTPUT SELECTOR I pick MPC 1000 > channel 1

As soon as I play a key, things kind of go haywire, the volume goes fully up and stays there, in the mpc if i go to see the bars by pressing mode+pad15, its like its getting random steps filled in, without pressing anything..

what I'm trying to do is use my keyboard to play sounds or data into the mpc, but my keyboard doesn't have midi, so I'm trying to go through pro tools to do it, the keyboard makes no difference at the time because even with it off it still does this even when i hit buttons on the mpc..

I'm missing something.. Any clues?

I use this exact configuration for my keyboard and it works perfectly, pro tools sends the midi information back to the keyboard and the keyboard plays..

I cant get the mpc to do this..

I would blame the cords but I just bought them, and I've never actually used the mpc or the mbox 2 pro for midi, so I'm guessing it's something I'm doing wrong..?

I do this in hopes to get my pro tools to send midi information to my mpc,

ANY TIPS ON A SOLUTION WOULD BE MUCH APPRECIATED!!


How did you ever get Protools to send MIDI information to a keyboard that does not have MIDI? What keyboard do you have that doesn't have MIDI?
By trustsound Wed Apr 06, 2011 6:11 am
Sorry it has usb midi..

Hey weirdest thing happen I changed to B2 and everything worked perfect

i went back to A1 it broke again

then i went back to b2 and its still broke lol.. im working on it now..
By trustsound Wed Apr 06, 2011 6:37 am
sucks.. brand new cords, radio shack sucks..

I tried so many things to fix this lol..

I try to always blame the hardware very last..



ANYWAYS KILL THREAD IF NEEDED!

PROBLEM FOUND