From: Glenn <glennervin@cableone.net>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: Speakup on the raspberry pi?
Date: Thu, 17 Jan 2013 22:56:31 -0600 [thread overview]
Message-ID: <82F4B6439A26450C93BE1135E83FD035@your2c061f0461> (raw)
In-Reply-To: <loom.20130118T054245-995@post.gmane.org>
What are you housing your Raspberry Pi in?
I bought a case for mine for a few bucks, but it is round, shaped like a
large smoke detector, and all I can think that I can do with the plugs is to
plug them in and run them through the hole in the middle of this smoke
detector.
I wonder if it would fit into a plastic cassette case?
An Altoids box would work if the tin did not have rounded corners.
Glenn
----- Original Message -----
From: "Tomi" <gt1991@Gmail.com>
To: <speakup@braille.uwo.ca>
Sent: Thursday, January 17, 2013 10:47 PM
Subject: Re: Speakup on the raspberry pi?
Kelly Prescott <kprescott <at> coolip.net> writes:
>
> Guys, I have compiled speakup for debian and arch on the pi.
> I am in the process of moving to a new apartment just now, so I cannot
> post my links, but I will write up a little howto and post the compiled
> modules early next week.
> I was going to do it earlier, but the holidays got me busy.
> Thanks.
> kp
Hi Kelly and others on this list,
I really, really hope this isn't too soon to re-post about this topic... I'm
just wondering if any progress has been made by anyone on making the Pi
talk.
I've done a few experiments as per trying to reduce the pops made by the
audio
device.
Also, why is this list so low traffic? It saddens me deeply! Has it moved to
another server?
Anyway. iIinstalled pulseaudio on the pi, thinking it would stop the
crackles.
It really didn't because pulse goes through Alsa.
What's even weirder is that speech-dispacher can't seem to be able to speak
through spd-say, but espeak talks just through the espeak command. I don't
know
why this is, but I suspect it's a hardware thing. I've reconfigured speech
dispatcher, without much luck. I even got orca to run in the standard
desktop,
but all I hear is a loud pop when it starts (alt+F2 still works to open a
run
dialog in the desktop environment, so after apt-get gnome-orca one can
blindly
run it). I suspect that this is because orca obviously passes stuff to
speech
dispacher, which can't talk.
All the best,
Tomi
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
speakup on the Raspberry Pi Kelly Prescott
` Peter Lecky
` Kelly Prescott
` Jason Miller
` Kelly Prescott
` Peter Lecky
` Kelly Prescott
` Jim Kutsch
` Kelly Prescott
` Glenn
` Jason Miller
` Glenn
` Kelly Prescott
` Glenn
` Kelly Prescott
` Jason Miller
` Glenn
` Kelly Prescott
` Glenn
` Glenn
` speakup on the Raspberry Pi / compiling speakup modules Robert Epprecht re
` Speakup on the raspberry pi? Tomi
` Glenn
` Kelly Prescott
` Tomi
` Tomi
` Glenn [this message]
` speakup in raspberry pi modules Kelly Prescott
` Scott D. Henning
` Jason Miller
` Georgina Joyce
` John G. Heim
` Jason Miller
` Kelly Prescott
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=82F4B6439A26450C93BE1135E83FD035@your2c061f0461 \
--to=glennervin@cableone.net \
--cc=glennervin@gmail.com \
--cc=speakup@linux-speakup.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).