Good example Don.
This issue was resolved in the first SD7 OS release ... unfortunately, it came a tad late - after you had sold your SD7, but this is a good example indeed - and one we will prevent from happening in the future.
Thanks for contributing to this.
AJ that's all well and good but these major things should all be worked out
"Before" release when people are spending mega bucks on a keyboard...with so much stiff competition customers will drift away very quickly...that said you have always been good to me and my needs I'm glad I was close to the "lab" during my ketron days just in case I needed you..
You cant work out all these things before release... its just not possible with software, that runs on dedicated hardware...
If you want software to run flawlesslly it requires thousands of testers.. that report back.. with inhouse testing, you are fully dependant on testing procedures.. and they just cant test it all..
What matters for a product like this is that the company has a fast way to report and to react based on problems reported by users..
But everyone working in the software buiseness knows that internal testing can do only so much.. they will tell you what you wish for is near impossible and incredible expensive and time consuming..
Where Ketron goes wrong is in the way how they where handling this.
Previous Topic
Index
