All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: [PATCH] Full duplex dmix,dsnoop
Date: Thu, 25 Mar 2004 19:37:22 +0000	[thread overview]
Message-ID: <406334F2.4020101@superbug.demon.co.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 863 bytes --]

See attached patch for suggested new pcm device.

It works for: -
arecord -fdat -Dplug:duplex | aplay -Dplug:duplex

bash-2.05b# arecord -fdat -Dplug:duplex | aplay -Dplug:duplex
Recording WAVE 'stdout' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo
Playing WAVE 'stdin' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo

but fails for: -
arecord -fcd -Dplug:duplex | aplay -Dplug:duplex

bash-2.05b# arecord -fcd -Dplug:duplex | aplay -Dplug:duplex
Recording WAVE 'stdout' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Playing WAVE 'stdin' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
arecord: pcm.c:5920: snd_pcm_mmap_commit: Assertion `frames <= 
snd_pcm_mmap_avail(pcm)' failed.
Aborted by signal Aborted...

This last example with -fcd, outputs one period, maybe two then exits 
with the above error.

Can anybody help?

Cheers
James

[-- Attachment #2: duplex.dmix.dsnoop.patch --]
[-- Type: text/x-patch, Size: 263 bytes --]

--- alsa.conf.org	2004-02-04 12:28:31.000000000 +0000
+++ alsa.conf	2004-03-25 19:27:34.207640104 +0000
@@ -228,6 +228,12 @@
 	}
 }
 
+pcm.duplex {
+	type asym
+		playback.pcm "dmix"
+		capture.pcm "dsnoop"
+}
+
 pcm.shm {
 	@args [ SOCKET PCM ]
 	@args.SOCKET {

             reply	other threads:[~2004-03-25 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-25 19:37 James Courtier-Dutton [this message]
2004-03-25 19:40 ` [PATCH] Full duplex dmix,dsnoop Jaroslav Kysela
2004-03-25 21:11   ` James Courtier-Dutton

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=406334F2.4020101@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.