Important notice: kX Project was started more than 15 years ago, in 2002. kX driver allowed thousands of people to better use their sound cards for DSP, playback and recording, ASIO and so on.
We are very glad to have been with you these years. But now it is time to go on. This web site will be permanently closed in November, 2018. Full source code for the driver, as well
as pre-compiled driver binaries will be available from github. Please update your bookmarks.
Thank you for being with us all these years.
kX BETA Testing Initiative
What is BETA Testing?
Beta testing is a special development phase when a new version is released but it is not
announced on our site to let the experienced kX Users to test it thoroughly.
We sometimes call these versions 'development releases'.
Can I particiapte in BETA Testing?
Certainly! We encourage our users to take part in beta testing. This helps us to track
bugs and errors before a new version of the driver is officially released.
Each 'development release' is announced on our forum.
Do I need special skills for BETA testing?
We suggest that only experienced users take part in BETA testing. Development releases
might be very unstable, cause certain problems with your software / hardware etc...
You should be ready to dedicate certain amount of time for testing the new release and
sending us your comments and feedback.
I've decided to participate. What now?
We are currently developing special testing procedures ('testsuits') for each
driver application (SoundFont and MIDI, AC-3, ASIO, Games, etc...). We also need to choose
the team of beta-testing coordinators. If you wish to coordinate the testing of any particular
driver feature, please go to our Support Forum, find the appropriate
topic and post a message. If you wish to become a 'regular' beta-tester, please
stay tuned -- (and watch our forums)! We'll be informing of any progress we have.
What is 'Coordinator'?
'Coordinator' is supposed to collect all the feedback from our beta-testers, coordinate
and manage any information circulated and summarize the information by sending short
'reports' to our development team. That is, say, the coordinator recevies a 'bug report'
from a beta-tester. He/she should try to reproduce the bug or to apply to other beta-testers
to do that. As soon as enough information is collected about the issue, the Coordinator
sends a message to the kX development team with a detailed description of the bug. That's it :)