Please keep the conversation on the mailing list. (though it looks like I forgot to do that too) 2011/2/23 Cristina Cristea <doina.cristina at gmail.com>: > No, the glitches are now more rarely and smaller. But, after 31 minutes of > playing (with only one small glitch, bearly audible, on min 27), PulseAudio > started to display a lot of underrun messages and died. Died, as in crashed? Verbose log output would be interesting here. Most likely the CPU load limiter kicked in and pulse shut itself down. > Also, module-loopback causes PulseAudio to be a a very big CPU consumer on > my system-like about 80%. That should not be. Can you get this behaviour also without module-loopback? (e.g. by recording from the bluetooth source with parec) For further information on how to debug this, see http://pulseaudio.org/wiki/HowToDebugCPULoadBugs > I'll do more testing these days and see if I can improve. > Thanks for support and I really appreciate what you guys are doing. > > Cristina > > > I'll do more testing the Maarten > On 02/22/2011 09:36 PM, Maarten Bosmans wrote: >> >> 2011/2/22 Cristina Cristea<doina.cristina at gmail.com>: >> >>> >>> Thanks Maarten, that really makes the sample rate adjustment to not be >>> noticed by the listener. >>> Unfortunately, I still get the underrun issues. Here is a log snippet: >>> >> >> Do the underruns still occur after a minute of playing? Do they result >> in audible glitches? >> >> As I mentioned in the mail that went with these patches a couple of >> weeks ago, I have not tested it on any non-trivial module-loopback >> setup (e.g. bluetooth source to alsa sink), so some underrun problems >> can indeed still be expected. >> >> Maarten
