Test my MPC project on your MPC for stuttering & shuffling

i get an error: Server Error in '/' Application. (ok fixed! im downing)

Did you assigned that extra kick to Zone 2 in the "Drums" program before recording? So three kicks are layered and nothing else is changed on the project..? Thx mate

Ikke, Check your midi filtering page. THis happens to any MPC when you have a lot of controller data and especially with sysex and aftertouch data.

If you are not using sysex, aftertouch, or external CC's, filter them out. Because otherwise the sequencer is recording all that at the same time and trying to play it back with the other data.

You should be able to go into step edit and view all except notes, or SYSex and aftertouch data and you should erase what is not there intentionally.

All this is a problem with any sequencer because midi is serial data, and it doesnt matter how fast your sequencer is, everything goes one at a time, and the extra data makes each message take longer, so you get weird timing.

It happened on my 60 once I I freaked out, then I realized I was recording sysex and aftertouch for synths that don't use it. It was never a problem until I had reached a certain level of seq tracks (I think it was 60 at that time.)

That's definitly it I bet. Check that midi filter.

ikke wrote:i get an error: Server Error in '/' Application. (ok fixed! im downing)

Did you assigned that extra kick to Zone 2 in the "Drums" program before recording? So three kicks are layered and nothing else is changed on the project..? Thx mate

yea done all that... let me know what happens

elmacaco, think you might be right cause the sequence is shuffling on Drestas machine too! ( Dresta, listen closely with hi pass on to the shakes (hats) they are different in each 4 bar loop! On my machine it shuffles a bit harder tho

Fjjiiieeeuuwwwww.... My MPC aint broke! Lets get some beer
Ill try filtering some midi data. ill let ya guys know!

Thanks all for the help and all. Much appreciated

Cheers!

Well check it in step edit, and delete the non essential data. and set your filtering to filter sysex, CC's, and aftertouch. Only disable the filtering when you want to use it and record that track only then filter it again.

60 man saves the day.

i hear it now...lol i thought it was meant to be like that...

elmacaco wrote:Well check it in step edit, and delete the non essential data. and set your filtering to filter sysex, CC's, and aftertouch. Only disable the filtering when you want to use it and record that track only then filter it again.

60 man saves the day.

hehe you take the words out of my mouth .. "Here he comes to save the daaaayy" El Mighty Mouse Macaco

tho I cant find any midi data other than the notes..

you sure? You know how to make sysex and CC's visible in step edit on the 4k?

WHat do your midi filters say for sysex and aftertouch?

there is nothing filtered out
I can see the Control Change in seq edit & step edit, no data there. Checked every track.. How can I check the sysex and aftertouch? Oh, aftertouch, while we are at it, maybe you can help me out (no one seems to know about this) .. but how can I let the pads send aftertouch to internal programs? WHen I press a pad and keep my finger on it, I can see the MIDI out meter go up and down, I can keep the meter in the middle, so the pad is pressed with a velocity of lets say about 60 for a longer period. So my guess is that the pads do send aftertouch, tho programs wont react to it.. Ive checked the manual but nothing in there, or maybe ive mist it as usual

THey do send aftertouch, but you'd have to route it to control something in the internal architecture. I don;t have a 4k so I couldn't tell ya.

you know what you might try, copt the sequence that causes the trouble, then load it by itself into the 4k, see if you still get the trouble.

Then hit the erase button and erase all but notes or whatever the 4000 calls it, and set your midi filter to filter out sysex and aftertouch. Once that shyt is recorded it stays unless you erase it.

You'll need to set aftertouch to pass if you want to use it from the pads in the sequencer for internal or external use, but shut it down after you're done using it or it can clog up your data stream.

It could be CC messages too if you were tweaking knobs on something that sends CC's, but if you were not filtering sysex that could be it.

ok got it (sysex and all the rest, its in the step edit) :
BUT no data except for midi notes on all tracks in all sequences.
I have cleaned out the rest of the project too,
Nothing is routed in the modulation matrix.
i have tried your method of loading them stuff all seperatly
...
still no luck, the notes shuffle, the locator goes slower when more notes are on top of eachother.

So I downgraded the OS. (OS 1.70 is equal to 1.71) OS 1.60 did a better job handling the MIDI notes. OS 1.51 slightly better than 1.60. But OS 1.51 pops a bit while playing the rhythm.. Cause thats what it is.. nothing but a rhythm.. Seq 3 mentioned earlier does run on OS 1.60 but my new seq doesnt and it doesnt have a rhodes or a synth.. only a rhythm with a kick, hat, snare, 4 congas + 4 shakers and a mono sequenced bass. Only thing thats altered are some filters.. I think this would even fit in the MPC60´s memory

The most wicked shuffling is always at the end of the sequence, be it 2, 4 or 8 bars. Just before it loops back to the first bar, the midi notes stutter.

I gonna make a complete new setup, make some rhythms again and see what happens.. maybe its some bad ass programs wich is causing this crazyness! (but I dont think so.. )

OR maybe I did reached the limit and THIS is what people are saying about the timing of the new MPC´s.. I mean everybody screams: "MPC60/3000 has tight MIDI timing! 1000/4000 are wack!!"

btw.. while switching between OS´s this fast, I noticed that the lower OS you go, the faster the screens redraw! I mean OS 1.51 is real quick and tight
OS 1.70 is real slow with about everything!
Just so you know..
OS 1.60 is somewhat inbetween and does everything it has to, so thats where Im going.

In the end Im really glad it aint my MPC hardware, but its the software wich can be updated!


Can someone send this thread to [email protected]?

Whoa, so t isn';t the sysex? Check your filtering and remake the track fresh like you said, see if it still happens. It does seem more like a computer now doesn't it?

Yes... sad... but true
I cant find how to setup the pads´ aftertouch 2 programs either.. I think the aftertouch should control the amplitude, no? I can let the aftertouch affect all kinds of stuff but cant seem to find the right one (and nothing happens when aftertouch controls stuff in the mod window) and of course the manual is silent as a grave on this ... as always.
Anyone else have succesfully controlled programs with aftertouch from the pads? A 4k dinosaur mebee?

holy macaronies! The stuttering timeline, popping and clicking was because the digital outsync was set to wordclock (i dont have that), I have set that to wordclock because when I set it to internal, the mpc sends out stuff through adat to the pc wich I dont want.. When I set the clock to internal, no probs ..... WOOOOPZZ

Also, the better midi note performance on Destras machine was probably cause he ran his mpc at 44100hz. Can Destra confirm?