Advice need - interface audio for weak CPU

[Jaworrr]

Hi everyone, I need some advice.
Which audio interface get to avoid latency in my case.

DAW is Reaper.
I'm using Neural DSP vst like John Petrucci and Rabea Massaad.
My hardware: CPU i5-8350U (8x1,7Ghz - that is the problem, single core is weak), SSD, 16GB RAM.

I tried two interfaces: Focusrite Scarlett 2i2 and UAD VOLT2. Both gives me cracling when keeping bufor 'low' (128) and quite long latency like 20ms.

I thought about get UA Apollo Twin because it has CPU for VST, but only for AU VST.
So my eyes focused on RME Babyface because of great drivers. But I'm not sure is that enaught to resolve latency and cracling problem.

What do you guys think?
Thanks from the mountain.

[resistorman]

You might consider upgrading your computer

[James Perrett]

If anything will do it, RME will. I have an older computer (2nd gen i7) and the Digiface USB is happy at 64 samples which is far better than other interfaces that I've used with it. I can also use the RME with Wifi switched on whereas I always turn Wifi off if I'm doing serious recording with other interfaces.

(Though to be on the absolute safe side I do increase the buffer size and turn Wifi off when using the RME for serious work - I just don't want to run any risk of missing anything).

[Wonks]

I'll assume this is a Win laptop.

Have you tried running LatencyMon to see if there are any background processes that are hogging the CPU and causing the dropouts? https://www.resplendence.com/latencymon

Is any power saving scheme set to full performance/no power saving?

Has all the manufacturer's bloatware utilities been removed from the laptop?

What's in your startup program list?

Have you got more than one anti-virus program running?

Can you turn off the wi-fi when recording?

[MarkOne]

I’ve been out of PC land for everything music related for 15 years, so I’m out of touch. When I was running cubase on PC it was on a much lower spec machine, so good performance on your CPU should be possible.

Presumably Reaper requires an ASIO driver to talk to the interface. So are you using the latest ASIO driver for the audio interface?

From memory, trying to run the native windows driver means huge latency.

But this might be outdated knowledge on my part.

[James Perrett]

Presumably Reaper requires an ASIO driver to talk to the interface. So are you using the latest ASIO driver for the audio interface?

Yes, check that you are using the ASIO driver model rather than the standard Windows Drivers. Reaper is very versatile when it comes to interfacing with other hardware and software but that also means that it is easy to choose the wrong interface model.

[Jaworrr]

Guys, you rules.

@Jame Perrett
Digiface USB. I don't see if it has guitar jack input. Looks better than RME Babyface because of half it price but what I found out it is not typical audio interface.
Drivers. I was using dedicated by manufacurer ASIO drivers ore some recommended one.

@Wonks, lot of areas, I have to quote you;
Have you tried running LatencyMon to see if there are any background processes that are hogging the CPU and causing the dropouts? https://www.resplendence.com/latencymon
-> I didn't know this software before, I have to try.

Is any power saving scheme set to full performance/no power saving?
-> BIOS set to full performacje. Windows in efficiency mode.

Has all the manufacturer's bloatware utilities been removed from the laptop?
->I don't think so, performance monitor shows cpu usage near 0% almost all time. Even browser was keeping closed.

What's in your startup program list?
->Quite short list, but I just realize that 4 of this apps is related with sound.
BSDECK, Wavessvc64, RAVBg64, RtkNGIU64. That comes from past when I was using diffrent apps for some audio hardware. I gues I have to uninstall what is not unneserssary.

Have you got more than one anti-virus program running?
Just one anty-virus.

Can you turn off the wi-fi when recording?
I didn't know that has a matter.

@MarkOne. Good shot but ASIO drivers was fine I think.

So it looks like the i5 has chance to works for me. Now I have to try with uninstall some unnecessary audio drivers, turn off wifi, check all with latencymon. But first of all... I have to buy an interface again, because I already send back those two I had.

[James Perrett]

@Jame Perrett
Digiface USB. I don't see if it has guitar jack input. Looks better than RME Babyface because of half it price but what I found out it is not typical audio interface.
Drivers. I was using dedicated by manufacurer ASIO drivers ore some recommended one.

No, the Digiface USB doesn't have any analogue inputs but all the RME range use similar drivers so I was using it as a known reference point. The Babyface would probably be the best for you although RME prices have increased quite a bit recently.

[ef37a]

I am in total agreement with Wonks, that i5 machine should be easily powerful enough.

I have just done a quick test with my MOTU M4 plugged into my venerable HP laptop (i3 307M 2.4G). It ran a two track clip perfectly with a 64 sample buffer and I was staggered that it was also glitch free at 32 samples. Not until I dropped to 16 did the audio start to break up. At 64 samples Task Manager showed a total CPU hit of an average of 25%.

That was on Samplitude ProX 6 and that is not as CPU efficient as Reaper. (but I's used to it!)

For several years I ran the HP with a Native Instruments KA6 and never had any latency concerns at all.

Something in that laptop is messing with you. (forgot. HP is Win 7 Home)

Dave.

[Drew Stephenson]

There's a big difference between playing back a 2-track clip and running a VSTi though Dave, especially if it's part of a larger project.

[ajay_m]

On a very old surface 3 pro with a core i5 processor I could certainly play vsts around 6ms latency with a Scarlett 6i6 but that does depend on the vst and where kontakt is the vst, some third party libraries with extensive scripting could be problematic like embertones string libraries. They need a better CPU to be playable at lower latency.

[ef37a]

There's a big difference between playing back a 2-track clip and running a VSTi though Dave, especially if it's part of a larger project.

I do understand that Drew but that was all I had handy! In the past I have run the demo track that comes with Pro X and that is a dozen or more tracks with MIDI parts in it. As I said, I have run the HP with the KA6 and done tests with an Evo keyboard controller, seemed pretty bloody fast to me!

MOTU have always had a reputation for great drivers and very low latency, second only perhaps to RME? If OP has bother with an M2/M4 it is DEFINITELY his PC!

But in any case Drew, this question has come up before, years ago when an i5 processor was just an idle dream and peeps got by?

Dave.

[Drew Stephenson]

But in any case Drew, this question has come up before, years ago when an i5 processor was just an idle dream and peeps got by?

Dave.

True, but sample libraries and virtual instruments have got larger and more complex.
In my case I've got an i7 desktop but as soon as I get more than a couple of dozen tracks up and running I can't get anything close to playable latency. I just turn off the input monitoring and take one ear-cup off, and that's not even recording a VSTi track.

[ef37a]

But in any case Drew, this question has come up before, years ago when an i5 processor was just an idle dream and peeps got by?

Dave.

True, but sample libraries and virtual instruments have got larger and more complex.
In my case I've got an i7 desktop but as soon as I get more than a couple of dozen tracks up and running I can't get anything close to playable latency. I just turn off the input monitoring and take one ear-cup off, and that's not even recording a VSTi track.

Maybe your computer needs a seeing to as well Drew?

Dave.

[Drew Stephenson]

Probably, it's never been the same since I had to reload it to factory settings after the W11 install corrupted. Unfortunately at that point I lost the stripped back settings that it had when Scan delivered it. My interface is probably getting on for 15 years old now as well which probably doesn't help.

[ef37a]

Probably, it's never been the same since I had to reload it to factory settings after the W11 install corrupted. Unfortunately at that point I lost the stripped back settings that it had when Scan delivered it. My interface is probably getting on for 15 years old now as well which probably doesn't help.

Sorry if I hit a nerve there Drew! My conclusions go back to the ever so missed "PC Notes" by Martin Walker. He gave very solid, sensible advice on optimizing Windows computers and when the notes stopped (*&&^% them as did it) computers were nowhere near as powerful as they are now pound for pound (that's £4£ not mass!) . Even so people were running scores of tracks and VSTis.

Dave.

[Jaworrr]

Ok, so i just get MOTU M4 (1/4 RME Babyface price) and made some tests.

Before unit was connection, everything not needed was uninstalled from laptop.
I ensure that things like C-states, SpeedStep, Type-C connector power, Shift technology everything what I found is set for maximum efficiency. So bios and windows, let say, are in performance mode.
Wifi OFF.
Motu Drivers installed and configured in Reaper.
M4 connected via usb C (laptop->M4)

Sample Rate 48000Hz
Use lowest latency safety offset (v)
Bufer:
64 ~1.8/4.2ms (6ms total)
128 ~ 3.2/6.8ms (10ms total) - description below is via this setting.
256 ~ 5.8/9.5 (15.5 total)

I'm not sure if it is ok because from time to time there are some pops and scratches. Depends on track and effects engadged in song. When few fx turn on, 9 tracks, recording is not possible. CPU rich 80% (Reaper takes 60%) then, sound is one big artefact. I have to turn the fx-s off.
When just 2 tracks goes like drums + guitar recording, CPU at 20%, then recording is possible and sounds rather good.
I have to do more tests, and possibly realize when recording, most fx must be turn off.

Now, LatencyMon. It shows conslusion like below. Some crazy results I don't understand. The biggest problem can be this service ACPI.sys - Sterownik ACPI dla systemu NT, Microsoft Corporation.

If anyone can try to judge if I could do something more, let me know plese.

_________________________________________________________________________________________________________
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:28:24 (h:mm:ss) on all processors.

_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: NBGJAWOREK
OS version: Windows 11, 10.0, version 2009, build: 22621 (x64)
Hardware: Latitude 5490, Dell Inc.
BIOS: 1.27.1
CPU: GenuineIntel Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz
Logical processors: 8
Processor groups: 1
Processor group size: 8
RAM: 16242 MB total

_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 1696 MHz
Reported CPU speed (registry): 1896 MHz

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 INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
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): 12058,90
Average measured interrupt to process latency (µs): 8,225787

Highest measured interrupt to DPC latency (µs): 12047,30
Average measured interrupt to DPC latency (µs): 2,524274

_________________________________________________________________________________________________________
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): 394,435127
Driver with highest ISR routine execution time: ACPI.sys - Sterownik ACPI dla systemu NT, Microsoft Corporation

Highest reported total ISR routine time (%): 0,015099
Driver with highest ISR total time: ACPI.sys - Sterownik ACPI dla systemu NT, Microsoft Corporation

Total time spent in ISRs (%) 0,015148

ISR count (execution time <250 µs): 159050
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 2
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µ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): 11942,718882
Driver with highest DPC routine execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.

Highest reported total DPC routine time (%): 0,030361
Driver with highest DPC total execution time: ACPI.sys - Sterownik ACPI dla systemu NT, Microsoft Corporation

Total time spent in DPCs (%) 0,108662

DPC count (execution time <250 µs): 8618786
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 23595
DPC count (execution time 1000-2000 µs): 683
DPC count (execution time 2000-4000 µs): 32
DPC count (execution time >=4000 µs): 3

_________________________________________________________________________________________________________
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: system

Total number of hard pagefaults 133634
Hard pagefault count of hardest hit process: 39894
Number of processes hit: 125

_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 197,353681
CPU 0 ISR highest execution time (µs): 394,435127
CPU 0 ISR total execution time (s): 10,791503
CPU 0 ISR count: 159052
CPU 0 DPC highest execution time (µs): 11942,718882
CPU 0 DPC total execution time (s): 59,790064
CPU 0 DPC count: 7088569
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 27,128244
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): 3499,915612
CPU 1 DPC total execution time (s): 1,261686
CPU 1 DPC count: 141613
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 33,344828
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): 3132,646624
CPU 2 DPC total execution time (s): 2,808152
CPU 2 DPC count: 274571
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 27,085398
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): 3339,212553
CPU 3 DPC total execution time (s): 1,798526
CPU 3 DPC count: 169061
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 40,620658
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): 2246,84230
CPU 4 DPC total execution time (s): 5,080793
CPU 4 DPC count: 402039
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 25,983243
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): 3026,211498
CPU 5 DPC total execution time (s): 1,448350
CPU 5 DPC count: 141809
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 37,142275
CPU 6 ISR highest execution time (µs): 0,0
CPU 6 ISR total execution time (s): 0,0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 3007,272152
CPU 6 DPC total execution time (s): 3,639268
CPU 6 DPC count: 285882
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 26,790210
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 4458,357595
CPU 7 DPC total execution time (s): 1,582532
CPU 7 DPC count: 139555
_________________________________________________________________________________________________________

