Latence Ableton Live 9 Lite
- 41 réponses
- 4 participants
- 868 vues
- 3 followers
mashmer
23
Nouvel·le AFfilié·e
Membre depuis 11 ans
Sujet de la discussion Posté le 14/09/2019 à 04:37:39Latence Ableton Live 9 Lite
Bonjour à tous, j'ai un sérieux problème avec Live car j'ai constament des bruits parasites (comme des craquements) lorsque j'essaye d'enregistrer ma guitare en utilisant Addictive drums2. J'ai essayé de règler la latence mais rien n'y fait, C'est désespérant car je ne sais plus comment faire si balancer mon pc à la poubelle ou le jeter par la fenêtre...
HELP!!!!!!
(ici le résumé de mon matos:
PC intelcore i3-2120 3.30ghz +8GB de RAM
windows 10 home 64bits
carte son focusrite scarlett 6i6
guitar rig 5
addictive drums 2
HELP!!!!!!
(ici le résumé de mon matos:
PC intelcore i3-2120 3.30ghz +8GB de RAM
windows 10 home 64bits
carte son focusrite scarlett 6i6
guitar rig 5
addictive drums 2
mashmer
23
Nouvel·le AFfilié·e
Membre depuis 11 ans
11 Posté le 19/09/2019 à 17:54:52
Bonjour, Dsy, il-y-at'il des controleurs ,qui en les désactivant dans le gestionnaire de périfériques feraient planter le PC? (type controleurs de la carte video etc...)
dsy
4313
Squatteur·euse d’AF
Membre depuis 22 ans
12 Posté le 19/09/2019 à 18:07:04
Oui tu peux casser ton Windows
mashmer
23
Nouvel·le AFfilié·e
Membre depuis 11 ans
13 Posté le 19/09/2019 à 19:47:07
Alors comment faire sans planter le pc???
dsy
4313
Squatteur·euse d’AF
Membre depuis 22 ans
14 Posté le 19/09/2019 à 20:02:23
ben désactiver que les cartes réseaux comment j'ai indiqué. Commence par la carte réseau ethernet puis tu testes le DPC. Et tu refais pareil pour le Wi-Fi si pas d'amélioration.
Ne touche pas au reste.
Ne touche pas au reste.
mashmer
23
Nouvel·le AFfilié·e
Membre depuis 11 ans
15 Posté le 20/09/2019 à 00:22:43
J'ai désactivé les cartes réseaux WAN et rien ne change à mon problème...Et apparement il n'y a pas de nouveaux drivers pour la carte video et le bios...
dsy
4313
Squatteur·euse d’AF
Membre depuis 22 ans
16 Posté le 20/09/2019 à 02:51:39
Est-ce que ndis.sys est la cause des DPC lorsque tu as les 2 cartes réseaux désactivées ?
mashmer
23
Nouvel·le AFfilié·e
Membre depuis 11 ans
17 Posté le 20/09/2019 à 15:49:24
Bonjour, après avoir désactivés les cartes réseaux, ndis.sys n'est plus la cause des DPC mais un pilote de NVIDIA : nvlddmkm.sys
voici le rapport de latencymon
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. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. 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:24:49 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: ANTHEUS
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: H61H2-LM3, MEDION
CPU: GenuineIntel Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz
Logical processors: 4
Processor groups: 1
RAM: 8155 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3293 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.
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 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): 1398,70
Average measured interrupt to process latency (µs): 7,340827
Highest measured interrupt to DPC latency (µs): 1361,10
Average measured interrupt to DPC latency (µs): 1,796050
_________________________________________________________________________________________________________
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): 676,935925
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,074431
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,086306
ISR count (execution time <250 µs): 277098
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 526
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): 1165,452171
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 390.77 , NVIDIA Corporation
Highest reported total DPC routine time (%): 0,082185
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,211374
DPC count (execution time <250 µs): 3713225
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 337
DPC count (execution time 1000-1999 µs): 4
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: avp.exe
Total number of hard pagefaults 42264
Hard pagefault count of hardest hit process: 8572
Number of processes hit: 135
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 45,714881
CPU 0 ISR highest execution time (µs): 676,935925
CPU 0 ISR total execution time (s): 5,139337
CPU 0 ISR count: 277574
CPU 0 DPC highest execution time (µs): 1165,452171
CPU 0 DPC total execution time (s): 11,182035
CPU 0 DPC count: 3613153
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 30,467402
CPU 1 ISR highest execution time (µs): 112,914667
CPU 1 ISR total execution time (s): 0,001093
CPU 1 ISR count: 50
CPU 1 DPC highest execution time (µs): 920,587914
CPU 1 DPC total execution time (s): 0,471060
CPU 1 DPC count: 36311
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 14,211411
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): 1039,865776
CPU 2 DPC total execution time (s): 0,501570
CPU 2 DPC count: 35448
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 17,812372
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): 884,741877
CPU 3 DPC total execution time (s): 0,434891
CPU 3 DPC count: 28654
_________________________________________________________________________________________________________
voici le rapport de latencymon
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. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. 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:24:49 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: ANTHEUS
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: H61H2-LM3, MEDION
CPU: GenuineIntel Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz
Logical processors: 4
Processor groups: 1
RAM: 8155 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3293 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.
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 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): 1398,70
Average measured interrupt to process latency (µs): 7,340827
Highest measured interrupt to DPC latency (µs): 1361,10
Average measured interrupt to DPC latency (µs): 1,796050
_________________________________________________________________________________________________________
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): 676,935925
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,074431
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,086306
ISR count (execution time <250 µs): 277098
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 526
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): 1165,452171
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 390.77 , NVIDIA Corporation
Highest reported total DPC routine time (%): 0,082185
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,211374
DPC count (execution time <250 µs): 3713225
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 337
DPC count (execution time 1000-1999 µs): 4
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: avp.exe
Total number of hard pagefaults 42264
Hard pagefault count of hardest hit process: 8572
Number of processes hit: 135
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 45,714881
CPU 0 ISR highest execution time (µs): 676,935925
CPU 0 ISR total execution time (s): 5,139337
CPU 0 ISR count: 277574
CPU 0 DPC highest execution time (µs): 1165,452171
CPU 0 DPC total execution time (s): 11,182035
CPU 0 DPC count: 3613153
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 30,467402
CPU 1 ISR highest execution time (µs): 112,914667
CPU 1 ISR total execution time (s): 0,001093
CPU 1 ISR count: 50
CPU 1 DPC highest execution time (µs): 920,587914
CPU 1 DPC total execution time (s): 0,471060
CPU 1 DPC count: 36311
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 14,211411
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): 1039,865776
CPU 2 DPC total execution time (s): 0,501570
CPU 2 DPC count: 35448
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 17,812372
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): 884,741877
CPU 3 DPC total execution time (s): 0,434891
CPU 3 DPC count: 28654
_________________________________________________________________________________________________________
dsy
4313
Squatteur·euse d’AF
Membre depuis 22 ans
18 Posté le 20/09/2019 à 16:54:39
On est passé de 73.414 msec à 1.165 msec pour le DPC, c'est plutôt pas mal.
Si tu regardes les DPC Count, c'est globalement mieux sans la carte réseau.
Donc je pense que la carte réseau est en grande partie responsable mais est-ce la carte ethernet ou Wi-Fi ? Il faudrait désactiver l'une ou l'autre.
Mais si tu me dis qu'au niveau son, cela ne change rien alors cela veut dire que le problème est ailleurs.
Je compare aussi les page faults, tu en as pas mal. Est-ce que tu peux désactiver ton anti-virus et faire un test ?
Si tu regardes les DPC Count, c'est globalement mieux sans la carte réseau.
Donc je pense que la carte réseau est en grande partie responsable mais est-ce la carte ethernet ou Wi-Fi ? Il faudrait désactiver l'une ou l'autre.
Mais si tu me dis qu'au niveau son, cela ne change rien alors cela veut dire que le problème est ailleurs.
Je compare aussi les page faults, tu en as pas mal. Est-ce que tu peux désactiver ton anti-virus et faire un test ?
mashmer
23
Nouvel·le AFfilié·e
Membre depuis 11 ans
19 Posté le 20/09/2019 à 18:27:55
J'ai désactivé mon antivirus, ainsi que le firewall Windows defender et les cartes réseaux et rien ne change...
voici le rapport de LatencyMon
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:03:25 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: ANTHEUS
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: H61H2-LM3, MEDION
CPU: GenuineIntel Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz
Logical processors: 4
Processor groups: 1
RAM: 8155 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3293 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.
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 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): 1198,10
Average measured interrupt to process latency (µs): 7,862116
Highest measured interrupt to DPC latency (µs): 1171,0
Average measured interrupt to DPC latency (µs): 2,028509
_________________________________________________________________________________________________________
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): 675,262375
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,108364
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,126887
ISR count (execution time <250 µs): 59694
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 152
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): 1166,148497
Driver with highest DPC routine execution time: Wdf01000.sys - Motor en tiempo de ejecución del marco de controlador en modo kernel, Microsoft Corporation
Highest reported total DPC routine time (%): 0,088876
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,266154
DPC count (execution time <250 µs): 526657
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 248
DPC count (execution time 1000-1999 µs): 5
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: avp.exe
Total number of hard pagefaults 2878
Hard pagefault count of hardest hit process: 925
Number of processes hit: 44
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 7,244337
CPU 0 ISR highest execution time (µs): 675,262375
CPU 0 ISR total execution time (s): 1,031002
CPU 0 ISR count: 59423
CPU 0 DPC highest execution time (µs): 1166,148497
CPU 0 DPC total execution time (s): 2,059837
CPU 0 DPC count: 517697
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 4,394348
CPU 1 ISR highest execution time (µs): 404,848770
CPU 1 ISR total execution time (s): 0,009553
CPU 1 ISR count: 423
CPU 1 DPC highest execution time (µs): 277,563620
CPU 1 DPC total execution time (s): 0,040985
CPU 1 DPC count: 3033
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 2,065299
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): 1096,983905
CPU 2 DPC total execution time (s): 0,039703
CPU 2 DPC count: 2907
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2,792452
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): 677,922867
CPU 3 DPC total execution time (s): 0,042108
CPU 3 DPC count: 3273
_________________________________________________________________________________________________________
voici le rapport de LatencyMon
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:03:25 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: ANTHEUS
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: H61H2-LM3, MEDION
CPU: GenuineIntel Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz
Logical processors: 4
Processor groups: 1
RAM: 8155 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3293 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.
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 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): 1198,10
Average measured interrupt to process latency (µs): 7,862116
Highest measured interrupt to DPC latency (µs): 1171,0
Average measured interrupt to DPC latency (µs): 2,028509
_________________________________________________________________________________________________________
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): 675,262375
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,108364
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,126887
ISR count (execution time <250 µs): 59694
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 152
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): 1166,148497
Driver with highest DPC routine execution time: Wdf01000.sys - Motor en tiempo de ejecución del marco de controlador en modo kernel, Microsoft Corporation
Highest reported total DPC routine time (%): 0,088876
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,266154
DPC count (execution time <250 µs): 526657
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 248
DPC count (execution time 1000-1999 µs): 5
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: avp.exe
Total number of hard pagefaults 2878
Hard pagefault count of hardest hit process: 925
Number of processes hit: 44
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 7,244337
CPU 0 ISR highest execution time (µs): 675,262375
CPU 0 ISR total execution time (s): 1,031002
CPU 0 ISR count: 59423
CPU 0 DPC highest execution time (µs): 1166,148497
CPU 0 DPC total execution time (s): 2,059837
CPU 0 DPC count: 517697
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 4,394348
CPU 1 ISR highest execution time (µs): 404,848770
CPU 1 ISR total execution time (s): 0,009553
CPU 1 ISR count: 423
CPU 1 DPC highest execution time (µs): 277,563620
CPU 1 DPC total execution time (s): 0,040985
CPU 1 DPC count: 3033
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 2,065299
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): 1096,983905
CPU 2 DPC total execution time (s): 0,039703
CPU 2 DPC count: 2907
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2,792452
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): 677,922867
CPU 3 DPC total execution time (s): 0,042108
CPU 3 DPC count: 3273
_________________________________________________________________________________________________________
dsy
4313
Squatteur·euse d’AF
Membre depuis 22 ans
20 Posté le 20/09/2019 à 18:56:35
Effectivement les page faults ont bcp diminués et les interruptions aussi. Pas sûr qu'on puisse faire mieux de ce côté là.
Addictive Drums 2 peut aussi fonctionner seul (sans séquenceur). Peux-tu vérifier qu'il fonctionne sans drop tout seul en utilisant le pilote ASIO de ta carte son ?
Addictive Drums 2 peut aussi fonctionner seul (sans séquenceur). Peux-tu vérifier qu'il fonctionne sans drop tout seul en utilisant le pilote ASIO de ta carte son ?
- < Liste des sujets
- Charte