Bug 10963
Summary: | ymfpci: can't play sounds with bitrate 44100 | ||
---|---|---|---|
Product: | Drivers | Reporter: | Akkana Peck (akkzilla) |
Component: | Sound(ALSA) | Assignee: | Jaroslav Kysela (perex) |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | CC: | bunk, tiwai |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.25.7 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Attachments: |
patch to revert to 2.6.23.17
Fix initialization of 44.1kHz volume |
Description
Akkana Peck
2008-06-22 11:52:03 UTC
Bugzilla won't let me attach the mp3 (undef error - Undefined subroutine Fh::slice at data/template/template/en/default/global/hidden-fields.html.tmpl line 58), but if you need a sample, I've put it for now at http://shallowsky.com/bugs/mocker.mp3. Created attachment 16579 [details]
patch to revert to 2.6.23.17
I'm sure this patch is more than is really needed, but it does work, in case anyone else needs it.
Do you set "Wave Playback Volume" properly? If you still have the problem after setting "Wave" volume, run alsa-info.sh with --no-upload option and attach the generated file for further analysis. The script is found at http://www.alsa-project.org/alsa-info.sh Thanks. Yes, that's it. I installed alsamixergui and it shows two fields identically named "Wave"; when I boot off the problematic kernels, the first "Wave" field is at 100% but the second one is at zero. Setting the second Wave to 100% cures the problem for that session, but it's back at zero at the next reboot. I don't know what mixer app you are using, but one is "Wave Playback Volume" and another is "Wave Capture Volume". Looking through the code, I found that the initialization for 44.1kHz volume is missing. Could you try the patch below? Created attachment 16623 [details]
Fix initialization of 44.1kHz volume
... and I must have been blind without a coffee. alsamixergui could be buggy regarding the handling of the same playback/capture volume. Check alsamixer instead. (The patch is still valid, though.) First, the patch works great. I can play the problematic clips with it without needing to adjust anything. With the patch, alsamixergui still shows the second Wav field at zero (and the first at 100). alsamixer (non-gui), if I type F5 to show both Wav fields, shows Wav Playback at 100 and Wav Capture at 0. So I guess it's Wav Capture that needed to be moved off 0 in order to hear sound in 2.6.25 without the patch, however odd that sounds. fixed by commit 4a3b6983232cd296ea260e06461d031f10065d63 |