Chris, No the no speech is not due to SSH. That's how I connect to the Pi. Try these steps: First try running this: speaker-test -c 2 You should hear a load of pink noise alternating between right and left channels. Stop it with control C. Next, try turning up the volume/un-muting with: alsamixer When alsamixer starts listen to your screen-reader and if at some point it says 'mute' press the up arrow a large number of times until the screen-reader no longer gabbles. Now press escape to exit alsamixer. Try the speaker-test again. I guess this will solve it because I think the sound is muted by default. Now. if you still have no sound, check you have the espeak data files. I think these are installed along with the synth so you should get a result: sudo find / -name phontab If no file is found, do this: sudo apt-get install espeak-data If you do this step, try speaking again once the install of the data files has finished. If you get no speech, try doing it as root, like this: sudo espeak "text to be spoken" 2> /dev/null If still nothing then I will try flashing a fresh install of Raspbian and see what I need to do to get it working. I know this is a silly question, but I presume you do have speakers or headphones plugged in and they are turned on/up? Careful with headphones because the Pi can be loud. Mike On 14/03/2013 14:34, Christopher Emery wrote: > Hello Michael, > No I didn't get any sound (sad face). Is this because I am sshing into the > pi? If so how can I get sound to come out of my computer setup that I am > sshing / remoting into ? > > Sincerely in Christ, > Christopher > > On Thu, Mar 14, 2013 at 10:16 AM, Michael A. Ray > <mike.ray@xxxxxxxxxxxxxx>wrote: > >> Chris, >> >> It's normal to get these errors. I don't know how to get rid of them. >> >> You still got the speech though, right? >> >> You could avoid these errors by doing this: >> >> espeak "text to be spoken" 2> /dev/null >> >> That directs error text to go to /dev/null which is just a 'bit bucket', >> a kind of black hole into which to throw stuff. >> >> You could create an alias command for espeak and not have to type '2> >> /dev/null' after every command. >> >> It's useful when running something that takes a long time, like: >> >> sudo apt-get upgrade >> >> To put a command which will tell you when it's done: >> >> sudo apt-get upgrade && espeak "Finished upgrade" 2> /dev/null >> >> Although in the above example the text will only be spoken if the >> command before the '&&' succeeds. >> >> Mike >> > > > =========================================================== > The raspberry-vi mailing list > Archives: //www.freelists.org/archives/raspberry-vi > Administrative contact: <mike.ray@xxxxxxxxxxxxxx> > ----------------------------------------------------------- > Raspberry Pi and the Raspberry Pi logo are trademarks of the Raspberry Pi > Foundation. > > This list is not affiliated to the Raspberry Pi Foundation and the views and > attitudes expressed by the subscribers to this list do not reflect those of > the Foundation. > > Mike Ray, list creator, January 2013 > > -- Michael A. Ray Analyst/Programmer Witley, Surrey, South-east UK github username: cromarty raspberrypi.org username: cromarty Ham Radio Call-sign: G4XBF, licensed since 1982 'Entia non sunt multiplicanda praeter necessitatem' - Ockham's razor Raspberry VI: http://www.raspberryvi.org/ NVDA, the best free screen-reader in the world: http://www.nvda-project.org/ =========================================================== The raspberry-vi mailing list Archives: //www.freelists.org/archives/raspberry-vi Administrative contact: <mike.ray@xxxxxxxxxxxxxx> ----------------------------------------------------------- Raspberry Pi and the Raspberry Pi logo are trademarks of the Raspberry Pi Foundation. This list is not affiliated to the Raspberry Pi Foundation and the views and attitudes expressed by the subscribers to this list do not reflect those of the Foundation. Mike Ray, list creator, January 2013