[Alsa-user] asound.state
Where does the stuff in this file actually come from? Does alsalib
interrogate the sound card driver for all this info, and then translate it
into this human-readable form? Or is some of this file created by a human
in the first place, in order to provide alsalib with additional
information that can't be obtained from the driver?
For instance, my Intel sound system with a Realtek ALC888 codec includes
the following item:
control.25 {
iface MIXER
name 'IEC958 Playback Switch'
index 16
value false
comment {
access 'read write'
type BOOLEAN
count 1
}
}
Is "25" the physical number of something, or just an arbitrary array
index? Is "MIXER" a name known to the driver, built into alsalib, or
arbitrary? How about "IEC958 Playback Switch"? What about "index 16"? Is
the "access" item alsalib's way of telling me that this is a read/write
variable, which it knows from the driver, or is it somebody's way of
telling alsalib that this is a read/write variable?
--
Ciao, Paul D. DeRocco
Paulmailto:pdero...@ix.netcom.com
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] asound.state
Paul D. DeRocco wrote: > Where does the stuff in this file actually come from? It's written by "alsactl store". > Does alsalib interrogate the sound card driver for all this info, and then > translate it into this human-readable form? Yes. Regards, Clemens -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140 ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] asound.state Q if Lee Revell is reading this
Just a little query, as I know you use ubuntu. I'm trying to help someone with a sound problem on Ubuntu. he can't access alsamixer on the CLI. Ironically on booting my Kubuntu install (Dapper) , I too have no access to alsamixer, and consequently no sounds. I've had problems with the asound.state file before on various distros, so renamed the one in /var/lib/alsa to asound.state.old. Then I shut the machine down, and booted up again. Now I have access to alsamixer on the CLI again, and sounds are working. The question is though. What has happened to the asound.state file, which is apparently being used for the various settings on alsamixer. I can no longer find an asound.state file. Looking in /var/lib/alsa, all I find there is the asound.state file, that I renamed to asound.state.old, and there is nothing in the /etc directory where the asound.state file is on fedora distros. Any ideas where I can find the asound.state file on Kubuntu/Ubuntu btw. I have been experimenting on various distros with upgrading the alsa driver, just to see how easy it is. The alsa driver on Kubuntu Dapper is 1.0.10, and I upgraded the alsa driver for one of the kernels on Dapper to 1.0.15. I'm not sure if I may have created problems here, but is just a bit more info. Mind you, I've also upgraded the alsa driver on other distros, and havn't had any sound problems after doing so. Thanks for any suggestions. Nigel. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
