Anyone have an in depth treatise on xruns and how to minimize them. By
that I dont mean just adjusting the buffer size, I mean really getting
into the gears of why xruns happen and how to potentially minimize them.
Reason I ask is that I use jack on a live music basis amd it is crucial
for me to get no more than 2.9ms latency.
I can hear and feel every latency above above that.
I am lucky with mixbus and jack on Linux to get 2.9ms with the
occasional xrun every 2 minutes, but I want to see if I cannot eliminate
Any advice or point to very relevant reference material will be
I found audit=0 on
---------- Forwarded message ----------
Date: Sun, 28 Jul 2019 10:32:15 +0200 (CEST)
From: Holger Marzen <holger(a)marzen.de>
To: Ralf Mardorf <ralf.mardorf(a)alice-dsl.net>
Cc: liebrecht(a)grossmann-venter.com, jack-devel(a)lists.jackaudio.org
Subject: Re: [Jack-Devel] advice on xruns
On Sun, 28 Jul 2019, Ralf Mardorf wrote:
> On Sun, 28 Jul 2019 08:40:07 +0200 (CEST), Holger Marzen wrote:
> >"nohz=off threadirqs noibrs noibpb nopti
> >nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable
> >no_stf_barrier mds=off mitigations=off quiet splash"
> With those spectre mitigations turned off, it still might be of value
> to disable audit, see
Can I disable it on the kernel command line if it's compiled in the kernel?
> Why do you disable nohz?
Got an error message in syslog, googled a bit, disabled it without
I'm running an ALSA -> PulseAudio -> Jack bridge setup on an Ubuntu 18.04
x86 laptop. Sound played via ALSA directly seems to be much louder than via
gst-launch-1.0 audiotestsrc freq=200 volume=1.0 ! alsasink
is much louder than
gst-launch-1.0 audiotestsrc freq=200 volume=1.0 ! jackaudiosink
I've looked at every volume knob I can find (via alsamixer, qasmixer, pactl
list, etc.), and they're all at 100%. Does the PulseAudio -> Jack bridge
have a volume parameter hidden in a config file, or something like that?