RE: Apollo synthesizer problem

RE: Apollo synthesizer problem

[Tim Burgess]

Hi,

If I remember rightly (and it was a long time ago) the buffering and
indexing on the Apollo/Juno synths got changed in one of the firmware
updates that Dolphin issued.  Might be that you've fell foul of this if
yours is a very old unit that's never had an update.  Can't remember the "@"
command for finding out the firmware revision though - probably worth
checking your manual or calling your dealer.

Hope that helps.

Tim


-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Kirk Reiser
Sent: 01 October 2002 20:34
To: speakup@braille.uwo.ca
Subject: Re: Apolo synthasizer problem


I may have seen a little choppieness with the Apollo but not anywhere
near what you indicate in your example.  There are lots of folks on
the list using the Apollo so maybe we can get some more feedback from
them.  From your example I can't tell anything.

  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

Apolo synthasizer problem

[Darragh]

Hello all,
I'm using Speak up with an Apolo 2 synthasizer.  I'm just writing to ask why
its so jumpy.  for example.  if I read a line man page for emacspeak it will
read ma n pa age for EMacspeak.  Any one have any ideas?

P.S. I got the keyboard issue sorted out.  Was my own mistake.

Darragh

Re: Apolo synthasizer problem

[Buddy Brannan]

I couldn't swear to this...I have used a Juno with Speakup--same thing
as the Apollo really--and got the same results. Anyway, I think it has
to do with the way that the Apollo receives stuff to speak...I think
(if I remember the docs rightly) that it has like an 8K buffer, which
probably includes all he control commands. I expect that what's
happening is that when the buffer fills up, it empties and speaks the
next bit...regardless of whether it's split in the middle of a word or
not. This is a slight annoyance, but I don't know that there's a way
around it. (Maybe there is, but I don't know what it is in the
constraints of a kernel-space speech driver.) Anyway, I'm sure Kirk
will tell me if I've got the whole reason wrong :)
-- 
Buddy Brannan, KB5ELV/3   | "And if the ground yawned,
Phone: (814) 455-7333     | I'd step to the side and say,
Email: davros@ycardz.com  | "Hey ground! I'm nobody's lunch!"
http://www.ycardz.com/    | --Eddie From Ohio

Re: Apolo synthasizer problem

[Toby Fisher]

On Tue, 1 Oct 2002, Buddy Brannan wrote:

> I couldn't swear to this...I have used a Juno with Speakup--same thing
> as the Apollo really--and got the same results. Anyway, I think it has
> to do with the way that the Apollo receives stuff to speak...I think
> (if I remember the docs rightly) that it has like an 8K buffer, which
> probably includes all he control commands. I expect that what's
> happening is that when the buffer fills up, it empties and speaks the
> next bit...regardless of whether it's split in the middle of a word or
> not. This is a slight annoyance, but I don't know that there's a way
> around it. (Maybe there is, but I don't know what it is in the
> constraints of a kernel-space speech driver.) Anyway, I'm sure Kirk
> will tell me if I've got the whole reason wrong :)

Hmmm, I don't think this can be the whole story, as I used to use a Juno
under DOS with Hal, and didn't have this problem, at least not as often.
If the buffer got too full, about 2 or 3 pages, it just emptied it and
carried on scrolling, so you'd miss huge chunks.  My guess it's more
likely to have something to do with how stuff is sent to the serial port,
though I can't be certain of course.

Cheers.

-- 
Toby Fisher	Email: toby@g0ucu.freeserve.co.uk
Tel.: +44(0)1480 417272	Mobile: +44(0)7974 363239
ICQ: #61744808
   Please avoid sending me Word or PowerPoint attachments.
   See http://www.fsf.org/philosophy/no-word-attachments.html

Re: Apolo synthasizer problem

[Kirk Reiser]

I may have seen a little choppieness with the Apollo but not anywhere
near what you indicate in your example.  There are lots of folks on
the list using the Apollo so maybe we can get some more feedback from
them.  From your example I can't tell anything.

  Kirk

-- 

Kirk Reiser				The Computer Braille Facility
e-mail: kirk@braille.uwo.ca		University of Western Ontario
phone: (519) 661-3061

Re: Apolo synthasizer problem

[Darragh]

Sorry, I don't really know how to explain it, its as if your reading very
short lines with a damaged word rap function.  One part of the word is on
the end of one line and the rest is on the next.  I didn't have the problem
with 7.3 as much but it was at times noticible, for example when reading the
man pages.  I hope thats clarafied something

