jahrome wrote:Sovereign, there are forum members that have reported bugs to Akai.
The only issue I have with Akai OS 1.22 is the MTC, which I don't use very often.
There are very few problems with the Akai OS. For those claiming just the opposite, simply post the steps that produce the problem so we can get it to the right people.
Actually Jahrome if you have had any real communication with people at Akai you would understand that they have had a lot of whinning and feature request but very few people gave them intelligent explanations of problems.
It don't work.
The sh*t is broken.
It corrupted my d*mn files.
Are not usable info.
The MTC did actually work but had an underlying problem.
When that was fixed it cause it to ignore the start and stop message.
It will be fixed but it's a scheduling problem based on other projects.
I hate to say this but the real problem with the 2500 isn't really a bug it's a improperly implemented function.
The DETECT TEMPO function.
It just was done in a non-functional way and as you can see JJ was able to tweak it to work thus the reason he added the XL style MANUAL function for TEMPO DETECT.
I wish I could get the Akai OS to have file problems so I could actually see what causes it but I have never been able to get it to do it.
That's been with v1.1, 1.2, 1.21 and 1.22 using a 40g Toshiba, Akai 128, CD-M25 and a ScanDisk 512 CF.
With the amount of actual debugging and feature adds Akai has done to the 2500, at 1 year is to be concidered ahead of the MPC curve based on past models with upgradable OS's.
Also people need to understand there are 3 stages in the Akai equation;
Product Specialist
Technical Specialist
Engineers
Problems have to go through the channels and that's how they determine when a problem has to be escalated to the front.
Example the SYSTEM ERROR FREEZE UP Bug.
At any rate I have too much time logged in on the various MPC's not to appreciate the 2500.
Well all except the 1k and 500 since what they bring to the table doesn't suit my needs.