That version is no more supported
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/533921
Title:
[lucid regression] HDA:
I believe Daniel Chen set this to WontFix prematurely. This report
isn't wahh, I don't like how pulseaudio works. It's an actual bug.
When I set the volume with gnome's mixer applet or with pavucontrol, and
pulseaudio's level reaches 15%, then Alsa's Master channel reaches
zero. Therefore, at
Sorry, forgot to note that I'm seeing this behavior on a system running
Maverick, packages fully updated as of a few hours ago.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/533921
Title:
[lucid
@Mike Are you using the same hardware as the original reporter, Toby?
If not, you should file a separate bug report against alsa-driver
(`ubuntu-bug alsa-base`).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So is there a way to differentiate between the codecs and controllers
such that the dB measurements can be used for my specific combination?
--
[lucid regression] HDA: pulseaudio volume control sets alsa master to 0 when
still at 15% (incorrect db data?)
https://bugs.launchpad.net/bugs/533921
Sure; see the individual codec dumps in /proc/asound/card*/codec*
On Jul 14, 2010 4:31 AM, Maarten Bosmans mkbosm...@gmail.com wrote:
So is there a way to differentiate between the codecs and controllers
such that the dB measurements can be used for my specific combination?
--
[lucid
I have an HDA Intel (ICH 7) soundcard on a Samsung NC10 netbook.
With the pulseaudio dbverify utility I verified that the dB values for my
soundcard are wrong. The Master mixer control is OK, but the PCM mixer (with
fine-grained steps 0-255 of 0.2 dB each) seems off.
If this can be corrected,
The endpoint value should match, but the rest is codec- and
controller-dependent.
On Jul 13, 2010 11:41 AM, Maarten Bosmans mkbosm...@gmail.com wrote:
I have an HDA Intel (ICH 7) soundcard on a Samsung NC10 netbook.
With the pulseaudio dbverify utility I verified that the dB values for my
My computer is a Lenovo 3000N100; specifically a 0768-04U. It has the
ALC 861-VD sound card.
My following another thread I found the following:
Edit (use sudo) /etc/modprobe.d/alsa-base.conf
by adding the line
options snd-hda-intel model=3stack
to the end of the file. Restart. No promises,
I've not been able to use Lucid because of this. And it looks like
Karmic won't work either. I'm not an expert, so would require detailed
instructions on how to get info to you; but would certainly be willing
to do that.
My computer is a Lenovo 3000N100 with the Intel ALC861VD sound processor
This issue also affects me.
The audio card that I use, as given by 'lspci -nn' is:
00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD
Audio Controller [8086:284b] (rev 02)
Attached is a sceenshot showing the audio levels being different in
AlsaMixer and in the PulseAudio
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/40424485/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/40424486/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/40424487/BootDmesg.txt
**
http://pulseaudio.org/wiki/PulseAudioStoleMyVolumes
** Package changed: alsa-driver (Ubuntu) = pulseaudio (Ubuntu)
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: pulseaudio (Ubuntu)
Status: New = Confirmed
** Also affects: pulseaudio (Ubuntu Lucid)
I read the document, but it didn't really explain the bug; I understand
how the logic works, but I don't understand how pulseaudio makes the
error. Unless, of course, the db data is suddenly wrong, or if there is
a bug in pa's implementation of the logic on this hardware. It's
curious, though,
I intend to freeze as much of the userspace audio stack as possible
before Beta 1. You should provide a verbose PA log and carefully check
for dB output from snd_pcm_dump(). Furthermore, unless you intend to
chase this one yourself, this symptom is not the highest priority audio
bug.
--
[lucid
15 matches
Mail list logo
