the template i meant above is the basic designs of control naming, and i don't mean that this is the kernel issue. (well, in the case of "master" volume, we cannot handle it simply by abstraction but need a new control, though.)
i believe it's just a question which is easier to implement. i agree that almost all cases can be solved by a higher abstraction, and i prefer that, too.
Yes, I think that we might use the kernel to create the "user defined" controls which can be created from the user space. In this case, we can nicely do all kinds of abstractions in the user space.
Jaroslav
I agree, that the less work done in kernel space the better.
I also think it is a good idea to have user space creating virtual controls (abstractions), but of course, the values/state given to these virtual controls has to be stored somewhere, and kernel space will probably have to store them, otherwise their state will not survive across application stop/start.
How would one start supporting some of the multichannel features availiable on some cards. E.g. surround sound 7.1 (8 channels)
I think we should take the names for the speakers from the AC3 or DTS specifications.
AC3 names: -
Left
Center
Right
Left Surround
Right Surround
Low Frequency Effects.
DTS names: - Left Center Left Center Center Right Right Surround Left1 Surround Right1 Surround Left2 Surround Right2 Rear Left Rear Center Rear Right Overhead Low Frequency Effects.
We would also need to add: - Headphones
So, I conclude from this, that maybe we should add to the config files a way for the user to say what is plugged into what, and name it themselves.
Cheers James
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel