Kx ASIO driver issues in FL 3.5.6

Robotic · Jan 27, 2003, 09:55 PM

I've found that when running Fruityloops 3.5.6 with the v3.528 Kx project ASIO drivers(ASIO DirectX Full Duplex, to be specific) at 44100Hz, everytime I click the mouse to do something, the program pauses for roughly 1 second, and then continues as normal.

This is a constant, and I've only tried using this Kx ASIO driver, with a latency of 11ms(512 samples buffer length).

If it helps any, I'm running Win98SE with a SB Live! card, on an AMD Athlon XP 1600+ with 256mb of DDR RAM.
If anyone knows how to correct this, any help would be more than appreciated.

Thanks.

Mata Hari · Feb 14, 2003, 05:15 AM

ASIO DirectX Full Duplex is the cubase asio driver using directSound output, not the kX asio driver...
the kX can only output at 48000 anyways, not 44100

IF you want to use the Full Duplex drivers (specially in fruity) try an higher buffer length (I sometimes had this problem too, increasing buffers helped, but just using the asio kX drivers works better :-))

Jan 27, 2003, 09:55 PM	#1
Robotic DriverHeaven Newbie Join Date: Jan 2003 Location: Toronto Posts: 1 Rep Power: 0	Kx ASIO driver issues in FL 3.5.6 I've found that when running Fruityloops 3.5.6 with the v3.528 Kx project ASIO drivers(ASIO DirectX Full Duplex, to be specific) at 44100Hz, everytime I click the mouse to do something, the program pauses for roughly 1 second, and then continues as normal. This is a constant, and I've only tried using this Kx ASIO driver, with a latency of 11ms(512 samples buffer length). If it helps any, I'm running Win98SE with a SB Live! card, on an AMD Athlon XP 1600+ with 256mb of DDR RAM. If anyone knows how to correct this, any help would be more than appreciated. Thanks.

Feb 14, 2003, 05:15 AM	#2
Mata Hari HardwareHeaven Lover Join Date: Feb 2003 Posts: 213 Rep Power: 0	ASIO DirectX Full Duplex is the cubase asio driver using directSound output, not the kX asio driver... the kX can only output at 48000 anyways, not 44100 IF you want to use the Full Duplex drivers (specially in fruity) try an higher buffer length (I sometimes had this problem too, increasing buffers helped, but just using the asio kX drivers works better :-))