Latence Ableton Live 9 Lite
- 41 réponses
- 4 participants
- 870 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
21 Posté le 20/09/2019 à 21:11:29
En ayant désactivé les cartes réseaux,l'antivirus et le firewall de Windows, Addictive drums fonctionne correctement avec le driver Asio de ma carte son(par contre il ne fonctionne pas avec asioforall) il fonctionne également avec direct sound et windows audio.
(Le problème vient lorsque je veux graver)
Par contre en utilisant addictive drums via ableton, dans ces mêmes conditions, seul le son est correctement restitué avec MME/directX (asioforall ne donne aucun son comme dans le premier cas) mais si je veux utiliser guitar rig avec addictive drums, là c'est guitar rig qui plante, car la latence est bien trop grande.
(Le problème vient lorsque je veux graver)
Par contre en utilisant addictive drums via ableton, dans ces mêmes conditions, seul le son est correctement restitué avec MME/directX (asioforall ne donne aucun son comme dans le premier cas) mais si je veux utiliser guitar rig avec addictive drums, là c'est guitar rig qui plante, car la latence est bien trop grande.
[ Dernière édition du message le 20/09/2019 à 21:13:06 ]
dsy
4313
Squatteur·euse d’AF
Membre depuis 22 ans
22 Posté le 20/09/2019 à 23:37:49
Je suppose que Guitar Rig et Addidictive Drums fonctionnent bien en standalone. Seul le pilote ASIO de ta carte son Focusrite nous intéresse car c'est celui qui doit offrir la meilleure latence.
Peux-tu essayer avec Reaper plutôt que Live ? https://www.reaper.fm/download.php (Windows 64 bits)
Peux-tu essayer avec Reaper plutôt que Live ? https://www.reaper.fm/download.php (Windows 64 bits)
mashmer
23
Nouvel·le AFfilié·e
Membre depuis 11 ans
23 Posté le 21/09/2019 à 15:42:55
En ayant désactivé les cartes réseaux,l'antivirus et le firewall de Windows et en utilisant cette fois Reaper, le problème est toujours identique: addictive drums a des craquements 
dsy
4313
Squatteur·euse d’AF
Membre depuis 22 ans
24 Posté le 21/09/2019 à 17:20:31
Pour résumer :
- AD standalone : ok
- AD en VSTi : craquements
Peux-tu stp confirmer les conditions de test dans les 2 cas :
- pas d'autres VSTi ou VST dans Live ou Reaper.
- pas d'autres programmes
- même carte son : Focusrite
- même driver ASIO : Focusrite
- même paramètres ASIO
- AD standalone : ok
- AD en VSTi : craquements
Peux-tu stp confirmer les conditions de test dans les 2 cas :
- pas d'autres VSTi ou VST dans Live ou Reaper.
- pas d'autres programmes
- même carte son : Focusrite
- même driver ASIO : Focusrite
- même paramètres ASIO
mashmer
23
Nouvel·le AFfilié·e
Membre depuis 11 ans
25 Posté le 21/09/2019 à 19:09:38
Dans quels cas dois-je faire les tests? (Addictive drums seul et avec live?)
Dois-je désactiver l'antivirus, le firewall de windows et les cartes réseaux également?
Dois-je désactiver l'antivirus, le firewall de windows et les cartes réseaux également?
dsy
4313
Squatteur·euse d’AF
Membre depuis 22 ans
26 Posté le 21/09/2019 à 19:22:59
En fait il y a 2 tests :
- Reaper ou Live + AD 2
- AD 2 seul
Tu devrais désactiver l'antivirus et les cartes réseaux. Tu peux laisser le firewall mais il faut les autres conditions :
- pas d'autres VSTi ou VST dans Live ou Reaper.
- pas d'autres programmes sauf ceux qui sont vitaux
- même driver ASIO : Focusrite
- même paramètres ASIO
- même conditions dans AD 2 : sample, pattern, etc
- Reaper ou Live + AD 2
- AD 2 seul
Tu devrais désactiver l'antivirus et les cartes réseaux. Tu peux laisser le firewall mais il faut les autres conditions :
- pas d'autres VSTi ou VST dans Live ou Reaper.
- pas d'autres programmes sauf ceux qui sont vitaux
- même driver ASIO : Focusrite
- même paramètres ASIO
- même conditions dans AD 2 : sample, pattern, etc
Anonyme
292
27 Posté le 21/09/2019 à 20:02:59
Salut, je n'ai pas tout lu, mais si ça n'a pas été fait encore, il faut aller faire un tour dans les paramètres d'alimentation de Windows: c'est souvent une des causes de ce genre de problèmes.
- choisis un profil d'alimentation type 'performances maximales'
- Il faut que la fréquence d'horloge mini et maxi du processeur soit réglée sur 100%
- desactive la suspension selective USB
- désactive la gestion d'alimentation du bus. PCI
- arrêt du disque dur sur '0' (jamais)
- choisis un profil d'alimentation type 'performances maximales'
- Il faut que la fréquence d'horloge mini et maxi du processeur soit réglée sur 100%
- desactive la suspension selective USB
- désactive la gestion d'alimentation du bus. PCI
- arrêt du disque dur sur '0' (jamais)
mashmer
23
Nouvel·le AFfilié·e
Membre depuis 11 ans
28 Posté le 21/09/2019 à 21:07:28
Les résultats en ayant désactivé les cartes réseaux et l'antivirus, sont tous négatifs : dans tous les cas en utilisant le driver Asio de ma carte son provoquent tous des craquements
Voici les détails de LatencyMon
1/cas Live+AD
________________________________________________________________________________________________________
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 0:00:34 (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): 5056,20
Average measured interrupt to process latency (µs): 11,467063
Highest measured interrupt to DPC latency (µs): 4985,30
Average measured interrupt to DPC latency (µs): 4,665682
_________________________________________________________________________________________________________
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): 603,023990
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,156746
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,187058
ISR count (execution time <250 µs): 15971
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 31
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): 4613,170665
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,392824
Driver with highest DPC total execution time: Wdf01000.sys - Motor en tiempo de ejecución del marco de controlador en modo kernel, Microsoft Corporation
Total time spent in DPCs (%) 0,648142
DPC count (execution time <250 µs): 74597
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 297
DPC count (execution time 1000-1999 µs): 47
DPC count (execution time 2000-3999 µs): 16
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: msmpeng.exe
Total number of hard pagefaults 69
Hard pagefault count of hardest hit process: 33
Number of processes hit: 9
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 1,909754
CPU 0 ISR highest execution time (µs): 603,023990
CPU 0 ISR total execution time (s): 0,242744
CPU 0 ISR count: 15490
CPU 0 DPC highest execution time (µs): 4613,170665
CPU 0 DPC total execution time (s): 0,843171
CPU 0 DPC count: 71387
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,610449
CPU 1 ISR highest execution time (µs): 319,342241
CPU 1 ISR total execution time (s): 0,011862
CPU 1 ISR count: 505
CPU 1 DPC highest execution time (µs): 250,341026
CPU 1 DPC total execution time (s): 0,012402
CPU 1 DPC count: 521
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,919634
CPU 2 ISR highest execution time (µs): 4,057698
CPU 2 ISR total execution time (s): 0,000024
CPU 2 ISR count: 7
CPU 2 DPC highest execution time (µs): 88,988764
CPU 2 DPC total execution time (s): 0,012292
CPU 2 DPC count: 1963
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,423755
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): 155,053750
CPU 3 DPC total execution time (s): 0,014412
CPU 3 DPC count: 1090
Voici les détails de LatencyMon
1/cas Live+AD
________________________________________________________________________________________________________
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 0:00:34 (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): 5056,20
Average measured interrupt to process latency (µs): 11,467063
Highest measured interrupt to DPC latency (µs): 4985,30
Average measured interrupt to DPC latency (µs): 4,665682
_________________________________________________________________________________________________________
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): 603,023990
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,156746
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,187058
ISR count (execution time <250 µs): 15971
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 31
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): 4613,170665
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,392824
Driver with highest DPC total execution time: Wdf01000.sys - Motor en tiempo de ejecución del marco de controlador en modo kernel, Microsoft Corporation
Total time spent in DPCs (%) 0,648142
DPC count (execution time <250 µs): 74597
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 297
DPC count (execution time 1000-1999 µs): 47
DPC count (execution time 2000-3999 µs): 16
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: msmpeng.exe
Total number of hard pagefaults 69
Hard pagefault count of hardest hit process: 33
Number of processes hit: 9
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 1,909754
CPU 0 ISR highest execution time (µs): 603,023990
CPU 0 ISR total execution time (s): 0,242744
CPU 0 ISR count: 15490
CPU 0 DPC highest execution time (µs): 4613,170665
CPU 0 DPC total execution time (s): 0,843171
CPU 0 DPC count: 71387
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,610449
CPU 1 ISR highest execution time (µs): 319,342241
CPU 1 ISR total execution time (s): 0,011862
CPU 1 ISR count: 505
CPU 1 DPC highest execution time (µs): 250,341026
CPU 1 DPC total execution time (s): 0,012402
CPU 1 DPC count: 521
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,919634
CPU 2 ISR highest execution time (µs): 4,057698
CPU 2 ISR total execution time (s): 0,000024
CPU 2 ISR count: 7
CPU 2 DPC highest execution time (µs): 88,988764
CPU 2 DPC total execution time (s): 0,012292
CPU 2 DPC count: 1963
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,423755
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): 155,053750
CPU 3 DPC total execution time (s): 0,014412
CPU 3 DPC count: 1090
[ Dernière édition du message le 21/09/2019 à 21:11:34 ]
mashmer
23
Nouvel·le AFfilié·e
Membre depuis 11 ans
29 Posté le 21/09/2019 à 21:08:14
2 cas/Reaper+AD
Test Reaper+ AD >rendu avec craquements
_________________________________________________________________________________________________________
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 0:00:34 (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): 4295,90
Average measured interrupt to process latency (µs): 12,777795
Highest measured interrupt to DPC latency (µs): 4254,50
Average measured interrupt to DPC latency (µs): 4,753664
_________________________________________________________________________________________________________
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): 443,721227
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,092533
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,113664
ISR count (execution time <250 µs): 8886
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 31
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): 4369,974795
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,494854
Driver with highest DPC total execution time: Wdf01000.sys - Motor en tiempo de ejecución del marco de controlador en modo kernel, Microsoft Corporation
Total time spent in DPCs (%) 0,736578
DPC count (execution time <250 µs): 76617
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 664
DPC count (execution time 1000-1999 µs): 53
DPC count (execution time 2000-3999 µs): 17
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: runtimebroker.exe
Total number of hard pagefaults 1893
Hard pagefault count of hardest hit process: 1020
Number of processes hit: 9
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 1,803570
CPU 0 ISR highest execution time (µs): 443,721227
CPU 0 ISR total execution time (s): 0,140821
CPU 0 ISR count: 8414
CPU 0 DPC highest execution time (µs): 4369,974795
CPU 0 DPC total execution time (s): 0,940986
CPU 0 DPC count: 71548
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,554230
CPU 1 ISR highest execution time (µs): 368,126025
CPU 1 ISR total execution time (s): 0,013826
CPU 1 ISR count: 501
CPU 1 DPC highest execution time (µs): 418,001822
CPU 1 DPC total execution time (s): 0,017077
CPU 1 DPC count: 831
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 1,091773
CPU 2 ISR highest execution time (µs): 4,532038
CPU 2 ISR total execution time (s): 0,000008
CPU 2 ISR count: 2
CPU 2 DPC highest execution time (µs): 197,012754
CPU 2 DPC total execution time (s): 0,024806
CPU 2 DPC count: 3544
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,513252
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): 78,782265
CPU 3 DPC total execution time (s): 0,019349
CPU 3 DPC count: 1430
Test Reaper+ AD >rendu avec craquements
_________________________________________________________________________________________________________
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 0:00:34 (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): 4295,90
Average measured interrupt to process latency (µs): 12,777795
Highest measured interrupt to DPC latency (µs): 4254,50
Average measured interrupt to DPC latency (µs): 4,753664
_________________________________________________________________________________________________________
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): 443,721227
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,092533
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,113664
ISR count (execution time <250 µs): 8886
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 31
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): 4369,974795
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,494854
Driver with highest DPC total execution time: Wdf01000.sys - Motor en tiempo de ejecución del marco de controlador en modo kernel, Microsoft Corporation
Total time spent in DPCs (%) 0,736578
DPC count (execution time <250 µs): 76617
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 664
DPC count (execution time 1000-1999 µs): 53
DPC count (execution time 2000-3999 µs): 17
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: runtimebroker.exe
Total number of hard pagefaults 1893
Hard pagefault count of hardest hit process: 1020
Number of processes hit: 9
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 1,803570
CPU 0 ISR highest execution time (µs): 443,721227
CPU 0 ISR total execution time (s): 0,140821
CPU 0 ISR count: 8414
CPU 0 DPC highest execution time (µs): 4369,974795
CPU 0 DPC total execution time (s): 0,940986
CPU 0 DPC count: 71548
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,554230
CPU 1 ISR highest execution time (µs): 368,126025
CPU 1 ISR total execution time (s): 0,013826
CPU 1 ISR count: 501
CPU 1 DPC highest execution time (µs): 418,001822
CPU 1 DPC total execution time (s): 0,017077
CPU 1 DPC count: 831
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 1,091773
CPU 2 ISR highest execution time (µs): 4,532038
CPU 2 ISR total execution time (s): 0,000008
CPU 2 ISR count: 2
CPU 2 DPC highest execution time (µs): 197,012754
CPU 2 DPC total execution time (s): 0,024806
CPU 2 DPC count: 3544
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,513252
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): 78,782265
CPU 3 DPC total execution time (s): 0,019349
CPU 3 DPC count: 1430
mashmer
23
Nouvel·le AFfilié·e
Membre depuis 11 ans
30 Posté le 21/09/2019 à 21:08:59
3/ cas AD seul toujours les mêmes craquements
_______________________________________________________________________________________________________
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 0:00:34 (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): 4310,60
Average measured interrupt to process latency (µs): 10,590790
Highest measured interrupt to DPC latency (µs): 4225,30
Average measured interrupt to DPC latency (µs): 3,527526
_________________________________________________________________________________________________________
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): 436,936836
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,147304
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,175325
ISR count (execution time <250 µs): 14888
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 21
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): 4609,507744
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,493061
Driver with highest DPC total execution time: Wdf01000.sys - Motor en tiempo de ejecución del marco de controlador en modo kernel, Microsoft Corporation
Total time spent in DPCs (%) 0,878093
DPC count (execution time <250 µs): 97556
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 810
DPC count (execution time 1000-1999 µs): 34
DPC count (execution time 2000-3999 µs): 11
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: msmpeng.exe
Total number of hard pagefaults 711
Hard pagefault count of hardest hit process: 609
Number of processes hit: 19
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 2,424805
CPU 0 ISR highest execution time (µs): 436,936836
CPU 0 ISR total execution time (s): 0,217696
CPU 0 ISR count: 13957
CPU 0 DPC highest execution time (µs): 4609,507744
CPU 0 DPC total execution time (s): 1,096926
CPU 0 DPC count: 91664
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,483584
CPU 1 ISR highest execution time (µs): 271,560887
CPU 1 ISR total execution time (s): 0,020963
CPU 1 ISR count: 952
CPU 1 DPC highest execution time (µs): 203,842393
CPU 1 DPC total execution time (s): 0,042843
CPU 1 DPC count: 2702
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,359318
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): 91,614333
CPU 2 DPC total execution time (s): 0,012104
CPU 2 DPC count: 1009
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,438872
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): 347,562101
CPU 3 DPC total execution time (s): 0,043423
CPU 3 DPC count: 3038
_________________________________________________________________________________________________________
_______________________________________________________________________________________________________
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 0:00:34 (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): 4310,60
Average measured interrupt to process latency (µs): 10,590790
Highest measured interrupt to DPC latency (µs): 4225,30
Average measured interrupt to DPC latency (µs): 3,527526
_________________________________________________________________________________________________________
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): 436,936836
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,147304
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,175325
ISR count (execution time <250 µs): 14888
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 21
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): 4609,507744
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,493061
Driver with highest DPC total execution time: Wdf01000.sys - Motor en tiempo de ejecución del marco de controlador en modo kernel, Microsoft Corporation
Total time spent in DPCs (%) 0,878093
DPC count (execution time <250 µs): 97556
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 810
DPC count (execution time 1000-1999 µs): 34
DPC count (execution time 2000-3999 µs): 11
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: msmpeng.exe
Total number of hard pagefaults 711
Hard pagefault count of hardest hit process: 609
Number of processes hit: 19
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 2,424805
CPU 0 ISR highest execution time (µs): 436,936836
CPU 0 ISR total execution time (s): 0,217696
CPU 0 ISR count: 13957
CPU 0 DPC highest execution time (µs): 4609,507744
CPU 0 DPC total execution time (s): 1,096926
CPU 0 DPC count: 91664
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,483584
CPU 1 ISR highest execution time (µs): 271,560887
CPU 1 ISR total execution time (s): 0,020963
CPU 1 ISR count: 952
CPU 1 DPC highest execution time (µs): 203,842393
CPU 1 DPC total execution time (s): 0,042843
CPU 1 DPC count: 2702
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,359318
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): 91,614333
CPU 2 DPC total execution time (s): 0,012104
CPU 2 DPC count: 1009
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,438872
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): 347,562101
CPU 3 DPC total execution time (s): 0,043423
CPU 3 DPC count: 3038
_________________________________________________________________________________________________________
- < Liste des sujets
- Charte