From: "Rodolfo Brasnarof" <rodob@ciudad.com.ar>
To: rdmartinml@infinito.it
Cc: linux-hams@vger.kernel.org
Subject: Re: Soundmodem && SBLive!
Date: Tue, 15 Apr 2003 20:24:39 -0300 [thread overview]
Message-ID: <3E9C6A87.22232.37320@localhost> (raw)
In-Reply-To: <200304140816.37438.rdmartinml@infinito.it>
---
On 14 Apr 2003 at 8:16, Giuseppe Martino wrote:
> Il Monday 14 April 2003 07:34, Rodolfo Brasnarof ha scritto:
> > So, try the user-space one, which should work with ANY
> > soundcard supported by OSS. Is your card working with OSS?
>
> Yes, It is.
>
> > Then it should work with the user-space soundmodem.
>
> But Is soundmodem kernel-space no longer mantained?
I don't know, but the user-space soundmodem is easier to
configure, more flexible, and works with virtually any
soundcard supported by the kernel.
The kernel soundmodem only works with soundblaster or
windows sound system compatible cards. Those include
SoundBlaster, SBPro, SB16, AWE32, AWE64, and many
compatibles, for example those with Crystal chipsets (I have
one with this chip and made it work with the kernel module,
in both SB and WSS mode). Those are mainly isa cards. Sound
Blaster PCI cards (like mine PCI128) don't work with this,
and perhaps no pci card would work. This is a restriction
the other soundmodem doesn't have (and an important one if
your card is not supported).
Other thing is flexibility. When you configure the user
soundmodem, for example in afsk modulation, you can choose
the tones you want to use. This is not posible with the
kernes soundmodem. A friend and I are using 2400bps afsk
with custom tones (we choosed the tones which worked best).
Other thing is that when I tried the kernel soundmodem, I
had problems unloading the module (the module gives a
segmentation fault).
And finaly, there's the mixer. You can use the usual mixer
to change audio levels. I use aumix in command line mode
from within a script, but you can use what you like.
One bad thing is that if you want to use the configuration
utility you need X. But you can take a sample configuration
file and edit it yourself.
prev parent reply other threads:[~2003-04-15 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-12 18:05 Soundmodem && SBLive! Giuseppe Martino
2003-04-12 18:40 ` Ben Stienstra
2003-04-13 1:38 ` Hamish Moffatt
2003-04-14 5:34 ` Rodolfo Brasnarof
[not found] ` <200304140816.37438.rdmartinml@infinito.it>
2003-04-15 23:24 ` Rodolfo Brasnarof [this message]
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=3E9C6A87.22232.37320@localhost \
--to=rodob@ciudad.com.ar \
--cc=linux-hams@vger.kernel.org \
--cc=rdmartinml@infinito.it \
/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