Le 03/11/2017 à 10:05, Tanu Kaskinen a écrit : > On Thu, 2017-11-02 at 21:32 +0100, 21naown at gmail.com wrote: >> Le 01/11/2017 à 10:55, Tanu Kaskinen a écrit : >>> On Mon, 2017-10-30 at 15:40 +0100, 21naown at gmail.com wrote: >>>> Hello, >>>> >>>> >>>> I would like to know how can I check visually (with an indicator for >>>> example) for XRUNs/drop-out/interruptions and similar? >>>> I use (on Debian): >>>> â?? pulseaudio (configured to work with jack); >>>> â?? pulseaudio-module-jack; >>>> â?? qjackctl. >>>> >>>> I know QjackCtl can display the XRUNs but in my mind, it can only >>>> display part of the existing XRUNs when it works with PulseAudio, but >>>> maybe I am wrong. >>> I think QJackCtl shows all xruns that happen in jack. Whether >>> PulseAudio is being used or not shouldn't make any difference. >>> >>> As for drop-outs in PulseAudio, QJackCtl won't show those, unless they >>> also cause xruns in jack. PulseAudio doesn't currently provide any >>> mechanism for getting notifications about drop-outs. >>> >> Thank you for your answer. >> >> Even in logs (â??syslogâ?? if I am not wrong)? Do you think the developers >> can add this easily (for drop-outs and similar)? It would be really >> useful for me, but I hope I am not alone. > Drop-outs are logged, but you need to enable verbose logging. > PulseAudio generates a lot of logs in the verbose mode, I don't know if > you want all that in your syslog. It's possible to set the log target > to a file, though. > Super! I will change the target of the log file yes (I saw â??--log-target=file:PATHâ??). Do you know the error message or a keyword for the drop-outs to find them in the logs? What is the â??log-levelâ?? to show them? (if I am not wrong, â??noticeâ??, which is â??2â??, is the default) You can confirm any problem similar to a drop-out (= which modifies the value of the sound whereas it should not) is logged if it is the PulseAudioâ??s fault?
