[Lucid] Front, Surround, LFE, and Center volume meters are default muted with 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01) sound card

[Attila Hammer]

Dear Developers,

In Ubuntu 10.04.3 release if an user booted with the live CD, default the live system with following volum,e meters are default muted, I copyed amixer names:
'Front',0
'Surround',0
'Center',0
'LFE',0
If I launch with GNOME Volume Control preference tool, mincreasing the output slider and uncheck the mute checkbox, the problem is resolved.
Of course, this problem fixing is important for a11y related, because a screen reader user is important to default hear the screen reader audio output.
I don't no yet this problem are present with newest Ubuntu releases this soundcard chipset, and I not often possible to use this machine with testing this problem.

I attaching two amixer text file, first file is showing the original result, second shoving the results after I unchecked the mute checkbox with GNOME Volume Control preference tool.

To easyest your work, I doed a diff output with two text file with diff -u command, see the results:
--- hang1.txt 2011-09-29 13:26:00.941940936 +0200
+++ hang2.txt 2011-09-29 13:27:00.877940898 +0200
@@ -8,32 +8,32 @@
   Playback channels: Front Left - Front Right
   Limits: Playback 0 - 255
   Mono:
- Front Left: Playback 255 [100%] [0.00dB]
- Front Right: Playback 255 [100%] [0.00dB]
+ Front Left: Playback 254 [100%] [0.20dB]
+ Front Right: Playback 254 [100%] [0.20dB]
 Simple mixer control 'Front',0
   Capabilities: pvolume pswitch penum
   Playback channels: Front Left - Front Right
   Limits: Playback 0 - 64
   Mono:
- Front Left: Playback 52 [81%] [-9.00dB] [on]
- Front Right: Playback 52 [81%] [-9.00dB] [on]
+ Front Left: Playback 64 [100%] [0.00dB] [on]
+ Front Right: Playback 64 [100%] [0.00dB] [on]
 Simple mixer control 'Surround',0
   Capabilities: pvolume pswitch penum
   Playback channels: Front Left - Front Right
   Limits: Playback 0 - 64
   Mono:
- Front Left: Playback 64 [100%] [0.00dB] [off]
- Front Right: Playback 64 [100%] [0.00dB] [off]
+ Front Left: Playback 64 [100%] [0.00dB] [on]
+ Front Right: Playback 64 [100%] [0.00dB] [on]
 Simple mixer control 'Center',0
   Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
   Playback channels: Mono
   Limits: Playback 0 - 64
- Mono: Playback 64 [100%] [0.00dB] [off]
+ Mono: Playback 64 [100%] [0.00dB] [on]
 Simple mixer control 'LFE',0
   Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
   Playback channels: Mono
   Limits: Playback 0 - 64
- Mono: Playback 64 [100%] [0.00dB] [off]
+ Mono: Playback 64 [100%] [0.00dB] [on]
 Simple mixer control 'Line Jack Mode',0
   Capabilities: enum
   Items: 'Mic In' 'Line In' 'Line Out'

Attila

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gnome-media 2.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-generic i686
Architecture: i386
Date: Thu Sep 29 13:37:52 2011
LiveMediaBuild: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1)
ProcEnviron:
 LANGUAGE=hu_HU:en
 LANG=hu_HU.UTF-8
 LC_MESSAGES=hu_HU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-media

[Attila Hammer (hammera)]

Hy,

I played little this volume meters in terminal when I restarted the live CD.
Because the testing machine with I reported this bug are connected only
two speakers, following amixer command resolves this problem:
amixer set 'LFE',0 on
After I ran this command, I begin hear Orca Screen Reader produced audio
outputs.

I think this problem is an Alsa related issue, but I am not full sure.
If I would like making a patch for resolve this bug, how can I begin?

Difficultest me this problem fix and testing, because I am not always
near this testing machine my work place. Usual I am working on my home,
the distance the testing machine with I found this problem and my home
is 68 KM.

My colleagues says me he's experiencing two other machines with similar
problems, perhaps different soundcard chipset and different volume
meters, Unfortunately when I tested this sound card not have enough time
looking the two other computers.
If I going next time my working place for example a meeting or
consultation, and testing the two other sound card, need reporting other
volume meters related problems with separate bugs?

Attila

[Attila Hammer (hammera)]

Hy,

I have got a last question:
In hungary I am developing a little derivative Ubuntu distribution for
visual impaired users since 2008 year, with provide basic visual
impaired profile and screen reader support with default. The
distribution name is BeLin.
If I would like decreasing this type problems until this type bug is not
fixed with various sound card drivers, possibleI doing a workaround
solution?
For example, how can possible detecting what defauld mixer track are
muted, or what mixer track volume level is 0?
I tryed determining under GNOME level the default audio mixer and
default mixer tracks, both two this topic related gconf keys are
returned empty values.
I tryed using following official gconf keys without luck:
/desktop/gnome/sound/default_mixer_device,
/desktop/gnome/sound/default_mixer_tracks

I would like doing for Orca Screen Reader a custom script. If the visual
impaired user machine for example muted the sound card default output
volume meter, and press a keystroke, I would like unmute absolute sure
the default output sound track.
Not only my hungarian visual impaired users oriented distribution need
resolving this problem temporary until this type problems not possible
fixing, for example the international Vinux distribution have similar
problems.
For example, Vinux distribution homepage is following:
http://vinuxproject.org/

