This bug affects me to.
--
When volume <= 15% the alsa master is at 0%
https://bugs.launchpad.net/bugs/448528
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.
I had a chat in the #pulseaudio IRC channel and they convinced me that
the problem is ALSA.
If the volume is mute at 0% then it should be reported as mute also in
the decibel data (with a value lower than -200 db).
Is there an ALSA expert which can try to make a patch for our sound
cards?
--
Whe
On Wed, Mar 31, 2010 at 10:33 PM, Omega wrote:
> First solution worked for me on an Inspiron 9400. This is still a
> problem with the 10.04 beta. We seriously just need to get this fixed
> guys. My ears can't take it every time I upgrade! ;)
Please file a new bug using ubuntu-bug alsa-base so t
https://wiki.ubuntu.com/DebuggingSoundProblems/KarmicCaveats#Volume%20range%20anomalies
First solution worked for me on an Inspiron 9400. This is still a
problem with the 10.04 beta. We seriously just need to get this fixed
guys. My ears can't take it every time I upgrade! ;)
--
When volume <
** Tags added: karmic
--
When volume <= 15% the alsa master is at 0%
https://bugs.launchpad.net/bugs/448528
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.co
After talking again to pulseaudio developers, they are sure that the bug is in
ALSA.
And they are also sure that this bug will be fixed here rather than by ALSA
developers.
Of course I still haven't understood what should be done.
** Changed in: alsa-driver (Ubuntu)
Status: New => Incompl
Sorry, to tell the truth I didn't understand, the explanations are too
technical for me. Read the upstream ALSA bug and tell us what do you
think about it.
--
When volume <= 15% the alsa master is at 0%
https://bugs.launchpad.net/bugs/448528
You received this bug notification because you are a me
** Changed in: pulseaudio
Status: Unknown => New
--
When volume <= 15% the alsa master is at 0%
https://bugs.launchpad.net/bugs/448528
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
How? PA clearly uses ALSA's exposed dB information.
** Changed in: alsa-driver (Ubuntu)
Status: Invalid => New
** Changed in: pulseaudio (Ubuntu)
Status: New => Incomplete
--
When volume <= 15% the alsa master is at 0%
https://bugs.launchpad.net/bugs/448528
You received this bug n
After talking with ALSA upstreaml, the bug seems to be caused by
pulseaudio
** Bug watch added: PulseAudio sound server #580
http://pulseaudio.org/ticket/580
** Also affects: pulseaudio via
http://pulseaudio.org/ticket/580
Importance: Unknown
Status: Unknown
--
When volume <= 15
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => Invalid
--
When volume <= 15% the alsa master is at 0%
https://bugs.launchpad.net/bugs/448528
You received this bug notification because you are a memb
** Bug watch added: ALSA Bug Tracker #4956
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4956
** Also affects: alsa-driver via
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4956
Importance: Unknown
Status: Unknown
--
When volume <= 15% the alsa master is at 0%
h
This is an alsa bug.
Alsa should report that 0% volume corresponds to -inf dB, but the value
reported is -48 dB
** Package changed: linux (Ubuntu) => alsa-driver (Ubuntu)
--
When volume <= 15% the alsa master is at 0%
https://bugs.launchpad.net/bugs/448528
You received this bug notification bec
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: pulseaudio
When I lower the volume to 15% in the gnome volume control applet, the
alsa master volume is set to 0%.
ProblemType: Bug
Architecture: amd64
ArecordDevices:
List o
I've filed a bug against pulseaudio, they told me that the problem is that our
audio card gives wrong information about current dB value.
Running alsamixer shows the current dB value ,which in my case is -48.0 dB. The
device should report another value when it's mute.
What is your value?
--
Whe
** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
When volume <= 15% the alsa master is at 0%
https://bugs.launchpad.net/bugs/448528
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
The first fix listed there worked for me. Thanks!
On Fri, Nov 13, 2009 at 3:39 PM, Daniel T Chen
wrote:
> Please see
> https://wiki.ubuntu.com/DebuggingSoundProblems/KarmicCaveats#Volume%20range%20anomalies
> specifically the portion regarding passing control=foo to
> module-alsa-sink.
>
> --
> W
Please see
https://wiki.ubuntu.com/DebuggingSoundProblems/KarmicCaveats#Volume%20range%20anomalies
specifically the portion regarding passing control=foo to
module-alsa-sink.
--
When volume <= 15% the alsa master is at 0%
https://bugs.launchpad.net/bugs/448528
You received this bug notification
I have been experiencing this same bug ever since I installed Karmic.
--
When volume <= 15% the alsa master is at 0%
https://bugs.launchpad.net/bugs/448528
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/33437815/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/33437817/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/33437819/BootDmesg.txt
** Att
20 matches
Mail list logo
