IK doesn’t have that. They have tech support do the testing in their spare time. And they’re not any better at that job, either.IF Ik is like many other larger software developers there is a chain.
QA gets stuff first, they figure out a repro.. if they do, it then moves up the chain.
I assume what Peter calls Tester is what other companies called QA (Quality Assurance). Those are usually full time employees whose job it is to test and make sure stuff is working properly (that is they are paid beta testers) and when a bug is reported they work out a repro and write a detailed repro to the developer team.
rsp
That’s what I mean by “IK doesn’t have real testers.”
So I’m left wondering if it was actually tested at all. Was it thoroughly and correctly tested with multiple Tone Models on all platforms and all plugin formats? Or did someone not really understanding the problem just do a quickly drive-by and dismiss it?
I experienced it in VST3 on Mac. Maybe it’s only an issue on one or the other? Was it tested there?
Anyways, I’ll install 1.5.1 and see if it is still occurring. I’m quite taken aback by Peter’s attitude. It’s like he’s threatening me with leaving bugs unaddressed as punishment for speaking the truth.
Peter works for IK, and it’s IK’s software. He should have more of an interest in his company’s software working correctly. It’s not just for me, you know.
Reporting a bug to the same half-assed tech support team that does an equally poor job of testing isn’t going to get anything fixed.
Has the JCM Slash gain bug that’s been around since AmpliTube 3.7.1 ever been fixed? Or even investigated by the “testers”?
Are they just “not able to reproduce” that one either? It’s most certainly been reported by many people over many years.
The only way stuff actually gets fixed is if it is relayed directly to the developers in Italy.
Statistics: Posted by jamcat — Thu Jan 18, 2024 9:06 pm