From: noreply@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000334]: EMU10K1, capturing audio is impossible
Date: Sun, 13 Jun 2004 23:30:17 +0200 [thread overview]
Message-ID: <77289ce89a0aa6ae86e4bf326b2e5dd3@bugtrack.alsa-project.org> (raw)
The following bug has been SUBMITTED.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000334
======================================================================
Reported By: netslayer
Assigned To:
======================================================================
Project: ALSA - driver
Bug ID: 334
Category: PCI - emu10k1
Reproducibility: always
Severity: block
Priority: normal
Status: new
Distribution: Gentoo
Kernel Version: 2.6.7rc love-sources
======================================================================
Date Submitted: 06-13-2004 23:30 CEST
Last Modified: 06-13-2004 23:30 CEST
======================================================================
Summary: EMU10K1, capturing audio is impossible
Description:
I have an Audigy (EMU10K2 -- on EMU10K1 drivers). It has worked perfectly
in 0.9.8, and in 1.0.x I can playback audio fine, but capturing seems
impossible.
In 0.9.8 I was able to select a capture source in alsamixer by selecting
it with the space bar. The source had "---" areas above it that meant it
had the capture ability. In 1.0.x that whole functionality is gone, and I
see no more way to capture audio.
I have all my sources up to 100%, and when I plug in an audio to source
into LINE IN on the Audigy, I hear nor can record anything. If I unmute
LINE IN in alsamixer, then I hear pass through audio, which I don't want.
I want to be able to record it, but not hear it through a pass through.
I know several people with this problem, and I myself have a few of these
cards dedicated to MythTV PVR boxes, and this problem makes it impossible
to upgrade ALSA... It's been 6 months since I tried this, and since nobody
reported it, I thought I would.
======================================================================
Bug History
Date Modified Username Field Change
======================================================================
06-13-04 23:30 netslayer New Bug
06-13-04 23:30 netslayer Distribution => Gentoo
06-13-04 23:30 netslayer Kernel Version => 2.6.7rc love-sources
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
next reply other threads:[~2004-06-13 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-13 21:30 noreply [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-13 23:38 [ALSA - driver 0000334]: EMU10K1, capturing audio is impossible noreply
2004-06-14 6:19 noreply
2004-06-28 7:15 noreply
2004-08-30 10:04 bugtrack
2004-11-09 15:13 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=77289ce89a0aa6ae86e4bf326b2e5dd3@bugtrack.alsa-project.org \
--to=noreply@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