Se connecter
Se connecter
Mot de passe oublié ?
ou
Créer un compte
ou
Se connecter avec Facebook
Notifications
< Retour vers Séquenceurs généralistes
Agrandir
Séquenceurs généralistes
Séquenceurs logiciels & STAN
Séquenceurs généralistes
Produits 606 606
Actu 1 250 1,3k
Articles 104 104
Médias 11 749 11,7k
Tutoriels Tutos 309 309
Avis 1 817 1,8k
Petites annonces Annonces 39 39
Forums 29 427 29,4k

Sujet Latence Ableton Live 9 Lite

  • 41 réponses
  • 4 participants
  • 853 vues
  • 3 followers
Sujet de la discussion Latence 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
2
Salut, tu devrais lister ce que tu as déjà fait pour éviter les répétitions.

Que donne le test de charge de Live ?
Driver focusrite à jour ?
Test avec LatencyMon ?
3
j'ai mis à jour le driver de la carte son
Qu'est-ce le test de charge et latencyMon?
4
Test de charge :
Regarde dans les options de Ableton Live : Audio / Test.
Active "Test Tone" et augmente la charge CPU (CPU Usage Simulator) pour voir jusqu'ou tu peux aller sans craquement.

LatencyMon : https://www.resplendence.com/latencymon
Permet de tester ta configuration pour la MAO et diagnostiquer des problèmes d'interruption du flux audio.
5
Bonjour,
Je ne sais pas si ça peut aider, mais j'ai connu le phénomène des craquements à l'écoute. Ca venait de ASIO que j'avais dû mal régler.
A tout hasard essaye de changer de pilote (Préférences -> audio -> type de pilote).
Bon courage
6
Déjà je dois vous dire un GRAND MERCI à vous deux!

Alors commençons par DSY, certes je n'ai pas résumé toutes les manipulations des options de Live que j'ai pu réaliser car elles sont bien trop ENORMES pour vous condenser en un simple message, mais le test auquel tu te réfères a été des premiers et à 128 de buffer et à 80% de la charge du cpu il n'y a pas de craquement
Et pourtant dès lors que je lance le plug in de batterie c'est la CATA!
Jacques Lesage, j'ai cru pendant un court instant que tu m'avais résolu le problème en changeant le pilote ASIO par MME, le son était limpide lorsque je lançait le plug in de batterie (Addictive drums 2)mais par contre il n'enregistre pas...
Je suis perdu dans les méandres informatiques, l'analogique c'était mieux...
7
Je viens d'avoir le verdict de Latencymon :
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. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 4:27:55 (h:mm:ss) on all processors.

Vraiment faut-il que je change de PC????
8
Non suivre les recommandations devrait déjà améliorer ton système. Cela aurait été bien de nous donner les chiffres.
9
Bonjour, voici les résultats complets de LatencyMon:
(Par contre, je ne vois pas ce que dois faire pour résoudre mon problème)
_________________________________________________________________________________________________________
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. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 3:21:22 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: ANTHEUS
OS version: Windows 10 , 10.0, version 1803, build: 17134 (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): 66482,570815
Average measured interrupt to process latency (µs): 9,540130

Highest measured interrupt to DPC latency (µs): 66453,025079
Average measured interrupt to DPC latency (µs): 3,913837


_________________________________________________________________________________________________________
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): 601,265411
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0,040781
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%) 0,049067

ISR count (execution time <250 µs): 1565423
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 1095
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): 73414,333131
Driver with highest DPC routine execution time: ndis.sys - Especificación de interfaz de controlador de red (NDIS), Microsoft Corporation

Highest reported total DPC routine time (%): 0,492745
Driver with highest DPC total execution time: ndis.sys - Especificación de interfaz de controlador de red (NDIS), Microsoft Corporation

Total time spent in DPCs (%) 0,674440

DPC count (execution time <250 µs): 15044894
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 59742
DPC count (execution time 1000-1999 µs): 3758
DPC count (execution time 2000-3999 µs): 957
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 214613
Hard pagefault count of hardest hit process: 86485
Number of processes hit: 172


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 507,093848
CPU 0 ISR highest execution time (µs): 601,265411
CPU 0 ISR total execution time (s): 20,430152
CPU 0 ISR count: 1384800
CPU 0 DPC highest execution time (µs): 73414,333131
CPU 0 DPC total execution time (s): 309,965635
CPU 0 DPC count: 13844695
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 71,114224
CPU 1 ISR highest execution time (µs): 522,187671
CPU 1 ISR total execution time (s): 3,256377
CPU 1 ISR count: 177080
CPU 1 DPC highest execution time (µs): 2548,904950
CPU 1 DPC total execution time (s): 7,928326
CPU 1 DPC count: 558102
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 55,414514
CPU 2 ISR highest execution time (µs): 268,168843
CPU 2 ISR total execution time (s): 0,026369
CPU 2 ISR count: 4343
CPU 2 DPC highest execution time (µs): 2533,393866
CPU 2 DPC total execution time (s): 3,656135
CPU 2 DPC count: 346703
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 46,320748
CPU 3 ISR highest execution time (µs): 14,538718
CPU 3 ISR total execution time (s): 0,001689
CPU 3 ISR count: 295
CPU 3 DPC highest execution time (µs): 2353,559672
CPU 3 DPC total execution time (s): 4,415684
CPU 3 DPC count: 360145
_________________________________________________________________________________________________________
10
Essaie de désactiver ta carte réseau dans le gestionnaire de périphérique. Idem pour le Wi-Fi si tu as une carte Wi-Fi.
Tu as des valeurs trés hautes de DPC mais le rapport ne donne pas la cause exacte (ndis.sys est un driver générique).