kX ASIO not working/ASIO Control Panel will not open

Russ · Jun 3, 2007, 02:22 PM

After successfully using kX ASIO earlier in the day, it suddenly stopped working when I attempted to use it later on.

I received such errors (in different apps) as:

------
ASIO Driver Error:
kX ASIO Init error: no error
------

------
Not enough ASIO output channels available: At least 2 channels are needed.
------

In some case, no error was displayed, but kX ASIO was not available in the application.

Also, the kX ASIO Control panel would not open.

I tracked the problem down to the following registry key (the values shown under that key seemed off to me):
HKEY_CURRENT_USER\Software\kX\ASIO

I have no idea what caused the info in this registry key to change to invalid settings, but deleting the key fixed the problem (the key is automatically recreated when kX ASIO is used, or the ASIO Control Panel is opened).

In any case, I just thought I would share this info in case anyone else runs into the same problem, etc.

-Russ

------
kX 3538m
Windows XP

Doug W · Jun 3, 2007, 02:47 PM

Here are my registry settings, what value was whacky enough to stick out?

I am using 3534f and 98SE on this computer.

(Default) (value not set)
ASIO0 "1024"
ASIO0Rate "48000"
DefDevice 0x00000000 (0)

Russ · Jun 3, 2007, 06:44 PM

Most of the values were 0, which didn't seem right.

"ASIO0"="1024"
"ASIO0Rate"="48000"
"BPS_0"="0"
"Latency_0"="0"
"Freq_0"="0"
"Rec_0"="0"
"Pb_0"="0"
"AsioMethod_0"="0"

The last one ("AsioMethod_0") appears to be what was preventing the ASIO Control Panel from opening, as upon further testing, deleting that one entry lets the CP open, at which point the rest of the settings are updated with valid settings.

<edit>
Here is an example of good values (for comparison):

"ASIO0"="1024"
"ASIO0Rate"="48000"
"BPS_0"="16"
"Latency_0"="384"
"Freq_0"="48000"
"Rec_0"="16"
"Pb_0"="16"
"AsioMethod_0"="131073"

The above is for the following ASIO Control Panel Settings:

Latency: 8.00 ms (384 samples)
Format: 16 bit / 48 kHz [16+16]
Sync: Default
<edit>

BRNNN · Jun 9, 2007, 06:09 PM

I have the same problem RUSS, in past few days.

It seems that causing by UFX plugs. I uninstalled all, and then installed only 3538m.
ASIO works fine! When I again installed UFX_39_PRE , ASIO disappear again.

I will try your advise to resolve a problem. THANKS !

Russ · Jun 9, 2007, 06:39 PM

I am not sure why installing UFX would cause problems with ASIO (it has not given me any such problems).

In any case:
Are you not able to open the Asio Control Panel?
Did you seea any error messages?

Also, make sure that Hardware Accleration is set to full, as ASIO will not work otherwise.

BRNNN · Jun 18, 2007, 08:26 AM

Defnetely I solved the problem when I deleted registry keys "more asio". I deleted it complete and reinstalled drivers. Try that Russ. After that I installed again UFX and it all seems ok.

Russ · Jun 18, 2007, 08:41 AM

Quote:

Originally Posted by BRNNN

Defnetely I solved the problem when I deleted registry keys "more asio".

"more asio"?
I do not have any such key.

Lex Nahumury · Jun 27, 2007, 09:36 PM

Quote:

Originally Posted by Russ

"more asio"?
I do not have any such key.

He means "more kX" which is UFX key.