[Jimmy B]

This is a good set of data to look at. I have one question:
I see that you ran this for 2 hours and 28 minutes. That seems a very long time. Did you have Reaper or other software running at the same time? The FAQ suggest that you shouldn't, as LatencyMon creates a simulated audio load by itself. I just tried this with my laptop,and if I had Reaper playing some tracks I got similar results to what you have reported. If Reaper was stopped, all was reported as fine.

[Jaworrr]

I run LatencyMon and forgot to turn it off when going for shopping. That's why test takes that long period of time
Reaper and other application was off.

[ajay_m]

You don't want to see spikes over 1000us (1ms) no matter how long you run the test. Disable WiFi and network adaptor and retest as a starting point. If you have a display adaptor that isn't just a integrated adaptor, eg a GPU, boot the system into safe mode and retest. This will eliminate the usual suspects which are in particular badly written WiFi drivers where the 1 min scan for channels that automatically occurs causes a dpc spike or optimisations in some video drivers that can also cause issues. Then let us know what you find.

[merlyn]

... I'm using Neural DSP vst like John Petrucci and Rabea Massaad. ...

It's possible that that plugin is too heavy duty for your processor to run at a low latency, and no audio interface is going to fix that.

If you look in Task Manager you can see the CPU usage. If the CPU is at 100% that is what is causing the crackling.

