Linux Sound subsystem development
 help / color / mirror / Atom feed
From: "Eric B. Mitchell" <emitchell@altaira.com>
To: linux-sound@vger.kernel.org
Subject: Re: Full Duplex (Play + Record simultaniously)
Date: Thu, 04 Mar 1999 15:58:49 +0000	[thread overview]
Message-ID: <marc-linux-sound-92056343611643@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-92048039409666@msgid-missing>



Thomas Sailer wrote:
> 
> Georg Wendt wrote:
> 
> > I wanna use a record-programm running in one shell and playback audio
> > started on another shell.
> > However, whenever one of the programs has started, it blocks the
> > dsp-device and the other application can't work.
> 
> Depends on the soundcard and the driver. With some drivers this works.
> 
> > Is there a way to avoid this effect?
> 
> Yep - don't access the audio device directly, use an intermediate
> program. EsounD might provide what you need.

The OSS drivers allow full duplex operation on some sound cards.
My SB AWE 32 works great for it.  EsounD will use it if it's 
available, but I'm not sure how robust the error handling is
should the full duplex operation fail (haven't had the problem
myself =).

> > Another way: What about using two soundcards, one for playback, the
> > other for recording? Since I can decide the sound-device used by the
> > applications, this should work, shouldn't it?
> 
> In this case you get plesiochronous sampling rates. If that is a
> problem depends on the application.

plesiochronous? i assumes that translates roughly into "skewed data"?

> Tom

-- ebm
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+
| Eric B. Mitchell         mailto:ericmit@ix.netcom.com |
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+

  parent reply	other threads:[~1999-03-04 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-03 16:55 Full Duplex (Play + Record simultaniously) Georg Wendt
1999-03-03 17:25 ` Raoul Boenisch
1999-03-04 11:35 ` Thomas Sailer
1999-03-04 15:58 ` Eric B. Mitchell [this message]
1999-03-04 18:32 ` Thomas Sailer

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=marc-linux-sound-92056343611643@msgid-missing \
    --to=emitchell@altaira.com \
    --cc=linux-sound@vger.kernel.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