ASIO initializing problem

Vadim_K · Sep 17, 2007, 10:07 PM

I use KX ASIO for a long time with some audio applications like Cubase/0Nuendo; Reaktor (standalone), etc. at 44,1 Khz sample rate. The problem is that sometimes, when I use it at low latency settings (2 - 8 ms) application sounds normally without any clicks/buffer drop-outs, but at a one moment these clicks appears... And what I need to do is to go to the application's ASIO settings - change something in Kx ASIO Panel (latency or sync) and it sounds normaly again - then I can go to the settings again and change the settings back to the settings at what I worked till the problem appears and all will be ok. I don't know for sure from what KX version this problem started, but I know that it was on 3538, and now I have 3539 installed - and the problem still exists.

The interesting thing, is that buffer drop-outs start in R-channel first in 80% of cases... But not always... The most often situation is that, for example, I work with audioapplication some time - the I closed it. After this I don't change ASIO or any other settings in KX. But when I run this application next time - it starts sound with crackles until I go the KX ASIO settings and change something, like latency or sync method. Then, as I said before, I can change it back - and all will be OK.

It seems that, may be, something (latency or sync ?) is initialized incorrectly in ASIO sometimes, when I run audio application, because when I change settings manually - problem disappears.

I usually use Cubase/Nuendo at higher latency settings 10-36 ms, depending of CPU usage. And sometimes it starts crackling - I go to the settings, change something, ASIO re-initializes as I understand, - and all is ok again. And I use NI Reaktor standalone a lot with lower latency settings (2-8 ms). And this problem very often appears at low latency settings, until I re-initialize ASIO settings manually (change latency or sync method). So, the problem was in all 3538 releases as I remember, and in 3539 too. I don't remember if it was in 3537 - I didn't use audio applications yet in the times of 3537....

My ASIO settings are: 16bit/44,1khz (2 ouputs + 0 inputs), with "default" or "used thread" sync methods.
SBlive, P4 3.0 Ghz HT enabled, WinXP SP2.

I don't know if it's KX ASIO bug or not.... So, please suggest something.

Maddogg6 · Sep 17, 2007, 11:29 PM

Im curious why you chose to use 44.1Khz... I would think kX is more 'optimized' with 48Khz... may explain your 'odd' problem... ??

Ive done extensive recording with ASIO in Sonar with 3538 - and while I feel 3538H was more stable - 3538L/M gives better latency for me.
With L/M I get more frequent occasions where I have to restart SONAR (sound starts buzzing under heavy track load) - but Sonar is more stable when this happens now..I used to have to reboot WinXP when that happened - less frequently, but imho a bigger PITA. ??

Vadim_K · Sep 18, 2007, 12:33 AM

I don't think that KX ASIO is more optimized for 48 Khz. I used it at 48 Khz for some time and I didn't notice any difference between using 48 or 44,1 in CPU usage, stability and other... I think that 48 Khz is the native sample rate for sblive's DSP, but not for ASIO driver

It's sad that you need to reboot Windows because of this issue even))) I think you joke, because driver re-initializes when you turn it to other driver (DX or something) temporarily or change settings, as I do)) You don't have any need to restart Sonar, but your restart even windows))

But it's not normaly anyway. Because, as I know, these issues do not happen with pro-soundcards like EMU1212M, ESI Juli@ and even with pro FireWire soundcards... seems that it's because of more stable ASIO drivers, or may be it re-initializaes automaticaly ? I don't know... But anyway, I think there is something what can be fixed or improved in KX ASIO, because it's very strange, that sometimes drop-outs appear immediately after starting the application and re-initializing with the same settings solves the problem))

Sep 17, 2007, 10:07 PM	#1
Vadim_K DriverHeaven Junior Member Join Date: Nov 2003 Location: Latvia Posts: 59 Rep Power: 0	ASIO initializing problem I use KX ASIO for a long time with some audio applications like Cubase/0Nuendo; Reaktor (standalone), etc. at 44,1 Khz sample rate. The problem is that sometimes, when I use it at low latency settings (2 - 8 ms) application sounds normally without any clicks/buffer drop-outs, but at a one moment these clicks appears... And what I need to do is to go to the application's ASIO settings - change something in Kx ASIO Panel (latency or sync) and it sounds normaly again - then I can go to the settings again and change the settings back to the settings at what I worked till the problem appears and all will be ok. I don't know for sure from what KX version this problem started, but I know that it was on 3538, and now I have 3539 installed - and the problem still exists. The interesting thing, is that buffer drop-outs start in R-channel first in 80% of cases... But not always... The most often situation is that, for example, I work with audioapplication some time - the I closed it. After this I don't change ASIO or any other settings in KX. But when I run this application next time - it starts sound with crackles until I go the KX ASIO settings and change something, like latency or sync method. Then, as I said before, I can change it back - and all will be OK. It seems that, may be, something (latency or sync ?) is initialized incorrectly in ASIO sometimes, when I run audio application, because when I change settings manually - problem disappears. I usually use Cubase/Nuendo at higher latency settings 10-36 ms, depending of CPU usage. And sometimes it starts crackling - I go to the settings, change something, ASIO re-initializes as I understand, - and all is ok again. And I use NI Reaktor standalone a lot with lower latency settings (2-8 ms). And this problem very often appears at low latency settings, until I re-initialize ASIO settings manually (change latency or sync method). So, the problem was in all 3538 releases as I remember, and in 3539 too. I don't remember if it was in 3537 - I didn't use audio applications yet in the times of 3537.... My ASIO settings are: 16bit/44,1khz (2 ouputs + 0 inputs), with "default" or "used thread" sync methods. SBlive, P4 3.0 Ghz HT enabled, WinXP SP2. I don't know if it's KX ASIO bug or not.... So, please suggest something. Last edited by Vadim_K; Sep 17, 2007 at 10:15 PM.

Sep 18, 2007, 12:33 AM	Thread Starter #3
Vadim_K DriverHeaven Junior Member Join Date: Nov 2003 Location: Latvia Posts: 59 Rep Power: 0	I don't think that KX ASIO is more optimized for 48 Khz. I used it at 48 Khz for some time and I didn't notice any difference between using 48 or 44,1 in CPU usage, stability and other... I think that 48 Khz is the native sample rate for sblive's DSP, but not for ASIO driver It's sad that you need to reboot Windows because of this issue even))) I think you joke, because driver re-initializes when you turn it to other driver (DX or something) temporarily or change settings, as I do)) You don't have any need to restart Sonar, but your restart even windows)) But it's not normaly anyway. Because, as I know, these issues do not happen with pro-soundcards like EMU1212M, ESI Juli@ and even with pro FireWire soundcards... seems that it's because of more stable ASIO drivers, or may be it re-initializaes automaticaly ? I don't know... But anyway, I think there is something what can be fixed or improved in KX ASIO, because it's very strange, that sometimes drop-outs appear immediately after starting the application and re-initializing with the same settings solves the problem)) Last edited by Vadim_K; Sep 18, 2007 at 12:42 AM.

Sep 17, 2007, 11:29 PM	#2
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 50	Im curious why you chose to use 44.1Khz... I would think kX is more 'optimized' with 48Khz... may explain your 'odd' problem... ?? Ive done extensive recording with ASIO in Sonar with 3538 - and while I feel 3538H was more stable - 3538L/M gives better latency for me. With L/M I get more frequent occasions where I have to restart SONAR (sound starts buzzing under heavy track load) - but Sonar is more stable when this happens now..I used to have to reboot WinXP when that happened - less frequently, but imho a bigger PITA. ??