For playing live through the computer I would consider a 128 sample buffer the absolute maximum. There's a big difference between running a DAW with a few light plugins at a generous buffer size, and trying to get low latency with (what may be) a heavy duty plugin.

[Drew Stephenson]

This thread is enlightening. I can't even get a project to play back without pops and crackles at less than 512 samples, let alone trying to record.
Time to run that there latency monitor and see what it throws up.

[Drew Stephenson]

Time to run that there latency monitor and see what it throws up.

Well, nothing of concern showing up there.

[Wonks]

Drew, I'd check your interface to see if you've dropped any Rice Krispies into it.

[Jaworrr]

@merlyn those VST are not heavy, in my opinion. Reaper is showing cpu meter in corner when VST in edit mode. Witch both of them shows about 7%.

@ajay_m
Wifi - disabled.
All network adapter - disabled.
Display adapter - only integtrated GPU. (I try to run LatenycMon in safe mode as well, but then system inform that the driver for LatencyMon was not loaded because of safe mode so test in this enviroment wasn't possible.)

I have to admin that I have BitLocker installed od laptop. I know it may cause same system slowness, it doesn't speed up computer for sure, but to we see it in the LatencyMon logs?

Test on regular WIN11 logon:
________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. 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 0:10:10 (h:mm:ss) on all processors.

_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: NBGJAWOREK
OS version: Windows 11, 10.0, version 2009, build: 22621 (x64)
Hardware: Latitude 5490, Dell Inc.
BIOS: 1.27.1
CPU: GenuineIntel Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz
Logical processors: 8
Processor groups: 1
Processor group size: 8
RAM: 16242 MB total

_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 1896 MHz
Reported CPU speed (registry): 1896 MHz

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 INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
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): 1128,50
Average measured interrupt to process latency (µs): 8,258469

Highest measured interrupt to DPC latency (µs): 1118,70
Average measured interrupt to DPC latency (µs): 2,313912

_________________________________________________________________________________________________________
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): 146,020570
Driver with highest ISR routine execution time: ACPI.sys - Sterownik ACPI dla systemu NT, Microsoft Corporation

Highest reported total ISR routine time (%): 0,019182
Driver with highest ISR total time: ACPI.sys - Sterownik ACPI dla systemu NT, Microsoft Corporation

Total time spent in ISRs (%) 0,019183

ISR count (execution time <250 µs): 12592
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 0
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µ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): 1294,177215
Driver with highest DPC routine execution time: ACPI.sys - Sterownik ACPI dla systemu NT, Microsoft Corporation

Highest reported total DPC routine time (%): 0,038150
Driver with highest DPC total execution time: ACPI.sys - Sterownik ACPI dla systemu NT, Microsoft Corporation

Total time spent in DPCs (%) 0,125715

DPC count (execution time <250 µs): 719087
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 2209
DPC count (execution time 1000-2000 µs): 66
DPC count (execution time 2000-4000 µ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: system

Total number of hard pagefaults 23571
Hard pagefault count of hardest hit process: 4916
Number of processes hit: 47

_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 13,404365
CPU 0 ISR highest execution time (µs): 146,020570
CPU 0 ISR total execution time (s): 0,936919
CPU 0 ISR count: 12592
CPU 0 DPC highest execution time (µs): 1294,177215
CPU 0 DPC total execution time (s): 4,333587
CPU 0 DPC count: 424640
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 1,669621
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): 181,694093
CPU 1 DPC total execution time (s): 0,047468
CPU 1 DPC count: 6436
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 2,178760
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): 158,563819
CPU 2 DPC total execution time (s): 0,230942
CPU 2 DPC count: 31373
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 1,650076
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): 108,165612
CPU 3 DPC total execution time (s): 0,055132
CPU 3 DPC count: 7255
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 2,500924
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): 493,054325
CPU 4 DPC total execution time (s): 0,251458
CPU 4 DPC count: 26540
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 2,446085
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): 87,926160
CPU 5 DPC total execution time (s): 0,461384
CPU 5 DPC count: 96863
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 3,142867
CPU 6 ISR highest execution time (µs): 0,0
CPU 6 ISR total execution time (s): 0,0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 89,723101
CPU 6 DPC total execution time (s): 0,644896
CPU 6 DPC count: 118241
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 1,786472
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 184,232068
CPU 7 DPC total execution time (s): 0,115047
CPU 7 DPC count: 10014
_________________________________________________________________________________________________________