[pulseaudio-discuss] [PATCH 1/2] alsa-mixer: Implement support for setting element specific upper limits for volume.

2011-03-10 Thread Tanu Kaskinen
From: Tanu Kaskinen ext-tanu.kaski...@nokia.com This feature is mainly useful in embedded systems that have built-in speakers. In such situations the full audio path is known beforehand, so it's possible to know what is the maximum sensible volume, and any higher volume can be disabled. The

[pulseaudio-discuss] [PATCH 2/2] alsa-mixer: When figuring out the max_dB of a path, use only channels that are used by the path elements.

2011-03-10 Thread Tanu Kaskinen
Without this, p-max_dB could never be less than 0 dB, because the loop at the end of pa_alsa_path_probe() would reset p-max_dB to 0 as soon as the loop encountered a channel that wasn't touched by any element. --- src/modules/alsa/alsa-mixer.c | 13 + 1 files changed, 9

[pulseaudio-discuss] [PATCH] Make pulse compile with clang

2011-03-10 Thread Maarten Bosmans
As discussed on IRC. This is basically a correctly formatted version of the patch attached to http://pulseaudio.org/ticket/883 with a small improvement in configure.ac added. Maarten 0001-Make-pulse-compile-with-clang.patch Description: Binary data

[pulseaudio-discuss] What tests on AMD and ARM are needed for Orc-based optimised volume scaling?

2011-03-10 Thread Paul Menzel
Dear Arun, your commit messages of commit 4cd90d9e [1] says the following. … Since I haven't been able to test on other architectures, the Orc code is only used when MMX/SSE* is present. This can be changed in the future after testing on AMD and ARM machines. What tests

Re: [pulseaudio-discuss] What tests on AMD and ARM are needed for Orc-based optimised volume scaling?

2011-03-10 Thread Arun Raghavan
Hi Paul, On Thu, 2011-03-10 at 13:02 +0100, Paul Menzel wrote: Dear Arun, your commit messages of commit 4cd90d9e [1] says the following. … Since I haven't been able to test on other architectures, the Orc code is only used when MMX/SSE* is present. This can be

[pulseaudio-discuss] [RFC] Pulseaudio jack sense

2011-03-10 Thread Margarita Olaya
Hi, I have some initial code for jack sense implementation, the approach is to listen /dev/input/eventX and pass that data as argument to a new module called module-jack-detect where a thread wakes when the jack has been inserted. Using the current code I'm able to catch jack insertion and

Re: [pulseaudio-discuss] [RFC] Pulseaudio jack sense

2011-03-10 Thread David Henningsson
On 2011-03-10 22:47, Margarita Olaya wrote: Hi, I have some initial code for jack sense implementation, the approach is to listen /dev/input/eventX and pass that data as argument to a new module called module-jack-detect where a thread wakes when the jack has been inserted. Using the current