In Reply to: Mark Brown
> On Fri, Oct 07, 2011 at 07:21:44PM +0200, Paul Menzel wrote:
>
> > I am not sure. 4 W power consumption of a sound chip sounds quite a lot
> > to me. Additionally as written above please try a newer version.
>
> That's many orders of magnitude more than is sane unless
In Reply to: Arun Raghavan
> > This is already setup and works fine indeed for everything but this one
> application. It will not allow free text entry of an ALSA device, but will
> instead present only devices listed in /proc/asound/pcm ("real" hardware
> devices).
> >
> > I don't care how d
In Reply to: Pierre-Louis Bossart
> > So it is not about CPU consumption, pulseaudio is economical with CPU as is.
>
> Have you loaded the module module-suspend-on-idle? If nothing is playing
> (and your volume UI isn't showing), the output device should be burn any
> power.
Thanks also. This m
In Reply to: Baek Chang
> "module-suspend-on-idle" should suspend the alsa devices when no clients are
> idle or not connected for 5 seconds by default.
> try loading that module and see if it actually closes the handle to the alsa
> devices.
Thanks a lot. It can be that easy. That did the trick
In Reply to: Paul Menzel
> > Running Debian Squeeze (stable) with Kernel 3.0.1
>
> Is the PA version 0.9.21-3+squeeze1 [1]? I guess the ALSA version is
> quite old then too. PA 1.0 was released recently.
Yes, correct. I should have provided that information. ALSA is 1.0.23+dfsg-2
> Could you so
I have one (closed-source) application (Zoiper) which can only access ALSA
(because it will not allow me to input non-hardware ALSA device names like
pcm.pulse).
Is there some hack/workaround to get such applications to talk to pulseaudio?
Andreas
__
Hello everyone,
First a big thank you for a quality piece of software. I am a first time user
and am amazed at the flexiblity that PA provides. I installed PA because I
wanted to have better integration of my Bluetooth headset and works perfectly.
Running Debian Squeeze (stable) with Kernel 3.0
