* Speakup and Apollo 2
@ Michela Botti
` Kirk Reiser
0 siblings, 1 reply; 4+ messages in thread
From: Michela Botti @ UTC (permalink / raw)
To: speakup
Hi listers!
I've been apart from the list for a couple of months this summer, and I
didn't check out if this argument has already been treated.
I want to report two little problems of the Apollo 2 driver (or whatever
thise problems are concerned with).
While moving not too sloly the reading cursor around the screen, the sinth
sometimes says the word "f8", even if it isn't found on the screen.
When using the numpad 7, 8, and 9 command or while reading more than one
line of text, Apollo 2 doesn't read continuously, but it inserts frequent
short breaks (maybe one evry 10 or 15 words) even whithin a word; it is
sometimes necessary to read a text with the numpad 4 and numpad 6 commands
(most of all while reading in English which is not my mothertong), and this
may take a longer time.
Best regards
Michela
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Speakup and Apollo 2
Speakup and Apollo 2 Michela Botti
@ ` Kirk Reiser
0 siblings, 0 replies; 4+ messages in thread
From: Kirk Reiser @ UTC (permalink / raw)
To: speakup
Hi Michela: The f8 problem is common to most of the serial synths.
It is because the first character of the command sequence is being
cleared but the remainder of the sequence is making it through. Once
I have the next version of speakup released I am planning on going
back through the drivers and trying to fix some of those little
irritations. The breaking up of synth output I am also aware of but
thought that I had fixed the problem. It is an issue with how much
time to keep the processor and yet not slow down the system for all
other processes. I will go back and take a look at the apollo code
and make changes if I can. What version of speakup are you using?
Kirk
--
Kirk Reiser The Computer Braille Facility
e-mail: kirk@braille.uwo.ca University of Western Ontario
phone: (519) 661-3061
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: Speakup and Apollo 2
@ Holmes, Steve
0 siblings, 0 replies; 4+ messages in thread
From: Holmes, Steve @ UTC (permalink / raw)
To: 'speakup@braille.uwo.ca'
What version are we up to now. I recently downloaded 0.09 from a link
through Joe Norton's web site. I so far have just used the boot disk for
Speakout and loaded that image into my boot kernel image. I haven't done
any kernel patch/recompile yet. My box has only been running a couple weeks
so far.
-----Original Message-----
From: Kirk Reiser [mailto:kirk@braille.uwo.ca]
Sent: Wednesday, November 29, 2000 5:49 AM
To: speakup@braille.uwo.ca
Subject: Re: Speakup and Apollo 2
Hi Michela: The f8 problem is common to most of the serial synths.
It is because the first character of the command sequence is being
cleared but the remainder of the sequence is making it through. Once
I have the next version of speakup released I am planning on going
back through the drivers and trying to fix some of those little
irritations. The breaking up of synth output I am also aware of but
thought that I had fixed the problem. It is an issue with how much
time to keep the processor and yet not slow down the system for all
other processes. I will go back and take a look at the apollo code
and make changes if I can. What version of speakup are you using?
Kirk
--
Kirk Reiser The Computer Braille Facility
e-mail: kirk@braille.uwo.ca University of Western Ontario
phone: (519) 661-3061
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: Speakup and Apollo 2
@ Holmes, Steve
0 siblings, 0 replies; 4+ messages in thread
From: Holmes, Steve @ UTC (permalink / raw)
To: 'speakup@braille.uwo.ca'
I notice something similar with the Speakout as well. In my case, I hear
things like P3 which is a pitch command for the Speakout. I think what is
happening here is when pressing keys rapidly and interrupting speech that
some commands intended for the synthesizer are getting spoken instead of
being obeyed:). With Speakout, ctrl-E is the command code and I think that
code is getting dropped thus the remaining command text will get spoken. Is
F8, by chance, a command string for the Apollo? I used to see a lot of this
with serial synthesizers in the past with DOS and windows but then things
improved over time. At least, I don't hear other characters being dropped
so I do think the hardware handshaking is working OK.
-----Original Message-----
From: Michela Botti [mailto:mibotti@tiscalinet.it]
Sent: Wednesday, November 29, 2000 5:17 AM
To: speakup@braille.uwo.ca
Subject: Speakup and Apollo 2
Hi listers!
I've been apart from the list for a couple of months this summer, and I
didn't check out if this argument has already been treated.
I want to report two little problems of the Apollo 2 driver (or whatever
thise problems are concerned with).
While moving not too sloly the reading cursor around the screen, the sinth
sometimes says the word "f8", even if it isn't found on the screen.
When using the numpad 7, 8, and 9 command or while reading more than one
line of text, Apollo 2 doesn't read continuously, but it inserts frequent
short breaks (maybe one evry 10 or 15 words) even whithin a word; it is
sometimes necessary to read a text with the numpad 4 and numpad 6 commands
(most of all while reading in English which is not my mothertong), and this
may take a longer time.
Best regards
Michela
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
^ 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 and Apollo 2 Michela Botti
` Kirk Reiser
Holmes, Steve
Holmes, Steve
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).