All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Cc: tiwai@suse.de, pzad@pobox.sk
Subject: emu10k1 device naming
Date: Sun, 25 Jul 2004 00:29:27 -0400	[thread overview]
Message-ID: <1090729766.1952.7.camel@mindpipe> (raw)

Now that the emu10k1 driver supports low latency, multichannel capture,
it would be useful to rearrange the devices.  Currently you have to use
hw:0,0 for playback, and hw:0,2 for capture.  This works down to 32
frames (you have to record more than 2 channels to get 32 frames,
because 512 bytes is the smallest period JACK supports).  JACK requires
the playback and capture device to be the same for both directions.

The current hw:0,0 device could be moved to hw:0,2.  This is the best
arrangement, because these are the only two devices that it makes sense
to use for full-duplex.  The hw:0,2 playback device is a special AC3
passthrough device, there is no capture device that corresponds to it. 
The same applies to the current hw:0,0 (ADC capture) and hw:0,1 (mic
capture - 8000 Hz) devices, there is no corresponding playback device.

It was suggsted to use the 'asym' PCM plugin for this, but JACK does not
support using a PCM as the device name, you need to give it a hardware
device.

Lee 





-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click

             reply	other threads:[~2004-07-25  4:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-25  4:29 Lee Revell [this message]
2004-07-25  8:15 ` emu10k1 device naming Jaroslav Kysela
2004-07-25 18:15   ` Lee Revell
2004-07-27  6:55     ` Jaroslav Kysela
2004-07-27 15:56       ` Takashi Iwai
2004-07-27 17:38         ` Jaroslav Kysela
2004-07-27 19:17           ` Lee Revell
2004-07-28 15:16             ` Takashi Iwai
2004-07-28 17:21               ` Lee Revell
2004-07-25 10:53 ` Florian Schmidt

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=1090729766.1952.7.camel@mindpipe \
    --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.