By colonyrecords
Fri May 09, 2014 6:59 pm
I feel the need to share this, not sure if someone has already pointed this out.
I have had my 5000 for about 3 years now and it has always had bad midi clock. My last hope was to purchase the innerclock sync gen (not cheap) to resolve the issue. The sync gen helped with the midi jitter but still couldn't fix the random midi clock start delay the 5000 has. The sync gen fixed all midi clock issues with my other equipment except the 5000. I was just about to give up and sell the 5k when I thought to try an older OS (1.02). Mines came with 2.0 so I never even thought about any other OS's. After loading 1.02 I can say the 5000 now syncs perfectly when using midi clock, no more random midi clock start delays. How could akai screw up midi clock so badly with the 2.0 OS, didn't they check this stuff before releasing it.
Long story short, if you are pissed off about bad midi clock on the 5k downgrade to os1.02. Only problem is you will lose a lot of features but for my uses having a functioning midi clock was more important.
I have had my 5000 for about 3 years now and it has always had bad midi clock. My last hope was to purchase the innerclock sync gen (not cheap) to resolve the issue. The sync gen helped with the midi jitter but still couldn't fix the random midi clock start delay the 5000 has. The sync gen fixed all midi clock issues with my other equipment except the 5000. I was just about to give up and sell the 5k when I thought to try an older OS (1.02). Mines came with 2.0 so I never even thought about any other OS's. After loading 1.02 I can say the 5000 now syncs perfectly when using midi clock, no more random midi clock start delays. How could akai screw up midi clock so badly with the 2.0 OS, didn't they check this stuff before releasing it.
Long story short, if you are pissed off about bad midi clock on the 5k downgrade to os1.02. Only problem is you will lose a lot of features but for my uses having a functioning midi clock was more important.


