Comment # 20 on bug 1163046 from Felix Miata

Given the infrequency of having sound just work in a wide variety of
environments, and not just in Tumbleweed and Leap, sound configuration is
obviously too complex for automagic configuration. Thus there needs to be some
kind of official documentation that suggests a path to finding success, walking
through the booby traps involved in making it work, something to translate
output from alsa-info.sh and aplay -l into steps in configuration, what plughw
and card 1: HDMI [HDA Intel HDMI], device 9: HDMI 3 [HDMI 3] mean, something to
explain why 2 or 5 or 7 or more sound devices and subdevices exist, how to
choose, and enumeration of the places where sound configuration is stored, so
that an admin's need for mousing around diverse user interfaces is mitigated.
When it's all done, a process that worked should be able to be replicated with
minimal effort, at most copying and tweaking one or two files if necessary.

Or,  enable YaST to handle these all things, or if not all, at least point to
pavucontrol or alsactl or whatever else where necessary, and announce what it's
actually doing when clicking on test. Isn't YaST a major reason why people come
to openSUSE in the first place, and to stay with it?

A wiki isn't much use when no mere mortal users with documentation skills
understand how the pieces fit together enough to populate it usefully.