Playback lags [solved]

Very strange thing going on here…

I started a score on my notebook. It’s a piece for wind band, with about 30 staves including percussion. On this notebook it plays back wonderfully.
Today I opened the file on my PC, which has stronger hardware, and playback lags terribly. It’s ok when only 10 instruments are playing at the same time, but when the full orchester is at work I first hear some seconds of the whole sound, then a short time of silence, then a second of music, and then only silence. While all this, the green marker proceeds normally.

I don’t have any specific audio hardware in my PC, it’s a “Generic Low Latency ASIO Driver”. I tried increasing the puffer to 100ms, that did not help.
Task Manager tells me that the system is nowhere near its limit in terms of RAM or CPU.

Any other ideas from the more technical sound guys out there…? :confused:


Update: On Facebook I was asked to try and install the Asio4All driver. It shows the very same problems, no matter if I use the standard 512 samples buffer size or if I increase it to 2048 samples.

Then it could be some other driver that is getting in the way. E.g. drivers for Wireless LAN are known to sometimes interfere with the ASIO system.
Please download and run this:
And post the output here.

Hi, Ulf.
Thanks for your response.
I installed the software and let it run during playback.
Here are the results:


Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:01:03 (h:mm:ss) on all processors.



Computer name: *****
OS version: Windows 10 , 10.0, build: 16299 (x64)
Hardware: GA-970A-DS3, ECT, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD FX™-6100 Six-Core Processor
Logical processors: 6
Processor groups: 1
RAM: 8189 MB total



Reported CPU speed: 3322 MHz
Measured CPU speed: 1 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.

WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.



The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 293,124790
Average measured interrupt to process latency (µs): 8,615211

Highest measured interrupt to DPC latency (µs): 159,045628
Average measured interrupt to DPC latency (µs): 3,807770



Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 127,388922
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0,095906
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%) 0,135412

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



DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 324,143588
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 388.13 , NVIDIA Corporation

Highest reported total DPC routine time (%): 0,068015
Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.

Total time spent in DPCs (%) 0,214703

DPC count (execution time <250 µs): 209789
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 5
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µs): 0
DPC count (execution time >=4000 µs): 0



Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

Process with highest pagefault count: none

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



CPU 0 Interrupt cycle time (s): 2,783984
CPU 0 ISR highest execution time (µs): 127,388922
CPU 0 ISR total execution time (s): 0,511866
CPU 0 ISR count: 47713
CPU 0 DPC highest execution time (µs): 324,143588
CPU 0 DPC total execution time (s): 0,744379
CPU 0 DPC count: 200673

CPU 1 Interrupt cycle time (s): 0,654788
CPU 1 ISR highest execution time (µs): 12,290488
CPU 1 ISR total execution time (s): 0,000120
CPU 1 ISR count: 13
CPU 1 DPC highest execution time (µs): 69,701686
CPU 1 DPC total execution time (s): 0,011634
CPU 1 DPC count: 1699

CPU 2 Interrupt cycle time (s): 0,669964
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 55,73540
CPU 2 DPC total execution time (s): 0,017008
CPU 2 DPC count: 2438

CPU 3 Interrupt cycle time (s): 0,707660
CPU 3 ISR highest execution time (µs): 0,0
CPU 3 ISR total execution time (s): 0,0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 86,301023
CPU 3 DPC total execution time (s): 0,016151
CPU 3 DPC count: 2109

CPU 4 Interrupt cycle time (s): 0,688041
CPU 4 ISR highest execution time (µs): 0,0
CPU 4 ISR total execution time (s): 0,0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 81,612282
CPU 4 DPC total execution time (s): 0,013357
CPU 4 DPC count: 1672

CPU 5 Interrupt cycle time (s): 0,686118
CPU 5 ISR highest execution time (µs): 0,0
CPU 5 ISR total execution time (s): 0,0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 60,969296
CPU 5 DPC total execution time (s): 0,009254
CPU 5 DPC count: 1203

New Update: I solved the issue by increasing the used CPUs in the HALion player.
Only increasing the available RAM amount did not do the trick.

Thanks to everybody who spent some time for me! :slight_smile: