midi buffer full

wtf? i searched the forum. os is 1.71, not 1.50.

i have a bunch of discrete sequences all stacked up in "song" mode. when i "convert to sequence" i get a MIDI BUFFER FULL message at bar 39 (specifically, 039.01.001 - so literally the first hit) as the sequence plays through. mpc triggers a (non-sequenced) not from one of my synths and then keeps chugging along. what in the sh!t is going on here?

what's more, the corresponding sequence (bar 39 in long sequence = seq 12 in song mode) plays back just fine, both by itself and in song mode.

i have NOTHING plugged into the midi ins. i'm gonna futz around with the internal midi sends and see if i can get a reaction but in the meantime if anybody has any ideas i'm all ears. and naturally, i have a gig tomorrow.

- jim

more weirdness: if i divide the BIG sequence into two smaller points using the problem spot 039.01.001 as the break point it works fine. however, combining these two back into one sequence nets the same midi buffer full error.

don't get me wrong...i LOVE my mpc4k (and i tried the 5k and maschine) but for pete's sake can't somebody make a machine that works right from top to bottom? i really feel like the 4k is the best of the best and it's SO close to being flawless but there are still bugs...

Maybe at that precise point in the song you have too many midi 'note on's' appearing at once? Also does the midi monitor reveal anything that may be causing the problem (pitchwheel data, mod wheel data, program changes or other midi CC messages)??

ah, finally...a response. thanks clint.

you may be right. i have a lot of midi data being sent out (4-5 channels all via midi out A) and i was thinking the same thing. i moved a few to output B but that didn't help. on "songs" where i have minimal midi data going out (and most of the action happening internally) i don't get the problem. i'm just kinda surprised if this is the case and the 4K has such a low ceiling as far as midi output.

i'll double-check with the midi monitor...i'm pretty sure i didn't see anything that appeared out of the ordinary. admittedly i was in a hurry and need to pour over the thing again...i only came across the problem the day before a gig, so i just left everything in song mode and carried on.

even if it isn't sorted it's not a deal-breaker. i'd prefer to have songs converted to sequence for simplicity's sake but what are you gonna do.

- jim

viewtopic.php?f=2&t=120255
viewtopic.php?f=2&t=52186
viewtopic.php?f=2&t=26307
viewtopic.php?f=2&t=92156

From these earlier thread on 'midi buffer full' there is no definitive solution. If it were me I'd look at the midi monitor and the midi filter to see if i could shed any light. I'd also want to discount excessive midi CC (control change), Sysex (System Exclusive) and Q-link data along with mod and pitchwheel data during the process of elimination. Another valid suggestion is a midi feedback loop from external hardware or computers.

The above threads mostly have one thing in common, converting a song to a sequence, so theres the possibility that its an unresolved bug that was more prominent in earlier OS 1.5x.

I do remember an OS update one christmas where it was just a FARCE, the "MIDI OUT BUFFER FULL" message was coming on non-stop, I was like "AKAI, ARE YOU ON CRACK???" I mean did they ever test their code AT ALL?

CRACKAI?

Based on everything I see, I would consider that an appropriate name.