public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Adam Myrow <amyrow@midsouth.rr.com>
To: speakup@braille.uwo.ca
Subject: Re: recommended Alsa version for an AWE64?
Date: Wed, 16 Oct 2002 19:07:09 -0500	[thread overview]
Message-ID: <5.1.0.14.2.20021016185253.009eb510@pop-server> (raw)
In-Reply-To: <Pine.LNX.4.44.0210160951590.12671-100000@babel.hpcc.noaa.g ov>

At 09:53 AM 10/16/02 -0400, you wrote:
>Hi,
>Well, with the2.4 kernels you aren't supposed to have to use isapnp
>tools.

I wasn't.  I'm using the native ISAPNP support.  So far, Alsa has given 
extremely mixed results.  As I stated, I had to go back to beta 12.  Some 
sounds sound better than with the stock drivers and some have a loud pop or 
squeal at the end.  Next, the whole thing about muting all channels by 
default is absolutely insane.  I had my /etc/modules.conf set up to 
auto-load Alsa and after a short time, the modules unload and when they 
reload, everything is muted again.  I got around this by manually loading 
the modules in /etc/rc.d/rc.modules so that they stay in memory.  I'll 
probably leave it that way anyway as it's faster.  Anyway, all this has 
been a let down when it comes to Speak Freely.  I've tried both the stock 
7.2 and the CVS version and had very unsatisfying results.  Both versions 
work fine in half duplex, but I may as well use the stock drivers if I have 
to use half duplex.  When trying full duplex, a person reported that I was 
sending dead carrier.  Further testing with an echo-back server reveals 
that what is happening is that I send out a long period of silence then 
audio.  Finally, it is as if the last packet gets held up until I close the 
connection.  When I kill sfspeaker, I will get a burst of sound like the 
last part of a word and then all sounds I play will play about half speed 
with a horrible clicking over the top.  It's like the old APH tape 
recorders that claimed to let you adjust the speed and keep the pitch 
sounding the same.  They produced a very similar sound.  In other words, 
Speak Freely is messing up Alsa.  I've tried every combination from the 
default flags to the -DLINUX_SMALL_BUFFER flag and removing the 
-DAUDIO_BLOCKING flag which produced noise instead.  With the stock driver, 
I could sort of get full duplex with the sflaunch front-end, but after a 
few minutes, incoming audio would start breaking up and get progressively 
worse until becoming unusable.  Sflaunch doesn't seem to work at all with 
Alsa most of the time.  Also, with the stock drivers, I got a log of 
recording overruns even when I wasn't talking.  The bottom line is I've 
never gotten satisfactory performance from the Unix/Linux version of Speak 
Freely.  I thought Alsa would be the solution, but I'm just about to go 
back to the stock driver and live with half duplex.  If anybody has 
actually gotten Speak Freely working with an AW64 in full duplex mode, 
regardless of what drivers they used, I'd like to hear about it!



  parent reply	other threads:[~ UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 recomended " Adam Myrow
 ` Toby Fisher
 ` Charles Hallenbeck
   ` Steve Holmes
 ` Christopher Moore
   ` Adam Myrow
     ` jwantz
     [not found]     ` <Pine.LNX.4.44.0210160951590.12671-100000@babel.hpcc.noaa.g ov>
       ` Adam Myrow [this message]
         ` recommended " Igor Gueths
           ` Adam Myrow
             ` Igor Gueths
             ` Igor Gueths
               ` Charles Hallenbeck
               ` Adam Myrow
                 ` Charles Hallenbeck
                   ` Christopher Moore
                 ` Igor Gueths
 igueths
 igueths

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=5.1.0.14.2.20021016185253.009eb510@pop-server \
    --to=amyrow@midsouth.rr.com \
    --cc=speakup@braille.uwo.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).