Description of problem: I'm using a 5.1 hardware device using the snd-firewire-speakers module. It has no hardware level controls. The balance slider works correctly. The fade slider does not. Moving it toward rear mutes all channels. The subwoofer slider does nothing. The datastream sent to the device for the subwoofer channel is always silent. Version-Release number of selected component (if applicable): gnome-media-2.91.6-10.fc16 How reproducible: always Steps to Reproduce: 1.build snd-firewire-speakers module, load it. 2.Wait for pulseaudio to notice the new sound device. 3.Go to System->Preferences->Sound and make it the default output device on the Hardware tab. 4. Start some music playing 5. Go to the Output tab and attempt to manipulate the Fade and Subwoofer sliders. 6. (optional) watch the audio data being sent to the device with Nosy or a similar sniffer tool. Note that the subwoofer channel is always 000000 I have not tried this with a PCI 5.1 sound card. This may only happen on devices that have no hardware level controls. Actual results: Sliders do not work correctly. Expected results: Sliders work correctly. Sound is output on the subwoofer channel. Additional info: I have the hardware here in Westford if you want to poke at it in person.
This is a problem in PulseAudio as we correctly check whether it can fade, or has an LFE channel. Lennart says that the mixer channel names are probably broken.
Most likely tha channel names in the alsa mixer are wrong. Might be worth verfying that with "alsamixer -c0".
I switched to using the on-motherboard 5.1 sound card rather than the FireWire device, to remove the experimental firewire driver from the equation. I started alsamixer -c0 in one xterm, with the sound controls next to it, then opened another xterm to run speaker-test and ogg123. speaker-test worked as expected, showing that it could output sound to all six channels. Alsamixer shows the following controls: Master PCM(s) Front(s) Surround(s) Center LFE Side 3(s) Line(s) Mic(s) Mic Boost(s) S/PDIF (toggle) S/PDIF Default PCM(toggle) Beep(s) Stereo controls are marked with (s). With ogg123 running, adjusting the balance slider had no effect on the alsa mixer controls, although the sound audibly shifted between LF and RF. The Fade mixer moved by itself toward Front and back to center as I adjusted the balance. Adjusting the Fade slider toward Front had no effect anywhere. Moving it toward Rear caused the Master mixer control to lower, until it reached 0, then the PCM control abruptly lowered toward 0 as well, at full Rear both Master and PCM were 0. Adjusting the Subwoofer control had no effect whatsoever on the alsa mixer output. No output from ogg123 went to the LFE channel, ever. rerunning ogg123, I tried manually adjusting the mixer controls in alsamixer. Adjusting the Master control changed the volume of the LF, RF and Center outputs, and caused the Subwoofer slider to move toward Minimum as I lowered Master, and toward Maximum as I raised it. Adjusting PCM did not work well, as something kept resetting it, while changing Master. PulseAudio? Adjusting Front changed the volumes of LF and RF as expected. As it was lowered, the Fade slider moved toward Rear, and back to center. Adjusting Surround changed the volumes of LR and RR as expected. The Fade slider never moved. Adjusting Center changed the volume of the center channel. Lowering it also caused the Fade slider to move toward Rear. Adjusting the LFE slider had no effect on the silent LFE channel, but caused the Subwoofer slider to move toward Minimum and Maximum as if it was having some effect.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.