Only screen reader users are critical important to have possibility to
unmute the default soundcard volumes. Of course, have various soundcard
manufacturers, various sound card chipsets, so possible this problem fix
with workarounds are impossible.
Both Vinux and BeLin already containing an Orca customization script,
with are provide changing master volume meter volume percentage, and
change master volume meter mute status. Unfortunately, various sound
card models are naming different the volume meters, and this type script
are not provide full good percentage.

Attila

[Attila Hammer (hammera)]

Hy,

For example, my desktop machine I reported an another soundcard volume
meter related bug with affected the Lucid branch awailable alsa-utils
package in 2010 I think, look following bugreport:
https://bugs.launchpad.net/bugs/564472

I think my other reported bug are fixed with Maverick repository, but
not applied the fix with Lucid branch for alsa-utils package.
I downloading now an Oneiric system to verify the newest Ubuntu release
producing my desktop machine equals issue my motherboard sound card or
not with master volume meter related.
Not have an audio volume meter related metabug with possible reporting
this type issues?

Attila

[Attila Hammer (hammera)]

Because my desktop machine have similar issue with an Nvidia integrated
soundcard related, I looked again what volume meters are muted default
when I booted with Ubuntu 10.04.3 live CD my desktop machine.
The results is very similar with I experienced the Intel N10 soundcard
related.
I only doed following:
1. After the desktop presented my screen, I opened GNOME Terminal, and
ran amixer >sound1.txt command to store original mixer values with a
text file.
2. I launch Sound preference tool, and uncheck only the mute check box,
not increased volume meters.
3. I ran again with amixer >sound2.txt command to generate new changed
volume meters with an another text file.
4. I ran diff -u sound1.txt sound2.txt command to generate a diff style
output what volume meters status are changed from off to on after I
unchecked the mute checkbox in Sound preference tool.

I attaching the sound1.txt, sound2.txt, and
sound-volumes-differences.txt files.
To easyest your work, I copyed diff output:
--- sound1.txt 2011-10-02 09:27:14.057861934 +0200
+++ sound2.txt 2011-10-02 09:28:24.398364608 +0200
@@ -42,25 +42,25 @@
    Playback channels: Front Left - Front Right
    Limits: Playback 0 - 31
    Mono:
- Front Left: Playback 0 [0%] [-46.50dB] [off]
- Front Right: Playback 0 [0%] [-46.50dB] [off]
+ Front Left: Playback 0 [0%] [-46.50dB] [on]
+ Front Right: Playback 0 [0%] [-46.50dB] [on]
  Simple mixer control 'Center',0
    Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
    Playback channels: Mono
    Limits: Playback 0 - 31
- Mono: Playback 0 [0%] [-46.50dB] [off]
+ Mono: Playback 0 [0%] [-46.50dB] [on]
  Simple mixer control 'LFE',0
    Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
    Playback channels: Mono
    Limits: Playback 0 - 31
- Mono: Playback 0 [0%] [-46.50dB] [off]
+ Mono: Playback 0 [0%] [-46.50dB] [on]
  Simple mixer control 'Side',0
    Capabilities: pvolume pswitch penum
    Playback channels: Front Left - Front Right
    Limits: Playback 0 - 31
    Mono:
- Front Left: Playback 0 [0%] [-46.50dB] [off]
- Front Right: Playback 0 [0%] [-46.50dB] [off]
+ Front Left: Playback 0 [0%] [-46.50dB] [on]
+ Front Right: Playback 0 [0%] [-46.50dB] [on]
  Simple mixer control 'Line',0
    Capabilities: pvolume pswitch penum
    Playback channels: Front Left - Front Right

After I done this three file generation, I reboot with live CD, and look
in terminal what volume meter status change resulting sound turning on
this sound card resulting I hear sound again.
When I ran amixer set 'LFE',0 on command, I hear sound again, because my
machine only have connected two speakers.

So you see, my desktop machine the Nvidia sound card related little
different volume meters are muted by default, but amixer set 'LFE',0 on
command result sound turning on too if two speakers are connected this
other sound card.
I try making a patch with merging this two bugreport fix with one patch.
When I done this fix, generating a custom live CD and testing two
machines the patch.
I attaching future this bugreport the patch, or the other bugreport Bug
564472)? What type fix you are accept future?
I attached the my deskt...

[Attila Hammer (hammera)]

Hy,

Please review this patch.
I generated a custom Ubuntu 10.04.3 live CD with containing the patched alsa-utils script in /sbin directory.
When I booted this custom live CD, my desktop machine Nvidia soundcard is not muted by default (see bug 564472 for details). I am absolute sure this patch will resolve the mute problem for this Intel N10 soundcard too.
I added both the Intel N10 soundcard experienced muted channels and the Nvidia soundcard experienced muted channels with the patch.

I have got a question if you accept this type fix with final patch and perhaps commit this fix Lucid and Oneiric branch:
What method are better to fix this problem? Use the switch_control method to only switch the muted status from off to on, or use the unmute_and_set_level method this new channels and setting for example with a 80% volume value?

Attila

[Attila Hammer (hammera)]

I try assigning this bug, if you are reviewing my now sent patch, and perhaps tell me what can need changing my patch to you final commit my fix.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "A possible solution to resolve with this soundcard experienced problem and for example an Nvidia soundcard experienced problem my desktop machine" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-sponsors please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

[dino99 (9d9)]

Closing that outdated report as EOL has been reached long time ago