HanHuman wrote:kday wrote:That's who they need to also help fix the bugs that customers run into with their own systems. Without the public, how will they know XY& Z new bugs now exist? Akai has their own resources, but to find bugs everybody is needed, Akai can't do all that alone otherwise all old bugs would be fixed already.
Nice one 
But seriously though, they know very well some bugs have been there since many older updates. They're just unable to fix a good amount of them and are still creating new ones with every new updates. Even on older features that used to work fine.
If they need beta testers, then they should release beta versions. And make an older 'stable' version with little to no bug at all for people needing stability. That's how many other manufacturers do it. What is the stable, bugless version of AKAI os? They all have their issues, some worse than others but still.
Gonna be the negative guy again but whatever, it is what it is.
All older bugs that they can reproduce in their systems are being worked on. And will be fixed in time. Fixing things is not as easy as tightening a screw. Research has to be done to determine what caused the issue first, which can be indirectly three to four code layers or more back. If a bug wasn't fixed yet, it's because it's not as easy as you may think, and takes a lot more research than you probably expected, otherwise it would be done. The research team aren't in the back room failing at trying to kill a fly with a sledge hammer.
Akai release Beta versions, to the Beta teams that signed up to be Beta testers.
Akai's bugs are bigger than they can initially control. I'm sure Akai is doing all they can to fix bugs they can reproduce. But if we the public can't reproduce the bugs we say exist, how will they know what bug to fix? This is why they need you, To become Akai's public Bug reporter too! Your local government aren't the only one that needs you, Akai does too!