Btw Russ;
For no apparent reason I also experienced the same issue (asio control panel won't open etc.)
In my case, simply deleting
HKEY_CURRENT_USER\Software\kX\ASIO
as you describe did not solve it either.
I also had to do a complete 'm' reinstall.

Did you already post this isue in the 'm' bug report thread?

cheers,

/lex.

Russ · Jun 27, 2007, 11:24 PM

No, I didn't post a bug report on this, as I was not sure that it was a kX bug.

I guess I will post something, but I wish we had more info before reporting it as a bug.

Lex Nahumury · Jun 28, 2007, 06:02 PM

Quote:

Originally Posted by Russ

I guess I will post something, but I wish we had more info before reporting it as a bug.

You probably mean reproducable.
That could prove to be hard, but it is definatly a kX bug.

Russ · Jun 28, 2007, 09:20 PM

BTW: From what I can remember, I had been recording using ASIO (using Krystal Audio Engine) earlier in the day, and it was working fine (I exited out of the program when I was finished, etc). Later on that day (no reboots or standby/sleep, etc), I was going to try out the 4Front Bass Module VSTi, and that is when ASIO stopped working. At first I thought that maybe that installer for the VTSi (or the VSTi itself) may have caused the problem (as it was the only thing to change since earlier), but I could not think of, or find any reason why it would do so. I then ran DxDiag looking for any possible problems there and didn't find anything. I then did all the basic kX troubleshooting (with no success), and eventually moved on to the registry looking for any ASIO related registry keys, and I came across the aforementioned registry key, and was able to resolve the problem.

I just thought I would post this info in case anyone notices anything in common, etc (I doubt it, but you never know).

Obviously, in my case, to recreate the symptoms, you only need to change the registry key entries, but I do not know what caused the initial problem, and thus far it has only happened the one time.

@Lex, (out of curiosity) I know that deleting the reg key did not work for you, but did you happen to notice if any of the values were off before you deleted it? (Again, just looking for some commonalities, etc.)

Lex Nahumury · Jun 29, 2007, 09:00 AM

Quote:

Originally Posted by Russ

@Lex, (out of curiosity) I know that deleting the reg key did not work for you, but did you happen to notice if any of the values were off before you deleted it? (Again, just looking for some commonalities, etc.)

Yes, iirc, they where off. (I don't remember the exact values)
But this info could serve as a pointer for Eugene during bug fixing.
I don't think it's hard to fix.
Probably some small registry corruption bug in the ASIO driver code.

Loupitour · Jul 30, 2007, 03:41 PM

Hi
I have exactly the same problem : I can't open kX ASIO control panel and when I launch FL Studio, I get "Not enough ASIO output channels available. At least 2 channels are needed." error message.
I tried deleting the ASIO registry key an a full reinstall of 3538m driver but it's the same thing.
Btw, in the audio device list of FL Studio I have all kX devices but there are (emulated) as in : "kX Wave SB022xb 10k1 [a000] 6/7 (emulated)".
I checked in the device properties and dxdiag.exe but the acceleration is set to full but when I try to reinstall the driver the acceleration get back to the lowest.
This is really weird and I don't know where it comes from so if any of you have an idea, I'm interested =)

Russ · Jul 30, 2007, 04:53 PM

@Loupitour
What OS are you using?

The errors you are getting are most likely related to the issue with hardware acceleration. I would start with troubleshooting that. Did DxDiag show any DirectX errors?

Loupitour · Jul 30, 2007, 05:22 PM

Yes it seems that this is a problem with hardware acceleration but I have no idea on how to fix this...
I'm running Windows XP pro SP1 and dxdiag doesn't show me any error.

Edit : I tried installing an other sound card (some old SB 128) and it's also emulated, it seems that the whole Directsound got badly bugged but I dont know how to fix it... =/

Russ · Jul 30, 2007, 05:48 PM

And DxDiag does not show any problems with any files, etc?

Hmm...
Try checking the Event Viewer for any problems.
Are you using latest version of DirectX?

Try booting Windows in Safe Mode and check Device Manager for phantom devices, etc.

When did the problem start? Do you have a recent Restore point (before the problem started)?

Maybe try reinstalling SP1 (Is there some reason why you are not using SP2?).

Loupitour · Jul 30, 2007, 05:53 PM

No there aren't any problem with anything in dxdiag...
I'm using DirectX 9.0c and I guess that's the last version.
The problem started today when I was trying different tricks because I experienced sound freezes in Warcraft III (only in this application) so I guess something messed up but I really don't see why since I don't remember doing something with Directsound.

Edit : I tried booting with last working parameters but it's the same thing...

Russ · Jul 30, 2007, 06:23 PM

It sounds like maybe a file got corrupted, but it is hard to say.

Are you certain that you completely un-did whatever tricks you tried?

I would try downloading the DirectX 9.0c full install (not the web-update), and run the install and see if it fixes the problem.

Beyond that, (again) reinstalling SP1 (or a later Service Pack) could potentially replace any files that might have gotten damaged.

SUN · Jul 31, 2007, 02:49 PM

Hi again Russ,

i now see what i've overlooked in our PM's (or better what's on page 1 written in this thread)
that i didn't had the "AsioMethod_0"="131073" in my registry! (hole entry missing)

After some tries to get the ASIO-Setup (without foobar playing

i have this Entry!

Et voila - it work's...

btw- even an oldie make errors: i didn't deinstalled 3538h

before upgrading
(i know i'm a bad boy ;-)

SUN

Russ · Jul 31, 2007, 04:17 PM

Quote:

Originally Posted by SUN

Hi again Russ,

i now see what i've overlooked in our PM's (or better what's on page 1 written in this thread)
that i didn't had the "AsioMethod_0"="131073" in my registry! (hole entry missing)

Some of the values are only added after changing certain parameters in the ASIO Control Panel, etc, but for me, everything works OK, even with that entry missing (just so long as it is not a bad value), so there still may be something related to this that we haven't figured out as of yet.

In any case, I am glad that you got it working.

ReWired · Dec 9, 2007, 09:45 AM

The problem for me is solved.
I reproduced this 10 times in a row.
Installing UFX.39 cause the "ASIO missing / ASIO Control Panel won't open".
Uninstalling UFX does NOT fix the problem.
Simply DELETE this KEY:
HKEY_CURRENT_USER\Software\kX\ASIO
The WHOLE "folder" ASIO, not only the keys inside it.
Close the editor, you even do not need to restart kXMixer., just close the regedit.
Then try to open kX ASIO panel from the tray icon...
For me it works perfectly.
HKEY_CURRENT_USER\Software\kX\ASIO <-- is recreated (with "non-zero values" keys inside) after you open ASIO panel.

EDIT: If you do not want to use UFX - deinstall them and do the steps, mentioned earlier.
If you want to use UFX - install them (the bug will appear), then do the same steps and you will have both things working again (ASIO & UFX).
Somehow...the restart of KX Mixer AFTER installing UFX changes all keys in HKEY_CURRENT_USER\Software\kX\ASIO to 0 values.
I can't detect if the actual installation of UFX do this before restarting of KX Mixer...or the KX Mixer by itself..

ap1325 · Dec 22, 2007, 11:25 PM

Quote:

Originally Posted by Russ

After successfully using kX ASIO earlier in the day, it suddenly stopped working when I attempted to use it later on.

I received such errors (in different apps) as:

------
ASIO Driver Error:
kX ASIO Init error: no error
------

------
Not enough ASIO output channels available: At least 2 channels are needed.
------

In some case, no error was displayed, but kX ASIO was not available in the application.

Also, the kX ASIO Control panel would not open.

I tracked the problem down to the following registry key (the values shown under that key seemed off to me):
HKEY_CURRENT_USER\Software\kX\ASIO

I have no idea what caused the info in this registry key to change to invalid settings, but deleting the key fixed the problem (the key is automatically recreated when kX ASIO is used, or the ASIO Control Panel is opened).

In any case, I just thought I would share this info in case anyone else runs into the same problem, etc.

-Russ

------
kX 3538m
Windows XP

My advice is uninstall the driver and then uninstall the kx package; reboot your computer let the original drivers install. Reboot again and reinstall the KX drivers; reboot again and you are set.

If your card is not detected after deleting the KX drivers and rebooting; then go to the device manager, delete the sound card drivers from there and reboot. Then follow the above instructions.

If it does not work just try it all over again (I don't think it will be necesary but sometimes it is).

Max M. · Dec 23, 2007, 05:48 AM

>I can't detect if the actual installation of UFX do this before restarting of KX Mixer...or the KX Mixer by itself..

Well, UFX installer does not touch any of kX's registry keys (except those related to plug-ins), so...
The workaround would be just to close kxmixer before installing UFX.

hasyrein · Jan 1, 2008, 02:22 AM

I use Sound Blaster LIVE! SB0102 + Kx + ASIO4ALL + Foobar ASIO component = No problem at all.
The sound is so f**kin nice!! Well balance and so details!
Love it.

Russ · Jul 18, 2008, 06:32 AM

Update: I just ran into this issue again with kX 3543 (right after installing UFX this time)...

The fix worked same as before, but only if you restart kxmixer once first.

Here is the registry info containing the default settings ([COLOR=Gray]for one card only[/COLOR]):

Code:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\kX\ASIO]
"BPS_0"="16"
"Latency_0"="384"
"Freq_0"="48000"
"Rec_0"="16"
"Pb_0"="16"
"AsioMethod_0"="131073"

After installing UFX, the above keys (for some unknown reason) all got set to zero (but you only see it after restarting kxmixer).

Here is step-by-step info for reproducing and fixing:

Install UFX.

Try opening the ASIO CP.

If it does not open, restart kxmixer (reboot is not necessary).

Use above .reg info to restore the kX ASIO settings.

Try opening the ASIO CP again... (should work).

...

I also tried quitting kxmixer before/while running the UFX installer (as Max suggested), and that seemed to work (as in prevent the problem from happening) as well.

...
[COLOR=Gray]Note: If you have more than one card installed, than the above reg info will be repeated once for each card.

i.e.

"BPS_0"="16"
"Latency_0"="384"
"Freq_0"="48000"
"Rec_0"="16"
"Pb_0"="16"
"AsioMethod_0"="131073"
"BPS_1"="16"
"Latency_1"="384"
"Freq_1"="48000"
"Rec_1"="16"
"Pb_1"="16"
"AsioMethod_1"="131073"
[/COLOR]