asound.state

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
Paul                mailto:pderocco@xxxxxxxxxxxxx


------------------------------------------------------------------------------
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&iu=/4140
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user



[Index of Archives]     [ALSA Devel]     [Linux Audio Users]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]

  Powered by Linux