Asio Latency Help

[boombaxx]

Hi wondering if anyone can help me with ASIO latency in Buzz. I am using DPC latency checker and i am getting unexplainable spikes in the latency which is causing clicks and pops in any real time recordings i do. It will be fine for a while then it goes mental. No matter what latency setting i use in the asio buffer. I thought it could be the cpu but it is a quad core 2.5ghz or ram 4gig 1333mhz Kingstone Hyper X WIn7 64bit. I am only utilizing 25% of the available resources and it is still spiking. I have virus checked and run reg cleaner disk defrag switched off everything i could in the device manager still with the spikes

[mcbpete]

What's your audio interface - Is it internal/usb/firewire ?

[boombaxx]

Usb 2 it is a NI Kore audio interface

[mcbpete]

Ah my hypothesis of the firewire controller being the problem clearly isn't the issue then ! I had exactly the same problem with my new laptop as it had a crappy Ricoh controller so had to go the USB2 route. But as you're there already, apologies - I haven't a clue ... sorry man

I take it you've already gone the updating firmware and driver route ?

[UNZ]

http://www.resplendence.com/latencymon

try this one, it will tell you which driver causes the dpc latency, probably the gfx or something. try updating.

[boombaxx]

everything is running between 3-4000 milli seconds. USB seems to be taking the longest

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines executed by a driver running in your system appear to be executing for too long. Also one or more ISR routines executed by a driver running in your system appear to be executing for too long. Also your system appears to be having trouble which may be attributed to SMIs, IPIs, CPU bugs or unexplainable stalls. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:08:10 (h:mm:ss) on all processors in the system.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: HOME-PC
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q8300 @ 2.50GHz
Logical processors: 4
Processor groups: 1
RAM: 4094 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3000.0 MHz
Measured CPU speed: 2431.0 MHz (approx.)

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.


_________________________________________________________________________________________________________
MEASURED KERNEL TIMER LATENCIES
_________________________________________________________________________________________________________
Highest measured kernel timer latency (µs): 5879.730732


_________________________________________________________________________________________________________
MEASURED SMIs AND CPU STALLS
_________________________________________________________________________________________________________
Highest measured SMI, IPI or CPU stall (µs) 3683.279597


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
Highest DPC routine execution time (µs): 6393.2050
Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation

Highest reported total DPC routine time (%): 1.097095
Driver with highest DPC total execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation

Total time spent in DPCs (%) 2.593058

DPC count (execution time <250 µs): 1938594
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 4395
DPC count (execution time 1000-1999 µs): 4238
DPC count (execution time 2000-3999 µs): 3841
DPC count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Highest ISR routine execution time (µs): 3599.517667
Driver with highest ISR routine execution time: hal.dll - Hardware Abstraction Layer DLL, Microsoft Corporation

Highest reported total ISR routine time (%): 0.101403
Driver with highest ISR total time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation

Total time spent in ISRs (%) 0.235274

ISR count (execution time <250 µs): 1497600
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 1245
ISR count (execution time 1000-1999 µs): 328
ISR count (execution time 2000-3999 µs): 62
ISR count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Process with highest pagefault count: none

Total number of hard pagefaults 22335
Hard pagefault count of hardest hit process: 13857
Highest hard pagefault resolution time (µs): 1838215.242667
Total time spent in hard pagefaults (%): 10.985947
Number of processes hit: 0


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 23.421950
CPU 0 ISR highest execution time (µs): 3599.517667
CPU 0 ISR total execution time (s): 1.585906
CPU 0 ISR count: 742138
CPU 0 DPC highest execution time (µs): 6393.2050
CPU 0 DPC total execution time (s): 20.136810
CPU 0 DPC count: 1246298
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 13.039088
CPU 1 ISR highest execution time (µs): 2148.4050
CPU 1 ISR total execution time (s): 0.974101
CPU 1 ISR count: 251914
CPU 1 DPC highest execution time (µs): 6334.777333
CPU 1 DPC total execution time (s): 10.309755
CPU 1 DPC count: 229974
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 12.838193
CPU 2 ISR highest execution time (µs): 2654.8750
CPU 2 ISR total execution time (s): 1.031203
CPU 2 ISR count: 252983
CPU 2 DPC highest execution time (µs): 6247.407333
CPU 2 DPC total execution time (s): 10.243385
CPU 2 DPC count: 230423
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 12.787991
CPU 3 ISR highest execution time (µs): 2686.147667
CPU 3 ISR total execution time (s): 1.028811
CPU 3 ISR count: 252200
CPU 3 DPC highest execution time (µs): 5573.177333
CPU 3 DPC total execution time (s): 10.229412
CPU 3 DPC count: 245149
_________________________________________________________________________________________________________

[boombaxx]

I think it is a faulty core in the cpu. No way to turn off individual cores on intel or amd for testing purposes

[UNZ]

i would consider other things before a faulty core to be honest

do you have the same problem with other hosts using asio ?
you might want to fiddle with polac asio settings (you're using polac asio, right?)
try the settings for buffers (2 sync or 2+1 async etc) and "Override ASIO thread priority".

also you mention you have a virus scanners, might be worth a try to get rid of that..

another thing to try: enable / disable multithreading in buzz.

you mentioned "I am only utilizing 25% of the available resources and it is still spiking". i assume you look at task manager: of course on a 4 core cpu, if you run buzz singlethreaded, 25% sounds about right for full load on audio thread. you might indeed already be limited by the cpu. you'll only get more out of it with multithreading (using all 4 cores).

finally, you can try unplug everything that isn't neccessary to run buzz + audiointerface (other usb stuff etc) or try a different usb port (2.0 vs 3.0 etc).

[mcbpete]

try a different usb port (2.0 vs 3.0 etc).

Ah yeah, I've heard that issue too - On my card (Scarlett 8i6) they'd only just fixed the issue of having the 2.0 audio interface plugged into the 3.0 usb port. Luckily for me the updated driver was released just before I purchased the card or I would've been royally pissed off (and no doubt very much confused )

[boombaxx]

I think i have found the root of the problem my HD has started to fail making funny noises. So going for the Momentus Xt 500gb with 4gb SSD which looks like a good compromise between performance and capacity. Just hope this drive is ok till it arrives

http://www.ebuyer.com/222310-seagate-50 ... 95005620as

[retrigger]

before you buy anything, turn off wireless and check DPC.


I do that and it works on both my laptops.

[boombaxx]

Tried it didn,t work thanks anyway

[bahador]

@Boomboxx so at the end of the day you say it was your hard drive causing the latency issue cuz I'm having some similar issues when recording vocals through adobe audition cs5 and cs6 both. could you please view my other thread regarding the issue and see if you've had the same issue?

viewtopic.php?f=2&t=1136