[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is still happening in Ubuntu 19.10, and I'm all but certain it will
continue to happen with 20.04 when I upgrade to it. I'll verify next
weekend when I finally have time for the upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue on a maintained version of Ubuntu please let us
know.
** Changed in: alsa-driver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
No effect for the default volume levels setting, the same behavior
continues (tested repeatedly).
No idea how to test the other thing you mention, since there's no
mention of PCM Capture anywhere in those pulseaudio files. Can you
offer up a concrete example of what you'd like me to add, and to
do you mean alsactl init does not turn pcm capture switch on
or pcm capture volume need to be unit too ?
http://cgit.freedesktop.org/pulseaudio/pulseaudio/tree/src/modules/alsa/mixer/paths
/analog-output.conf.common
[Element PCM]
switch = mute
volume = merge
override-map.1 = all
The simplest definition of the bug is that after bootup, the actual
state of the emu20k2 hardware is not accurately reflected in the
software (alsamixer, alsactl store). The easiest observable effect (in
my case) is the PCM Capture switch - it shows off even though it's
functioning as if it were
Ok...your latest suggestion (pulseaudio analog-input.conf.common
modifications) had no effect. The defect is still present.
Let me know if you'd like me to test something else.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You lost me - what's the o'clock capture switch? How do I set it? What
are the permissible values? It's not documented in the alsactl man page
either.
If you give me an example I'll be more than happy to test and relay the
results.
--
You received this bug notification because you are a member
CTL{name}=PCM Capture Switch,CTL{index}=1,CTL{do_search}==1, \
CTL{values}=on
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1133065
Title:
Default mixer settings for EMU20K2 enable PCM Input on
There would be a simple workaround if any of the command-line utilities
for alsa would allow me to change specific mixer settings. A script
could easily be devised to simply turn PCM Input on, then off, and that
would be that. Sadly, to my knowledge no such utility exists.
--
You received this
do you mean pcm capture switch is off ?
control.16 {
iface MIXER
name 'PCM Capture Switch'
value false
comment {
access 'read write'
type BOOLEAN
count
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1133065
Title:
Default mixer settings for EMU20K2 enable PCM Input on boot while
showing it as disabled
To manage notifications about this bug go to:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1133065
Title:
Default mixer settings for EMU20K2 enable PCM Input on boot while
showing it as disabled
To manage notifications about this bug go to:
Yes, precisely.
Take this sequence:
Start up the machine
Boot to Ubuntu
Log in
Open sound input settings (gnome-control-center sound, input tab)
Play some music
The input indicator moves with the music clearly denoting that the PCM
capture is enabled. However, alsactl store
As expected, login-logout had no effect. Therefore, it's safe to assume
the bug only manifests on a fresh boot. This reinforces the idea that
it's either something changing the card's state behind ALSA'S back, or
ALSA not properly restoring state to the card. The fact that alsactl
restore fails
http://git.alsa-project.org/?p=alsa-
utils.git;a=blob_plain;f=alsactl/init/default;hb=HEAD
if alsactl restore is not executed, try adding o'clock capture switch in
alsactl/init/default
http://cgit.freedesktop.org/pulseaudio/pulseaudio/tree/src/modules/alsa/mixer/paths
how about adding
16 matches
Mail list logo
