AKAI & AIR are looking for beta testers

AKAI could have been reading all those annoying users complaining.

AKAI beta test program:
https://twitter.com/Akai_Pro/status/1615096547842170886

AIR beta test program:
https://twitter.com/Akai_Pro/status/1615099068879114241

I've filled out that form so many times over the last 3 years and not once heard back from them on it heh.

In Akai we all are beta testers

Huh, so nothing new to expect here :/
Well…

What are the benefits? I can't see any. You're under NDA, have to use buggy software AND they don't fix their shit.

If I had another unit or still had the Force. Not sure I'm about beta testing on my main thing I use to make music.

Monotremata wrote:I've filled out that form so many times over the last 3 years and not once heard back from them on it heh.

I was accepted to the Force beta during the beginning .. the "you are accepted" registration link in the email never worked lol

kaydigi wrote:

Monotremata wrote:I've filled out that form so many times over the last 3 years and not once heard back from them on it heh.

I was accepted to the Force beta during the beginning .. the "you are accepted" registration link in the email never worked lol

That was a screening test.

You were supposed to report the bug to gain full access to the BETA program, gift bag and branded coffee mugs.

Testing these days should rely on automation. Your ability to deliver is determined by your ability to automate. Beta testing is needed to find out usability problems and fitness for purpose. My opinion only though.

Automated testing is a great supplement to manual testing, but it will never truly replace manual testing.

The hard problem with testing is that with increasing complexity comes exponential test surfaces to cover. Automated testing will never be able to test every single permutation or pattern of usage, so it is great for getting at repeatable things, or testing to make sure you're not introducing regressions in usage, but it isn't as great at replicating the very human randomness in timing, slight deviations in workflow choices, and all other manner of nonsense that we humans introduce into even simple systems.

Only for twitter users.

NearTao wrote:...

Akai seem to have problems with regression testing. Each new version breaks something that used to work before. No amount of manual testing is going to solve that problem.

But what comes to the topic, why would anyone want to be an unpaid beta tester? Either they don't know what it involves, or they're nuts.

I have been constantly trying to get in either Air plugin or mpc software testing with no luck. I guess the only people who are allowed in are well known instagram\youtube beatmakers so they get their beta testing done plus free publicity through zero day plugin reviews in their channels

It's crystal clear that Akai has huge problems finding good beta testers.
There must be something wrong in the process.
Do you really think you can find good pro testers just putting a module on internet?
My gosh.
It's gonna be a hell of bugs and bullshits for some more years.
I am starting to be bored with that.
Just hire serious workers, pay them, make it good.
Otherwise we are the beta testers and that's not nice. Beta testing during a live performance or a concert isn't the best thing to do, Akai Pro.
I find it difficult to write Pro next to Akai.