I think I should be able to get more out of Cubase 8 with my spec. I also know I can get more out of it than with C8, as Cubase 7.5 performs better on it, and Sonar X3 even better still.
I don’t know what’s causing this, I just want it resolved so I can get on with music and work.
Your new spec is a fair game ahead of mine… I have the i7 4770 (non-K) on an Asus Z87-A
Yes, I have been using that but it’s not really helped so far in resolving the problem…
I’ve had different results… sometimes storport.sys and ndis.sys are highlighted as high DPC latency, but it is only sometimes.
Today, I ran latency test 3 times so far, and no high DPC latency was reported… I pasted the results below.
But the C8 problem is there all the time.
I use AVG but I completely uninstalled that and it made no difference. I’ve uninstalled the MIDI controller and that made no difference. Same with firewire card.
This is dominating my days now, it’s madness.
CONCLUSION
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:11:38 (h:mm:ss) on all processors.
\
SYSTEM INFORMATION
Computer name: DARRENBROCK-PC
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., Z87-A
CPU: GenuineIntel Intel(R) Core™ i7-4770 CPU @ 3.40GHz
Logical processors: 4
Processor groups: 1
RAM: 32191 MB total
\
CPU SPEED
Reported CPU speed: 340 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.
\
MEASURED INTERRUPT TO DPC LATENCIES
The interrupt to DPC latency reflects the measured interval in which a DPC could execute in response to a hardware request from the moment the interrupt service routine started execution.
Highest measured interrupt to DPC latency (µs): 48.789876
Average measured interrupt to DPC latency (µs): 1.649448
\
REPORTED ISRs
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): 11.195588
Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Highest reported total ISR routine time (%): 0.070254
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in ISRs (%) 0.070901
ISR count (execution time <250 µs): 651896
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
\
REPORTED DPCs
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): 104.260588
Driver with highest DPC routine execution time: ndis.sys - NDIS 6.20 driver, Microsoft Corporation
Highest reported total DPC routine time (%): 0.426423
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in DPCs (%) 0.442706
DPC count (execution time <250 µs): 1087357
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µs): 0
DPC count (execution time >=4000 µs): 0
\
REPORTED HARD PAGEFAULTS
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.
NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.
Process with highest pagefault count: explorer.exe
Total number of hard pagefaults 30
Hard pagefault count of hardest hit process: 23
Highest hard pagefault resolution time (µs): 196138.127059
Total time spent in hard pagefaults (%): 0.010806
Number of processes hit: 3
\
PER CPU DATA
CPU 0 Interrupt cycle time (s): 14.444593
CPU 0 ISR highest execution time (µs): 11.195588
CPU 0 ISR total execution time (s): 1.981885
CPU 0 ISR count: 651896
CPU 0 DPC highest execution time (µs): 76.255294
CPU 0 DPC total execution time (s): 12.230661
CPU 0 DPC count: 938202
CPU 1 Interrupt cycle time (s): 0.222928
CPU 1 ISR highest execution time (µs): 0.0
CPU 1 ISR total execution time (s): 0.0
CPU 1 ISR count: 0
CPU 1 DPC highest execution time (µs): 104.260588
CPU 1 DPC total execution time (s): 0.052185
CPU 1 DPC count: 47078
CPU 2 Interrupt cycle time (s): 0.179676
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.865882
CPU 2 DPC total execution time (s): 0.034850
CPU 2 DPC count: 33945
CPU 3 Interrupt cycle time (s): 0.201887
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): 102.719118
CPU 3 DPC total execution time (s): 0.057201
CPU 3 DPC count: 68132
Unfortunately I think everyone using Kontakt needs to post these issues on the Native Instrument forum. I too have this problem. If I freeze Kontakt the spiking and heavy CPU issue goes away. I am guessing that Kontakt does not like Hyperthreading. I am loath to disable it, as otherwise my computer is working really well. I don’t think that Native instruments will look at this issue unless enough users put their case.
I know I state Kontakt in the title, but I mentioned Kontakt and Halion Sonic as they are two I use a lot.
But actually, in my case, this problem occurs with any VST Instruments I use.
The meters in Kontakt don’t seem to indicate heavy load or usage. In fact, in the project I have in mind, there is only 1 instance of Studio Drummer.
Dman,
I was just going through your Latency Monitor report and the section about your CPU got my attention. Your CPU needs to have Speed Step turned off in your computer’s BIOS.
Also I’m guessing your cores are still ‘parked’, see here:
Disable CPU Core Parking Utility.
Hope this helps.
Hi, yes I should have mentioned that software reports that wrongly for some reason on some systems. I have checked this with other software.
SpeedStep has always been turned off, as are C states etc, and I did actually try the very app you mentioned a couple of weeks ago, but it made no difference, sadly.
Well, I had basically given up and was getting on with building my new machine and I’d go from there . . . but . .
For the heck of it I tried turning off Graphics Acceleration for Cubase 8 with the Registry hack detailed here:
I did it ONLY for Cubase 8 - no plugins.
It seems to have worked. No random spikes. Performance seems OK.
Hard to tell if it’s “back to normal” because it’s been a while since I’ve seen “normal”.
I have had this same setup (without the hack) through several versions of Cubase and have not had the issue before - so it IS 8.02 related.
Several people in that thread have asked/pointed out that GPU acceleration SHOULD make things better - freeing up CPU time for other things - seems that way to me, too.
I am certainly NOT a programmer but it seems there must be something odd about the way Cubase is handling graphics that makes this hack necessary - and I certainly hope they clear it up VERY soon.
But for now I’m a bit happier.
Hugh
Just wondering, which GPU are you using Hugh?
NVIDIA GeForce 9500 GT.
Not any kind of powerhouse card.
And I actually had not updated the driver in ages (like, a couple years).
I DID update the driver a couple days ago when I became aware of these issues and it didn’t solve anything.
But, somehow, GraphicsAcceleration = 0 did the trick.
Hugh
Another thing you might look at is the send/inserts you may be using in your project, a few instances of NI Replika or even a single instance of Molekular or similar plugins from other software houses can easily bring a finely tuned rig it its knees, especially when used with the latest high resource demanding multi sampled libraries in Kontakt though Steinberg do need to address the way Cubase uses resources…
This is interesting:
I was researching whether to use Win 7 or 8.1 (yes, I’m a slow adopter on my OS) on the new machine I’m building.
No way Win 10 yet.
Anyway - a lot of interesting stuff - much of it dated (back to the first release of 8) - but I ran across this:
Fabio mentions mostly GPU enhancements in 8.1.
So . . I’m wondering if the fact that I had to turn off Graphics Acceleration for Cubase to solve my spiking issues is because I’m still on Win 7 (latest) on my current machine.
Maybe others that the hack worked for are also on 7?
I guess it’s 8.1 for the new machine.
Hugh
I agree on this. Some plug-in are very demanding; not much point having them if you can’t use them, though.
The number of VSTi / VST instances I can use on my machine is significantly higher when using, for example, Sonar X3.
Didn’t Steinberg ‘invent’ the VST/VSTi?
I can even get comparable usage to X3 from the latest Studio One. I have X3 projects that I simply cannot do in Cubase because of this.
This is vital for instrumental work and tv/film scores when you work ITB. But I want and need to work with only one DAW for workflow and productivity. At the moment, the issues I am experiencing with Cubase are pushing me elsewhere.
Because of the interface and workflow, I want to use Cubase. But the fact is, no matter how good that interface and workflow is for me, it’s no use as a DAW if I can’t do the music projects with it.
So my tech support request from Microsoft came back, and suggested that I completely turn off/disable Windows Aero. … the very thing I need on for Cubase 8.
Still stuck with this problem…
And still stuck with this problem.
For info, I installed the latest Cubase 8 update. Unfortunately, that did not help with the problems I am experiencing.
However, having looked at the version history/update documentation, I could not see anything that would suggest the update would make any difference.
I really need to have a solution for this.
Another Latency Mon report…
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 that belong to a driver running in your system appear to be executing for too long. 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 2:20:12 (h:mm:ss) on all processors.
\
SYSTEM INFORMATION
Computer name: DARRENBROCK-PC
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., Z87-A
CPU: GenuineIntel Intel(R) Core™ i7-4770 CPU @ 3.40GHz
Logical processors: 4
Processor groups: 1
RAM: 32191 MB total
\
CPU SPEED
Reported CPU speed: 3464 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.
\
MEASURED INTERRUPT TO DPC LATENCIES
The interrupt to DPC latency reflects the measured interval in which a DPC could execute in response to a hardware request from the moment the interrupt service routine started execution.
Highest measured interrupt to DPC latency (µs): 555.424508
Average measured interrupt to DPC latency (µs): 1.861688
\
REPORTED ISRs
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): 13.067841
Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Highest reported total ISR routine time (%): 0.127758
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in ISRs (%) 0.128373
ISR count (execution time <250 µs): 13731026
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
\
REPORTED DPCs
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): 2336.451790
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Highest reported total DPC routine time (%): 0.531236
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in DPCs (%) 0.552239
DPC count (execution time <250 µs): 20021189
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 1
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µs): 1
DPC count (execution time >=4000 µs): 0
\
REPORTED HARD PAGEFAULTS
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.
NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.
Process with highest pagefault count: svchost.exe
Total number of hard pagefaults 14999
Hard pagefault count of hardest hit process: 14557
Highest hard pagefault resolution time (µs): 1727136.135104
Total time spent in hard pagefaults (%): 0.030461
Number of processes hit: 4
\
PER CPU DATA
CPU 0 Interrupt cycle time (s): 232.858757
CPU 0 ISR highest execution time (µs): 13.067841
CPU 0 ISR total execution time (s): 43.195951
CPU 0 ISR count: 13731026
CPU 0 DPC highest execution time (µs): 2336.451790
CPU 0 DPC total execution time (s): 184.524840
CPU 0 DPC count: 18312517
CPU 1 Interrupt cycle time (s): 1.351434
CPU 1 ISR highest execution time (µs): 0.0
CPU 1 ISR total execution time (s): 0.0
CPU 1 ISR count: 0
CPU 1 DPC highest execution time (µs): 75.334007
CPU 1 DPC total execution time (s): 0.323770
CPU 1 DPC count: 526721
CPU 2 Interrupt cycle time (s): 2.567274
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): 85.367206
CPU 2 DPC total execution time (s): 0.588607
CPU 2 DPC count: 762824
CPU 3 Interrupt cycle time (s): 1.815983
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): 51.950058
CPU 3 DPC total execution time (s): 0.384648
CPU 3 DPC count: 419129
