From: David Ranch <linux-hams@trinnet.net>
To: linux-hams@vger.kernel.org
Subject: Re: soundmodem
Date: Thu, 27 Feb 2014 09:08:50 -0800 [thread overview]
Message-ID: <530F7122.9090207@trinnet.net> (raw)
In-Reply-To: <20140227163306.GH30054@belle.intranet.vanheusden.com>
Hello Folkert,
While Soundmodem is the old standby software TNC for LInux, there are
better solutions out there now. The one I've been recommending with
significantly better decodes is a new entry called Dire Wolf from WB2OSZ:
http://home.comcast.net/~wb2osz/site/
If you download the new beta source archive (
http://home.comcast.net/~wb2osz/Version%201.0/direwolf-1.0-src.zip ),
open up the zip, look in the User-Guide and check out Chapter 10. In
there, it gives a table of Dire wolf's # of decodes compared to all
kinds of TNCs including Soundmodem and safe to say, it blows away
Soundmodem due to it's multiple off frequency decoders, multi-bit error
correction, etc.. There is also a version for the Raspberry Pi as well!
Back to your original problem, I suspect your issue is in the Linux
sound system. Are you using PulseAudio? Did you run pavucontrol and
route the audio from Soundmodem to your desired soundcard?
--David
KI6ZHD
next prev parent reply other threads:[~2014-02-27 17:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 16:33 soundmodem folkert
2014-02-27 17:08 ` David Ranch [this message]
2014-02-27 17:37 ` soundmodem folkert
2014-02-27 18:39 ` soundmodem Apostolos Kefalas
2014-02-27 17:45 ` soundmodem Charles Boling
2014-02-27 20:51 ` soundmodem folkert
2014-02-27 21:34 ` soundmodem Charles Boling
2014-03-01 21:54 ` soundmodem folkert
2014-02-28 23:24 ` soundmodem Larry Levesque
-- strict thread matches above, loose matches on Subject: below --
2004-10-29 14:17 Soundmodem iw2esa
2004-10-29 14:33 ` Soundmodem Arno Verhoeven
2004-10-29 14:59 ` Soundmodem Rodolfo Brasnarof
2004-10-29 17:16 ` Soundmodem Bob Nielsen
2004-10-29 16:59 ` Soundmodem Tomi Manninen
2002-07-21 3:15 Soundmodem Mike Fenske
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=530F7122.9090207@trinnet.net \
--to=linux-hams@trinnet.net \
--cc=linux-hams@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 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.