[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 Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bu
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: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/b
is this widget similar to
http://git.kernel.org/cgit/linux/kernel/git/tiwai/hda-
emu.git/plain/codecs/vt1812-clevo-b5130m?id=HEAD
Node 0x3e [Audio Mixer] wcaps 0x200500: Mono
Power states: D0 D1 D2 D3
Power: setting=D0, actual=D0
Connection: 1
0x1c
--
You received this bug notific
send: NID=0x3e, VERB=0xf00(get_parameters), PARM=0xe(connect_len)
send: NID=0x3e, VERB=0xf02(get_connect_list), PARM=0x0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1227148
Tit
7.3.4.6 Audio Widget Capabilities The Audio Capabilities control returns
a set of bit fields describing the audio capabilities of the widget.
Parameter ID: 09h
Response Format:
23:20 Type
10 Power Cntrl
8 Conn List
0 Channel count
Figure 86. Audio Widget Capabilities Response Format
Tabl
Raymond, thanks for all your detailed help! I'm totally new to ALSA
debugging, so it's taken me a bit to digest what you've already posted,
but here is the output from hda-verb:
$ sudo ./hda-verb /dev/snd/hwC0D0 0x3e 0xf00 0x9
nid = 0x3e, verb = 0xf00, param = 0x9
value = 0x
$ sudo ./hda-
to verify that there node 0x3e is a hidden widget
use hda-verb to get the widget cap and check the return value to find
out node 0x3e is [audio mixer]/[audio selector] or not exist
send: NID=0x3e, VERB=0xf00(get_parameters), PARM=0x9(audio_wid_cap)
--
You received this bug notification because
how did you perform the recording test ? ( through pulseaudio or using
hw:0 )
you have to provide pulseaudio verbose log if you perform record through
pulseaudio
you have to provide output of alsa-info.sh or amixer instead of screen
shot as your screen shot does not provide dB value of the intern
> This is new territory for me, so forgive me if this is a goofy question, but
> how are these dmic dependent gain parameters
> typically provided? Is this something that should be provided in, say, the
> ACPI tables, or is this typically hard-coded in the drivers?
> How is this handled in the
The name should be "Internal Mic Boost Capture Volume" instead of
"Internal Mic Boost Volume" since node 0x30 is only connected to [Audio
Input] and there is no audio path from node 0x30 to output pins
capabilities should be cvolume instead of volume
Simple mixer control 'Internal Mic Boost',0
Node 0x24 [Pin Complex] wcaps 0x40050d: Stereo Amp-Out
Control: name="Speaker Playback Switch", index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Control: name="Speaker Phantom Jack", index=0, device=0
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0
seem strange to have "PCM Loopback Playback Volume" and "Mic Playback
Volume" at same index but 0x2a, 0x2b and 0x29 are input pin complexes
Node 0x21 [Audio Mixer] wcaps 0x20050b: Stereo Amp-In
Control: name="PCM Loopback Playback Volume", index=0, device=0
ControlAmp: chs=3, dir=In, idx=3,
Gotcha... guess I jumped the gun on the "phase inversion" :P
I attached a screen shot that shows the strange waveform I get in
Audacity when at 100% gain.
I'm waiting to hear back from our ODM on the exact dmics used, and
hopefully I'll get some other useful info as well.
This is new territory f
Very interesting. However, I think you should first try doing a stereo
recording (e g with audacity) to verify that this is actually the case.
If there is phase inversion, you should be able to see large values at
the highest gain, and you should be able to listen to one channel at a
time and verif
do you mean that you want to limit the dBmax to 0 instead of 30 ?
Amp-In caps: ofs=0x0b, nsteps=0x1f, stepsize=0x05, mute=1
Amp-In vals: [0x1e 0x1e]
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.
It is strange that Mic boost control is at node 0x2b since wcaps does
not support Amp-in
however dB range of capture volume control is -16.5 to 30 dB
Node 0x10 [Audio Input] wcaps 0x10051b: Stereo Amp-In
Control: name="Capture Volume", index=0, device=0
ControlAmp: chs=3, dir=In, idx=0, ofs
** Attachment added: "gain-min-broken.png"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1227148/+attachment/3827426/+files/gain-min-broken.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https:
** Attachment added: "gain-max-working.png"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1227148/+attachment/3827425/+files/gain-max-working.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
http
19 matches
Mail list logo
