Summary: | media-libs/alsa-lib-1.0.14a - no sound with ALSA_PCM_PLUGINS="" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Grzegorz {NineX} Krzystek <ninex> |
Component: | Current packages | Assignee: | Gentoo ALSA team <alsa-bugs> |
Status: | VERIFIED INVALID | ||
Severity: | normal | CC: | gentoo, jakub, lefsha, leonidp.lists, wltjr |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Grzegorz {NineX} Krzystek
2007-06-27 19:53:38 UTC
post the output of emerge -pv =media-libs/alsa-lib-1.0.14a [ebuild R ] media-libs/alsa-lib-1.0.14a USE="midi -alisp -debug -doc" ALSA_PCM_PLUGINS="-adpcm -alaw -asym -copy -dmix -dshare -dsnoop -empty -extplug -file -hooks -iec958 -ioplug -ladspa -lfloat -linear -meter -mulaw -multi -null -plug -rate -route -share -shm -softvol" 0 kB wirld but it seems that dmix dosn't work when i set output device to hw:0,0 in audacious music are plaing correctly (In reply to comment #3) > wirld but it seems that dmix dosn't work when i set output device to hw:0,0 in > audacious music are plaing correctly Because your ALSA_PCM_PLUGINS is empty as you can see above (despite the fact that all the plugins are enabled by default in base profile). Are you using USE="-*" in your make.conf? oops my fault (In reply to comment #4) > (In reply to comment #3) > > wirld but it seems that dmix dosn't work when i set output device to hw:0,0 in > > audacious music are plaing correctly > > Because your ALSA_PCM_PLUGINS is empty as you can see above (despite the fact > that all the plugins are enabled by default in base profile). Are you using > USE="-*" in your make.conf? > This is invalid. ALSA_PCM_PLUGINS should not have any effect from a useflag as they are to be defined seperately in make.conf reopen this bug and leave it to the appropriate herd. They are expanded to use flags via the USE_EXPAND mechanism. If you disagree with the behaviour, file a portage bug (assuming there is not one there already). The alsa package has no control over this behaviour. *** Bug 183664 has been marked as a duplicate of this bug. *** Just one question... in earlier portage days the behavior seemed to have been "expand to everything if unset". When has that changed? I noticed that among others with gphoto2 and the CAMERAS variable. (In reply to comment #9) This has nothing to do w/ behaviour change. You've explicitely *un*set all the default use-expanded flags by sticking -* to your USE. Don't do it if you don't know what you are doing. Yeah, just using -* since... 3-4years (back when gentoo did not include the year in the release numbers). Back in those days we did not have USE_EXPAND ;) Anyway, the change was in fact the introduction of the ALSA_PCM_PLUGINS useflags in 14a over 14_rc3, and the problem was me not looking with enough detail to the emerge -auvDNt world output. No problems ;) - now back to the e17 update. *** Bug 184780 has been marked as a duplicate of this bug. *** *** Bug 186365 has been marked as a duplicate of this bug. *** Re-opening bug for resolution :) Ok, it looks as if these plugins are no longer optional. IMHO they should not be optional anymore, flags removed etc. asym dmix empty softvol Before alsa-lib-1.0.14a this worked ALSA_PCM_PLUGINS="iec958 ioplug plug" Now I have to have set ALSA_PCM_PLUGINS="asym dmix empty iec958 ioplug plug softvol" Even though alsa-lib builds without those plugin flags set. Till we have a use case where it works less those flags. They should be dropped as flags, and plugins included all the time. Or by default at min, prefixing flags with a no. Discussed on IRC, this is a separate matter which has no relation to setting ALSA_PCM_PLUGINS to "". Closing. |