problems recording CC events

I'm not sure if this is a HW/SW issue or if I'm just pushing this thing too hard, but...

I have the Midi out of my Moog Voyager going into the 2500 and when for example I try to record a rapid filter sweep (i.e. twisting the knob rapidly back and forth) the MPC cannot handle it. It acts as if the memory is being maxxed out or something. The audio completely studders and the midi info stops recording. If I record a smooth filter sweep its no problem but whenever I rapidly twist the knob it completely F**S up.

Anybody else had this problem?

my moog voyager knocks out the mpc, too.
but fast knob movement is no problem here(moog and mpc with newest os).
when i record cc data for more than one loop, the mpc collapses,
and i cannot record movements of more than 3 or 4 different knobs
per loop. it seems to be too much data coming from the moog.
i tried the "midi running status" set to off but it didnt make anything better.

the next days i will watch out for a midipatchbay which has programable midifilters. maybe that will help. perhaps you can set a limit of midievents
beeing passed per tenth of a second or smth like that.
does anybody know?

you guys are scarring me!!!..... cause i am about to get my mini moog blue this friday!!!!....please tell me is aint so....what other problems have you noticed???

I just tried a test with my Virus, and recorded 5 tracks CHOCK full of cc# messages. The MPC didn't miss a beat.


Could the Moog sending out sysex or nrpn messages aswell as cc#?

If you have a computer, try grabbing the free MidiOX to analyse whats coming out of the moog.

http://www.midiox.com/

@ fragmentalist
to be honest, i dont really have to record movements of more than 2 knobs
for a synth line. so you´ll only get problems if your 6 handed alienfriend comes along to perform. the minimoog is great.you can rout several controllers to the modwheel via potmapping and modulation buss to get
big timbre changes just out of the modwheel. and its only the modwheel data to be recorded to the mpc --> so that works fine for me.
you have to be careful while recording, because if you move a controller for longer than one loop(when it starts overdubbing) the audio studders. also dont move anything while the count in is playing. all knobmovement of the count in time is recorded to the first step.
in step edit it looks like this:
001.01.00 cc: 1-mod.wheel :1
001.01.00 cc: 1-mod.wheel :2
001.01.00 cc: 1-mod.wheel :4
001.01.00 cc: 1-mod.wheel :9
001.01.00 cc: 1-mod.wheel :12
001.01.00 cc: 1-mod.wheel :17
001.01.00 cc: 1-mod.wheel :22
001.01.00 cc: 1-mod.wheel :30
001.01.00 cc: 1-mod.wheel :26
001.01.00 cc: 1-mod.wheel :24
001.01.00 cc: 1-mod.wheel :22
when i record modwheeldata with my nordlead to a 2 bar loop i can record
as long as i want, means i can let it loop for hundred times overdubbing
the cc and everything is fine(no timing problems). for some steps there is triple or more data entry but with minimoog after the second loop audio studders and i always find a step in stepedit where is more than 20 !! entries.
the same when i use different knobs for each overdub.
but u can live with that. the issue that emjay mentioned is more
annoying.
@emjay
did you install the latest os on minimoog?
do you get steps with these high amount of entries, too?

I played around with it some more last night, trying to overload it.. It seems this does only happen when overdubbing. I'm not really sure. I do have 3.1 installed. I need to experiment with it some more. I'll check out MidiOX. From reading this thread it does seem like a Voyager related issue and not an MPC issue. I'm wondering if it has anything to do with the Voyager sending out LSB and MSB per CC?

I realized this is being caused by a midi feedback loop. (DOH!)

word to Rozzer on the midiOX post, i had to learn that program at uni, midi ox and midiyoke, which for when i was workin on a laptop was sick because i could program my QWERTY keyboard as a midi controller, head up Safe... think i better test my microkorg nobs see if they work cool straight off.

Safe

emjay wrote:I realized this is being caused by a midi feedback loop. (DOH!)

Glad you got it sorted