<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - Pulse audio NOT USED multithreading" href="https://bugs.freedesktop.org/show_bug.cgi?id=90210#c33">Comment # 33</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - Pulse audio NOT USED multithreading" href="https://bugs.freedesktop.org/show_bug.cgi?id=90210">bug 90210</a> from <a class="email" href="mailto:tanuk@iki.fi" title="Tanu Kaskinen <tanuk@iki.fi>"> Tanu Kaskinen</a> <pre>(In reply to Alessandro Ferri from <a href="show_bug.cgi?id=90210#c32">comment #32</a>) > Dear Tanu, > I can control the latency of pulseaudio by file: > > daemon.conf > system.pa > client.conf > > and if I can configure the latency which setup should I have done? > I need to increase the latency of about 756ms. Sorry for a late reply, I haven't had time to read bugmail for a while. Are you loading module-loopback manually, or is it getting loaded automatically? If you're loading it manually, you can try using the latency_msec parameter of module-loopback. If module-loopback is getting loaded automatically, then it's not possible to control module-loopback's latency, because module-bluetooth-policy (which handles loading module-loopback) loads module-looback always with the default latency. You could modify system.pa to not load module-bluetooth-policy, and then load module-loopback manually, but manual loading may of course not be practical, if you have to do it every time you connect a bluetooth device... Another possibility might be to force the alsa sink latency to be higher. To try this, add tsched=no to module-udev-detect's parameters, and increase default-fragments and/or default-fragment-size-msec in daemon.conf (those parameters only have effect when tsched is disabled).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>