tubus

since this it my first post, the absolute first thing I want to say, as it was said many times before:

Thank you so much!!!
I just wanted to thank the developers of this project so very much for making it available and free.

this said, I would like to add a few things:
I'm a user of the kX-drivers from the very beginning, and yes from then on, it provided me with (mostly) stable multi-channel asio-IO for an unbeatable price! On the other hand: yes, I owe more than a few grey hairs to the kX-project!
Like other pieces of software (Reason, as a prominent example) the kX-Drivers combine almost unbelievable cleverness with some (for me almost unbelievable too) shortcomings.
No need to comment on the cleverness, as this is obvious. But may be on the shortcomings, as at least some of them may be fixed easy (or so it seems) and this may make an excellent product even better!

First of all: it used to be almost an imputation (if that's the correct word, i mean german:'Zumutung'), that with every update all the settings had to be reconstructed again & again (imagine that with a Wordprocessor you must throw away all your Documents with an update, the author of it would be killed!). Yes, it has improved meanwhile, but still they are deficiencies, At least: save the settings of the 'Save /Restore Settings' dialog. Well, this one should be really easy!

In the DSP-Window, well this may be my personal view, but, since all the signal are almost inevitably stereo, I would preferr *STEREO*-patchcords. This would save half of the work and would provide much more clarity.
Speaking of clarity: the possibility to place freely editable pictures into the different objects would also greatly enhance the usability of the DSP-window! No more need to keep a list of the pin-assignement of the different objects beside you, just create a bitmap with your favorite connections marked, and I'm sure, the kX-community would be eager to create a library of bitmaps for the various objects and Soundblaster-models.

Speaking of usability: *The* best overall improvement in my opinion would be: include level-indicators on the kX-mixerpage *itself*! That may be not so easy, but hey, the APS-driver had it, and everything else is only the second best. The Peak-object, while beeing indispensable, is just a hassle for monitoring levels.

Speaking of 'Goodies' on the wish-list: a MIDI-learn function for the twaking of DSP-settings would also be nice (like in Reason or Reaktor), Should'nt be too hard to implement either. Using MIDI-programm-change to switch preset or even load whole banks of DSP-settings would also be very nice ...

... ok, ok, I know, it's a little bit impudent from myself to say 'I want this, I want that', especially if considered that the kX-drivers are free.
But as it is said in german: 'Der Appetit kommt mit dem Essen' (appetite comes with eating)! Of good things, we always want more!

thanx again

tubus

B.T.W speaking of a donation: it's a pity that *real hard ware* cannot be sqeezed through the internet-cables Thanx to the kX I have quite a few SBs meanwhile, I would happily give away one or two! But, since i'm a programmer too, and one of my projects is a kX-frontend with a lot of goodies, I might donate this to the kX-community as soon it evolves beyond alpha-state.

Eugene Gavrilov

thanks for your message
I'll add some of the ideas into my 'todo' list (well, the list is too big already -- so, I cannot promise anything)

/E