Maybe in your country you can return the product you don't like, but mine is not,
I generally can, but although this is not just a matter of not liking, in that we're talking about deal breaker software problems, that just makes it more important to wait until a product has a reputation you can check out before you buy (as in being able to get clear answers when asking in this forum). I really don't think I've ever needed to return a product because I was surprised by a software bug which I wasn't able to live with, one that didn't have an already-available fix.
in fact I am using both SBLive and X-Fi together. The merit of using X-Fi is just on the hardware side (such as better DAC/ADC, no resample in 44.1k), not software.
Sounds like you've come up with a workaround you find sufficiently acceptable.
And your claim that kX driver is based on old CL's APS driver is incorrect. kX drvier is first released in 2001, it is WDM-based. At that time there was no workable WDM-based APS solutions at all. From user interface to functionality kX driver is completely different from APS driver.
You're right about that and I was wrong. My recollection had gotten hazy. kX was done because the APSLive drivers couldn't be used on Win2k due to the switch to WDM drivers by Microsoft. I don't know the genesis of xK, but I suspect there is a sense in which it was inspired by the APS drivers, and based on CL's old open source Linux drivers.
I am using kX since 2003, the five points I mentioned above are true
Point 1 is not sustainable when the user base is as large as it is for CL's drivers. It just means there aren't enough kX users to overwhelm its developers.isn't what is normally referred to as a programmable DSP chip. It's a hardwired, register-programmed chip which contains a sample-locked mixer/effects programmable DSP subcomponent.
Point 2 is interesting because the kX
Point 3 is probably really a matter of CL not needing to take things that far because the kX drivers are available.
Point 4 may only be a matter of the newness of the X-Fi. A counterpoint is that presently the kX drivers certainly do not have this problem on the X-Fi (i.e. due to lack of support), and the SBLive/SBAudigy have no such thing as an Audio Creation Mode.
Point 5 is a matter that CL has to make drivers which attempt to minimize confusion for the typical consumer (even though that's a tall order) while kX can basically ignore that.
kX doesn't support newer models very well because the developers cannot get enough information from Creative (they are commercial secrets),
Why doesn't matter. What's important is that they don't.
but for old models like old SBLive and Audigy it just worked fine.
All the kudos about how they do work "great" on non-X-Fi cards don't change that they don't when it comes to the X-Fi. And, in the current context, the same techniques for knowing that before buying are available.I'm not impressed by that link. Do you have CL statement they acknowledge those as bugs and don't intend to fix them?
I am gradually moving into software samplers because the soundfont system is so buggy.
Software samplers aren't immune to this sort of thing, but you probably don't change them right at the same time you change hardware, and you may not see them in the same terms of getting new features.