public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
* Speakup Configurator
@  Steve Holmes
   ` Thomas Ward
                   ` (2 more replies)
  0 siblings, 3 replies; 8+ messages in thread
From: Steve Holmes @  UTC (permalink / raw)
  To: speakup

I think what I'm gonna do is try and accomodate Speakout and Doubletalk
first. This will enable me to get the program to save valid parameter
features and ranges for each synthesiser so that the proper features and
ranges can be made available automatically depending on which synthesiser
is currently being used. Once this is accomplished, I should be able to
add other synthesisers in the future with much less fuss. Right now, I
hard coded things thinking of one box and well I got painted into a corner
real fast! Gee, thought my programming skills could have helped me avoid
that trap:).

One general question I would like to ask of all synthesiser users though,
What about parameters that allow for a hundred or more choices? I'm
thinking of a range of 00 to 99 or something like that. With my current
design, one could end up having to press up or down arrow a hundred times
to make the complete loop. Would it be necessary to stop at every point or
would it be acceptable to say, skip every ten values to scale our keyboard
approach to having ten choices instead of a hundred.

Whad do you all think?



^ permalink raw reply	[flat|nested] 8+ messages in thread
* RE: Speakup Configurator
@  Watson, Keith
  0 siblings, 0 replies; 8+ messages in thread
From: Watson, Keith @  UTC (permalink / raw)
  To: 'speakup@braille.uwo.ca'

Why not just set it up that ctrl-arrow increments by 10's and arrow
increments by 1's? That would solve the large number problem.

Keith

-----Original Message-----
From: Steve Holmes [mailto:steve@holmesgrown.com]
Sent: Monday, October 08, 2001 11:43 AM
To: speakup@braille.uwo.ca
Subject: Speakup Configurator


I think what I'm gonna do is try and accomodate Speakout and Doubletalk
first. This will enable me to get the program to save valid parameter
features and ranges for each synthesiser so that the proper features and
ranges can be made available automatically depending on which synthesiser
is currently being used. Once this is accomplished, I should be able to
add other synthesisers in the future with much less fuss. Right now, I
hard coded things thinking of one box and well I got painted into a corner
real fast! Gee, thought my programming skills could have helped me avoid
that trap:).

One general question I would like to ask of all synthesiser users though,
What about parameters that allow for a hundred or more choices? I'm
thinking of a range of 00 to 99 or something like that. With my current
design, one could end up having to press up or down arrow a hundred times
to make the complete loop. Would it be necessary to stop at every point or
would it be acceptable to say, skip every ten values to scale our keyboard
approach to having ten choices instead of a hundred.

Whad do you all think?


_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup


^ permalink raw reply	[flat|nested] 8+ messages in thread
* Speakup Configurator
@  Steve Holmes
   ` Buddy Brannan
  0 siblings, 1 reply; 8+ messages in thread
From: Steve Holmes @  UTC (permalink / raw)
  To: speakup

After sending sp-config to the list yesterday, I learned from a couple
DoubleTalk users that the tone and pitch parameters are apparently
different from how they work with the Speakout, my box of choice.

The program simply sends the parms to /proc/speakup/<whatever> like rate
goes to /proc/speakup/rate. I gues what I need next are two things:
- The various allowed parms for each synthesiser supported by Speakup.
- A good solid method of detecting what synth is currently being used.

I guess the second could be resolved in the short term by capturing the
name on the command line using the speakup-defined synthesiser names.
Since I don't own any of the other synth's, I'll have to colect this info
from you all; gee, this might repeat what other speakup developers have
done already:).

Once I have the synthesiser identified, I could go and add the additional
parms supported by that box as long as /proc/speakup files are available.

Thanks for the help.



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

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

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
 Speakup Configurator Steve Holmes
 ` Thomas Ward
 ` Michael
   ` Jason
 ` Thomas Stivers
  -- strict thread matches above, loose matches on Subject: below --
 Watson, Keith
 Steve Holmes
 ` Buddy Brannan

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