SO..... in order to maintain the thread OT. The FFT Debate - and work tranche has been shoveled across to
Reworking FFT code
================================================== ========
Back to the crux of the thread: Making the sound setup do things we want!
Let's have a quick play with
alsactl
Let's have a look at a vaguely relevant man page
http://linux.die.net/man/1/alsactl
okay, done that? onwards...
The version on the kindle is wee bit old:
Code:
[root@kindle bin]# alsactl --version
alsactl version 1.0.13
So we best bear that in mind - as there are a few
bugs out there that have been noted in several versions subsequent to this, which does not preclude their undiscovered existence in this version...
Code:
[root@kindle root]# alsactl store -f /mnt/us/opt/sound/alsactl.state
(I added .txt to the version attached. .TXT is "required" so it could be uploaded here. the name is inconsequential can be changed or used as is)
Here's the output of my alsactl.state - AS IS unamended on a k3gWifi
(the popular name used is asound.state, I prefer my name. call it what you want)
As ever filled with much unexciting dross, but there are maybe a few goodies in there for us to twiddle:
To determine exactly which
thing each setting refers to look under the
name attribute for example: mx35luigi {control.1 is in fact:
name 'Capture Volume'.
The type of access this value has is defined as
read write for all controls
The complete valid enumeration set is not available with the document.
Setting the
default values for some of the things could come in handy.
Some of them have two value attributes. (some, seemingly with duped info.)
Others have more obvious - single - value settings.
The
count of expected values is self-described under
comment.count
For example: 2
The expected values Types are conveniently self-describing and can be found under
comment.type
For example: INTEGER
Where enumerations are used - i.e: ENUMERATED
then a comment.item.[0indexing++] scheme is used:
For example:
comment.item.0 ALC
comment.item.1 Limiter
This is further backed up by a range attribute
comment.range
For example '0 - 63'
The interface is shared by all
iface MIXER and this more than likely refers to something in the alsa.conf somewhere.
That covers the schema for the document I believe.
So, what does this let us do? well if we have a quick look at the alsactl --help
Code:
Usage: alsactl <options> command
Available options:
-h,--help this help
-f,--file # configuration file (default /etc/asound.state or /etc/asound.names)
-F,--force try to restore the matching controls as much as possible
-d,--debug debug mode
-v,--version print version of this program
Available commands:
store <card #> save current driver setup for one or each soundcards
to configuration file
restore<card #> load current driver setup for one or each soundcards
from configuration file
We can see a restoration option is available for the now-amended files with our new
make-it-more-awesome values ; )
Next steps?
a)Decide what
make-it-more-awesome values we need - if any
b) check the restore doesn't exhibit strange behavior and works as expected.
That about wraps it up for how-to Store and fiddle around.
We can amend the values and using the alsactl restore [blah]