public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
* Re: speakup wierdness answers
   speakup wierdness answers tyler spivey
@  ` Kerry Hoath
   ` Geoff Shang
   ` Kirk Wood
  2 siblings, 0 replies; 4+ messages in thread
From: Kerry Hoath @  UTC (permalink / raw)
  To: speakup

There is no driver. You can't fudge it.
It won't work. You can't redirect to an emulated port, even if you could how
are you going to get the information back? A dectalk pc is not a dectalk express
with no serial port; it is a different beast.
What you are trying to do is impossible.
Doubletalks are cheap they work well and are reliable, consider saving for one.
Your dectalk PC will not work under speakup at this time no matter how many
cables you hook up or cludges you implement. It can't happen.
Speakup does not implement a raw ascii interface to the synthisizer with no
control codes because there is no way to silence the synth. If you want raw
text to a serial port use a serial console. Linux _can_ show everything on a
serial port and if you have a null modem cable serial console is the way to
go. If you can't buy more hardware; you'll have to use a serial
console and what you have currently.
On Wed, Oct 25, 2000 at 11:39:50PM -0700, tyler spivey wrote:
> i cant afford a synth right now, and i dont like transmitting at 19.2k baud 
> with my crappy uart.
> so i am trying to make speakup think decpc is a decext by setting screen 
> capture to its emulated port.
> i am just trying to make it send all its info to my dectalk,
> ignoring any input from the synth because speakup doesn't use indexing i 
> dont think.
> so i set up my screen capture to raw mode and speakup doesnt seem to send a 
> null to the synthasizer when it is done speaking.
> if it did that i think this would work.
> i think a new feature in speakup would be a way to zap cmds to a synth like 
> dos screen readers.
> and why isn't the shut up cmd recognized? like in the other synths it'll 
> shut up, but mine just keeps
> babaling.  i think it shut up after about 3 minutes of its boot messages.
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
--
Kerry Hoath: kerry@gotss.eu.org
Alternates: kerry@emusys.com.au kerry@gotss.spice.net.au or khoath@lis.net.au
ICQ UIN: 62823451



^ permalink raw reply	[flat|nested] 4+ messages in thread

* speakup wierdness answers
@  tyler spivey
   ` Kerry Hoath
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: tyler spivey @  UTC (permalink / raw)
  To: speakup

i cant afford a synth right now, and i dont like transmitting at 19.2k baud 
with my crappy uart.
so i am trying to make speakup think decpc is a decext by setting screen 
capture to its emulated port.
i am just trying to make it send all its info to my dectalk,
ignoring any input from the synth because speakup doesn't use indexing i 
dont think.
so i set up my screen capture to raw mode and speakup doesnt seem to send a 
null to the synthasizer when it is done speaking.
if it did that i think this would work.
i think a new feature in speakup would be a way to zap cmds to a synth like 
dos screen readers.
and why isn't the shut up cmd recognized? like in the other synths it'll 
shut up, but mine just keeps
babaling.  i think it shut up after about 3 minutes of its boot messages.



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: speakup wierdness answers
   speakup wierdness answers tyler spivey
   ` Kerry Hoath
@  ` Geoff Shang
   ` Kirk Wood
  2 siblings, 0 replies; 4+ messages in thread
From: Geoff Shang @  UTC (permalink / raw)
  To: speakup

Hi:

Firstly, a Dec PC is not a Dec express or external, and therefore there's
no real reason why any of the commands have to be the same.  Secondly,
you're putting another pipe between speakup and the synth.  Probably the
reason why shut up takes 20 years to work is because of the buffering by
your comms package.  Speakup is going to dump all it can in one shot if it
doesn't get told not to by your synth, so when you hit the shut up command,
speakup will send it then, not several seconds ago when the text you're
listening to was sent.

I agree with Kerry.  Run a serial console and you'll be just fine.  Linux
rarely crashes anyway, so it's not a real hassle.  I used a serial port
login, not even a console, for 10 months before my synth got supported, and
rarely if ever had trouble with it.  Either run a serial console or use a
normal serial login and edit inittab to dump system messages to your serial
port.  But a serial console will probably be just as simple to implement.  
Oh and invest in a decent UART otherwise you'll drive yourself nuts.

BTW: There is a direct interface to the synth via loadspk I think, but I
can't remember the command.

Geoff.


-- 
Geoff Shang <gshang10@scu.edu.au>
ICQ number 43634701



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: speakup wierdness answers
   speakup wierdness answers tyler spivey
   ` Kerry Hoath
   ` Geoff Shang
@  ` Kirk Wood
  2 siblings, 0 replies; 4+ messages in thread
From: Kirk Wood @  UTC (permalink / raw)
  To: speakup

Well the first thing that jumps out of this situation is that the dectalk
is well known to not shutup. The next thing is that adding a layer of
abstraction (having an internal synth emulate an external one) sounds like
an excelent plan to magnify such shortcommings.

Next thing is what is this screen capture thing? It really sounds like you
are trying to do something that is beyond the intent and design of the
program.

=======
Kirk Wood
Cpt.Kirk@1tree.net







^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~ UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
 speakup wierdness answers tyler spivey
 ` Kerry Hoath
 ` Geoff Shang
 ` Kirk Wood

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).