From: Colin Guthrie <gmane@colin.guthr.ie>
To: alsa-devel@alsa-project.org
Subject: Re: Questions regarding workaround for VMware
Date: Thu, 17 Sep 2009 14:06:04 +0100 [thread overview]
Message-ID: <h8tc7s$fg7$1@ger.gmane.org> (raw)
In-Reply-To: <4eccebac0909161727r540b42c6l4cf9a0cb994c0c93@mail.gmail.com>
'Twas brillig, and Bankim Bhavsar at 17/09/09 01:27 did gyre and gimble:
> On a side-note there seems to be some change in PulseAudio bring
> shipped with Ubuntu 9.10 over 9.04 that affects sound playback
> quality.
> With PulseAudio in 9.10, programmed DMA buffer is 64k and num_periods
> is always 1 and thereby number of interrupts generated per sec is just
> 2 for 16-bit, 44Khz, stereo.
> IMO the number interrupts is too low and this leads to under-runs.
> Whats the reason for choosing always 1 period and having large
> buffer/period size (power-savings?)?
>
> If I disable PulseAudio in 9.10, programmed DMA buffer is 64k with 16
> periods each of size 4k and virtual sound device would generate 46-48
> interrupts per sec. With this setting sound playback quality is good.
I'm not sure about Ubuntu setup but the disabling of interupts and using
timers is indeed all about power savings. The wakeup time is dynamically
adjusted when an underrun occurs so as to avoid it in the future.
Some Nokia/Intel folks (can't remember which) are experimenting with
very large latencies (e.g. up to about 10s) in order to get maximum
power savings.
You can read more about it here:
http://0pointer.de/blog/projects/pulse-glitch-free.html
You can disable this timer based scheduling by passing the argument
tsched=0 to module-hal-detect or module-udev-detect (whichever is in
use: the latter obsoleting the former) in /etc/pulse/default.pa
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mandriva Linux Contributor [http://www.mandriva.com/]
PulseAudio Hacker [http://www.pulseaudio.org/]
Trac Hacker [http://trac.edgewall.org/]
next prev parent reply other threads:[~2009-09-17 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 18:29 Questions regarding workaround for VMware Bankim Bhavsar
2009-08-28 19:51 ` Takashi Iwai
2009-09-13 18:17 ` Bankim Bhavsar
2009-09-15 11:00 ` Takashi Iwai
2009-09-17 0:27 ` Bankim Bhavsar
2009-09-17 13:06 ` Colin Guthrie [this message]
2009-09-18 7:00 ` Raymond Yau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='h8tc7s$fg7$1@ger.gmane.org' \
--to=gmane@colin.guthr.ie \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.