public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
* A comment on Slashdot that concerns me
@  Matthew Campbell
   ` cpt.kirk
                   ` (8 more replies)
  0 siblings, 9 replies; 21+ messages in thread
From: Matthew Campbell @  UTC (permalink / raw)
  To: speakup

Here is one comment that was posted on Slashdot regarding ZipSpeak and
probably Speakup in general:

(begin quote)

   This is nothing but a threat to independent producers, and
   "slashdot"'s unquestioning boosting of a LinusX technology in this
   specialised and delicate market is inappropriate. Although the goal of
   having universal access to LinusX is laudable, that is not what this
   product offers. Rather, it offers access for the blind so long as they
   buy a speech synthesiser which is on the approved list. Those of us
   who make speech syntehsisers which didn't make it onto this hallowed
   team end up losing a whole chunk of our market because, even though
   our synthesisers offer a lot of important functionality for the blind
   ("easy listening" modulated voices, automatic timbre management,
   etc.), we didn't promote our product at the right time to the right
   developer.
   
   This product is particularly cruel as it locks in people forever to an
   inferior technology, by exploting the fact that they need speech
   synthesis if they are to run Linux at all. Zipspeak should be forced
   to provide support for all speech synthesiser by writing the
   appropriate drivers, and should forfeit their FDA approval and the
   tax-deductibility of their product if they continue to tilt the
   playing field for synthesisers. It is wholly irresponsible of them to
   come into an orderly marketplace and shake things up like this. We
   never had these problems with Apple (a company which, IMO, really
   "gets it" with regard to open standards) and only a few with
   Microsoft. What a shame that the so-called "altruists" of the LinusX
   community couldn't be a bit more understanding.
   
   Stephen Mundy
   
   --Murrinco

(end quote)

What have we done wrong?  Or what have I done wrong?  Should I have
delayed my release of ZipSpeak until there were drivers for all known
synthesizers?  Or should I have spent my spring break writing
synthesizer drivers?  I probably couldn't anyway, because I know
little about kernel programming and don't have any documentation for
synthesizers other than the DoubleTalk (though I could have learned
some from Emacspeak driver code).  Perhaps I should release an updated
ZipSpeak with the new drivers which are on the Speakup FTP site, even
though they're not yet in the official Speakup release.  But I figured
that since they're not in the official Speakup release, they probably
aren't ready for general use yet.

I really didn't mean any harm to the makers of unsupported speech
synthesizers, but I guess this person doesn't think so.  What do you
all think?

-- 
Matt Campbell <mattcamp@crosswinds.net>
Web site:  http://www.crosswinds.net/~mattcamp/
ICQ #:  33005941



^ permalink raw reply	[flat|nested] 21+ messages in thread
* Re: A comment on Slashdot that concerns me
@  Martin G. McCormick
   ` Tommy Moore
  0 siblings, 1 reply; 21+ messages in thread
From: Martin G. McCormick @  UTC (permalink / raw)
  To: speakup

	I think the commenter on slashdot is misguided.  I don't
happen to have any of the synthesizers on the list, but I still think
that this is a very worthwhile effort and should be continued.  The
only thing I would suggest is to have a raw serial mode option that we
can feed in to another working P.C. if all else fails.  That would
allow anybody to use anything capable of serial data reception.  Of
course, somebody would gripe about that, but there are some who would
gripe if hung with a new rope provided free of charge.

Martin McCormick WB5AGZ


^ permalink raw reply	[flat|nested] 21+ messages in thread
* Re: A comment on Slashdot that concerns me
@  Martin G. McCormick
   ` Tommy Moore
  0 siblings, 1 reply; 21+ messages in thread
From: Martin G. McCormick @  UTC (permalink / raw)
  To: speakup

	That's quite true.  The only thing you don't have is serial
access during the initial configuration such as installation or during
the boot sequence.  Usually, it isn't all that necessary to have the
boot messages talking, but it is nice to have that capability if
something goes wrong and it is time to start being a diagnostition.

	I also got on to slashdot.org and read a lot of the linux VS
Windows thread.  I am not sure if some of those folks are actually
serious with some of their assumptions or are just jerking our chains
to see what we do.

	Anyway, the one thing I have not heard anybody say is that a
text-based interface is usable by everybody by one means or another.
A so-called graphical interface must be modified for any other form of
access.  When blind people use Windows, it is only because there has
been some progress in making it sort of behave like a command line
interface.  There just is not a good way to directly translate purely
visual information in to anything else that works as well.

	There is an interesting experiment that Bell Labs did in 1951.
I remember the year because it happens to be the year I was born so
things like that kind of stand out.

	What they did was to build a rather clever voice synthesizer
for that day out of a spinning wheel with bands of holes in it.  When
the wheel was spun at a certain rate, the holes raced past at
different frequencies.  A light shown through the holes and struck a photo
cell like the kind used in film projectors to convert the wavy band of
the film sound track to speech and music.  By blocking or unblocking
light from different bands of holes, the scientists could produce lots
of musical tones of different pitches.

	The next neat thing they did was to record a human voice on a
spectrograph which draws varying lines on a strip of film that
correspond to all the constituent frequencies in the sound being
recorded.  In this case, it was a man saying "Never kill a snake with
your bare hands."

	They took the film and used it to block and unblock the beams
of light through the bands of holes on their sound generator.  The
bands of holes corresponded to the center frequencies of all the
octave bands on the spectrograph machine.  The result was a voice that
sounds kind of like a DecTalk saying the recorded sentence very
clearly.

	The spectrogram looks like strange light and dark bands on the
film and means little to the eye except maybe that of an engineer, but
it did cause the generator to produce pretty good speech.

	The scientists then tried to make speech of their own by
manually painting spectrograms in a way that they thought would
produce new words and voices.  It never did anything but make weird
noises.

	My whole point is that the easiest way for a person who is
blind to do complex tasks on a computer is to use text.  It may be
that when tactile displays become dirt cheap and we can put our hands
on a screen and feel shapes, we may actually get closer to using a
GUI, but right now, we only use Windows when it can be bludgeoned in to
behaving like a command line.  Think about it.

	By the way, the only reason I remember the Bell Labs
experiments is because they appeared in a Bell Telephone Hour special
in the late fifties on television and I happened later to read about
them while doing a report in Graduate school.  My memory back to
earlier times is probably no better than anybody else's.  Just thought
I had better throw that in.

Martin McCormick WB5AGZ  Stillwater, OK 
OSU Center for Computing and Information Services Data Communications Group
Tommy Moore writes:
>Serial port accss is allready possible. I used it for months before
>speakup came out. You just have to figure out how to get the serial port
>to let you login off of it so that you can access it from another pc.
>
>
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup
>


^ permalink raw reply	[flat|nested] 21+ messages in thread
end of thread, other threads:[~ UTC | newest]

Thread overview: 21+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
 A comment on Slashdot that concerns me Matthew Campbell
 ` cpt.kirk
 ` Victor Tsaran
 ` Mike Gorse
   ` cpt.kirk
 ` cpt.kirk
   ` Tommy Moore
   ` Victor Tsaran
 ` Kirk Reiser
   ` cpt.kirk
     ` Victor Tsaran
   ` Janina Sajka
 ` Dave Talmage
   ` kestrell
 ` Brian Borowski
 ` Ron Kassen
 ` Peter Persuric
 Martin G. McCormick
 ` Tommy Moore
 Martin G. McCormick
 ` Tommy Moore

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