Hello Pierre, I have not tweaked around with the daemon conf file. The fragments and its size are set to 4 and 25ms respectively. So what does "your hardware cannot handle longer periods" mean? Would this mean I would encounter the issue even if I updated the ALSA driver? Please suggest the ALSA driver version that I should be using. Thanks a lot for your valuable feedback. -Rgds Vallabha On Mon, Aug 1, 2011 at 8:42 PM, pl bossart <bossart.nospam at gmail.com> wrote: > > I: alsa-sink.c: Using 16.0 fragments of size 8192 bytes (46.44ms), buffer > > I: alsa-sink.c: Time scheduling watermark is 20.00ms > > I indicated last week that this setting is not ok. > Either you are setting the number of fragments to a ridiculously high > value in daemon.conf, or your hardware cannot handle longer periods. > Either way, you will end-up with an audio interrupt rate that is > inconsistent with the latency settings you have specified; a ~5s > latency isn't going to help at all if the alsa interrupts occur every > 46ms. > I know that the OMAP drivers were updated to remove these ALSA > interrupts completely (need kernel 2.6.38+), this is something you may > want to look into to remove audio wakes > -Pierre > _______________________________________________ > pulseaudio-discuss mailing list > pulseaudio-discuss at lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20110801/fe1feba9/attachment.htm>