Darragh
----- Original Message -----
From: "Kirk Reiser" <kirk@braille.uwo.ca>
To: <speakup@braille.uwo.ca>
Sent: Tuesday, October 01, 2002 8:34 PM
Subject: Re: Apolo synthasizer problem


> I may have seen a little choppieness with the Apollo but not anywhere
> near what you indicate in your example.  There are lots of folks on
> the list using the Apollo so maybe we can get some more feedback from
> them.  From your example I can't tell anything.
>
>   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
>

Re: Apolo synthasizer problem

[Kirk Reiser]

What processor are you using?  Also, what version of the kernel?  This
almost sounds like you are suffering from the new hz = 1000 instead of
100 change.

  Kirk

-- 

Kirk Reiser				The Computer Braille Facility
e-mail: kirk@braille.uwo.ca		University of Western Ontario
phone: (519) 661-3061

Re: Apolo synthasizer problem

[Darragh]

The Kurnel version that I have installed is 2.4.18.14 on an I686.  I bought
the Apolo about hmm five months ago.

The disc that came with it gave useless information on connecting the synth
to a serial port so I just formatted it and used it for something else.  I
could probably find the contents on the hard disc somewhere if absolutely
necessary.

Darragh
----- Original Message -----
From: "Kirk Reiser" <kirk@braille.uwo.ca>
To: <speakup@braille.uwo.ca>
Sent: Tuesday, October 01, 2002 9:19 PM
Subject: Re: Apolo synthasizer problem


> What processor are you using?  Also, what version of the kernel?  This
> almost sounds like you are suffering from the new hz = 1000 instead of
> 100 change.
>
>   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
>

Re: Apolo synthasizer problem

[Buddy Brannan]

Half a mo...

They're still making the Apollo?!

Dolphin's Web site gives no indication of this!

The manual actually is useful. It has control codes in it :)
-- 
Buddy Brannan, KB5ELV/3   | "And if the ground yawned,
Phone: (814) 455-7333     | I'd step to the side and say,
Email: davros@ycardz.com  | "Hey ground! I'm nobody's lunch!"
http://www.ycardz.com/    | --Eddie From Ohio

Re: Apolo synthasizer problem

[William F. Acker WB2FLW +1-303-777-8123]

Kirk nailed this one.  HZ is set to 512.  To compensate, you'll need to 
change the timing variables for Speakup.  In the /proc/speakup/apollo 
directory, you'll se files called jiffy_delta and delay_time, among others.  
Note that I might not have spelled apollo the way it is in the 
/proc/speakup directory.  Use the "cat" command to display the value 
contained in the two pseudo files.  For example: "cat jiffy_delta" and "cat 
delay_time", without the quotes, of course.  To change a value, use the 
"echo" command.  For example: "echo 15 > jiffy_delta" and "echo 80> 
delay_time".  Using cat, find the value of jiffy_delta.  Multiply the value 
by five.  For example, if the value of jiffy_delta is 3, make it 15.  Then, 
find the value of delay_time.  Divide it by 5.  For example, if you find 
400, make it 80.  If this works, you can write a script to make this 
happen on boot.



          HTH.
-- 
          Bill in Denver


On 1 Oct 2002, Kirk Reiser wrote:

> What processor are you using?  Also, what version of the kernel?  This
> almost sounds like you are suffering from the new hz = 1000 instead of
> 100 change.
> 
>   Kirk
> 
> 

Re: Apolo synthasizer problem

[Darragh]

Excelent, that works a lot better.  If I devided and multiplied the values
by six seven or more would it get better?  Its still not continious.  If
that would work it would make the apolo a lot easier to listen to.

I suppose the next step is writing a script.  But How? with what?

Thanks again

Darragh
----- Original Message -----
From: "William F. Acker WB2FLW +1-303-777-8123" <wacker@octothorp.org>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, October 02, 2002 6:26 AM
Subject: Re: Apolo synthasizer problem


> Kirk nailed this one.  HZ is set to 512.  To compensate, you'll need to
> change the timing variables for Speakup.  In the /proc/speakup/apollo
> directory, you'll se files called jiffy_delta and delay_time, among
others.
> Note that I might not have spelled apollo the way it is in the
> /proc/speakup directory.  Use the "cat" command to display the value
> contained in the two pseudo files.  For example: "cat jiffy_delta" and
"cat
> delay_time", without the quotes, of course.  To change a value, use the
> "echo" command.  For example: "echo 15 > jiffy_delta" and "echo 80>
> delay_time".  Using cat, find the value of jiffy_delta.  Multiply the
value
> by five.  For example, if the value of jiffy_delta is 3, make it 15.
Then,
> find the value of delay_time.  Divide it by 5.  For example, if you find
> 400, make it 80.  If this works, you can write a script to make this
> happen on boot.
>
>
>
>           HTH.
> --
>           Bill in Denver
>
>
> On 1 Oct 2002, Kirk Reiser wrote:
>
> > What processor are you using?  Also, what version of the kernel?  This
> > almost sounds like you are suffering from the new hz = 1000 instead of
> > 100 change.
> >
> >   Kirk
> >
> >
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: Apolo synthasizer problem

[Geoff Shang]

On Wed, 2 Oct 2002, Darragh wrote:

> Excelent, that works a lot better.  If I devided and multiplied the values
> by six seven or more would it get better?  Its still not continious.

I should warn people that messing around with these values can crash your
system.  Remember you're changing the way the kernel operates, and extreme
values in either direction could cause the kernel to fall over.  Bare this
in mind when adjusting values in /proc/<synthname>.

Geoff.

Re: Apolo synthasizer problem

[Toby Fisher]

On Tue, 1 Oct 2002, William F. Acker WB2FLW +1-303-777-8123 wrote:

> Kirk nailed this one.  HZ is set to 512.  To compensate, you'll need to
> change the timing variables for Speakup.  In the /proc/speakup/apollo
> directory, you'll se files called jiffy_delta and delay_time, among others.
> Note that I might not have spelled apollo the way it is in the
> /proc/speakup directory.  Use the "cat" command to display the value
> contained in the two pseudo files.  For example: "cat jiffy_delta" and "cat
> delay_time", without the quotes, of course.  To change a value, use the
> "echo" command.  For example: "echo 15 > jiffy_delta" and "echo 80>
> delay_time".  Using cat, find the value of jiffy_delta.  Multiply the value
> by five.  For example, if the value of jiffy_delta is 3, make it 15.  Then,
> find the value of delay_time.  Divide it by 5.  For example, if you find
> 400, make it 80.  If this works, you can write a script to make this
> happen on boot.
>
>

Hmmm, it does improve it somewhat, but does not cure it altogether.

Cheers.
-- 
Toby Fisher	Email: toby@g0ucu.freeserve.co.uk
Tel.: +44(0)1480 417272	Mobile: +44(0)7974 363239
ICQ: #61744808
   Please avoid sending me Word or PowerPoint attachments.
   See http://www.fsf.org/philosophy/no-word-attachments.html

Re: Apolo synthasizer problem

[Darragh]

If I under stand you right, your having the same problem?  When I go back
into Linux later I'm going to have a bit of a mess around with it.  Its not
a permanant change so "hopefully" if it crashes on me I can just reboot and
try again.  I have a feeling though if you increase five to six it may
improve slightly.  I'll try it out of curiosity.

Darragh
----- Original Message -----
From: "Toby Fisher" <toby_fisher@bigfoot.com>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, October 02, 2002 1:25 PM
Subject: Re: Apolo synthasizer problem


> On Tue, 1 Oct 2002, William F. Acker WB2FLW +1-303-777-8123 wrote:
>
> > Kirk nailed this one.  HZ is set to 512.  To compensate, you'll need to
> > change the timing variables for Speakup.  In the /proc/speakup/apollo
> > directory, you'll se files called jiffy_delta and delay_time, among
others.
> > Note that I might not have spelled apollo the way it is in the
> > /proc/speakup directory.  Use the "cat" command to display the value
> > contained in the two pseudo files.  For example: "cat jiffy_delta" and
"cat
> > delay_time", without the quotes, of course.  To change a value, use the
> > "echo" command.  For example: "echo 15 > jiffy_delta" and "echo 80>
> > delay_time".  Using cat, find the value of jiffy_delta.  Multiply the
value
> > by five.  For example, if the value of jiffy_delta is 3, make it 15.
Then,
> > find the value of delay_time.  Divide it by 5.  For example, if you find
> > 400, make it 80.  If this works, you can write a script to make this
> > happen on boot.
> >
> >
>
> Hmmm, it does improve it somewhat, but does not cure it altogether.
>
> Cheers.
> --
> Toby Fisher Email: toby@g0ucu.freeserve.co.uk
> Tel.: +44(0)1480 417272 Mobile: +44(0)7974 363239
> ICQ: #61744808
>    Please avoid sending me Word or PowerPoint attachments.
>    See http://www.fsf.org/philosophy/no-word-attachments.html
>
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>