All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Max Klein <TobSnyder@gmx.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: echo-cancellation plugin advice?
Date: Tue, 08 May 2012 12:38:49 +0200	[thread overview]
Message-ID: <s5hsjfbneiu.wl%tiwai@suse.de> (raw)
In-Reply-To: <20120507141506.67270@gmx.net>

At Mon, 07 May 2012 16:15:06 +0200,
Max Klein wrote:
> 
> > Well, asym wouldn't be the answer.  Basically you'll need to open two
> > slave PCMs in one plugin.  So, it's no simple filter-type plugin.
> > It's doable, but not easy as it sounds, I guess.
> 
> Takashi, can you please further explain why asym is not the solution and what you see as a problem?

Well...  Do you understand what asym plugin is supposed to do?

> I am also trying to figure out if it would be possible to create such a plugin for ALSA? I am still searching for some good starting points on how to write an ALSA plugin...
> 
> Jean-Marc Valin (http://lists.linuxaudio.org/pipermail/linux-audio-dev/2005-June/012454.html) already released his work as part of speex but as far I know there is no plugin that has been made out of it?

For a good echo cancellation, you'll need both input and output
streams, i.e. the recording source and the playback stream you are
sending out.  A normal plugin works just like a filter.  Get one
stream, process it, and output.  But, now you need two streams in
different directions in a single plugin instance.

asym doesn't do that.  asym is just to pass through a slave PCM.
The only job of asym plugin is to provide the different pass-thru
slave PCM for each direction (input/output).  Nothing more than that.


Takashi

  reply	other threads:[~2012-05-08 10:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 14:15 echo-cancellation plugin advice? Max Klein
2012-05-08 10:38 ` Takashi Iwai [this message]
2023-10-27 10:38   ` [alsa-devel] " f.antonini
  -- strict thread matches above, loose matches on Subject: below --
2007-08-26 22:18 Robert Brewer

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=s5hsjfbneiu.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=TobSnyder@gmx.de \
    --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 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.