Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
By 1waymuzik Sat Apr 19, 2008 4:29 pm
That's what I do and I also choose the midi channel 1A and I change the track to a midi track. I believe that there is an issue with the midi channel settings because the midi information is being recorded correctly but its being transmitted wrong somehow!

m:t:c wrote:Are you sequencing everything in the same program (midis,samples etc.)? If yes, then there might be your problem and if your program is set to play notes in "mono" instead of "poly". This means that when new note begins the old one is cut out (ie. one note gets played at a time).


Try this: select a new track in your sequence, turn the program off, record your midi notes, see if it occurs again...

ps. Sorry if this wasn't helpful, had a hard time getting a grasp of the case here... :P
User avatar
By Mr modnaR Sat Apr 19, 2008 7:00 pm
m:t:c wrote:Are you sequencing everything in the same program (midis,samples etc.)? If yes, then there might be your problem and if your program is set to play notes in "mono" instead of "poly". This means that when new note begins the old one is cut out (ie. one note gets played at a time).


Try this: select a new track in your sequence, turn the program off, record your midi notes, see if it occurs again...

ps. Sorry if this wasn't helpful, had a hard time getting a grasp of the case here... :P


mono and poly only affect the sample playback engine of the mpc, not MIDI notes it sends out.
By 1waymuzik Sat Apr 19, 2008 8:43 pm
Yeah that's why I thought. But it appears to do the same thing like a the midi notes are cancelling each other out which throws off the midi clock. If anyone has a roland fantom go to the "techno synth" patches and select the sound "electro stars" the sound plays 4 beeps each going up in octave. When recorded on my mpc via midi sequencer this error Im having will only allow the first beep to be played at the first count of the first bar. Also when that happens the other 4 beeps are played on the 2nd, 3rd, and 4th bar. (Krazy)
User avatar
By arebee Sun Apr 20, 2008 10:41 pm
i'm wonderin why u have the kybd set to 'LOCAL' = 'ON'?

in my exp. - u woundn't need this 'ON' if the MPC is the master.....esp. if any notes u play off the kybd are received at the mpc then thats half the problem solved yeah? as i understand it, any sound module/kybd would be best set to NOT LOCAL, so the MASTER MPC solves all the midi routing for u.
AND if local is ON, then the kybd would trigger itself (doh) BUT the MPC would ALSO trigger exactly the same notes just played, so maybe THAT causes the notes to cut off.?

and anything that u want the mpc to play back on the kybd sounds, make sure the midi ch# is correct in the active MPC track, as its supposed to be the master.

++try making sure in the MPC that new recorded seq's are not trimmed to "seq length" in one of the "Seq+Mode+ window" pages....just a notion that maybe the truncation of the notes is being done at the recording stage....and your work habits are better supported if the seq's are trimmed by u manually later once u are sure that the notes arent being shortened due to the position they may be at the end of a seq length.

sorry if this is way off and i've missed a detail or two.
good luck, dont throw it though, take it to a store n compare your methods/results with a new machine, or a friends unit etc.....


pce