Smogbog wrote:Smogbog wrote:I've also just logged a ticket on this issues, so I will keep folks updated on here when I hear something back.
Akai support got back saying that going what I am reporting, it sounds like it could be a hardware issue. I doubt this though, given the inconsistency of the problem. 
Any thoughts?
Well it's affecting all my gen1 models equally and not my mpc live 3, so in that respect, yeah, it's a hardware problem as I suspect it's down to CPU or polyphony limits in the gen1 hardware 'as a whole'. But these projects worked fine in MPC 3.5, so it's ultimately due to something they changed in MPC 3.6 which is now likely causing some malfunction in certain projects that gen1 models don't have the necessary grunt to deal with.
So no, not a problem with your MPC, a problem with MPC 3.6. I have unfortunately given up trying to work out what might be causing it, I've tried everything except manually re-making the project entirely from scratch, as in literally re-constructing and re-performing every track from the ground up to ensure no remnants of 3.5 remain (just don't have the time for that).
But I have exported all the individual tracks and MIDI and re-created the project itself from a blank project, piece by piece. I have also tried disabling effects, limiting polyphony, shifting some events off 1:1:0, disable warping etc.
Later today I will submit a full bug report to the closed beta group, with the actual project files so they can try to pick it apart, but it's infuriating that I cannot first pinpoint what factors might be causing it. I hope others are submitting as well. I believe the Force is also experiencing a similar issue.
