Sujet Latence Ableton Live 9 Lite
- 41 réponses
- 4 participants
- 854 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
dsy
4313
Squatteur·euse d’AF
Membre depuis 22 ans
31 Posté le 22/09/2019 à 02:11:34
Donc ni les logiciels utilisés ni les problèmes de DPC et d'interruptions en général ne sont pas la cause principale des craquements.
r95 a raison, nous n'avons pas regardé les options de gestion d'énergie.
r95 a raison, nous n'avons pas regardé les options de gestion d'énergie.
Citation de r95 :
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)
mashmer
23
Nouvel·le AFfilié·e
Membre depuis 11 ans
32 Posté le 22/09/2019 à 16:18:19
Bonjour, bien qu'ayant suivi vos derniers conseils j'ai toujours ces craquements...
voici les test de LatencyMon
1/test Live+ AD
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:00:48 (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): 1046,30
Average measured interrupt to process latency (µs): 15,950662
Highest measured interrupt to DPC latency (µs): 989,90
Average measured interrupt to DPC latency (µs): 5,404751
_________________________________________________________________________________________________________
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): 154,131187
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,121142
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,143404
ISR count (execution time <250 µs): 11942
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µs): 0
ISR count (execution time >=4000 µs): 0
_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.
Highest DPC routine execution time (µs): 1196,888855
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,718548
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 (%) 1,021537
DPC count (execution time <250 µs): 105442
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 2771
DPC count (execution time 1000-1999 µs): 7
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: msmpeng.exe
Total number of hard pagefaults 1415
Hard pagefault count of hardest hit process: 579
Number of processes hit: 22
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 3,232675
CPU 0 ISR highest execution time (µs): 135,210446
CPU 0 ISR total execution time (s): 0,078391
CPU 0 ISR count: 5558
CPU 0 DPC highest execution time (µs): 1196,888855
CPU 0 DPC total execution time (s): 1,753642
CPU 0 DPC count: 94880
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 1,409350
CPU 1 ISR highest execution time (µs): 154,131187
CPU 1 ISR total execution time (s): 0,197485
CPU 1 ISR count: 6384
CPU 1 DPC highest execution time (µs): 343,608867
CPU 1 DPC total execution time (s): 0,146815
CPU 1 DPC count: 6469
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 1,577243
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): 117,779836
CPU 2 DPC total execution time (s): 0,043668
CPU 2 DPC count: 5473
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,585604
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): 60,207713
CPU 3 DPC total execution time (s): 0,021068
CPU 3 DPC count: 1398
voici les test de LatencyMon
1/test Live+ AD
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:00:48 (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): 1046,30
Average measured interrupt to process latency (µs): 15,950662
Highest measured interrupt to DPC latency (µs): 989,90
Average measured interrupt to DPC latency (µs): 5,404751
_________________________________________________________________________________________________________
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): 154,131187
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,121142
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,143404
ISR count (execution time <250 µs): 11942
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µs): 0
ISR count (execution time >=4000 µs): 0
_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.
Highest DPC routine execution time (µs): 1196,888855
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,718548
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 (%) 1,021537
DPC count (execution time <250 µs): 105442
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 2771
DPC count (execution time 1000-1999 µs): 7
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: msmpeng.exe
Total number of hard pagefaults 1415
Hard pagefault count of hardest hit process: 579
Number of processes hit: 22
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 3,232675
CPU 0 ISR highest execution time (µs): 135,210446
CPU 0 ISR total execution time (s): 0,078391
CPU 0 ISR count: 5558
CPU 0 DPC highest execution time (µs): 1196,888855
CPU 0 DPC total execution time (s): 1,753642
CPU 0 DPC count: 94880
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 1,409350
CPU 1 ISR highest execution time (µs): 154,131187
CPU 1 ISR total execution time (s): 0,197485
CPU 1 ISR count: 6384
CPU 1 DPC highest execution time (µs): 343,608867
CPU 1 DPC total execution time (s): 0,146815
CPU 1 DPC count: 6469
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 1,577243
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): 117,779836
CPU 2 DPC total execution time (s): 0,043668
CPU 2 DPC count: 5473
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,585604
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): 60,207713
CPU 3 DPC total execution time (s): 0,021068
CPU 3 DPC count: 1398
mashmer
23
Nouvel·le AFfilié·e
Membre depuis 11 ans
33 Posté le 22/09/2019 à 16:18:49
2/test AD seul
________________________________________________________________________________________________________
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:45 (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): 4201,90
Average measured interrupt to process latency (µs): 12,057561
Highest measured interrupt to DPC latency (µs): 4144,70
Average measured interrupt to DPC latency (µs): 4,610828
_________________________________________________________________________________________________________
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): 638,033404
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,143789
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,171054
ISR count (execution time <250 µs): 17649
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 64
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): 4291,042211
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,466958
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,742824
DPC count (execution time <250 µs): 102057
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 625
DPC count (execution time 1000-1999 µs): 68
DPC count (execution time 2000-3999 µs): 35
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 298
Hard pagefault count of hardest hit process: 222
Number of processes hit: 9
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 2,537236
CPU 0 ISR highest execution time (µs): 638,033404
CPU 0 ISR total execution time (s): 0,286636
CPU 0 ISR count: 16712
CPU 0 DPC highest execution time (µs): 4291,042211
CPU 0 DPC total execution time (s): 1,276015
CPU 0 DPC count: 95904
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,737123
CPU 1 ISR highest execution time (µs): 146,678409
CPU 1 ISR total execution time (s): 0,021370
CPU 1 ISR count: 1001
CPU 1 DPC highest execution time (µs): 247,681142
CPU 1 DPC total execution time (s): 0,021928
CPU 1 DPC count: 1098
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,598741
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): 160,164592
CPU 2 DPC total execution time (s): 0,013049
CPU 2 DPC count: 1102
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 1,320389
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): 81,492864
CPU 3 DPC total execution time (s): 0,026566
CPU 3 DPC count: 4682
_________________________________________________________________________________________________________
________________________________________________________________________________________________________
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:45 (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): 4201,90
Average measured interrupt to process latency (µs): 12,057561
Highest measured interrupt to DPC latency (µs): 4144,70
Average measured interrupt to DPC latency (µs): 4,610828
_________________________________________________________________________________________________________
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): 638,033404
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,143789
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,171054
ISR count (execution time <250 µs): 17649
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 64
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): 4291,042211
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,466958
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,742824
DPC count (execution time <250 µs): 102057
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 625
DPC count (execution time 1000-1999 µs): 68
DPC count (execution time 2000-3999 µs): 35
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 298
Hard pagefault count of hardest hit process: 222
Number of processes hit: 9
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 2,537236
CPU 0 ISR highest execution time (µs): 638,033404
CPU 0 ISR total execution time (s): 0,286636
CPU 0 ISR count: 16712
CPU 0 DPC highest execution time (µs): 4291,042211
CPU 0 DPC total execution time (s): 1,276015
CPU 0 DPC count: 95904
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,737123
CPU 1 ISR highest execution time (µs): 146,678409
CPU 1 ISR total execution time (s): 0,021370
CPU 1 ISR count: 1001
CPU 1 DPC highest execution time (µs): 247,681142
CPU 1 DPC total execution time (s): 0,021928
CPU 1 DPC count: 1098
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,598741
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): 160,164592
CPU 2 DPC total execution time (s): 0,013049
CPU 2 DPC count: 1102
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 1,320389
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): 81,492864
CPU 3 DPC total execution time (s): 0,026566
CPU 3 DPC count: 4682
_________________________________________________________________________________________________________
Anonyme
292
34 Posté le 22/09/2019 à 16:38:20
Salut, d'autres pistes:
- à part Live, as-tu des applis ou des services 'lourds' qui tournent en tâche de fond ? Tu peux le verifier en executant la commande 'msconfig'. Regardes dans les onglets 'Services' et 'Demarrage' et desactive ce qui te semble superflu
- tous tes drivers sont-ils à jour ? Pour en être sur vas sur 'Driverscloud.com', fais une vérification et mets les à jour
- as-tu un antivirus 'lourd', type Norton, MacAfee, etc...? Si oui je te conseille de le désactiver, voire même de le désinstaller et te contenter de l'antivirus intégré de Windows
- ton disque dur est-il plein, ou quasi plein ? Si oui fais du ménage car un disque plein ralentit fortement la machine,
- essaye aussi de faire un nettoyage avec CCleaner, ça peut parfois corriger des lenteurs
- à part Live, as-tu des applis ou des services 'lourds' qui tournent en tâche de fond ? Tu peux le verifier en executant la commande 'msconfig'. Regardes dans les onglets 'Services' et 'Demarrage' et desactive ce qui te semble superflu
- tous tes drivers sont-ils à jour ? Pour en être sur vas sur 'Driverscloud.com', fais une vérification et mets les à jour
- as-tu un antivirus 'lourd', type Norton, MacAfee, etc...? Si oui je te conseille de le désactiver, voire même de le désinstaller et te contenter de l'antivirus intégré de Windows
- ton disque dur est-il plein, ou quasi plein ? Si oui fais du ménage car un disque plein ralentit fortement la machine,
- essaye aussi de faire un nettoyage avec CCleaner, ça peut parfois corriger des lenteurs
mashmer
23
Nouvel·le AFfilié·e
Membre depuis 11 ans
35 Posté le 22/09/2019 à 17:27:24
Salut r95, je ne vois pas d'autres applis ou services lourds qui puissent ralentir le système,
les drivers sont à jours visiblement. l'antivirus et les cartes réseaux sont désactivées, le disque dur principal est occupé à 83% (j'ai 171gb libre de 880 gb occupés)
j'ai lancé ccleaner et toujours ces craquements insupportables
les drivers sont à jours visiblement. l'antivirus et les cartes réseaux sont désactivées, le disque dur principal est occupé à 83% (j'ai 171gb libre de 880 gb occupés)
j'ai lancé ccleaner et toujours ces craquements insupportables
Anonyme
292
36 Posté le 22/09/2019 à 19:07:45
Tu as quoi comme carte-son ?
Tu en as essayé une autre pour voir si ça vient de là ?
Tu en as essayé une autre pour voir si ça vient de là ?
dsy
4313
Squatteur·euse d’AF
Membre depuis 22 ans
37 Posté le 22/09/2019 à 19:09:59
Citation de r95 :
Tu as quoi comme carte-son ?
C'est une focusrite scarlett 6i6
Anonyme
292
38 Posté le 22/09/2019 à 19:10:36
Pour le disque 83% d'occupation ça commence à faire pas mal, cependant je pense pas que le problème vienne de là...
Mais va falloir songer à faire du nettoyage bientôt.
Est-ce ce que tu constates d'autres ralentissements ou problèmes mis à part Ableton Live ?
Mais va falloir songer à faire du nettoyage bientôt.
Est-ce ce que tu constates d'autres ralentissements ou problèmes mis à part Ableton Live ?
Anonyme
292
39 Posté le 22/09/2019 à 19:13:12
Je présume que dans les préférences de Live tu sélectionnes bien le driver Asio ?
Quel est ton reglage buffer ?
Si tu mets une valeur haute, genre 1028 samples ça craque toujours autant ?
Quel est ton reglage buffer ?
Si tu mets une valeur haute, genre 1028 samples ça craque toujours autant ?
Anonyme
292
40 Posté le 22/09/2019 à 19:28:37
Je reviens sur l'histoire du disque dur:
As tu constaté lors des craquements que le bouton 'D' en haut à droite de l'interface de Live s'allume en rouge ?
Si c'est le cas ça indique que le problème vient du disque.
As tu constaté lors des craquements que le bouton 'D' en haut à droite de l'interface de Live s'allume en rouge ?
Si c'est le cas ça indique que le problème vient du disque.
- < Liste des sujets
- Charte