From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001927]: Capture Device not working
Date: Thu, 23 Mar 2006 17:37:23 +0100 [thread overview]
Message-ID: <5cf793c1dc297aa505e638fffa446f2b@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1927>
======================================================================
Reported By: sk0rp10
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 1927
Category: PCI - hda-intel
Reproducibility: always
Severity: feature
Priority: normal
Status: assigned
Distribution: Slackware current
Kernel Version: 2.6.15.6 vanilla
======================================================================
Date Submitted: 03-15-2006 19:23 CET
Last Modified: 03-23-2006 17:37 CET
======================================================================
Summary: Capture Device not working
Description:
I tryed use krec to record from internal mic but no sound is recorded.
I applyed the patch from issue #1890.
here asound.state:
state.Intel {
control.1 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 127'
iface MIXER
name 'Master Playback Volume'
value.0 121
value.1 121
}
control.2 {
comment.access 'read write'
comment.type BOOLEAN
comment.count 2
iface MIXER
name 'Master Playback Switch'
value.0 true
value.1 true
}
control.3 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 15'
iface MIXER
name 'CD Capture Volume'
value.0 7
value.1 7
}
control.4 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 15'
iface MIXER
name 'Capture Volume'
value.0 11
value.1 11
}
control.5 {
comment.access 'read write'
comment.type BOOLEAN
comment.count 2
iface MIXER
name 'Capture Switch'
value.0 false
value.1 false
}
control.6 {
comment.access 'read write'
comment.type ENUMERATED
comment.count 1
comment.item.0 HP
comment.item.1 Unknown
comment.item.2 Mic
comment.item.3 PCM
iface MIXER
name 'Capture Source'
value Mic
}
control.7 {
comment.access 'read write user'
comment.type INTEGER
comment.count 2
comment.range '0 - 255'
iface MIXER
name 'PCM Playback Volume'
value.0 232
value.1 232
}
}
======================================================================
----------------------------------------------------------------------
sk0rp10 - 03-21-06 11:08
----------------------------------------------------------------------
Rised Capture Volume to max, installed current CVS, but no sound captured
by mic.
here the state:
state.Intel {
control.1 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 127'
iface MIXER
name 'Master Playback Volume'
value.0 108
value.1 108
}
control.2 {
comment.access 'read write'
comment.type BOOLEAN
comment.count 2
iface MIXER
name 'Master Playback Switch'
value.0 true
value.1 true
}
control.3 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 15'
iface MIXER
name 'Capture Volume'
value.0 15
value.1 15
}
control.4 {
comment.access 'read write'
comment.type BOOLEAN
comment.count 2
iface MIXER
name 'Capture Switch'
value.0 true
value.1 true
}
control.5 {
comment.access 'read write'
comment.type ENUMERATED
comment.count 1
comment.item.0 Mic
comment.item.1 PCM
iface MIXER
name 'Capture Source'
value Mic
}
control.6 {
comment.access 'read write user'
comment.type INTEGER
comment.count 2
comment.range '0 - 255'
iface MIXER
name 'PCM Playback Volume'
value.0 255
value.1 255
}
}
----------------------------------------------------------------------
tiwai - 03-23-06 17:37
----------------------------------------------------------------------
The Mic is for the mic jack. Maybe the internal mic is not supported.
Issue History
Date Modified Username Field Change
======================================================================
03-15-06 19:23 sk0rp10 New Issue
03-15-06 19:23 sk0rp10 Distribution => Slackware current
03-15-06 19:23 sk0rp10 Kernel Version => 2.6.15.6 vanilla
03-15-06 19:38 tiwai Note Added: 0008569
03-15-06 20:20 sk0rp10 Note Added: 0008572
03-15-06 20:21 sk0rp10 File Added: codec.tar.gz
03-15-06 20:47 sk0rp10 Issue Monitored: sk0rp10
03-19-06 17:48 sk0rp10 Note Added: 0008692
03-19-06 19:46 rlrevell Note Added: 0008696
03-21-06 11:08 sk0rp10 Note Added: 0008742
03-23-06 17:37 tiwai Note Added: 0008893
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next reply other threads:[~2006-03-23 16:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 16:37 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-23 22:23 [ALSA - driver 0001927]: Capture Device not working bugtrack
2006-03-21 10:08 bugtrack
2006-03-19 18:46 bugtrack
2006-03-19 16:48 bugtrack
2006-03-15 19:20 bugtrack
2006-03-15 18:38 bugtrack
2006-03-15 18:23 bugtrack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5cf793c1dc297aa505e638fffa446f2b@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox