Eugene Gavrilov

hi there,

pls check kx 3538k release:
http://download.kxproject.lugosoft.c...3538k-full.exe

previous build (3538j: http://www.hardwareheaven.com/general-discussion/97845-3538j-released.html)
please review this link for details. also read Project Status

note: there were NO significant changes in this version, except additional a2zs notebook features + some minor sb0610 (a4 value) initalization issue (I added an option that might affect digital output / line input - please check).
--
asio code is the same. I will probably check 3534f-3538 difference soon;
ac3 decoding stability -might- have improved (pls check)
--
as usual, no 24/96, 64 bit, EAX2 etc..
--
please check this build. try to reproduce BSOD issue with volume controls (I have never been able to do this myself): turn off automatic reboot (control panel - system - advanced - start-up and recovery: uncheck 'automatic restart', choose 'small memory dump') - if managed to, find minidump (usually in your c:\windows\minidump folder), WinRar it and send it to me with full bug description (include all BSOD numbers!)
--
known issues with a2zsnb and supported features:
- I cannot make analog inputs work. at all...
- SPDIF input/output + all analog outputs should be o.k.
- on the 'ins and outs' page there are invalid inputs + graphics for testing purposes. SPDIF Input is accessible as 'Generic' input.
- on certain chipsets a2zsnb produces the same 'constant noise instead of audio'. this might require PCI latency modifications. please review the thread in 'bug reports' forum and let me know if you manage to fix the issue. at the moment, it is possible to fix this by running 'kxctrl -rv' AND/OR playing a MIDI file AND/OR enable/disable device (don't forget to unload kxmixer first!).

"kxctrl -shw 22 value" will change input source (at least, will try to: values are 0,1,2,3 -- this doesn't work, unfortunately, but keep trying. review ALSA drivers if you have enough time. latest build, 1.12?, does not support line input, if I'm not mistaken)
--
future plans: I would like to release 3539 officially, based on 3538k, provided we fix BSOD issue. no additional features are expected in 3539. there will be NO 3538 final, the next stable build will be 3539. after that, I really hope to start working on x64 version of the driver, provided I get the hardware (might take 1-2 months). Vista support -might- come later.
--

good luck and enjoy
--

as always, any updates, new code, new effects, translations, whatever, are welcome. pls send them by e-mail. pls check 'delivery report' in your mail client to ensure I received your message.

E.

Russ

Download link does not appear to be working at the moment...

---
Thanks, fixed that! /E

Confirmed, it is now working...
-Russ

dj_stick

d/l link is fixed

__________________

Russ

You did not mention installation instructions... I had some problems (kxmixer crashing at startup) doing an upgrade install, probably due to incompatible plugins (seems 3538j plugins are not compatible). In any case, I started kxmixer manually (without the --startup switch), and reintialized the DSP to get it working, and then did a reset global settings to remove incompatible plugins. In any case, users may want to do a clean install, or if upgrading, reintialize the DSP before installing, and then reset global settings at some point (similair to installation for 3538j).

Mata Hari

yay :-)

Max M.

mm, is thereany 38k or 39 sdk available? (just getting scared of Russ reported incompability)

Russ

It includes the updated 3538 SDK that is compatible with 3538k.

Eugene Gavrilov

38k comes with 38k SDK
I will change plugin version # in 3539
--
I wonder what's the reason for incompatibilities...
yes: uninstall/re-install is preferred, since kX Setup does not handle versions with the same major number properly (e.g. 3538i and 3538j)

E.

Russ

Not sure, all the plugins do register successfully (with the exception of ProFX (v3.05), which gives an Error: invalid plugin libary (<-- still mis-spelled, hehe)), but kxmixer crashes if you try to load them. They do work fine however, when recompiled with the new SDK.

BTW: For those who may not understand, the bundled plugins (and .da plugins) work fine as usual.

ROBSCIX

Hey Max M, You said you were waiting for 3538 Final to release UFX. Now Eugene say's no 3538 only 3539 stable...so are you planning on doing a UFX for 3539? I would think alot of people are really interested. I really miss those plugins..I cannot use them on my new card because it's not compatible with older version of the driver....

NightBreed

So far, I haven't been able to reproduce the bsd with the volume change, so all looks good with that. Actually, the volume sliders seem to be a bit smoother in this release. The thing that was causing this for me was having the multimedia keyboard option selected, now it's working fine.

NightBreed

Is it me, or does the bass channel seem a bit improved too?

bzdang

FWIW, I was getting bsods in 3538j while using a usb connected Griffin Powermate knob to control master volume. Using 3538k now (with w2000) and will report any bsods that occur.

Looking fwd to stable 3539, and Max's UFX !

adi111p

To Eugene:

How can I playback multichannel at 96KHz using KernelStreaming? It seems that I can't manage to make it work on 3538k too...

I am using the same code that works with Creative drivers @96KHz and KX@48KHz/16bit, but no chance to work with KX@96KHz...

How KX needs the data? I used 24bit packed in 32bit, 96KHz and KSAUDIO_SPEAKER_QUAD flag used when trying 4channels, but CreateRenderPin returns null ...

Nando Dominguez

Hi all. Can anyone send me the lang.ini file? I want to update the spanish translation but I haven't got any computer with a sb card at the moment. I'm using an emu card and by installing kx I will really get in troubles.

Thanx
Nando

Maddogg6

strange - I did a search on my pc - and no lang.ini exists - nor is there anything that even looks like a lang.ini file (by a different name) ... ???

If you can tell be where to find it, maybe I can send it??

wmjordan

Use winrar to open the kxskin.kxs file (Hmm, yes, it is an RAR file actually), and lang.ini is there.

__________________
Me's box:

• Sempron 2200+, 1G DDR RAM,
• SBLive! CT3843 10k1,
• Windows 2003 Chinese Simplfied SP2, DirectX 9

Nando Dominguez

Yes, that is. Sorry, I didn´t explain myself enough.

Russ

@Nando, did you get the file you requested (did someone send it to you as of yet)?

Maddogg6

Ok - here it is - but dont thank me - thank Russ for it....
http://fileanchor.com/49200-d

Nando Dominguez

I've got it. Thank you Russ and thank you Maddogg6

Eugene Gavrilov

you need to open Wave HQ and allocate all outputs simultaneously (2 or 8)
both packed 24-bit and 32 bit will fit.

install any debugging monitor and watch its output - kx.sys will let you know if something goes wrong...

E.

NightBreed

Just posting an update to the BSOD info I posted a few days ago. So far, my machine has been up since that last post without a reboot and I've used the K build of the drivers in many ways possible and it would appear the bug has been fixed.

Vadim_K

So your last BSOD was on previous KX version ? And no more BSODs with K installed ?

I tried to get BSOD's info too, but I've reinstalled windows in 1-2 days after installing the K version, and I don't remember: there were BSODs in this 1-2 days witk K version or not. The result is that I have no BSODs too after installing K version on fresh Windows installaton, but I'm not sure that BSODs disappeared because of K version - may be it's because of Windows reinstalling. So, may be NightBreed is right that bug is fixed, but may be he's not right. And I advise to not hurry with resume, that bug is fixed and still test K-version at least 2-3 weeks. Cause I'm not sure that it will not happens again

NightBreed

My problems with the BSOD was only with the multimedia keyboard option selected in the previous version of the driver. No matter how many reinstalls of both KX and Windows that problem always resurfaced.

So, for my particular situation, the 'K' build of the drivers works great and I have not recieved a single BSOD from the time of driver install to present day. And my machine runs constant with little or no reboots for days, (unless one is needed for updates, installs, etc).... Hopefully that info gives some insite as to the stability of the drivers and the BSOD errors.

Vadim_K

The talk was about BSOD on moving Master Volume fader. There is topic about this problem here. I have this problem and other users too. I never used multimedia keyboard option and you are right: computer never have BSODs because of KX Driver and works for days or weeks if You don't change the volume by the Master Volume fader. The problem is that sometimes these BSODs happens 3-5 times in a day when moving the fader, but also BSODs don't happen for a weeks sometimes on moving the fader. And this is the reason why I propose to test K version some more time, to be sure that problem fixed.

bzdang

I haven't had any more BSODs with my Griffen Powermate knob, I consider the bug squished. Thanks!

Vadim_K

Ohh. I see that there was similar problem with remote control So I can say that I have no BSODs with K version installed, but from the other hand, may be it will happens again, cause, if I'm rightly understand, Eugen make nothing especially for fixing this bug in this K version, if Im not wrong/

NightBreed

I guess I should be a little more specific. When talking about the mutimedia keyboard and the BSOD, I should have stated that the BSOD was caused by having this enabled and controling the volume with but KX's mixer and another alternative method using tcl.

I know of the topics discussed on this because I participated in them .. lol ...

I'm not going to go into what my uses of the drivers are, that would be too extensive for the moment. But I will say, that at the time before this release the BSODs wouldn't allow my system to stay up and operational for as it is with the K version.

lao-koon

thank you very much for this great driver. with the privious driver i had from time to time this annoying sound bug. with 3538j the bug came not often, but now with 3538k it seems that it has totally been fixed - great !

running kx 3538k on following systems:
1.) amd x2 3800+, dfi nf-4 ultra-d, audigy 2zs
2.) amd x2 3800+, asrock dual-sataII, audigy player
3.) amd athlon xp (barton) 3000+, gigabyte ga-7nnxp (nf-2 u400), sb live! 5.1

excuse for my english, i'm from germany...