public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "hank smith" <hanksmith4@earthlink.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Speakup on an Echo
Date: Tue, 5 Jul 2005 21:51:54 -0700	[thread overview]
Message-ID: <004701c581e6$6ee88300$650fa8c0@home4rer2f14d7> (raw)
In-Reply-To: <20050706015757.GA10349@garrettk17.iquest.net>

is that the echo external you are using or the isa card?
----- Original Message ----- 
From: "Garrett Klein" <kleins@iquest.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Tuesday, July 05, 2005 6:57 PM
Subject: Re: Speakup on an Echo


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> Hello all,
>
> Just replying to confirm that this did in fact happen. I connected a patch 
> cable to the headphone jack of the echo PC and connected the other end to 
> the line-in on my minidisc recorder. The reason for the loudness is that 
> the amp is rather sensative.
>
> I found the following querks/differences of behavior when using the echo 
> with the bns driver.
> 1. The echo's buffer is too small to handle all text sent (either that or 
> it's just a piece3 of crap and can't handle things with multiple periods), 
> resulting in a 5-second pause sometimes. For example: linux 2.6.11... five 
> second pause... 7
> Last login:... five-second pause... bla bla bla bla.
> 2. The maximum pitch of a BNS is 17 while the echo can go up to 100. I 
> haven't figured out where the maximum allowable pitch for a synthesizer is 
> defined, so I haven't modified the driver yet.
> 3. Interrupting speech can be a bit... interesting. I find that numpad 
> enter doesn't always shut it up right away (buffer issues maybe?), but 
> things such as cursor movement do immediately make the echo stop what it 
> was doing and speak the new text.
>
> Hope at least someone finds this interesting. If anyone has some 
> suggestions for fixing the pause/buffer issue, don't hesitate to send them 
> to kleins@iquest.net. I'll be able to test them in August when I go back 
> to school.
>
> Garrett
>
> On Tue, Jul 05, 2005 at 12:28:14PM -0400, Igor Gueths wrote:
>> Hi all. I recently got a hold of a recording that Garrett Klein did of
>> his encounter with the PC version of an Echo. He managed to get it
>> working with Speakup using the BNS driver. I'm not sure how interested
>> people would be in this, however yesterday I uploaded
>> speakup_on_an_echo2.mp3. That was the entire file. However,
>> speakup_on_an_echo.mp3 is only a bit of the file since my connection
>> dropped and I had to restart the upload process. I checked to see if
>> speakup_on_an_echo2.mp3 had been moved to the goodies directory, however
>> I didn't see it. Should I re-upload the whole file to /pub/incoming? I
>> will say that the file right now is a little loud, however if there is
>> substancial interest for the re-upload I'll try again to turn down the
>> volume a bit.
>> -- 
>> How many chunks could checkchunk check if checkchunck could check chunks?
>> -- Alan Cox
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQFCyzqlpyN96jH+4g0RA54EAKCrxg16CMeaqBvMYSdU2gokrF93twCgktrd
> Z8a5vToj39rtdf4x5FITgPk=
> =jspN
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.323 / Virus Database: 267.8.9/39 - Release Date: 7/4/2005
>
> 



  parent reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Igor Gueths
 ` hank smith
   ` Jim Grimsby
 ` Nick Gawronski
 ` Garrett Klein
   ` Adam Myrow
     ` Gregory Nowak
   ` hank smith [this message]
   ` Jim Grimsby

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='004701c581e6$6ee88300$650fa8c0@home4rer2f14d7' \
    --to=hanksmith4@earthlink.net \
    --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).