On Sat, 10.01.09 18:43, Colin Guthrie (gm...@colin.guthr.ie) wrote:
> Lennart,
>
> You probably missed this but a while back someone posted a bunch of
> patches on IRC for NetBSD.
>
> Some of the patches are simple enough and it may be worth merging in the
> ones that make sense. I've not look
2009/1/22 Chris :
> Jan 22 00:16:17 localhost pulseaudio[2817]: module-alsa-sink.c:
> Increasing wakeup watermark to 23.95 ms
> Jan 22 00:16:30 localhost pulseaudio[2817]: module-alsa-sink.c:
> Increasing wakeup watermark to 47.89 ms
> Jan 22 00:16:37 localhost pulseaudio[2817]: module-alsa-sink.c:
Sorry to resurrect this thread again buy my audio problems persist and
are driving me mad.
I notice that when I start playing audio, things are pretty good, then
there's a glitch and the "wakeup watermark" is increased. After that,
the glitches become more frequent and the watermark is increased
a
>>The requirement that internal pause an application is a natural to
audio manager of embedded system.
That would be what you'd think but you would be surprised what a hack
some of these things are. It's what I do for a living. Certainly in the
products I work on, that kind of logic is left to the
I don't disagree with technical findings. Still, it would be sad if we have
no means to do what the iPhone does today. Cheers. Pierre
>From the iPhone 'missing manual' book:
If a phone call comes in, the music fades, and you hear your chosen
ringtone―
through your earbuds, if you're wearing them.
How is the latency obtained when using bluetooth in pulseaudio. By latency
I mean something similar to snd_pcm_delay(). Since bluetooth doesn't use
alsa, how is the time delay calculated from writing data to actually hearing
it out of the dac?
Thanks
Baek
