alsa softvol does not show up in amixer
I have a orangepi pc and need to setup an alsa softvol pcm to control the i2s dac volume.
Therefore I have create the following /etc/asound.conf
pcm.!default {
type plug
slave.pcm "softvol"
}
pcm.softvol {
type softvol
slave {
pcm "hw:1,0"
}
control {
name "SoftVol"
card 1
}
}
and here are the detected devices
root@orangepipcplus:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: audiocodec [audiocodec], device 0: SUNXI-CODEC sndcodec-0
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: snddaudio [snddaudio], device 0: SUNXI-TDM0 snddaudio-0
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: sndhdmi [sndhdmi], device 0: SUNXI-HDMIAUDIO sndhdmi-0
Subdevices: 1/1
Subdevice #0: subdevice #0
For some reason controlling the volume with alsamixer does nothing. And if I change the control block in the asound.conf from SoftVol to e.g. Master no control with the name Master appears in alsamixer after a reboot.
So my nasty suspicion is that my /etc/asound.conf is not read by alsa!
The OS I am using is Armbian -> Debian.
I have another pi (nanopi) also running Armbian -> Debian using the same /etc/asound.conf and there everything is working.
linux audio alsa
asked Mar 3 '18 at 12:28
PascalPascal
1112
add a comment |
I have a orangepi pc and need to setup an alsa softvol pcm to control the i2s dac volume.
Therefore I have create the following /etc/asound.conf
pcm.!default {
type plug
slave.pcm "softvol"
}
pcm.softvol {
type softvol
slave {
pcm "hw:1,0"
}
control {
name "SoftVol"
card 1
}
}
and here are the detected devices
root@orangepipcplus:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: audiocodec [audiocodec], device 0: SUNXI-CODEC sndcodec-0
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: snddaudio [snddaudio], device 0: SUNXI-TDM0 snddaudio-0
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: sndhdmi [sndhdmi], device 0: SUNXI-HDMIAUDIO sndhdmi-0
Subdevices: 1/1
Subdevice #0: subdevice #0
For some reason controlling the volume with alsamixer does nothing. And if I change the control block in the asound.conf from SoftVol to e.g. Master no control with the name Master appears in alsamixer after a reboot.
So my nasty suspicion is that my /etc/asound.conf is not read by alsa!
The OS I am using is Armbian -> Debian.
I have another pi (nanopi) also running Armbian -> Debian using the same /etc/asound.conf and there everything is working.
linux audio alsa
asked Mar 3 '18 at 12:28
PascalPascal
1112
not about alsa, but about "doesn't read": runinotifywait -m /etc/asound.conf(from inotify-tools) with appropriate privileges (best as root) to see real-time if the file is actually read or not.
– A.B
Mar 3 '18 at 14:40
ok the file is getting read. following this I managed to get the oldSoftVoldevice to disappear but the newly createdMasterSoftVol does not appear
– Pascal
Mar 3 '18 at 19:52
I vaguely remember that sunxi does some funny non-standard things related to sound, so that may (or may not) cause this problem. At least it's an aspect to look at.
– dirkt
Mar 4 '18 at 9:47
It is working on a NanoPi Neo. This device is using sunxi H3 too. I copied all alsa stuff from there but no softvol appears.
– Pascal
Apr 1 '18 at 9:50
add a comment |
I have a orangepi pc and need to setup an alsa softvol pcm to control the i2s dac volume.
Therefore I have create the following /etc/asound.conf
pcm.!default {
type plug
slave.pcm "softvol"
}
pcm.softvol {
type softvol
slave {
pcm "hw:1,0"
}
control {
name "SoftVol"
card 1
}
}
and here are the detected devices
root@orangepipcplus:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: audiocodec [audiocodec], device 0: SUNXI-CODEC sndcodec-0
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: snddaudio [snddaudio], device 0: SUNXI-TDM0 snddaudio-0
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: sndhdmi [sndhdmi], device 0: SUNXI-HDMIAUDIO sndhdmi-0
Subdevices: 1/1
Subdevice #0: subdevice #0
For some reason controlling the volume with alsamixer does nothing. And if I change the control block in the asound.conf from SoftVol to e.g. Master no control with the name Master appears in alsamixer after a reboot.
So my nasty suspicion is that my /etc/asound.conf is not read by alsa!
The OS I am using is Armbian -> Debian.
I have another pi (nanopi) also running Armbian -> Debian using the same /etc/asound.conf and there everything is working.
linux audio alsa
asked Mar 3 '18 at 12:28
PascalPascal
1112
I have a orangepi pc and need to setup an alsa softvol pcm to control the i2s dac volume.
Therefore I have create the following /etc/asound.conf
pcm.!default {
type plug
slave.pcm "softvol"
}
pcm.softvol {
type softvol
slave {
pcm "hw:1,0"
}
control {
name "SoftVol"
card 1
}
}
and here are the detected devices
root@orangepipcplus:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: audiocodec [audiocodec], device 0: SUNXI-CODEC sndcodec-0
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: snddaudio [snddaudio], device 0: SUNXI-TDM0 snddaudio-0
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: sndhdmi [sndhdmi], device 0: SUNXI-HDMIAUDIO sndhdmi-0
Subdevices: 1/1
Subdevice #0: subdevice #0
For some reason controlling the volume with alsamixer does nothing. And if I change the control block in the asound.conf from SoftVol to e.g. Master no control with the name Master appears in alsamixer after a reboot.
So my nasty suspicion is that my /etc/asound.conf is not read by alsa!
The OS I am using is Armbian -> Debian.
I have another pi (nanopi) also running Armbian -> Debian using the same /etc/asound.conf and there everything is working.
linux audio alsa
linux audio alsa
asked Mar 3 '18 at 12:28
PascalPascal
1112
asked Mar 3 '18 at 12:28
PascalPascal
1112
edited Mar 4 '18 at 9:29
Pascal
asked Mar 3 '18 at 12:28
PascalPascal
1112
asked Mar 3 '18 at 12:28
PascalPascal
1112
asked Mar 3 '18 at 12:28
PascalPascal
1112
1112
not about alsa, but about "doesn't read": runinotifywait -m /etc/asound.conf(from inotify-tools) with appropriate privileges (best as root) to see real-time if the file is actually read or not.
– A.B
Mar 3 '18 at 14:40
ok the file is getting read. following this I managed to get the oldSoftVoldevice to disappear but the newly createdMasterSoftVol does not appear
– Pascal
Mar 3 '18 at 19:52
I vaguely remember that sunxi does some funny non-standard things related to sound, so that may (or may not) cause this problem. At least it's an aspect to look at.
– dirkt
Mar 4 '18 at 9:47
It is working on a NanoPi Neo. This device is using sunxi H3 too. I copied all alsa stuff from there but no softvol appears.
– Pascal
Apr 1 '18 at 9:50
add a comment |
not about alsa, but about "doesn't read": runinotifywait -m /etc/asound.conf(from inotify-tools) with appropriate privileges (best as root) to see real-time if the file is actually read or not.
– A.B
Mar 3 '18 at 14:40
ok the file is getting read. following this I managed to get the oldSoftVoldevice to disappear but the newly createdMasterSoftVol does not appear
– Pascal
Mar 3 '18 at 19:52
I vaguely remember that sunxi does some funny non-standard things related to sound, so that may (or may not) cause this problem. At least it's an aspect to look at.
– dirkt
Mar 4 '18 at 9:47
It is working on a NanoPi Neo. This device is using sunxi H3 too. I copied all alsa stuff from there but no softvol appears.
– Pascal
Apr 1 '18 at 9:50
not about alsa, but about "doesn't read": run
inotifywait -m /etc/asound.conf (from inotify-tools) with appropriate privileges (best as root) to see real-time if the file is actually read or not.– A.B
Mar 3 '18 at 14:40
not about alsa, but about "doesn't read": run
inotifywait -m /etc/asound.conf (from inotify-tools) with appropriate privileges (best as root) to see real-time if the file is actually read or not.– A.B
Mar 3 '18 at 14:40
ok the file is getting read. following this I managed to get the old
SoftVol device to disappear but the newly created Master SoftVol does not appear– Pascal
Mar 3 '18 at 19:52
ok the file is getting read. following this I managed to get the old
SoftVol device to disappear but the newly created Master SoftVol does not appear– Pascal
Mar 3 '18 at 19:52
I vaguely remember that sunxi does some funny non-standard things related to sound, so that may (or may not) cause this problem. At least it's an aspect to look at.
– dirkt
Mar 4 '18 at 9:47
I vaguely remember that sunxi does some funny non-standard things related to sound, so that may (or may not) cause this problem. At least it's an aspect to look at.
– dirkt
Mar 4 '18 at 9:47
It is working on a NanoPi Neo. This device is using sunxi H3 too. I copied all alsa stuff from there but no softvol appears.
– Pascal
Apr 1 '18 at 9:50
It is working on a NanoPi Neo. This device is using sunxi H3 too. I copied all alsa stuff from there but no softvol appears.
– Pascal
Apr 1 '18 at 9:50
add a comment |
1 Answer
1
active
oldest
votes
The mixer will not show up until it is used for the first time. Per alsa.opensrc.org:
Note: The new volume control won't appear immediately! Only after the first
usage of the newly defined device (e.g. with the command above), should
amixer controls | grep <control name>display your new control. Mixers that
were already started before the first usage (like KMix) have to be restarted to
adopt the changes. If you still don't see the new control, try restarting ALSA or
your PC.
Since your config sets the default to the softvol device, running speaker-test or using aplay to play a .wav file should be sufficient to make the volume control appear.
answered Jan 13 at 20:49
RussellRussell
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fsuperuser.com%2fquestions%2f1300097%2falsa-softvol-does-not-show-up-in-amixer%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
The mixer will not show up until it is used for the first time. Per alsa.opensrc.org:
Note: The new volume control won't appear immediately! Only after the first
usage of the newly defined device (e.g. with the command above), should
amixer controls | grep <control name>display your new control. Mixers that
were already started before the first usage (like KMix) have to be restarted to
adopt the changes. If you still don't see the new control, try restarting ALSA or
your PC.
Since your config sets the default to the softvol device, running speaker-test or using aplay to play a .wav file should be sufficient to make the volume control appear.
answered Jan 13 at 20:49
RussellRussell
1
add a comment |
The mixer will not show up until it is used for the first time. Per alsa.opensrc.org:
Note: The new volume control won't appear immediately! Only after the first
usage of the newly defined device (e.g. with the command above), should
amixer controls | grep <control name>display your new control. Mixers that
were already started before the first usage (like KMix) have to be restarted to
adopt the changes. If you still don't see the new control, try restarting ALSA or
your PC.
Since your config sets the default to the softvol device, running speaker-test or using aplay to play a .wav file should be sufficient to make the volume control appear.
answered Jan 13 at 20:49
RussellRussell
1
add a comment |
The mixer will not show up until it is used for the first time. Per alsa.opensrc.org:
Note: The new volume control won't appear immediately! Only after the first
usage of the newly defined device (e.g. with the command above), should
amixer controls | grep <control name>display your new control. Mixers that
were already started before the first usage (like KMix) have to be restarted to
adopt the changes. If you still don't see the new control, try restarting ALSA or
your PC.
Since your config sets the default to the softvol device, running speaker-test or using aplay to play a .wav file should be sufficient to make the volume control appear.
answered Jan 13 at 20:49
RussellRussell
1
The mixer will not show up until it is used for the first time. Per alsa.opensrc.org:
Note: The new volume control won't appear immediately! Only after the first
usage of the newly defined device (e.g. with the command above), should
amixer controls | grep <control name>display your new control. Mixers that
were already started before the first usage (like KMix) have to be restarted to
adopt the changes. If you still don't see the new control, try restarting ALSA or
your PC.
Since your config sets the default to the softvol device, running speaker-test or using aplay to play a .wav file should be sufficient to make the volume control appear.
answered Jan 13 at 20:49
RussellRussell
1
answered Jan 13 at 20:49
RussellRussell
1
answered Jan 13 at 20:49
RussellRussell
1
answered Jan 13 at 20:49
RussellRussell
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1300097%2falsa-softvol-does-not-show-up-in-amixer%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
not about alsa, but about "doesn't read": run
inotifywait -m /etc/asound.conf(from inotify-tools) with appropriate privileges (best as root) to see real-time if the file is actually read or not.– A.B
Mar 3 '18 at 14:40
ok the file is getting read. following this I managed to get the old
SoftVoldevice to disappear but the newly createdMasterSoftVol does not appear– Pascal
Mar 3 '18 at 19:52
I vaguely remember that sunxi does some funny non-standard things related to sound, so that may (or may not) cause this problem. At least it's an aspect to look at.
– dirkt
Mar 4 '18 at 9:47
It is working on a NanoPi Neo. This device is using sunxi H3 too. I copied all alsa stuff from there but no softvol appears.
– Pascal
Apr 1 '18 at 9:50