Asio with 2.33ms Latency with 3530?

njoha · Mar 4, 2003, 07:28 AM

The new Asio driver is far more stable than the previous ones. No more -5 bugs (Cubase SX crashes though sometimes when changing from 2.33 to 5.66 and back to 2.33 with reason running).

One major prob I encountered is when I use a latency of 2.33 ms. There are many clicks and pops and the CPU usage in Cubase is higher than it was on previous versions. This latency is practically unusable with 3530.

I use such a low latency cause I play the bass and monitor straight from Cubase applying EQ and other effects in real time.

Darkie · Mar 4, 2003, 08:24 AM

Hi there!!

I experienced the very same problem when trying to use the 2.66ms latency setting, but I think that the whole thing has already been discussed. kX developers recommend disabling ACPI if you're running under WinXP. Other kX users have also tried to change their PCI Latency (BIOS) to a higher setting (96 instead of 32).
Maybe you should try this - keep me posted, though. I'd like to know how it works out.

Darkie

njoha · Mar 4, 2003, 09:37 AM

ACPI is disabled and my system is tuned for audio use. I didn't have this problem before 3530, so I think it's driver related. Maybe the developers sacrificed a little bit of performance for the sake of stability, i don't know.

Max M. · Mar 4, 2003, 03:01 PM

well, as i know 30 have no modification of ASIO comparing to previouse versions (well it has many WDM Audio interface changes but it shoud not affect ASIO in any way..) but who knows... i dunno what it could be... well i'd checked everything once more (starting from BIOS setting through Windows settings to Cubase's settings)... well, 2ms is two extremal latency to give some advices...

njoha · Mar 4, 2003, 08:14 PM

Thanx Max. I'll re-check everything.
Although I think 3530 has some modifications in Asio compared to 3528 the version I was using before (3529 was a bit buggy with Asio), or else the -5 bug wouldn't be gone right?

Max M. · Mar 4, 2003, 08:25 PM

or else the -5 bug wouldn't be gone right? - ah, that's right... then it could be related to this.

**Eugene Gavrilov** · Mar 6, 2003, 08:23 PM

>> -5 bug wouldn't be gone right? - ah, that's right

not exactly
the '-5' bug was memory-management related
it was fixed, but it has nothing to do with the latency
memory allocation happens on driver initialization and doesn't affect timings, latencies etc...

I think the problem is elsewhere

/Eugene

~~bluelight~~ · Mar 9, 2003, 03:48 PM

2.6 ms lateny is practically possible to run only if you have a very fast machine or if you do not load ´the machine to much.

Im running an Athlon 1.6 and i use 5 ms latency.This is enough to do work in realtime.

With 5 ms i can run up to 16-20 channels and effects before the performance starts stuttering.

Bluelight

Air · Mar 13, 2003, 04:32 AM

Just for your information, I am experiencing the same pops and clics problem when using 2.66 ms latency with Cubase SX, with 3530, Win98SE, Pentium 4, 1.5GHz, EMU APS. (However, I have no idea of what do you mean with "being tunned for audio" or ACPI or PCI latency so I have not tried anything to improve it).

With 5.33 ms seems to work clean (except for another problem which I am still trying to solve: the analog sound inputs are either too low or too noisy, but this doesn´t have anything to do with latency).

Jan_Dsson · Mar 14, 2003, 10:03 AM

Hi!

I've got this problem earlier mentioned aout pops and stuff recording with cubase. Someone was talking about ACPI and i want to know what that is and how i turn it off!?

Pls help me..

/D

njoha · Mar 17, 2003, 08:23 AM

http://kxproject.spb.ru/acpi.php?language=en

You'll find all the info you need here.