From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001440]: headphone output loops to microphone input
Date: Thu, 22 Sep 2005 00:13:28 +0200 [thread overview]
Message-ID: <addfa9ed09005edd6d08ec929708b007@bugtrack.alsa-project.org> (raw)
The following issue has been SUBMITTED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1440>
======================================================================
Reported By: dyfrgi
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1440
Category: PCI - intel8x0
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: Gentoo
Kernel Version: 2.6.13.1
======================================================================
Date Submitted: 09-22-2005 00:13 CEST
Last Modified: 09-22-2005 00:13 CEST
======================================================================
Summary: headphone output loops to microphone input
Description:
I cannot use the headphone port when using full duplex on my laptop. Here
are four scenarios, and the results:
1. System speakers, no microphone plugged in
RESULTS:
When recording from the microphone input, there is no sound. As expected.
2. System speakers, microphone plugged in
RESULTS:
Only the sound that should be picked up by the microphone is recorded
through the microphone input. As expected.
3. Headphones plugged in, microphone not plugged in.
RESULTS:
No sound when recording. As expected.
4. Headphones plugged in, microphone plugged in.
RESULTS:
Audio coming in through the microphone input is a combination of the
expected audio and the audio that is being played through the headphone
output. This is the problem.
Could this be an ALSA issue, or should I have the laptop hardware looked
at? I should note that this also happens if I use the OSS driver. That
doesn't mean it's not a driver issue, though; it could be that some
register is not being set up properly.
The loopbacked volume is lower than if I set Mix or Mix Mono to be the
capture channel. I'm using jaaa with noise output turned on to monitor.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
09-22-05 00:13 dyfrgi New Issue
09-22-05 00:13 dyfrgi Distribution => Gentoo
09-22-05 00:13 dyfrgi Kernel Version => 2.6.13.1
======================================================================
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
next reply other threads:[~2005-09-21 22:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 22:13 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-31 2:20 [ALSA - driver 0001440]: headphone output loops to microphone input bugtrack
2005-12-31 6:47 bugtrack
2005-12-31 6:56 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=addfa9ed09005edd6d08ec929708b007@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.