From: David Ranch <linux-hams@trinnet.net>
To: linux-hams@vger.kernel.org
Subject: Re: Soundmodem problems
Date: Sat, 31 Jan 2015 20:56:47 -0800 [thread overview]
Message-ID: <54CDB20F.8040201@trinnet.net> (raw)
In-Reply-To: <1422692681.5081.9.camel@freemail.gr>
Hello Apostolos,
> I am using soundmodem version 0.18 on a Debian Jessie system and I have
> two problems.
Though soundmodem should be workable, it hasn't been supported in years
and it doesn't work all that well. Fortunately, we have an excellent
replacement:
Direwolf - https://home.comcast.net/~wb2osz/site/
Download 1.1 and read the User Guide. If you doubt my point on
Soundmodem not working well, read the appendix of the User Guide that
shows the decode counts on soundmodem vs Direwolf and many other HW TNCs
even!
Ps. Once you get 1.1 working, it's worth noting there is a known
annoyance with an overly long TX-TAIL setting with it. The new 1.2Beta
version has fixed this.
--David
KI6ZHD
next prev parent reply other threads:[~2015-02-01 4:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 8:24 Soundmodem problems Apostolos Kefalas
2015-02-01 4:56 ` David Ranch [this message]
2015-02-13 14:53 ` conversd-saupp-1.62a Paul Lewis
2015-02-13 19:09 ` conversd-saupp-1.62a Thorsten Kranzkowski
2015-02-13 19:18 ` conversd-saupp-1.62a Paul Lewis
2015-02-13 23:59 ` conversd-saupp-1.62a Paul Lewis
2015-02-14 11:12 ` conversd-saupp-1.62a Thorsten Kranzkowski
2015-02-14 12:15 ` conversd-saupp-1.62a Paul Lewis
2015-02-14 13:54 ` conversd-saupp-1.62a Thorsten Kranzkowski
2015-02-14 14:47 ` conversd-saupp-1.62a Paul Lewis
2015-02-14 13:18 ` conversd-saupp-1.62a Paul Lewis
-- strict thread matches above, loose matches on Subject: below --
2015-01-31 8:02 Soundmodem problems Apostolos Kefalas
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=54CDB20F.8040201@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).