Alsa and alsactl: init, store and default configuration of control file
Clash Royale CLAN TAG#URR8PPP
The target kernel is: 2.6.35.14 (old) and its running on an embedded platform and the codec is a wm8753.
I am trying to understand how the alsactl system works. I found a file asound.play @ etc/alsa and this is the configuration file the man pages refer to. I am not sure why mine is called asound.play instead of asound.state but running:
#alsactl init
#alsactl -f /etc/alsa/asound.play store
will default the asound.play file. With the customized version sound works but it doesn't with the default configuration. Here is an excerpt from the asound.play file for a default configuration and the custom configuration. Keep in mind this is just one control block of 85:
Default:
control.1
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 255'
comment.dbmin -12750
comment.dbmax 0
iface MIXER
name 'PCM Volume'
value.0 215
value.1 215
custom:
control.1
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 255'
iface MIXER
name 'PCM Volume'
value.0 250
value.1 250
It isn't obvious to me how the person who originally customized the file knew that she/he needed to get rid of comment.dbmin and dbmax. So how might one go about figuring out how they should be customizing this file so that sound works? Guess and check?
linux-kernel audio alsa
add a comment |
The target kernel is: 2.6.35.14 (old) and its running on an embedded platform and the codec is a wm8753.
I am trying to understand how the alsactl system works. I found a file asound.play @ etc/alsa and this is the configuration file the man pages refer to. I am not sure why mine is called asound.play instead of asound.state but running:
#alsactl init
#alsactl -f /etc/alsa/asound.play store
will default the asound.play file. With the customized version sound works but it doesn't with the default configuration. Here is an excerpt from the asound.play file for a default configuration and the custom configuration. Keep in mind this is just one control block of 85:
Default:
control.1
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 255'
comment.dbmin -12750
comment.dbmax 0
iface MIXER
name 'PCM Volume'
value.0 215
value.1 215
custom:
control.1
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 255'
iface MIXER
name 'PCM Volume'
value.0 250
value.1 250
It isn't obvious to me how the person who originally customized the file knew that she/he needed to get rid of comment.dbmin and dbmax. So how might one go about figuring out how they should be customizing this file so that sound works? Guess and check?
linux-kernel audio alsa
add a comment |
The target kernel is: 2.6.35.14 (old) and its running on an embedded platform and the codec is a wm8753.
I am trying to understand how the alsactl system works. I found a file asound.play @ etc/alsa and this is the configuration file the man pages refer to. I am not sure why mine is called asound.play instead of asound.state but running:
#alsactl init
#alsactl -f /etc/alsa/asound.play store
will default the asound.play file. With the customized version sound works but it doesn't with the default configuration. Here is an excerpt from the asound.play file for a default configuration and the custom configuration. Keep in mind this is just one control block of 85:
Default:
control.1
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 255'
comment.dbmin -12750
comment.dbmax 0
iface MIXER
name 'PCM Volume'
value.0 215
value.1 215
custom:
control.1
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 255'
iface MIXER
name 'PCM Volume'
value.0 250
value.1 250
It isn't obvious to me how the person who originally customized the file knew that she/he needed to get rid of comment.dbmin and dbmax. So how might one go about figuring out how they should be customizing this file so that sound works? Guess and check?
linux-kernel audio alsa
The target kernel is: 2.6.35.14 (old) and its running on an embedded platform and the codec is a wm8753.
I am trying to understand how the alsactl system works. I found a file asound.play @ etc/alsa and this is the configuration file the man pages refer to. I am not sure why mine is called asound.play instead of asound.state but running:
#alsactl init
#alsactl -f /etc/alsa/asound.play store
will default the asound.play file. With the customized version sound works but it doesn't with the default configuration. Here is an excerpt from the asound.play file for a default configuration and the custom configuration. Keep in mind this is just one control block of 85:
Default:
control.1
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 255'
comment.dbmin -12750
comment.dbmax 0
iface MIXER
name 'PCM Volume'
value.0 215
value.1 215
custom:
control.1
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 255'
iface MIXER
name 'PCM Volume'
value.0 250
value.1 250
It isn't obvious to me how the person who originally customized the file knew that she/he needed to get rid of comment.dbmin and dbmax. So how might one go about figuring out how they should be customizing this file so that sound works? Guess and check?
linux-kernel audio alsa
linux-kernel audio alsa
edited Dec 18 at 21:01
asked Dec 18 at 20:14
Rob
1065
1065
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I'd guess that the dbmin
/dbmax
comments are missing because that file was generated with an older version of the driver that did not yet have dB information.
Anyway, comments are ignored by alsactl restore
, so this does not matter.
The iface
and name
entries identify a mixer control; the value
values specify the value(s) of that control.
To get the sound to work, you have to know how these mixer controls affect the hardware. Obviously, whoever created those customized settings did know.
So anything that says comment.(stuff) is insignificant? All I need to worry about is: iface, name, value.0 and value.1? Do you know off hand if there is somewhere I can go to learn how these mixer controls effect the hardware?
– Rob
Dec 18 at 21:46
Yes. Yes. That would be the documentation of your embedded platform.
– CL.
Dec 18 at 21:55
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489760%2falsa-and-alsactl-init-store-and-default-configuration-of-control-file%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I'd guess that the dbmin
/dbmax
comments are missing because that file was generated with an older version of the driver that did not yet have dB information.
Anyway, comments are ignored by alsactl restore
, so this does not matter.
The iface
and name
entries identify a mixer control; the value
values specify the value(s) of that control.
To get the sound to work, you have to know how these mixer controls affect the hardware. Obviously, whoever created those customized settings did know.
So anything that says comment.(stuff) is insignificant? All I need to worry about is: iface, name, value.0 and value.1? Do you know off hand if there is somewhere I can go to learn how these mixer controls effect the hardware?
– Rob
Dec 18 at 21:46
Yes. Yes. That would be the documentation of your embedded platform.
– CL.
Dec 18 at 21:55
add a comment |
I'd guess that the dbmin
/dbmax
comments are missing because that file was generated with an older version of the driver that did not yet have dB information.
Anyway, comments are ignored by alsactl restore
, so this does not matter.
The iface
and name
entries identify a mixer control; the value
values specify the value(s) of that control.
To get the sound to work, you have to know how these mixer controls affect the hardware. Obviously, whoever created those customized settings did know.
So anything that says comment.(stuff) is insignificant? All I need to worry about is: iface, name, value.0 and value.1? Do you know off hand if there is somewhere I can go to learn how these mixer controls effect the hardware?
– Rob
Dec 18 at 21:46
Yes. Yes. That would be the documentation of your embedded platform.
– CL.
Dec 18 at 21:55
add a comment |
I'd guess that the dbmin
/dbmax
comments are missing because that file was generated with an older version of the driver that did not yet have dB information.
Anyway, comments are ignored by alsactl restore
, so this does not matter.
The iface
and name
entries identify a mixer control; the value
values specify the value(s) of that control.
To get the sound to work, you have to know how these mixer controls affect the hardware. Obviously, whoever created those customized settings did know.
I'd guess that the dbmin
/dbmax
comments are missing because that file was generated with an older version of the driver that did not yet have dB information.
Anyway, comments are ignored by alsactl restore
, so this does not matter.
The iface
and name
entries identify a mixer control; the value
values specify the value(s) of that control.
To get the sound to work, you have to know how these mixer controls affect the hardware. Obviously, whoever created those customized settings did know.
answered Dec 18 at 21:36
CL.
2,116913
2,116913
So anything that says comment.(stuff) is insignificant? All I need to worry about is: iface, name, value.0 and value.1? Do you know off hand if there is somewhere I can go to learn how these mixer controls effect the hardware?
– Rob
Dec 18 at 21:46
Yes. Yes. That would be the documentation of your embedded platform.
– CL.
Dec 18 at 21:55
add a comment |
So anything that says comment.(stuff) is insignificant? All I need to worry about is: iface, name, value.0 and value.1? Do you know off hand if there is somewhere I can go to learn how these mixer controls effect the hardware?
– Rob
Dec 18 at 21:46
Yes. Yes. That would be the documentation of your embedded platform.
– CL.
Dec 18 at 21:55
So anything that says comment.(stuff) is insignificant? All I need to worry about is: iface, name, value.0 and value.1? Do you know off hand if there is somewhere I can go to learn how these mixer controls effect the hardware?
– Rob
Dec 18 at 21:46
So anything that says comment.(stuff) is insignificant? All I need to worry about is: iface, name, value.0 and value.1? Do you know off hand if there is somewhere I can go to learn how these mixer controls effect the hardware?
– Rob
Dec 18 at 21:46
Yes. Yes. That would be the documentation of your embedded platform.
– CL.
Dec 18 at 21:55
Yes. Yes. That would be the documentation of your embedded platform.
– CL.
Dec 18 at 21:55
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489760%2falsa-and-alsactl-init-store-and-default-configuration-of-control-file%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown