<div>"module-suspend-on-idle" should suspend the alsa devices when no clients are idle or not connected for 5 seconds by default.</div><div>try loading that module and see if it actually closes the handle to the alsa devices.</div> <div><br></div><div class="gmail_quote">On Fri, Oct 7, 2011 at 10:21 AM, Paul Menzel <span dir="ltr"><<a href="mailto:paulepanter@users.sourceforge.net">paulepanter@users.sourceforge.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> Dear Andreas,<br> <br> <br> Am Freitag, den 07.10.2011, 17:03 +0200 schrieb Andreas Bauer:<br> <div class="im"><br> > First a big thank you for a quality piece of software. I am a first<br> > time user and am amazed at the flexiblity that PA provides. I<br> > installed PA because I wanted to have better integration of my<br> > Bluetooth headset and works perfectly.<br> <br> </div>thank you for such positive feed back. I guess developers (not me)<br> should get that more often.<br> <div class="im"><br> > Running Debian Squeeze (stable) with Kernel 3.0.1<br> <br> </div>Is the PA version 0.9.21-3+squeeze1 [1]? I guess the ALSA version is<br> quite old then too. PA 1.0 was released recently.<br> <br> Could you somehow test a more recent version. I am not sure if there is<br> a live CD for that purpose or if you have a spare storage medium where<br> you can try Debian Sid/unstable.<br> <div><div></div><div class="h5"><br> > Now I have three issues which I hope someone can point me to a<br> > possible solution.<br> ><br> > On my Lenovo X201 laptop with Intel HDA I do see a heavy increase in<br> > power consumption when I activate pulseaudio. The system is already<br> > optimised so without pulseaudio it will idle at 6-9W with wifi on,<br> > with pulseaudio started it will jump to 13W. No pulseaudio client<br> > connected (no sound played)<br> ><br> > Averaged battery reading every 5s<br> ><br> > 1267000<br> > 1311000<br> > 1330000<br> > 1347000 <- here pa-suspender is started<br> > 1192000<br> > 1091000<br> > 986000<br> > 952000<br> > 943000<br> > 988000<br> > 970000<br> > 943000<br> ><br> > I have already optimised the PA setup for my needs (e.g. low quality<br> > resampling-method), so I investigated further:<br> ><br> > From top:<br> ><br> > 8816 ab 9 -11 211m 3832 2832 S 0 0.1 0:00.06 pulseaudio<br> ><br> > From powertop:<br> ><br> > 695,7 ľs/s 13,6<br> > Process /usr/bin/pulseaudio --start --log-target=syslog<br> ><br> > So it is not about CPU consumption, pulseaudio is economical with CPU<br> > as is.<br> ><br> > The same thing (also drawing about the same amount of extra juice)<br> > happens with this:<br> ><br> > root@charly:~# mv /etc/asound.conf /etc/asound.pulse<br> > root@charly:~# aplay -d front /boot/vmlinuz-*<br> > Wiedergabe: Rohdaten '/boot/vmlinuz-3.0.1' : Unsigned 8 bit, Rate:<br> > 8000 Hz, mono<br> ><br> > So clearly, it is the power consumption of the sound chip. I suspect<br> > that pulseaudio activates the sound chip even when no sound is being<br> > played. Is there any way to have it only access the hardware when at<br> > minimum one client is connected (e.g. audio playing)?<br> <br> </div></div>I am not sure. 4 W power consumption of a sound chip sounds quite a lot<br> to me. Additionally as written above please try a newer version.<br> <div class="im"><br> > I was not successful with this shot (old syntax?):<br> ><br> > add-autoload-sink alsa_sink module-alsa-sink device="hw:0"<br> > add-autoload-source alsa_source module-alsa-source device="hw:0"<br> <br> </div>You can also take a look at the ALSA Wiki [2] and provide the output of<br> `alsa-info.sh` which should give a lot of useful information to the<br> developers.<br> <div class="im"><br> > Second issue: I have one application (Zoiper) which can only access<br> > ALSA at the moment (because it will not allow me to input non-hardware<br> > ALSA device names like pcm.pulse). Is there some hack/workaround to<br> > get such applications to talk to pulseaudio?<br> <br> </div>Please open a new thread by sending a new message with an appropriate<br> subject line for this topic.<br> <br> <br> Thanks,<br> <br> Paul<br> <br> <br> [1] <a href="http://packages.debian.org/squeeze/pulseaudio" target="_blank">http://packages.debian.org/squeeze/pulseaudio</a><br> [2] <a href="http://alsa-project.org/main/index.php/Help_To_Debug" target="_blank">http://alsa-project.org/main/index.php/Help_To_Debug</a><br> <br>_______________________________________________<br> pulseaudio-discuss mailing list<br> <a href="mailto:pulseaudio-discuss@lists.freedesktop.org">pulseaudio-discuss@lists.freedesktop.org</a><br> <a href="http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss" target="_blank">http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss</a><br> <br></blockquote></div><br><br clear="all"><div><br></div>-- <br>-baeksanchang<br>