Sujet Click à faible charge CPU ?
- 1 réponse
- 1 participant
- 245 vues
- 1 follower
vincemal
9
Nouvel·le AFfilié·e
Membre depuis 14 ans
Sujet de la discussion Posté le 13/12/2018 à 13:04:13Click à faible charge CPU ?
Bonjour à vous,
j'écris ce petit message en espérant que quelqu'un pourra me venir en aide.
J'ai le plus grand mal à optimiser les performances de mon Live 10, j'ai récemment téléchargé Pigments (la version d'essai pour le moment, ouf) et quand je fais tourner ce VST c'est encore plus criant. Alors que ma jauge CPU ne dépasse quasiment jamais les 25%, les playbacks sur Ableton sont toujours ponctués d'une multitudes de clicks et de temps morts.
Je le fais tourner sur un ordi portable datant du mois de septembre, avec un i7, un DD assez rapide et un SDD également (je ne sais pas si il est utilisé correctement par Ableton par contre). Côté carte son j'ai une Quad-capture de Roland avec son propre driver ASIO, mais j'ai aussi essayé avec ASIO 4 ALL par acquis de conscience. J'ai essayé 41, 48 et 96 kHz, un plus ou moins grand buffer... rien n'y change. Pour le contrôle j'ai un clavier maitre Alesis VI25.
On dirait principalement que les clicks apparaissent vers 20, 25% de charge CPU, comme si il paniquait à partir de ce moment là. Pourtant il est aussi capable très rarement de charger le CPU à plus de 50% donc je pense qu'il sait utiliser tout les coeurs de mon i7...
L'un d'entre vous aurait une idée ?
Merci beaucoup pour votre aide !
j'écris ce petit message en espérant que quelqu'un pourra me venir en aide.
J'ai le plus grand mal à optimiser les performances de mon Live 10, j'ai récemment téléchargé Pigments (la version d'essai pour le moment, ouf) et quand je fais tourner ce VST c'est encore plus criant. Alors que ma jauge CPU ne dépasse quasiment jamais les 25%, les playbacks sur Ableton sont toujours ponctués d'une multitudes de clicks et de temps morts.
Je le fais tourner sur un ordi portable datant du mois de septembre, avec un i7, un DD assez rapide et un SDD également (je ne sais pas si il est utilisé correctement par Ableton par contre). Côté carte son j'ai une Quad-capture de Roland avec son propre driver ASIO, mais j'ai aussi essayé avec ASIO 4 ALL par acquis de conscience. J'ai essayé 41, 48 et 96 kHz, un plus ou moins grand buffer... rien n'y change. Pour le contrôle j'ai un clavier maitre Alesis VI25.
On dirait principalement que les clicks apparaissent vers 20, 25% de charge CPU, comme si il paniquait à partir de ce moment là. Pourtant il est aussi capable très rarement de charger le CPU à plus de 50% donc je pense qu'il sait utiliser tout les coeurs de mon i7...
L'un d'entre vous aurait une idée ?
Merci beaucoup pour votre aide !
[ Dernière édition du message le 13/12/2018 à 16:27:13 ]
vincemal
9
Nouvel·le AFfilié·e
Membre depuis 14 ans
2 Posté le 15/12/2018 à 20:01:40
Si ça peut aider voilà le rapport de Latency Monitor :
_________________________________________________________________________________________________________
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:01:54 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: LAPTOP-MAPJINUT
OS version: Windows 10 , 10.0, build: 17134 (x64)
Hardware: VivoBook S15 X530UA, ASUSTeK COMPUTER INC., X530UA
CPU: GenuineIntel Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
Logical processors: 8
Processor groups: 1
RAM: 8071 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 1992 MHz
Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.
_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.
Highest measured interrupt to process latency (µs): 1295,935410
Average measured interrupt to process latency (µs): 7,978357
Highest measured interrupt to DPC latency (µs): 1292,851073
Average measured interrupt to DPC latency (µs): 2,779363
_________________________________________________________________________________________________________
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): 89,393072
Driver with highest ISR routine execution time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation
Highest reported total ISR routine time (%): 0,002901
Driver with highest ISR total time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation
Total time spent in ISRs (%) 0,002935
ISR count (execution time <250 µs): 11185
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): 1359,843373
Driver with highest DPC routine execution time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation
Highest reported total DPC routine time (%): 0,173842
Driver with highest DPC total execution time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation
Total time spent in DPCs (%) 0,426482
DPC count (execution time <250 µs): 314101
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 1347
DPC count (execution time 1000-1999 µs): 62
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: chrome.exe
Total number of hard pagefaults 481
Hard pagefault count of hardest hit process: 186
Number of processes hit: 12
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 8,446463
CPU 0 ISR highest execution time (µs): 89,393072
CPU 0 ISR total execution time (s): 0,024962
CPU 0 ISR count: 10646
CPU 0 DPC highest execution time (µs): 1359,843373
CPU 0 DPC total execution time (s): 2,314893
CPU 0 DPC count: 267406
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 7,908861
CPU 1 ISR highest execution time (µs): 29,417671
CPU 1 ISR total execution time (s): 0,001803
CPU 1 ISR count: 539
CPU 1 DPC highest execution time (µs): 1206,158635
CPU 1 DPC total execution time (s): 0,176966
CPU 1 DPC count: 5360
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 4,031799
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): 171,284639
CPU 2 DPC total execution time (s): 0,007027
CPU 2 DPC count: 827
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 4,375862
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): 480,688253
CPU 3 DPC total execution time (s): 0,006193
CPU 3 DPC count: 528
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 5,657266
CPU 4 ISR highest execution time (µs): 0,0
CPU 4 ISR total execution time (s): 0,0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 369,230422
CPU 4 DPC total execution time (s): 0,011289
CPU 4 DPC count: 1085
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 2,610187
CPU 5 ISR highest execution time (µs): 0,0
CPU 5 ISR total execution time (s): 0,0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 154,883032
CPU 5 DPC total execution time (s): 0,007618
CPU 5 DPC count: 700
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 7,194515
CPU 6 ISR highest execution time (µs): 0,0
CPU 6 ISR total execution time (s): 0,0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 381,244980
CPU 6 DPC total execution time (s): 0,012085
CPU 6 DPC count: 1085
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 11,555739
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 754,620984
CPU 7 DPC total execution time (s): 1,353440
CPU 7 DPC count: 38519
_________________________________________________________________________________________________________
- < Liste des sujets
- Charte