From: Lee Revell <rlrevell@joe-job.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Alsa-devel@lists.sourceforge.net, pzad@pobox.sk
Subject: Re: emu10k1 latency / capture period
Date: Fri, 18 Jun 2004 19:26:33 -0400 [thread overview]
Message-ID: <1087601193.1073.15.camel@debian> (raw)
In-Reply-To: <s5hacz1p5vd.wl@alsa2.suse.de>
On Fri, 2004-06-18 at 05:33, Takashi Iwai wrote:
> But my guess is that ASIO uses the playback interrupt
> for capture, too.
>
A few thing I noticed looking at the code is that the FXBus
channels are only available as a playback device. Shouldn't
these also be capture devices? This implies that the FXBus
channels cannot be used for multichannel recording. Is this
correct?
Maybe modifying the driver to expose the FXBus channels as capture
devices is all that is needed. This is really how the hardware
works - the channels act as buses, so it's simultaneously a playback
and a capture device.
rlrevell@debian:$ cat /proc/asound/pcm
00-00: emu10k1 : EMU10K1 : playback 32 : capture 1
00-01: emu10k1 mic : EMU10K1 MIC : capture 1
00-02: emu10k1 efx : EMU10K1 EFX : capture 1
00-03: emu10k1 : EMU10K1 FX8010 : playback 8
I also noticed that the driver only seems to be aware of 16 FXBus
channels - the Audigy has 32. This I am going to take a shot at fixing
myself.
Lee
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
next prev parent reply other threads:[~2004-06-18 23:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 9:06 emu10k1 latency / capture period Peter Zubaj
2004-06-17 18:37 ` Lee Revell
2004-06-17 23:26 ` Paul Davis
2004-06-18 9:33 ` Takashi Iwai
2004-06-18 19:39 ` Lee Revell
2004-06-18 23:26 ` Lee Revell [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-21 8:03 Peter Zubaj
2004-06-21 15:26 ` Takashi Iwai
2004-06-21 20:27 ` Lee Revell
2004-06-16 20:14 Lee Revell
2004-06-16 20:52 ` James Courtier-Dutton
2004-06-16 21:02 ` Lee Revell
2004-06-20 4:06 ` Lee Revell
2004-06-21 15:35 ` Takashi Iwai
2004-06-21 15:54 ` Takashi Iwai
2004-06-21 20:20 ` Lee Revell
2004-06-22 11:13 ` Takashi Iwai
2004-06-22 11:29 ` Jaroslav Kysela
2004-06-22 12:47 ` Takashi Iwai
2004-06-22 21:15 ` Lee Revell
2004-06-28 20:44 ` Lee Revell
2004-06-22 20:26 ` Lee Revell
2004-06-22 18:48 ` Lee Revell
2004-06-21 20:25 ` Lee Revell
2004-07-08 0:40 ` Lee Revell
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=1087601193.1073.15.camel@debian \
--to=rlrevell@joe-job.com \
--cc=Alsa-devel@lists.sourceforge.net \
--cc=pzad@pobox.sk \
--cc=tiwai@suse.de \
/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.