SaschaFranck Posted April 22, 2020 Share Posted April 22, 2020 1 hour ago, molul said: As a developer, it's easy to explain: they received bug reports, checked what settings the problematic units had, and found a testing case that reproduced the problem, that wasn't taken into consideration in their QA department so far. It happens more usually than you might think, and everywhere, especially in complex software with so many possible combinations of either modules or settings. Ok, I usually don't like saying so, but I have around 2 decades of audio software betatesting on my belt. So, I do know there's plenty of chances for software to be released while there's still some bugs (a lot easier to sort them out inside a closed, hardwarebased ecosystem such as the Helix, though, as you have to deal with way less variables). Fine. But then there's "showstoppers". Bugs that you won't allow to get into the wild. IMHO, the messed up tap tempo functionality absolutely qualifies as a showstopper (in fact, for me it would be if I was playing live - which I only ain't because of C19, otherwise I'd instantly roll back to 2.82). So, how comes 2.9 is released as is, though? Either Line 6 doesn't care. I doubt that. Or they haven't aquired proper betatesting personnel (no idea about those, but I do at least sort of doubt it, too). Or there's simply not enough testers. IMO that's the most likely scenario. I mean, in this thread alone there's several people having tap tempo issues - how comes none of the testers were running into these issues? Because apparently there's not enough of them to cover all likely scenarios. Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.