Public bug reported:

The new designed gnome-volume-control manager has now moved completely
to depending on Pulse Audio instead of Alsa. The problem is Pulse Audio
sits on top of Alsa and does not have expose controls to mixers at the
ALSA level or have mixers that correlate to those controls.

Part of the problem is Pulse Audio's inability to expose multiple codecs
(mixers) on a single device.

This ends up with a regression for the following use cases in Jaunty:

Microphone / Input
--------------------------
1) If sound card has more then one mic codec, user has no way to choose which 
microphone to choose from.  
     *This mainly effects laptop users who have both built-in mic & front mic 
plugin. User needs the ability to
      toggle which mic input they want to take in from.

2) Many sound cards that have "mic boost" for the mic input(s) can
nolonger be manipulated.

3) User have no way to choose to record from a "line in" codec or if there are 
multiple "line in" codecs 
   supported by the sound chip.
      *This is more so on desktop machines. But there are many laptops with 
"line in" support

Output
---------
1) Users unable to manipulate IEC958 mixer for HDMI audio, Optical Output, or 
digital Coax
       * All need to be exposed
       * related LP#317292

2) Users unable to manipulate volumes for headphone, front, back, & LFE codecs
        * Currently headphone volume starts out at 70% at the ALSA level. No 
way to manipulte this.
        * This is also case where all mixers should not start out at max 
volume. LFE is the subwoofer
           volume has to be independent of other mixers. If you have a full 
stereo system and
           a receiver with a subwoofer, even though you have a master volume, 
you leave the
            subwoofer at it's own independent volume so it will not over take 
the other audio, and
           make your house shake like mad.

3) If a program manipulates the volume or mutes a mixer at the ALSA level. The 
users has no way
    to know and manipulate it. 
         * Many programs will directly manipulate the ALSA mixer. IF something 
happens or it
            leaves it in an undesired state. The user has no way to fix it.

4) Users cannont toggle switches presented at the ALSA level
         * Many sound cards have switches to enable/disable many features.
         * Some have the ability to toggle the headphone or speaker on and off.
         ***this may not really need to be exposed as long as switches are 
enabled
             on startup

Apps
---------
1) Most thrid party application who manipulate the volume will go directly to 
the ALSA level.
     Example:
                 * Skype
2) Gnome-sound-recorder  is nolonger able to select an input to record from. It 
is only presented
    with "Capture"

3) Any gstreamer Application such as Totem has no way to enable 3+
channel Audio through Pulse Audio.

These are just the cases that just the cases I have been able to
compile. There are most likely more.

** Affects: gnome-media (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: pulseaudio (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
       Status: New

-- 
gnome-volume-control in Jaunty has many use case regressions with move to Pulse 
Audio
https://bugs.launchpad.net/bugs/322909
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.com/mailman/listinfo/ubuntu-bugs

Reply via email to