The new MPC's were released in July of 2017, have gone through about 3 new firmware version updates since then, and none of them have addressed the external sync timing issues. At one point I was communicating with David from Innerclock systems, who had just bought the MPC Live for testing, and found the issue so severe he immediately returned it to the store. I have contacted Akai support several times with no real reply (other than pre-written responses saying they forward all issues to development team), and there are have been countless threads and replies on the Akai message boards with people experiencing the same issues since initial release. To be clear, the 22ms is not a consistent delay or latency in the hardware, the timing of all notes played are unpredictably early or late, so there is no possible way to try solving this issue with delay compensation of any sort. You can hear the timing issues just from enabling the click track audio & comparing timing against other gear the MPC is apparently "sync'd" to, without even needing to record/quantize any musical sequences. So bad that i've visually measured up to 22ms of note timing drift (clock jitter) which is very noticeable when trying to sync with any sort of external gear, and for most people renders the MPC useless for any serious music production in this situation (when trying to sync with other gear). The new MPC's are great, except for one major flaw in that they all have horrible timing instability when you try to sync them to an external clock. Sadly Akai have continued not to address this problem since the new MPC Live & X release. I figure there are a lot of synth heads on here who, like me, imagined adding the new MPC to their existing setup. I strongly feel this is a serious product functionality flaw so i'm posting this warning thread to spread awareness to other potential MPC users who want to sync their MPC to an external clock source in their setup, and to hopefully put some pressure on Akai to take seriously the severity of this issue and fix it as soon as possible. **UPDATE*** See my post from Feb 15th for testing results using new v2.1 firmware.
0 Comments
Leave a Reply. |