On 28 September 2011 22:56, Spidey / Claudio spide...@gmail.com wrote:
On Thu, Sep 29, 2011 at 00:44, Arun Raghavan
arun.ragha...@collabora.co.uk wrote:
On Thu, 2011-09-29 at 00:20 -0300, Spidey / Claudio wrote:
I haven't tried the masked version, but I follow the PA maillist and
haven't seen
On 10/06/2011 04:34 PM, ext Mark Brown wrote:
On Thu, Oct 06, 2011 at 04:22:33PM +0300, Matti J. Aaltonen wrote:
But the handling of the analog audio isn't that straightforward, or
maybe it is... I'm not familiar with pulse audio.
It's trivial and can be done entirely in kernel as with all
On 10/06/2011 05:46 PM, ext Mark Brown wrote:
On Thu, Oct 06, 2011 at 05:11:07PM +0300, Matti J. Aaltonen wrote:
On 10/06/2011 04:34 PM, ext Mark Brown wrote:
All the audio power management flows from audio routing - when you
disconnect the audio path that connects the FM radio from an output
On Fri, Oct 07, 2011 at 10:24:40AM +0300, Matti J. Aaltonen wrote:
But then I don't get why the radio should be able to say when the
[analog] stream starts and stops (and what do you actually mean by
that?). Isn't it possible in the above scenario to simply turn on
the cross wired amp if the
On Fri, Oct 07, 2011 at 03:21:33PM +0300, Matti J. Aaltonen wrote:
by the DAC codec. Now to have on output for the analog radio the amplifier
should be handled as a separate audio card, right? And then the
No. When I said this should all be a single card that's what I meant.
Yes, but what I
On Fri, Oct 07, 2011 at 03:39:02PM +0300, Matti J. Aaltonen wrote:
On 10/07/2011 03:33 PM, ext Mark Brown wrote:
by the DAC codec. Now to have on output for the analog radio the amplifier
should be handled as a separate audio card, right? And then the
No. When I said this should all be a
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
Dear Andreas,
Am Freitag, den 07.10.2011, 17:03 +0200 schrieb Andreas Bauer:
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
On Fri, Oct 7, 2011 at 7:03 AM, pierre-louis.boss...@linux.intel.comwrote:
I've attached the PA config files I am using, along with the log
output(pulselog). The most suspicious thing in there is the failure to
get
RT scheduling. Is there something obviously wrong with the configs
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.
I was not successful with this shot (old syntax?):
Hello,
I'm new to PulseAudio and couldn't find the following online:
Can PulseAudio take advantage of advanced sound cards, e.g., mixing and
resampling?
Does it allow for bit-for-bit playback?
I'm building an media pc, but might have wrong ideas about the requirements
-- I do lite the highest
Makes sense, I'll take a look at what pacat is actually filling the
buffer attributes with and see if I can track this down.
here are some additional explanations. Hang on to your hat, this isn't
simple stuff:
pacat has this 'process-time-msec' parameter which defines the min_req
value (not a
On Fri, Oct 7, 2011 at 11:02 PM, CC ccom...@gmail.com wrote:
Hello,
I'm new to PulseAudio and couldn't find the following online:
Can PulseAudio take advantage of advanced sound cards, e.g., mixing and
resampling?
Does it allow for bit-for-bit playback?
I'm building an media pc, but might
In Reply to: Paul Menzel paulepan...@users.sourceforge.net
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
On Fri, 2011-10-07 at 17:03 +0200, Andreas Bauer wrote:
Second issue: I have one application (Zoiper) which can only access
ALSA at the moment (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
In Reply to: Baek Chang baek...@ccrma.stanford.edu
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
Watermark level and latency values are not restored when
resuming, the values used prior to suspending are reused.
This leads to side effects when underruns happen and buffer
sizes are updated, PulseAudio can never meet lower latency
requirements.
Solution: keep track of watermark and latency
In Reply to: Pierre-Louis Bossart pierre-louis.boss...@linux.intel.com
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
18 matches
Mail list logo
