From: braddock@braddock.com
To: Linux-Hams@vger.kernel.org
Cc: Patrick Ouellette <kb8pym@vzavenue.net>, t.sailer@alumni.ethz.ch
Subject: Re: user soundmodem problems on Inspiron 8200 i810 chipset...
Date: Tue, 9 Mar 2004 16:52:14 -0600 [thread overview]
Message-ID: <20040309225214.GA529@braddock.com> (raw)
In-Reply-To: <20040309213542.GA27566@braddock.com>
I have found a (kludgy) fix to my i810 chipset sampling problems.
The problem does indeed seem to have something to do with the sound
sampling rate with the i810 ALSA driver. By forcing soundmodem to
capture at the more standard 22500 samp/sec instead of the 9600
samp/sec that it wants to, I get PERFECT RECEPTION! (now I wish I
hadn't ordered that hardware TNC this morning...*sigh*)
Specifically what I did was to force the sample rate in the
afsk/modem.c file in the modconfig() function. soundmodem tries to
set it to 8*baudrate. I just hard code it to 22500.
/* *samplerate = 8 * s->bps;*/ /* OLD */
*samplerate = 22500; /* NEW - braddock's ALSA kludge */
This presumably won't be sufficient for 9600 baud, but it
gets me working fine at 1200 which is all I need right now.
I suspect there is some portion of soundmodem which relies on that 8 *
bps sample rate. One thing I did find is that if I force the rate to
48000 samp/sec, DCD stops working almost entirely. Maybe Tom Sailer
could shed some light on this, or point me to code that I can fix it?
Or maybe it's just another driver quirk. I also found that if I force
the rate to 8000 samp/sec that I saw the same anomaly in the scope
that I described for 9600 samp/sec.
It should be a simple matter to allow the user to add a prefered
sample rate on the command line.
Braddock Gaskill
On Tue, Mar 09, 2004 at 03:35:42PM -0600, braddock@braddock.com wrote:
> On Tue, Mar 09, 2004 at 02:50:38PM -0500, Patrick Ouellette wrote:
> I did notice one anomaly that occurred frequently on the soundmodem
> diagnostic scope that I'm thinking might be signs of trouble. In the
> capture, the line traced on the scope would occasionally draw a
> straight horizontal line within the signal at random places (both
> horizontally and vertically). This "dead spot" seems to be uniformly
> about 4 1200 Hz cycles (~3 ms). This does not seem to be clipping
> because it occurs at random levels.
>
> Here is an excellent screen shot of the scope showing two instances of
> this anomaly in an otherwise pretty clean looking signal:
>
> http://braddock.com/soundmodem.png
>
> I'm wondering if this is a sampling problem with the ALSA i810 driver?
> If anyone could take a look at that scope image and let me know if
> that's normal behavior within the scope or a sound capture problem it
> would help us narrow this down. It occurs at all sound levels AFAIK.
>
> Also, I tried running soundmodem on a desktop system (vs my Inspiron
> laptop) that also has the Intel i810 sound chipset and ALSA drivers,
> with the exact same results.
>
> All help much appreciated!
>
> -Braddock Gaskill
next prev parent reply other threads:[~2004-03-09 22:52 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 [this message]
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
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=20040309225214.GA529@braddock.com \
--to=braddock@braddock.com \
--cc=Linux-Hams@vger.kernel.org \
--cc=kb8pym@vzavenue.net \
--cc=t.sailer@alumni.ethz.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