NEXT SEQ = IMMEDIATELY PLAY timing issue.

hello cats.
this the problem:
usually i build my livesets using only mpc1000 with jjos2xl updated for drums, breaks and loops and a waldorf blofeld synth to do most of the melodic\harmonic parts. now the blofeld is on repairs, so my latest liveset is mpc1000 only.
im having lots of fun doin it all in the box cause the limitations always force you to push the boundaries further on.
BUT:
with the old sets i never had timing issues when switching from a seq to another using immediately play, also when jumping in the middle of a pattern. this time, on some jumps , it seems to me that the timing is slightly off, i want to know if anyone is experiencing the same problem and what do you think:
1)it is because im over stressing the machine? (i do complex programming, this is a dubstep\uk garage set ith tons of syncopated, off-beat elements)
2)it is caused by the latest updates and additions? (q-links automation and stuff)

3)other ideas about possible causes?

thanks a lot guys.

btw, does any of you know if changing the T.C. settings affects the way IMMEDIATELY PLAY works? im tryng with diff. settings, and it seems to me that it does but not quite sure.


anyway, love this little beast. doing an entire liveset with only a small machine like this seems crazy!

sorry man, never had such issues. The only thing I can think of is that your sequences are missing data at the very beginning.

hyena wrote:timing issues when switching from a seq to another

To quote myself from a long post I made last week:

"note the difference in tightness between letting one sequence loop and switching between seq1 and seq2."
This is one of the issues I found and wrote to JJ about.
Check my post related to timing issues: http://www.mpc-forums.com/viewtopic.php?f=25&t=131271.

JJ's final response was that it was a problem inherent in mpc's and says that timing goes sloppier as polyphony increases, even when you are under the polyphony limit.

BUT, this does not answer my question as to why timing is very sloppy when switching from one seq to another compared with having the same seq looping.

thanks jimmie, i read your post but somehow managed to miss that specific part about switching seq.
anyway i made a couple experiments:
it seems that when switching with the data wheel from the main page the problem disappears!!!!
plus: i tested from the next seq , jumping continually to the same seq made it sloppier and sloppier!
in fact im always about 24 voices of poliphony in this set, with peaks at 29...
anyway, it also seems that goin to TC settings and makin strenght=100% , swing=50% and tc=off it goes a bit better.
anyway, the correct behaviour when switching with the data wheel kind of suggests that the problem isnt related to mpc's timing but to the NEXT SEQ interface....
im gonna post this to jj.

submitted.

Bump to this one.. Played live this weekend, and this issue just got worse and worse during my set. Has never got this problem before.

Cheers

this issue I have noticed since I suggested to JJ to introduce the automation of QLink next sequence mode

it surely is related to the amount of calculations mpc's cpu can do realtime.
its a bit of a shame.
im thinkin bout downgrading to some past version.

Does anybody have a link to XL version 1.33??

Cheers

MikkelM wrote:Does anybody have a link to XL version 1.33??

Cheers

http://www.filedropper.com/mpc2500xl133

I haven't got any mpc1000 versions.

Thanks a lot but I need the mpc-1000 version of 1.33.
As far as I can remember the q-slider Real Time on Next seq, was done in version 1.34

Cheers

Switching to 1.33 now to see if the bad timing goes away. It's the reason I haven't used my mpc a lot lately. MPC gives worse timing than any sequencer I've ever used with this bug.

Cool! Let me know if it helps, then I will start hunting down version 1.33 for mpc-1000

MikkelM wrote:Thanks a lot but I need the mpc-1000 version of 1.33.
As far as I can remember the q-slider Real Time on Next seq, was done in version 1.34

Cheers

Here's 1.33 for the 1k...
https://www.yousendit.com/download/aHlUS3dzR3NBNkZjR0E9PQ

I can confirm after testing that JJOS2XLv1.33 on mpc2500 has much better, tighter timing than JJOSv1.37 and above versions (I haven't tested v1.34, 1.35 or 1.36 yet).
So, I'll be using v1.33 until the sloppy timing is fixed in a new release, because I cannot live with it at all. I mean, it really is absolutely terrible. I can't believe more people haven't commented.
I already did extensive testing and sent all my reports to JJ about the sloppy timing issue. Read my posts above for JJ's response.
p.s. This has nothing to do with using IMMEDIATE PLAY or not. Also, using Mute Type: LEVEL severely affects the timing, so I stay well clear of ever turning that on.

I bought the MPC as a sequencer for it's timing. That is the MAIN reason. So this really boils my spleen. Musicians concerned with tight timing don't want any frilly crap buggering it up.
Timing is number one priority in a sequencer as far as I'm concerned and that's why I haven't touched my mpc since it started goin all sloppy with the latest JJOS2XL.