From: "Wilbert Knol" <w.knol@niwa.cri.nz>
To: linux-hams@vger.kernel.org
Subject: Re: ANN: gMFSK v0.4
Date: Mon, 8 Apr 2002 17:02:01 +1200 [thread overview]
Message-ID: <3CB1CD09.12082.1950EDB@localhost> (raw)
In-Reply-To: <02040805201200.01821@bcat>
I have the source RPM installed and running now, on a Mdk 8.1 distro,
KDE desktop, and it appears to be working very nicely.
Initially, gMSFK complained about read errors from the sound device. I
tried re-assigning DMA channels from the BIOS, and updating the OSS
module accordingly, but it went from read errors to write errors to a full
system freeze :-(
The fix was to ditch OSS for the ALSA drivers, and all is well now. I am
using a Toshiba laptop and the Yamaha sound system has always been a
bit tricky to get going.
Anyway, the KDE sound server does a pretty good job of sharing the
sound system between apps, I am going to try to record a sound bite of
transmitted audio into a file, and re-play it, to see what the transmitted
spectrum looks like. I am really intrigued by the MFSK, which sounds like
a mix between a flute and bag-pipes on fast-forward.
A question: I would like to extract PTT from a USB serial adapter, but the
device file for it doesn't show up in the pick list of gMFSK. Can I safely
add a symlink to the USB device file and call it, say /dev/ttyS99?
Wilbert, ZL2BSJ
next prev parent reply other threads:[~2002-04-08 5:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0203290250170.1587-100000@oh2bns.ampr.org>
2002-04-08 3:32 ` ANN: gMFSK v0.4 Aleksandar Ilic
2002-04-08 5:02 ` Wilbert Knol [this message]
2002-04-08 15:32 ` Tomi Manninen
2002-04-08 9:44 ` Tomi Manninen
2002-04-08 10:57 ` Tomi Manninen
2002-04-08 22:18 ` Aleksandar Ilic
2002-04-08 22:18 ` Aleksandar Ilic
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=3CB1CD09.12082.1950EDB@localhost \
--to=w.knol@niwa.cri.nz \
--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.