From: Dave Platt <dplatt@radagast.org>
To: "J. Lance Cotton" <joe@lightningflash.net>
Cc: Julian Moss <julian.g4ilo@gmail.com>, linux-hams@vger.kernel.org
Subject: Re: Problem with soundmodem on Eee PC
Date: Sat, 12 Sep 2009 16:12:33 -0700 [thread overview]
Message-ID: <4AAC2AE1.9090609@radagast.org> (raw)
In-Reply-To: <4AA85757.8010105@lightningflash.net>
> 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.
That's true, *if* you specify the "plughw:" ALSA device as the one
to use. This utilizes a library plugin which will perform sample-rate
and sample-depth conversion on the fly, so that the application will
get the rate it expects.
If you use the direct "hw:" device specification, the application
is restricted to only those exact sample rates / widths / formats
that the hardware supports. If the app tries to request an unsupported
configuration, the attempt to open the device will fail and the
app won't get any audio in/out over the channel.
The current version of the soundmodem configurator has "plughw:"
available in the menu of device choices for ALSA. It also has
some fixes to audio-channel management that are needed with some
ALSA devices (e.g. some USB audio converters). Older versions
of the soundmodem app may not work well with some devices when
using ALSA.
I have a feeling that some of the soundmodem utility code
(e.g. the scope) may need some of the same "restart cleanly
after an error" fixes that the main modem code required, in
order to work properly with ALSA.
next prev parent reply other threads:[~2009-09-12 23:12 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
2009-09-12 23:12 ` Dave Platt [this message]
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=4AAC2AE1.9090609@radagast.org \
--to=dplatt@radagast.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox