MMarking wrote on 2009-12-02: #36
* Output of cat /proc/asound/card0/codec#0 (13.1 KiB, text/plain)
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 3/3
Subdevice #0: subdevice #0
Subdevice #1:
Is this still being investigated? Since I've upgraded to Lucid, I can
confirm weird behaviour when adjusting volume levels either by the new
volume applet in Gnome (indicator) or by media keys. This is very
annoying since it renders volume control rather useless. Concerning the
system running here
I confirm this issue for gnome-volume-control 2.28.1 (Karmic). As
workaround I use 'gnome-alsamixer' to switch Headphone Jack Sense. BTW:
even an About dialog is missing, use --version instead.
$ sudo lspci -vv
...
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW
** Changed in: gnome-media (Ubuntu)
Status: New = Confirmed
--
future gnome-volume-control 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
unfortunately gnome-alsamixer is far less polished than old gnome-
volume-control. For example: https://bugs.launchpad.net/ubuntu/+source
/gnome-alsamixer/+bug/331460
--
future gnome-volume-control has many use case regressions with move to Pulse
Audio
https://bugs.launchpad.net/bugs/322909
You
There is still no complete frontend to alsamixer in current gnome. A
thing where you can see and tweak all channels and switches your
soundcard support. Regression is still exists. Pulseaudio tools are too
generalized.
--
future gnome-volume-control has many use case regressions with move to
** Changed in: pulseaudio (Ubuntu)
Status: New = Invalid
--
future gnome-volume-control 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.
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 3/3
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
card 0: Intel [HDA Intel], device 1: AD198x Digital [AD198x Digital]
Subdevices:
IMHO, regardless this is caused by hardware or not, the behaviour of
Pulseaudio's volume control is too complicated. It is not clear which tracks
are controlled and in what order. After upgrading to Ubuntu 9.10 sound and
media keys worked out of the box (good job for this). However, the
With a ThinkPad X60, to avoid distortion when the Master volume is at
100% the PCM volume must be at most 68% (-3dB), otherwise clipping
occurs. Historically, I always lowered the PCM to this level. The effect
is manifest using the Multimedia Systems Selector output test to produce
a sine wave,
Please allow me to reiterate that this symptom is not a PulseAudio bug
but a hardware one that can be worked around in the sound driver,
linux (with varying degrees of success for given hardware). The fact
that we have to work around it in PulseAudio (either by passing
ignore_dB=1 to module-udev*
This is not a bug in hardware. This is rather a weird feature: In some
soundcards PCM chanel gain range is not -X~0, but rather -X~+Y. A kind of
digital boost.
On my Realtek NVidia CK804 range of PCM chanel is -34.5~12.0. So it must not be
set on maximum in normal circumstances, but rather is
Daniel, the patch you linked fixes the problem with the pcm slider but not the
problem with the Front slider. In order to resolve this one, and make stay
where i put it, I asses to /usr/share/pulseaudio/alsa-mixer/paths/analog-output
the lines:
[Front]
volume = ignore
--
future
In Karmic Beta the only reasonable way to control audio without
pulseaudio - is with text-based alsamixer.
It is a disaster!
There is no sound applet with mixer
alsamixergui is outdated
gamix has a buggy gui geometry issues and meter drawing inconsistencies
gnome-alsamixer does not recognize
also, some gnome apps, like Totem, can't output sound. But others, like
aisleriot, do.
Sound output is set to alsa in Multimedia Systems Selector. But there is no
more audio preferences tool to set other categories to alsa, like it was in
jaunty.
--
future gnome-volume-control has many use
Moving from oem-priority as this bug has been split up into remaining
bugs.
--
future gnome-volume-control 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
This bug has been split into separate bugs. In Karmic many issues are
addressed. But there are still many not addressed. These bugs reflect
issues still pending:
1) Pulse audio control panel does not allow for 3, 5.1, 6.1, 7.1 speaker
multi channel audio if supported by sound card
LP#440253
2)
** Changed in: pulseaudio (Ubuntu)
Assignee: Canonical Ubuntu QA Team (canonical-qa) = (unassigned)
--
future gnome-volume-control 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
I have a related issue:
Every time I change the master volume using my laptop media keys (lg s1, ac97
audio) or using an app slider, it resets pcm front volumes to 100%.
This means that I get crackling audio almost immediately (max pcm and front
does that), and I must keep master volume down
On Thu, Oct 1, 2009 at 7:19 PM, Yotam Benshalom bensha...@gmail.com wrote:
Every time I change the master volume using my laptop media keys (lg s1, ac97
audio) or using an app slider, it resets pcm front volumes to 100%.
This means that I get crackling audio almost immediately (max pcm and
Thank you Daniel, you are an ear-saver! Your workaround gave me my audio
back.
Just in case it is not clear from the link, the way to revert the pcm
front volume sliders jump to 100% with every change to master volume,
resulting in crackling sound is:
1. sudo gedit
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) = Canonical Ubuntu QA Team (canonical-qa)
--
future gnome-volume-control 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
@Psy[H[]
This seems to be what Fedora 11 does. They still keep the gnome volume
mixer for alsa but call it Advanced Volume settings
Also you have pulse audio controls app (pakage pavucontrol ). Has
a configuration tab that will control profiles for a card. Seems worth
looking at for
It also would be nice to preserve modularity: ability to remove
pulseaudio without consequences. Right now many important packages
depend on pulseaudio components.
--
future gnome-volume-control has many use case regressions with move to Pulse
Audio
https://bugs.launchpad.net/bugs/322909
You
there are several gtk gui apps to alsamixer. One of them could be used,
launched through menu of sound applet.
--
future gnome-volume-control 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
the ubuntu team has decided to move forward for karmic rather than
distro patch code which is not being worked upstream for over a cycle
now
--
future gnome-volume-control has many use case regressions with move to Pulse
Audio
https://bugs.launchpad.net/bugs/322909
You received this bug
@Sebastien
Since this decision has been made, how does the ubuntu team plan to deal
with all the regressions caused by this decision?
--
future gnome-volume-control has many use case regressions with move to Pulse
Audio
https://bugs.launchpad.net/bugs/322909
You received this bug
There is no special ubuntu plan about that so far, first step would be
to open different bugs about each issues so those can be upstream and
tracked in a efficient way
--
future gnome-volume-control has many use case regressions with move to Pulse
Audio
https://bugs.launchpad.net/bugs/322909
This has returned in 9.10 alpha builds. Yet none of the issue have been
addressed.
** Also affects: oem-priority
Importance: Undecided
Status: New
--
future gnome-volume-control has many use case regressions with move to Pulse
Audio
https://bugs.launchpad.net/bugs/322909
You received
Indeed it has returned in harmic. I have to run sound wide open. Its
starting muted. Controls are missimg. To name a few issues.
--
future gnome-volume-control has many use case regressions with move to Pulse
Audio
https://bugs.launchpad.net/bugs/322909
You received this bug notification
** Also affects: gnome-media (Baltix)
Importance: Undecided
Status: New
--
future gnome-volume-control 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
** Changed in: gnome-media (Ubuntu)
Importance: Undecided = Low
** Changed in: gnome-media (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
--
future gnome-volume-control has many use case regressions with move to Pulse
Audio
https://bugs.launchpad.net/bugs/322909
I personally prefer OSSv4 over having to use alsa and a sound server.
Now I can't control my volume at all without some really difficult
keymappings. Thanks a bunch! :D
--
future gnome-volume-control has many use case regressions with move to Pulse
Audio
https://bugs.launchpad.net/bugs/322909
No, it's WONTFIX because the UI issues still exist in a future
development version.
--
future gnome-volume-control 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
This is not a jaunty issue any more, since we reverted to the intrepid
GUI for jaunty.
** Summary changed:
- gnome-volume-control in Jaunty has many use case regressions with move to
Pulse Audio
+ future gnome-volume-control has many use case regressions with move to Pulse
Audio
** Changed
Martin, wouldn't it more accurately be Invalid then, not Won't Fix?
There is nothing to (not) fix if the behavior has been reverted.
--
future gnome-volume-control has many use case regressions with move to Pulse
Audio
https://bugs.launchpad.net/bugs/322909
You received this bug notification
36 matches
Mail list logo
