From: "J. Lance Cotton" <joe@lightningflash.net>
To: Julian Moss <julian.g4ilo@gmail.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: Problem with soundmodem on Eee PC
Date: Wed, 09 Sep 2009 20:33:11 -0500 [thread overview]
Message-ID: <4AA85757.8010105@lightningflash.net> (raw)
In-Reply-To: <984e45570909091532n34cb261hd9cdd6f30d448bf7@mail.gmail.com>
On 09/09/2009 05:32 PM, Julian Moss wrote:
> I found a posting in a list here
> http://osdir.com/ml/linux.hams/2005-10/msg00058.html which suggested
> that this is caused by soundmodem opening the sound card at an
> unsupported sample rate of 9600. The post included a hack to make it
> use 11025.
I was the one who posted that original problem. My solutions were:
1) Use a different soundcard that supported the requested sample rate.
2) Use the ALSA sound system instead of the OSS system, which I think is
now standard on Ubuntu and most other 2.6 Linuxes. I had been sticking
with OSS for a while because I found the commercial (paid) OSS system to
be very stable on the old SuSE distro I was running. I now use Ubuntu
and the ALSA system will re-sample whatever audio comes in from whatever
soundcard to give the software what it asked for.
Works well.
-Lance
--
J. Lance Cotton, KJ5O
joe@lightningflash.net
http://kj5o.lightningflash.net
Three Step Plan: 1. Take over the world. 2. Get a lot of cookies. 3. Eat
the cookies.
next prev parent reply other threads:[~2009-09-10 1:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 22:32 Problem with soundmodem on Eee PC Julian Moss
2009-09-09 23:14 ` Alan Crosswell
2009-09-10 1:33 ` J. Lance Cotton [this message]
2009-09-12 23:12 ` Dave Platt
2009-09-13 7:11 ` Christof Bodner
2009-09-13 18:26 ` Dave Platt
2009-09-13 19:28 ` Christof Bodner
2009-09-14 6:29 ` David A. Ranch
2009-09-14 13:01 ` Alan Crosswell
-- strict thread matches above, loose matches on Subject: below --
2009-09-10 20:19 Christof Bodner
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=4AA85757.8010105@lightningflash.net \
--to=joe@lightningflash.net \
--cc=julian.g4ilo@gmail.com \
--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.