public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Brent Harding" <bharding@doorpi.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: [OT] emulating a hardware synth
Date: Tue, 3 Feb 2009 08:41:31 -0600	[thread overview]
Message-ID: <870A38BE6D114B058E8ADDE72AF67B7E@BRENT827E59CC1> (raw)
In-Reply-To: <20090203064540.GA31921@csy.ca>

So, do you just use this on an untaken serial port and tell VMWare to also 
use that serial port so they would end up virtually connected? I thought 
there was one called echo talk or something using the JFW API on the Windows 
side and simulating an echo synth to whatever is connected to that port.

----- Original Message ----- 
From: "Shane W" <shane-speakup@csy.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Tuesday, February 03, 2009 12:45 AM
Subject: Re: [OT] emulating a hardware synth


> Hi,
>
> Fyi, just put a new version of the Windows Acntsa emulator
> up:
> <http://www.csy.ca/~shane/winaccent.zip>
>
> This one gets the timeouts right so now works with Speakup
> either under an Vmware session or via a remote serial
> connection.
>
> Question to the speakup devs, why does the ACNTSA driver
> use a timeout of 0.16 seconds and rely on that to start
> transmitting even during keyboard io where you want to
> transmit as soon as a key is pressed, Ie with <esc>=F in
> the init string and 0x0d when a key is pressed.  That way
> there is no 0.14 second delay after a key is pressed before
> the letter is read allowed?
>
> Shane
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 


  parent reply	other threads:[~ UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Robert Epprecht
 ` Tyler Littlefield
 ` Gregory Nowak
     [not found]   ` <20090131004845.GA11780@csy.ca>
     ` Tyler Littlefield
     ` Glenn Ervin
     ` Tony Baechler
     [not found]       ` <20090131170911.GA18464@csy.ca>
         ` Tyler Littlefield
     [not found]           ` <20090201003624.GA9189@csy.ca>
             ` Zachary Kline
     [not found]               ` <20090201010547.GA10597@csy.ca>
                 ` Tyler Littlefield
     [not found]                   ` <20090203064540.GA31921@csy.ca>
                     ` Brent Harding [this message]
     [not found]                       ` <20090203165103.GB23477@csy.ca>
                         ` Brent Harding
     [not found]                           ` <20090203213929.GA8410@csy.ca>
                             ` Brent Harding
     [not found]                               ` <20090204032452.GA20917@csy.ca>
                                 ` Brent Harding
   ` Glenn Ervin
   ` Robert Epprecht

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=870A38BE6D114B058E8ADDE72AF67B7E@BRENT827E59CC1 \
    --to=bharding@doorpi.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).