From: Matti Aarnio <matti.aarnio@zmailer.org>
To: "David D. Hagood" <wowbagger@sktc.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Asterisk] DTMF noise
Date: Wed, 8 Jan 2003 15:04:40 +0200 [thread overview]
Message-ID: <20030108130440.GC5948@mea-ext.zmailer.org> (raw)
In-Reply-To: <3E1C1CDE.8090600@sktc.net>
On Wed, Jan 08, 2003 at 06:43:10AM -0600, David D. Hagood wrote:
> Thomas Tonino wrote:
> >Roy Sigurd Karlsbakk wrote:
> >>so - we DO NOT need a 'simplistic' DTMF decoder.
> >
> >You need a good one. But good can be simplistic, is what I'm saying.
> >
> >DTMF was designed to be easy to decode reliably. Complex doesn't
> >automatically mean better.
>
> I haven't looked at the code, but I'd recommend using a bank of Goertzel
> filters -
Do look into drivers/isdn/isdn_audio.c That does use Görtzel
filter, but does not do complete energy comparisons -> false detections.
/Matti Aarnio
next prev parent reply other threads:[~2003-01-08 12:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030107140012$1b66@gated-at.bofh.it>
[not found] ` <20030107150006$4896@gated-at.bofh.it>
2003-01-07 19:08 ` [Asterisk] DTMF noise Thomas Tonino
2003-01-07 22:46 ` Roy Sigurd Karlsbakk
2003-01-08 7:51 ` Thomas Tonino
2003-01-08 12:43 ` David D. Hagood
2003-01-08 13:04 ` Matti Aarnio [this message]
2003-01-08 15:49 ` Wolfgang Fritz
2003-01-08 16:30 ` Wolfgang Fritz
2003-01-08 19:48 ` Andrew McGregor
2003-01-08 22:19 ` Jamie Lokier
2003-01-09 12:51 ` David D. Hagood
2003-01-09 13:31 ` Wolfgang Fritz
2003-01-09 23:32 ` David D. Hagood
2003-01-10 6:52 ` Matti Aarnio
2003-01-10 12:42 ` David D. Hagood
2003-01-10 12:03 ` Roy Sigurd Karlsbakk
2003-01-08 20:22 ` Thomas Tonino
2003-01-09 12:42 ` David D. Hagood
2003-01-07 13:55 Roy Sigurd Karlsbakk
2003-01-07 14:49 ` [Asterisk] " Mark Spencer
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=20030108130440.GC5948@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wowbagger@sktc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox