Red Hat Bugzilla – Bug 525882
Aureon 5.1 driver exposes incorrect dB information for "Master" slider
Last modified: 2011-06-27 10:25:41 EDT
Description of problem:
When playing music using an application such as Rhythmbox, the volume jumps up suddenly and momentarily when a system sound plays. For example, enabling window and button sounds causes the volume to jump up during a button or window sound while playing music through Rhythmbox.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Sound Preferences->Sound Effects->Enable window and button sounds
2. Play music through Rhytmbox
3. Click on menus, hover to let tooltips open, maximize/restore windows
volume jumps lounder for a split second while the system sound is playing.
volume should remain constant.
Hmm, this is most likely an artifact caused by flat volume logic where the hw volume change and the PCM volume adjustment do not happen at the exact same time. We probably should try harder to align these more closely.
lennart, is this related to / a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=518512 ?
Fedora Bugzappers volunteer triage team
Adama, I don't think so.
This definitely needs fixing for F-12.
*** Bug 533352 has been marked as a duplicate of this bug. ***
*** Bug 531754 has been marked as a duplicate of this bug. ***
Please note that bug 533352 was not about where two sounds were playing at once. It was simply when skipping tracks in a media player.
Upstream bug report is here: http://www.pulseaudio.org/ticket/611 (for some bizarre reason I can't add in an External bug reference to the bug report).
So, these are actually two bugs.
One bug is that while an event sound or suchlike is playing a music stream might be incorrectly attenuated on cards where ALSA provides incorrect dB information. That bug needs to be fixed in the drivers, e.g. in Bastien's case in the USB audio driver as a quirk for the Aureon 5.1.
The other problem is that hardware mixer volume changes and software PCM volume changes don't necessarily happen at the exact same time, so that you can hear a very very short artifact where the mixer volume change was applied and the PCM stream volume change wasn't, or vice versa.
The first issue is discussed in this thread on alsa-devel right now:
The second issues what this upstream bug is about:
I will now rename this bug so it online covers the first issue, specifically for the Aureon 5.1, which I believe is the bigger problem. The second issue should probably be discussed in the upstream bug.
Reassigning to the kernel/alsa, because all that's missing to fix at least in the Aureon case is to add the measured dB data linked in the mail above as a quirk to the usb driver.
http://thread.gmane.org/gmane.linux.alsa.devel/70545/ is probably easier to read through.
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.
More information and reason for this action is here:
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.