From: Braddock Gaskill KD5ZVK <braddock@braddock.com>
To: Linux-Hams@vger.kernel.org
Cc: Thomas Sailer <sailer@scs.ch>
Subject: Re: user soundmodem problems on Inspiron 8200 i810 chipset...
Date: Wed, 10 Mar 2004 13:36:45 -0600 [thread overview]
Message-ID: <20040310193645.GA3882@braddock.com> (raw)
In-Reply-To: <404F540B.3050309@scs.ch>
On Wed, Mar 10, 2004 at 06:44:43PM +0100, Thomas Sailer wrote:
> >http://braddock.com/soundmodem.png
>
> Looks like alsa tries to do sample rate conversion, but
> "somewhat" imperfectly. Sigh. Does anyone know how to convince
The only strange thing about that theory (which I tend to agree
probably is what's going on) is that if I do a 9600 samp/sec capture
with SOX using the OSS interface, and look at the capture in Octave, I
don't see the anomaly. In fact, I can then take the 9600 samp/sec SOX
capture of APRS input and use it with an unmodified version of
soundmodem in "file" mode and get perfect copy.
The command I'm using for the sox capture is:
sox -V -r 9600 -t ossdsp /dev/dsp -t wav -b -u -r 9600 /tmp/output4.wav
(or -t raw to look at it in Octave)
Now, a dmesg reveals an ALSA warning message when the snd-ac97-codec
module is inserted:
ALSA ../../alsa-kernel/pci/ac97/ac97_codec.c:1861: MC'97 1 converters and GPIO not ready (0xff00)
I don't know if that warning is related.
Sox (in -V verbose mode) outputs:
sox: Input file /dev/dsp: using sample rate 9600
size bytes, encoding unsigned, 1 channel
sox: Input file /dev/dsp: comment "/dev/dsp"
sox: Writing Wave file: Microsoft PCM format, 1 channel, 9600 samp/sec
sox: 9600 byte/sec, 1 block align, 8 bits/samp
sox: Output file /tmp/output4.wav: using sample rate 9600
size bytes, encoding unsigned, 1 channel
sox: Output file: comment "/dev/dsp"
sox: Finished writing Wave file, 17408 data bytes 17408 samples
At any rate, it's at least good to have these findings in the list
archives for others if nothing else.
braddock gaskill (KD5ZVK)
next prev parent reply other threads:[~2004-03-10 19:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 2:23 user soundmodem problems on Inspiron 8200 i810 chipset braddock
2004-03-09 19:50 ` Patrick Ouellette
2004-03-09 21:11 ` Compile warnings on hfterm with Mandrake ravioli
2004-03-11 9:47 ` Günther Montag
2004-03-09 21:35 ` user soundmodem problems on Inspiron 8200 i810 chipset braddock
2004-03-09 22:52 ` braddock
2004-03-10 17:44 ` Thomas Sailer
2004-03-10 19:15 ` Dave Platt
2004-03-10 19:26 ` Thomas Sailer
2004-03-10 19:36 ` Braddock Gaskill KD5ZVK [this message]
2004-03-10 19:58 ` Dave Platt
2004-03-10 21:56 ` Dave Platt
2004-03-10 23:41 ` braddock
2004-03-11 9:30 ` Tomi Manninen
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=20040310193645.GA3882@braddock.com \
--to=braddock@braddock.com \
--cc=Linux-Hams@vger.kernel.org \
--cc=sailer@scs.ch \
/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