eLinux.org - User contributions [en]

RPi Text to Speech (Speech Synthesis)

2013-05-01T18:10:13Z

StevenP: Google script

This guide shows you three easy methods of getting your Raspberry Pi to talk, and describes the pros and cons of each.

== Why use Text to Speech? ==

It’s very easy add to your program - just output a string to the speech function instead of the screen.
You don’t need an expensive/complicated LCD or monitor for your project - just use any old mp3 player loudspeaker or PC loudspeaker which you have probably got lying around - or even an earphone works well for debugging purposes too.

You could use speech output for:
(i) status messages - e.g. internet connection made or IP address on a headless RPi;
(ii) user interface - e.g. speak the mode selected or station name with button presses on an RPi internet radio;
(iii) main functionality - e.g. tell the time and read the weather forecast on your RPi alarm clock.

== Install supporting packages ==

Speech output requires a few audio software packages to be installed on your RPi. They may be already there but it does no harm to try to install these listed below anyway. The installer will let you know if the package is already present on your RPi. The instructions below are based on the Raspbian distribution (August 2012).

Firstly I recommend updating your Raspbian distribution if you have not recently already done so. Speech did not work for me until I did this. This may take 30 - 60 minutes depending on your connection speed etc. To do this:

sudo apt-get update
sudo apt-get upgrade

If you do not already have sound on your RPi then you will need the alsa sound utilities:
sudo apt-get install alsa-utils
and edit the file /etc/modules using:
sudo nano /etc/modules
to have line:
snd_bcm2835
If this line is already there then leave the file as is!

Install the mplayer audio/movie player with:
sudo apt-get install mplayer
To sort out the mplayer error message, edit file /etc/mplayer/mplayer.conf using:
sudo nano /etc/mplayer/mplayer.conf
to add line
nolirc=yes

== Festival Text to Speech ==

The first speech package I tried was Festival. It worked fine and produces a voice like a rough sounding robot. This may be just what you need if you are adding speech to your RPi robot project.

Install Festival with:
sudo apt-get install festival

Try out Festival with:
echo “Just what do you think you're doing, Dave?” | festival --tts
or to speak RPi’s IP address:
hostname -I | festival -tts

== Espeak Text to Speech ==

Espeak is a more modern speech synthesis package than Festival. It sounds clearer but does wail a little. If you are making an alien or a RPi witch then it’s the one for you! Seriously it is a good allrounder with great customisation options.

Install Espeak with:
sudo apt-get install espeak

Test Espeak with:
English female voice, emphasis on capitals (-k), speaking slowly (-s) using direct text:-
espeak -ven+f3 -k5 -s150 "I've just picked up a fault in the AE35 unit"

== Google Text to Speech ==

Google’s Text to Speech engine is a little different to Festival and Espeak. Your text is sent to Google’s servers to generate the speech file which is then returned to your Pi and played using mplayer. This means you will need an internet connection for it to work, but the speech quality is superb.

I used used ax206geek’s bash script to access the Google Text to Speech engine:

Create a file speech.sh with:
nano speech.sh

Add these lines to the file and save it (in nano editor use CTRL-O writeOut)
#!/bin/bash
say() { local IFS=+;/usr/bin/mplayer -ao alsa -really-quiet -noconsolecontrols "http://translate.google.com/translate_tts?tl=en&q=$*"; }
say $*
Alternatively save from here: [[File:speech.sh]]

Add execute permissions to your script with:
chmod u+x speech.sh

Test it using:
./speech.sh Look Dave, I can see you're really upset about this.

EXTRA:
Dan Fountain improved on the above script to speak any length of text (Google limits you to 100 bytes normally). His excellent easy-to-read webpage describes this at http://danfountain.com/2013/03/raspberry-pi-text-to-speech/

== Recommendations ==

I hope this guide has given you some ideas of how you can make use of speech output in your own project. As to which speech package to recommend, Festival works well enough, Espeak is clearer and so easier to understand and the Google engine gives super quality but is useless if you internet connection goes down. Maybe implement a speech function which first does a ping to Google before deciding whether to use Google or Espeak as its output engine?

All comments/suggestions welcome! Let me know for what you have used speech on your Pi - StevenP on the official Raspberry Pi Forum.

RPi Text to Speech (Speech Synthesis)

2013-05-01T16:37:57Z

StevenP: Improved Google script

This guide shows you three easy methods of getting your Raspberry Pi to talk, and describes the pros and cons of each.

== Why use Text to Speech? ==

It’s very easy add to your program - just output a string to the speech function instead of the screen.
You don’t need an expensive/complicated LCD or monitor for your project - just use any old mp3 player loudspeaker or PC loudspeaker which you have probably got lying around - or even an earphone works well for debugging purposes too.

You could use speech output for:
(i) status messages - e.g. internet connection made or IP address on a headless RPi;
(ii) user interface - e.g. speak the mode selected or station name with button presses on an RPi internet radio;
(iii) main functionality - e.g. tell the time and read the weather forecast on your RPi alarm clock.

== Install supporting packages ==

Speech output requires a few audio software packages to be installed on your RPi. They may be already there but it does no harm to try to install these listed below anyway. The installer will let you know if the package is already present on your RPi. The instructions below are based on the Raspbian distribution (August 2012).

Firstly I recommend updating your Raspbian distribution if you have not recently already done so. Speech did not work for me until I did this. This may take 30 - 60 minutes depending on your connection speed etc. To do this:

sudo apt-get update
sudo apt-get upgrade

If you do not already have sound on your RPi then you will need the alsa sound utilities:
sudo apt-get install alsa-utils
and edit the file /etc/modules using:
sudo nano /etc/modules
to have line:
snd_bcm2835
If this line is already there then leave the file as is!

Install the mplayer audio/movie player with:
sudo apt-get install mplayer
To sort out the mplayer error message, edit file /etc/mplayer/mplayer.conf using:
sudo nano /etc/mplayer/mplayer.conf
to add line
nolirc=yes

== Festival Text to Speech ==

The first speech package I tried was Festival. It worked fine and produces a voice like a rough sounding robot. This may be just what you need if you are adding speech to your RPi robot project.

Install Festival with:
sudo apt-get install festival

Try out Festival with:
echo “Just what do you think you're doing, Dave?” | festival --tts
or to speak RPi’s IP address:
hostname -I | festival -tts

== Espeak Text to Speech ==

Espeak is a more modern speech synthesis package than Festival. It sounds clearer but does wail a little. If you are making an alien or a RPi witch then it’s the one for you! Seriously it is a good allrounder with great customisation options.

Install Espeak with:
sudo apt-get install espeak

Test Espeak with:
English female voice, emphasis on capitals (-k), speaking slowly (-s) using direct text:-
espeak -ven+f3 -k5 -s150 "I've just picked up a fault in the AE35 unit"

== Google Text to Speech ==

Google’s Text to Speech engine is a little different to Festival and Espeak. Your text is sent to Google’s servers to generate the speech file which is then returned to your Pi and played using mplayer. This means you will need an internet connection for it to work, but the speech quality is superb.

I used used ax206geek’s bash script to access the Google Text to Speech engine:

Create a file speech.sh with:
nano speech.sh

Add these lines to the file and save it (in nano editor use CTRL-O writeOut)
#!/bin/bash
say() { local IFS=+;/usr/bin/mplayer -ao alsa -really-quiet -noconsolecontrols "http://translate.google.com/translate_tts?tl=en&q=$*"; }
say $*
Alternatively save from here: [[File:speech.sh]]

Add execute permissions to your script with:
chmod u+x speech.sh

Test it using:
./speech.sh Look Dave, I can see you're really upset about this.

EXTRA:
Dan Fountain improved on the above to speak any length of text (Google limits you to 100 bytes normally). His webpage describes this at http://danfountain.com/2013/03/raspberry-pi-text-to-speech/

== Recommendations ==

I hope this guide has given you some ideas of how you can make use of speech output in your own project. As to which speech package to recommend, Festival works well enough, Espeak is clearer and so easier to understand and the Google engine gives super quality but is useless if you internet connection goes down. Maybe implement a speech function which first does a ping to Google before deciding whether to use Google or Espeak as its output engine?

All comments/suggestions welcome! Let me know for what you have used speech on your Pi - StevenP on the official Raspberry Pi Forum.

RPi raspi-config

2013-01-29T09:46:37Z

StevenP:

The raspi-config script was introduced to help you to configure your Pi.

== History ==

This utility script was first released with the Debian Wheezy image of 18 June 2012. It is expected to continue changing so the number of menu items and the ease of use of those items will increase with time. If anyone feels willing and able to improve raspi-config then please contact Alex Bradbury [https://github.com/asb/raspi-config].

== The raspi-config script ==

When you start your Pi the display shows the output from each of the start-up scripts (as lots of scrolling text). If starting for the first time using a new image you are logged in as a root user, and the raspi-config menu will then appear. It can also be started at any time from the command line or from a terminal window (see below).

It has the following entries (this is the layout from the Raspian 2012-12-16 image. It may be different on other images):

Raspi-config

info Information about this tool
expand_rootfs Expand root partition to fill SD card
overscan Change overscan
configure_keyboard Set keyboard layout
change_pass Change password for 'pi' user
change_locale Set locale
change_timezone Set timezone
memory_split Change memory split
ssh Enable or disable ssh server
boot_behaviour Start desktop on boot?
update Try to upgrade raspi-config

<Select> <Finish>

This is the layout from the Wheezy 2012-06-18 image:

Raspi-config

info Information about this tool
expand-rootfs Expand root partition to fill SD card
overscan Change overscan
configure-keyboard Set keyboard layout
change_pass Change password for ‘pi’ user
change_locale Set locale
change_timezone Set timezone
memory_split Change memory split
ssh Enable or disable ssh server
finish Finish config and don’t start raspi-config at boot

<Ok> <Exit>

== Moving Around the Menu ==

It looks like its running as a graphical application but in fact it isn't; its using the command line and graphical tools for the layout of the text. Cursor up/down keys move the highlight up and down menus.

At any point from within any of the menu or sub-menu options the Tab key will switch from the selected menu entry and the "buttons" at the bottom (inside angle brackets). So, move the highlight to the menu option you want to use, press Tab, then press Return.

Some of the menu entries take a while to read configuration information before they change what is displayed. Be patient.

== What raspi-config does ==

Some menu entries modify the file /boot/config.txt. This file, out of the box, contains a number of commented out configuration entries; raspi-config adds entries at the end of this file. You can see what raspi-config has done to the
file by viewing it on the Pi using Leafpad. More information on editing config.txt here [[R-Pi_ConfigurationFile]]

Other entries modify Linux configuration files. Some take effect immediately, others at the next boot.

== Running raspi-config another time ==

Following the first boot, your raspberry pi will boot into the command prompt or desktop (you choose in raspi-config). You can run it at any time after that from the command line or in a terminal window by typing (case sensitive):

sudo raspi-config

The sudo (do as superuser) is necessary because you will be changing files that you as user pi do not own.

== Menu Options ==

Here is a description of each menu entry.

=== info - Information About This Tool ===

It helpfully advises that it is for initial configuration, and can be run at any time. You may have difficulties if you have heavily customized your installation as the changes it makes might not be correct if what it attempts to change is not what it expects.

=== expand_rootfs - Expand root partition to fill SD card ===

The usual distribution images are 2 GB. When you copy the image to a larger SD card you have a portion of that card unused. This option expands the initial image to expand to fill the rest of the SD card, giving you more space. You need to reboot the Raspberry Pi to make this available. THERE IS NO CONFIRMATION - SELECTING THE OPTION EXPANDS THE PARTITION.

=== overscan - Change overscan ===

Old photographs had a border round the outside to allow for handling and mounting. Old TV sets had a significant variation in the size of the picture it produced; some had cabinets that overlapped the screen. Like the photographs, the TV pictures were given a black border so that none of the picture was lost. This is called overscan. Modern TVs and monitors don't need, and the signal doesn't have, the border. If the initial text shown on the screen disappears off the edge you need to enable overscan to add back the border.

Any changes will take effect after a reboot. You can have greater control over the settings by editing boot/config.txt.

On some displays, particularly monitors, just disabling Overscan will make the picture fill the whole screen and correct the resolution. For other displays it may be necessary to leave overscan enabled and adjust the Overscan values, more information here [[R-Pi_Troubleshooting#Big_black_borders_around_small_image_on_HD_monitors]].

=== configure-keyboard - Set keyboard layout ===

This option selects the keyboard being used, so that the characters produced are the same as those typed (important examples are # and /). It is slow to display, while it reads all the keyboard types. Changes usually take effect immediately, but may require a reboot.

Brands of keyboards are chosen first followed by other choices to set up the nationality of the keyboard. The default is a Generic 105-key (Intl) PC. If you cannot find your keyboard on the list then use one of the generic keyboards. Check [http://en.wikipedia.org/wiki/Keyboard_layout | this page] for most keyboard layouts. The next screen gives the keyboard layout. If you are not using the first choice of English UK select Other and you will be faced with a long list of other national keyboards.

You then select specific options:
* No AltGr key
* No compose key
* Shutdown XServer (use [Ctrl][Alt][Backspace] all pressed at the same time)

=== change_pass - Change password for ‘pi’ user ===

The default user for the Raspian install is "pi" and its password is "raspberry". If you change the password, other people will need to know the new password, including you, to logon to the Raspberry Pi. Each user/password combination can be different on each SD card.

=== change_locale - Set locale ===

This option selects the characters and other symbols being displayed on the screen, and is important if you want to use the non-english ones. It is slow to display, while it reads all the locale information. Changes usually take effect immediately, but may require a reboot.

You usually select only the one(s) you want (press space); this will generate the configuration data for all those you select. The default setting is en_GB UTF-8 UTF-8

=== change_timezone - Set timezone ===

This is where you setup your system clock; if it’s wrong it just means the date and time assigned to files you create (automatically when you make them) will be wrong. It is slow to display as there are lots of selections. First you select the continent, then select a City from that continent. You may have to select the one nearest to you.

The Raspberry Pi does not have an onboard clock (you can add one), so the "clock" stops when you power it off. If you are connected to the internet the Raspberry Pi can be set up to get the time from an online time signal.

=== memory_split - Change memory split ===

The Raspberry Pi has two processors, one for calculation tasks (the CPU) and one for graphical tasks (the GPU). The CPU is described as the ARM; the GPU as the VideoCore. This version takes account of the 256 MB or 512 MB boards, and allows a dynamic reallocation of memory, whereas older versions of raspi-config only split the 256 MB and could not set the dynamic option. The best setting will depend on what type of applications you are running on your Raspberry Pi.

=== ssh - Enable or disable ssh server ===

Enabling ssh will allow you to connect to your Raspberry Pi from another device on your network and use a terminal window remotely. You do not need a monitor or keyboard connected to your Raspberry Pi if you do this.

Unless you want to use the Raspberry Pi remotely you can disable this, as it stops the ssh service which takes a small amount of processing resources. If you want to set this up, see the [[RPi_A_Method_for_ssh_blind_login | ssh page]].

=== boot_behaviour - Start desktop on boot? ===

The official images are supplied with the Raspberry Pi booting into a command line, presumably because problems with connecting the display are fewer and simpler. If you think you are ok with the GUI interface you can boot to this. You can change this at any time.

* Desktop (GUI interface) - gives a picture based screen, similar to a Windows, Mac or smartphone, that requires a mouse to select actions (usually). This option also skips the login by using the pi user. Pressing the red Exit button on the right hand side of the screen will give the options to logout, shutdown or reboot. Using logout will give a GUI login screen. Using Ctrl-Alt-Backspace also gives a GUI login screen. To use a command line open the Terminal window. To get back to the command line, logout and press Ctrl-Alt-F1. To permanently get back the command line, run raspi-config and reset the boot behaviour and restart.

* Command line - gives a text based screen that requires the user to type commands on the keyboard only. Usually the mouse is not required, but some command line programs can use mouse control. You can switch to the GUI screen by typing "startx" and pressing 'Enter'. This time the red Exit button on the right hand side of the screen will only give the option to logout. This returns you to the command line. To stop or reboot the Raspberry Pi type "sudo halt" or "sudo reboot" and press 'Enter'.

=== update - Try to upgrade raspi-config ===

The raspi-config utility has changed quite a bit since it started, and is likely to continue to change. Use this option to check if your version of raspi-config is the latest, and if not download the latest version; you will need to be connected to the internet to update it. Once updating is complete, raspi-config will close. You should restart raspi-config with "sudo raspi-config" to make sure that you have completed all the options.

=== <Finish> ===

Use this 'button' when you have completed your changes. You will be asked whether you want to reboot or not. When used for the first time its best to reboot. This should restart your Pi. There will be a delay if you have chosen to resize your SD card.

= First-boot activity =

When a new image that contains the raspi-config utility is booted the first time, the session starts with the raspi-config screen. Use the help above when using the utility on first boot. This behaviour is driven by the '''raspi-config.sh''' script in the '''/etc/profile.d''' directory.

<pre>
#!/bin/sh
# Part of raspi-config http://github.com/asb/raspi-config
#
# See LICENSE file for copyright and license details

# Should be installed to /etc/profile.d/raspi-config.sh to force raspi-config
# to run at initial login

# You may also want to set automatic login in /etc/inittab on tty1 by adding a
# line such as:
# 1:2345:respawn:/bin/login -f root tty1 </dev/tty1 >/dev/tty1 2>&1 # RPICFG_TO_DISABLE

if [ $(id -u) -ne 0 ]; then
printf "\nNOTICE: the software on this Raspberry Pi has not been fully configured. Please run 'sudo raspi-config'\n\n"
else
raspi-config
exec login -f pi
fi
</pre>

This runs the '''raspi-config''' script (found as '''/usr/bin/raspi-config'''). When that has completed, the script above shows the login prompt for the '''pi''' user.

When the '''raspi-config''' script runs, and the user selects the '''Finish''' option, the script above is deleted so that it will not run again. When the Raspberry Pi is first booted it uses the '''/etc/inittab''' script, which does an automatic login as '''root'''. The Finish option of the raspi-config script modifies part of the inittab script, from the login as root:

<pre>
...
# 1:2345:respawn:/sbin/getty --noclear 38400 tty1 # RPICFG_TO_ENABLE
1:2345:respawn:/bin/login -f root tty1 </dev/tty1 >/dev/tty1 2>&1 # RPICFG_TO_DISABLE
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
...
</pre>

to the standard login action:

<pre>
...
1:2345:respawn:/sbin/getty --noclear 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
...
</pre>

== Is this useful? ==

This may be just a bit of background information, but it could be useful if you wish to distribute your own SD cards to friends, based on your own configuration. You may have added or removed packages, changed configurations, or any number of things that you and your friends think are useful.

You can create a backup image of your SD card, but that image will not execute the raspi-config script on first boot; your friends may need to run it because they have different hardware. To make that script run automatically, copy the top script to '''/etc/profile.d/raspi-config.sh''' and change the '''/etc/inittab''' script back to the original lines.

[[Category:RPi Linux]]

RPi Guides

2013-01-28T09:07:13Z

StevenP: /* Text to Speech (Speech Synthesis) */

{{Template:RPi_Learning}}

==Introduction==

This page contains a set of guides to show readers how to do useful tasks. These guides focus on achieving a goal as simply as possible, with the aim to build the confidence of the reader. Hopefully, the reader will also be inspired to learn at the same time.

The Raspberry Pi Forum has a list of [http://www.raspberrypi.org/forum/projects-and-collaboration-general/the-projects-list-look-here-for-some-ideas Project Ideas & Links], to help people get started.

Please add links to your guides (and ones you find interesting).

Fill in each section:
* Guide Title (as a link to the project webpage or connected wiki page)
* Guide Description (including any additional links or information
* Tags (key words related to the project, i.e. LCD Screen, Teaching, Python)
* Author(s) or group who have produced it (also if it is an Open/Community Project for anyone to contribute)
* Guide Status (Not Started/In-Progress/Available).

==Absolute beginners==
Suitable for absolute beginners who have never experimented with Linux before.
{| border="1" style="background:transparent;"
| style="width:15%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Title and Link'''
| style="width:40%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Description'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Tags'''
| style="width:10%; vertical-align:top; border:1px solid #aaa;" |
'''Author'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Status'''
|-
| vertical-align:top; border:1px solid #aaa;" |

===[[RPi Chromium | Installing Chromium web browser]]===
| vertical-align:top; border:1px solid #aaa;" |
Installing the Chromium web browser on Debian.
| vertical-align:top; border:1px solid #aaa;" |
Chromium
| vertical-align:top; border:1px solid #aaa;" |
bredman
| vertical-align:top; border:1px solid #aaa;" |
Ready for testing
|-
|}

==Easy==
Suitable for beginners who are confident typing commands into Linux but need a lot of guidance.
{| border="1" style="background:transparent;"
| style="width:15%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Title and Link'''
| style="width:40%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Description'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Tags'''
| style="width:10%; vertical-align:top; border:1px solid #aaa;" |
'''Author'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Status'''
|-
| vertical-align:top; border:1px solid #aaa;" |

===[[R-Pi NAS | Network Attached Storage]]===
| vertical-align:top; border:1px solid #aaa;" |
Network Attached Storage - Basic concept: A place to save copies of all your important files
| vertical-align:top; border:1px solid #aaa;" |
Samba
| vertical-align:top; border:1px solid #aaa;" |
[[User:bredman | bredman]] - Open Project
| vertical-align:top; border:1px solid #aaa;" |
Tested on Debian, some help needed with Fedora chapter
|-
| vertical-align:top; border:1px solid #aaa;" |

===[[Autoinstall Samba | Connect your RPi to your MS Windows machines]]===
| vertical-align:top; border:1px solid #aaa;" |
The guide above is a full NAS setup - This guide/script just configures and installs a very simple setup to allow you to read/write to your RPi files
| vertical-align:top; border:1px solid #aaa;" |
Samba
| vertical-align:top; border:1px solid #aaa;" |
[[User:SimpleSi | Simon Walters]] - Open Project
| vertical-align:top; border:1px solid #aaa;" |
Tested on Raspbian
|-
| vertical-align:top; border:1px solid #aaa;" |

===[[RPi Debian Python3 | Python 3 on Debian]]===
| vertical-align:top; border:1px solid #aaa;" |
Installing the latest Python 3 and common modules on Debian.
| vertical-align:top; border:1px solid #aaa;" |
Python
| vertical-align:top; border:1px solid #aaa;" |
croston
| vertical-align:top; border:1px solid #aaa;" |
Tested. Needs more modules adding
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi Debian Auto Login | Debian Auto Login/Startx]]===
| vertical-align:top; border:1px solid #aaa;" |
How to launch LXDE without the need of a username/Password in Debian.
| vertical-align:top; border:1px solid #aaa;" |
LXDE, Boot, Login, Auto
| vertical-align:top; border:1px solid #aaa;" |
Ian Hartwell (helpme1986)
| vertical-align:top; border:1px solid #aaa;" |
Early draft.
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPiForked-Daapd]]===
| vertical-align:top; border:1px solid #aaa;" |
How to install Forked-Daapd, an itunes media server
| vertical-align:top; border:1px solid #aaa;" |
Debian, streaming,
| vertical-align:top; border:1px solid #aaa;" |
Greg (pr1sm)
| vertical-align:top; border:1px solid #aaa;" |
Early draft.
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi Setting up a static IP in Debian | Setting up a static IP in Debian]]===
| vertical-align:top; border:1px solid #aaa;" |
How to set-up a static IP in Debian
| vertical-align:top; border:1px solid #aaa;" |
Debian, Static IP
| vertical-align:top; border:1px solid #aaa;" |
sleepy
| vertical-align:top; border:1px solid #aaa;" |
Available
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi Text to Speech (Speech Synthesis) | Text to Speech (Speech Synthesis)]]===
| vertical-align:top; border:1px solid #aaa;" |
Three easy methods of getting your Raspberry Pi to talk
| vertical-align:top; border:1px solid #aaa;" |
Raspbian
| vertical-align:top; border:1px solid #aaa;" |
StevenP
| vertical-align:top; border:1px solid #aaa;" |
Works fine
|-

| vertical-align:top; border:1px solid #aaa;" |

===[http://robotblogging.blogspot.co.uk/2013/01/pi-vision-10.html Installing a Web Cam]===
| vertical-align:top; border:1px solid #aaa;" |
Basic installation and testing of a usb web cam on Raspberry Pi
| vertical-align:top; border:1px solid #aaa;" |
web cam, ps eye, ffmpeg
| vertical-align:top; border:1px solid #aaa;" |
Chris Cummings
| vertical-align:top; border:1px solid #aaa;" |
Works
|-

|}

==Medium==
Suitable for beginners who are willing to experiment and only need a little guidance.
{| border="1" style="background:transparent;"
| style="width:15%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Title and Link'''
| style="width:40%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Description'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Tags'''
| style="width:10%; vertical-align:top; border:1px solid #aaa;" |
'''Author'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Status'''
|-
| vertical-align:top; border:1px solid #aaa;" |
===[[R-Pi PXE Server | Classroom Boot Server]]===
| vertical-align:top; border:1px solid #aaa;" |
Classroom boot server - Basic concept: A PXE server to allow cheap computers without hard disks to boot into Windows or Linux.
| vertical-align:top; border:1px solid #aaa;" |
PXE, netboot
| vertical-align:top; border:1px solid #aaa;" |
[[User:bredman | bredman]] - Open Project
| vertical-align:top; border:1px solid #aaa;" |
Lots of random text, needs organisation and testing
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi Ruby on Rails | Installing Ruby on Rails]]===
| vertical-align:top; border:1px solid #aaa;" |
Installing Ruby on Rails and common modules on Debian.
| vertical-align:top; border:1px solid #aaa;" |
Ruby, Rails
| vertical-align:top; border:1px solid #aaa;" |
Erik
| vertical-align:top; border:1px solid #aaa;" |
Partially tested. Still early draft.
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi VNC Screen Sharing | Share your screen with VNC]]===
| vertical-align:top; border:1px solid #aaa;" |
Installing Vino to allow remote control of the screen from another computer.
| vertical-align:top; border:1px solid #aaa;" |
Vino, VNC
| vertical-align:top; border:1px solid #aaa;" |
Jaix Bly
| vertical-align:top; border:1px solid #aaa;" |
Draft.
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi VNC Server | Remote Control of a Raspberry with VNC]]===
| vertical-align:top; border:1px solid #aaa;" |
Installing VNC to allow remote control a X11 session (not the console) from another computer.
| vertical-align:top; border:1px solid #aaa;" |
VNC
| vertical-align:top; border:1px solid #aaa;" |
Simon H
| vertical-align:top; border:1px solid #aaa;" |
Early draft.
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi XRDP Server | Remote Destop Server for Raspberry]]===
| vertical-align:top; border:1px solid #aaa;" |
Installing XRDP to allow Remote Desktop / Terminal Server on Raspberry Pi.
| vertical-align:top; border:1px solid #aaa;" |
rdp, xrdp
| vertical-align:top; border:1px solid #aaa;" |
Jaix Bly
| vertical-align:top; border:1px solid #aaa;" |
Draft.
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi iSCSI Initiator | iSCSI support and boot]]===
| vertical-align:top; border:1px solid #aaa;" |
Adding iSCSI initiator/target support, setting up iSCSI initiator, and configuring booting from an iSCSI volume.
| vertical-align:top; border:1px solid #aaa;" |
iSCSI, netboot
| vertical-align:top; border:1px solid #aaa;" |
Alex (nidO)
| vertical-align:top; border:1px solid #aaa;" |
Early draft, tested
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi_Email_IP_On_Boot_Debian | Send email containing Pi ip address on boot]]===
| vertical-align:top; border:1px solid #aaa;" |
Send email containing the ip of your Pi so you can access via SSH or other network protocol when your ip changes (moving networks) and you are working headless
| vertical-align:top; border:1px solid #aaa;" |
SSH, email, python
| vertical-align:top; border:1px solid #aaa;" |
--[[User:Geraldcor|Geraldcor]] 03:36, 18 June 2012 (UTC)
| vertical-align:top; border:1px solid #aaa;" |
Early draft, tested
|-

| vertical-align:top; border:1px solid #aaa;" |
===[http://www.penguintutor.com/linux/tightvnc Connecting securely to TightVNC over the Internet]===
| vertical-align:top; border:1px solid #aaa;" |
Guide to installing Tightvnc server on the Raspberry Pi and securing it using ssh to allow connecting over the Internet.
| vertical-align:top; border:1px solid #aaa;" |
VNC, ssh
| vertical-align:top; border:1px solid #aaa;" |
Stewart Watkiss
| vertical-align:top; border:1px solid #aaa;" |
Available
|-

| vertical-align:top; border:1px solid #aaa;" |
===[http://www.penguintutor.com/linux/raspberrypi-webserver Configuring a LAMP webserver]===
| vertical-align:top; border:1px solid #aaa;" |
Guide to configuring the Raspberry Pi as a LAMP (Linux, Apache, Mysql, PHP) webserver.
| vertical-align:top; border:1px solid #aaa;" |
apache, mysql, php
| vertical-align:top; border:1px solid #aaa;" |
Stewart Watkiss
| vertical-align:top; border:1px solid #aaa;" |
Available
|-

| vertical-align:top; border:1px solid #aaa;" |
===[https://github.com/ewindisch/chefiler Storage Filer/NAS via Chef]===
| vertical-align:top; border:1px solid #aaa;" |
Turn-key package to turn a machine into a storage filer / NAS. Developed and tested on a RaspberryPi. Still in early development. Deploys with Chef.
| vertical-align:top; border:1px solid #aaa;" |
samba, nfs, chef
| vertical-align:top; border:1px solid #aaa;" |
Eric Windisch
| vertical-align:top; border:1px solid #aaa;" |
Alpha/early-stage
|-

| vertical-align:top; border:1px solid #aaa;" |
===[http://elinux.org/RPI-Wireless-Hotspot Raspberry Pi WiFi Hotspot]===
| vertical-align:top; border:1px solid #aaa;" |
Turn your Raspberry Pi into a WiFi hotspot!
| vertical-align:top; border:1px solid #aaa;" |
wifi, hotspot, hostapd
| vertical-align:top; border:1px solid #aaa;" |
Isaac Smith
| vertical-align:top; border:1px solid #aaa;" |
Works like a charm.
|-

| vertical-align:top; border:1px solid #aaa;" |
===[http://robotblogging.blogspot.co.uk/2013/01/raspberry-pi-chats-to-arduino.html Raspberry Pi / Arduino Serial Communication]===
| vertical-align:top; border:1px solid #aaa;" |
Raspberry Pi talking to Arduino over serial uart
| vertical-align:top; border:1px solid #aaa;" |
arduino, serial, uart
| vertical-align:top; border:1px solid #aaa;" |
Chris Cummings
| vertical-align:top; border:1px solid #aaa;" |
Works perfectly!
|-

|}

==Advanced==
Suitable for confident users who want to try something more advanced.
{| border="1" style="background:transparent;"
| style="width:15%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Title and Link'''
| style="width:40%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Description'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Tags'''
| style="width:10%; vertical-align:top; border:1px solid #aaa;" |
'''Author'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Status'''
|-
| vertical-align:top; border:1px solid #aaa;" |
===[[RPi building and installing OpenELEC | building and installing OpenELEC]]===
| vertical-align:top; border:1px solid #aaa;" |
How to build and install OpenELEC,a embedded Multimedia Distro. You can learn (cross)compiling, building packages from source, how buildsystems are working and what is needed to install a OS on a SD-card for Raspberry Pi.
| vertical-align:top; border:1px solid #aaa;" |
XBMC, HTPC, Multimedia, Distro, compiling
| vertical-align:top; border:1px solid #aaa;" |
Stephan Raue
| vertical-align:top; border:1px solid #aaa;" |
Available
|-
| vertical-align:top; border:1px solid #aaa;" |
===[[RPi Using Skypekit | Using Skypekit]]===
| vertical-align:top; border:1px solid #aaa;" |
How to get started using Skypekit to make calls & chat. This is currently only useful for advanced users & developers.
| vertical-align:top; border:1px solid #aaa;" |
Skype, Skypekit
| vertical-align:top; border:1px solid #aaa;" |
Henry Cooke
| vertical-align:top; border:1px solid #aaa;" |
Alpha.
|-

| vertical-align:top; border:1px solid #aaa;" |

===[http://www.penguintutor.com/linux/raspberrypi-headless Pre-configuring SD card with a static IP address]===
| vertical-align:top; border:1px solid #aaa;" |
Guide to pre-configuring a SD image so that it boots with a static IP address. Useful for running headless without needing to know what DHCP address will be allocated.
| vertical-align:top; border:1px solid #aaa;" |
networking, tcpip
| vertical-align:top; border:1px solid #aaa;" |
Stewart Watkiss
| vertical-align:top; border:1px solid #aaa;" |
Available
|-

| vertical-align:top; border:1px solid #aaa;" |
===[http://rpipython.blogspot.com.es/2012/12/sending-remote-commands-to-our-pi.html Sending remote commands to our Pi thanks to Pastebin]===
| vertical-align:top; border:1px solid #aaa;" |
A guide to send remote commands to our Pi just by editing a pastebin!
| vertical-align:top; border:1px solid #aaa;" |
remote commands, notsureifuseful
| vertical-align:top; border:1px solid #aaa;" |
Itxaka Serrano Garcia
| vertical-align:top; border:1px solid #aaa;" |
Available
|-
|}

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Text to Speech (Speech Synthesis)

2012-10-14T06:09:52Z

StevenP:

This guide shows you three easy methods of getting your Raspberry Pi to talk, and describes the pros and cons of each.

== Why use Text to Speech? ==

It’s very easy add to your program - just output a string to the speech function instead of the screen.
You don’t need an expensive/complicated LCD or monitor for your project - just use any old mp3 player loudspeaker or PC loudspeaker which you have probably got lying around - or even an earphone works well for debugging purposes too.

You could use speech output for:
(i) status messages - e.g. internet connection made or IP address on a headless RPi;
(ii) user interface - e.g. speak the mode selected or station name with button presses on an RPi internet radio;
(iii) main functionality - e.g. tell the time and read the weather forecast on your RPi alarm clock.

== Install supporting packages ==

Speech output requires a few audio software packages to be installed on your RPi. They may be already there but it does no harm to try to install these listed below anyway. The installer will let you know if the package is already present on your RPi. The instructions below are based on the Raspbian distribution (August 2012).

Firstly I recommend updating your Raspbian distribution if you have not recently already done so. Speech did not work for me until I did this. This may take 30 - 60 minutes depending on your connection speed etc. To do this:

sudo apt-get update
sudo apt-get upgrade

If you do not already have sound on your RPi then you will need the alsa sound utilities:
sudo apt-get install alsa-utils
and edit the file /etc/modules using:
sudo nano /etc/modules
to have line:
snd_bcm2835
If this line is already there then leave the file as is!

Install the mplayer audio/movie player with:
sudo apt-get install mplayer
To sort out the mplayer error message, edit file /etc/mplayer/mplayer.conf using:
sudo nano /etc/mplayer/mplayer.conf
to add line
nolirc=yes

== Festival Text to Speech ==

The first speech package I tried was Festival. It worked fine and produces a voice like a rough sounding robot. This may be just what you need if you are adding speech to your RPi robot project.

Install Festival with:
sudo apt-get install festival

Try out Festival with:
echo “Just what do you think you're doing, Dave?” | festival --tts
or to speak RPi’s IP address:
hostname -I | festival -tts

== Espeak Text to Speech ==

Espeak is a more modern speech synthesis package than Festival. It sounds clearer but does wail a little. If you are making an alien or a RPi witch then it’s the one for you! Seriously it is a good allrounder with great customisation options.

Install Espeak with:
sudo apt-get install espeak

Test Espeak with:
English female voice, emphasis on capitals (-k), speaking slowly (-s) using direct text:-
espeak -ven+f3 -k5 -s150 "I've just picked up a fault in the AE35 unit"

== Google Text to Speech ==

Google’s Text to Speech engine is a little different to Festival and Espeak. Your text is sent to Google’s servers to generate the speech file which is then returned to your Pi and played using mplayer. This means you will need an internet connection for it to work, but the speech quality is superb.

I used used ax206geek’s bash script to access the Google Text to Speech engine:

Create a file speech.sh with:
nano speech.sh

Add these lines to the file and save it (in nano editor use CTRL-O writeOut)
#!/bin/bash
say() { local IFS=+;/usr/bin/mplayer -ao alsa -really-quiet -noconsolecontrols "http://translate.google.com/translate_tts?tl=en&q=$*"; }
say $*
Alternatively save from here: [[File:speech.sh]]

Add execute permissions to your script with:
chmod u+x speech.sh

Test it using:
./speech.sh Look Dave, I can see you're really upset about this.

== Recommendations ==

I hope this guide has given you some ideas of how you can make use of speech output in your own project. As to which speech package to recommend, Festival works well enough, Espeak is clearer and so easier to understand and the Google engine gives super quality but is useless if you internet connection goes down. Maybe implement a speech function which first does a ping to Google before deciding whether to use Google or Espeak as its output engine?

All comments/suggestions welcome! Let me know for what you have used speech on your Pi - StevenP on the official Raspberry Pi Forum.

RPi Text to Speech (Speech Synthesis)

2012-10-14T06:08:23Z

StevenP:

This guide shows you three easy methods of getting your Raspberry Pi to talk, and describes the pros and cons of each.

== Why use Text to Speech? ==

It’s very easy add to your program - just output a string to the speech function instead of the screen.
You don’t need an expensive/complicated LCD or monitor for your project - just use any old mp3 player loudspeaker or PC loudspeaker which you have probably got lying around - or even an earphone works well for debugging purposes too.

You could use speech output for:
(i) status messages - e.g. internet connection made or IP address on a headless RPi;
(ii) user interface - e.g. speak the mode selected or station name with button presses on an RPi internet radio;
(iii) main functionality - e.g. tell the time and read the weather forecast on your RPi alarm clock.

== Install supporting packages ==

Speech output requires a few audio software packages to be installed on your RPi. They may be already there but it does no harm to try to install these listed below anyway. The installer will let you know if the package is already present on your RPi. The instructions below are based on the Raspbian distribution (August 2012).

Firstly I recommend updating your Raspbian distribution if you have not recently already done so. Speech did not work for me until I did this. This may take 30 - 60 minutes depending on your connection speed etc. To do this:

sudo apt-get update
sudo apt-get upgrade

If you do not already have sound on your RPi then you will need the alsa sound utilities:
sudo apt-get install alsa-utils
and edit the file /etc/modules using:
sudo nano /etc/modules
to have line:
snd_bcm2835
If this line is already there then leave the file as is!

Install the mplayer audio/movie player with:
sudo apt-get install mplayer
To sort out the mplayer error message, edit file /etc/mplayer/mplayer.conf using:
sudo nano /etc/mplayer/mplayer.conf
to add line
nolirc=yes

== Festival Text to Speech ==

The first speech package I tried was Festival. It worked fine and produces a voice like a rough sounding robot. This may be just what you need if you are adding speech to your RPi robot project.

Install Festival with:
sudo apt-get install festival

Try out Festival with:
echo “Just what do you think you're doing, Dave?” | festival --tts
or to speak RPi’s IP address:
hostname -I | festival -tts

== Espeak Text to Speech ==

Espeak is a more modern speech synthesis package than Festival. It sounds clearer but does wail a little. If you are making an alien or a RPi witch then it’s the one for you! Seriously it is a good allrounder with great customisation options.

Install Espeak with:
sudo apt-get install espeak

Test Espeak with:
English female voice, emphasis on capitals (-k), speaking slowly (-s) using direct text:-
espeak -ven+f3 -k5 -s150 "I've just picked up a fault in the AE35 unit"

== Google Text to Speech ==

Google’s Text to Speech engine is a little different to Festival and Espeak. Your text is sent to Google’s servers to generate the speech file which is then returned to your Pi and played using mplayer. This means you will need an internet connection for it to work, but the speech quality is superb.

I used used ax206geek’s bash script to access the Google Text to Speech engine:

Create a file speech.sh with:
nano speech.sh

Add these lines to the file and save it (in nano editor use CTRL-O writeOut)
#!/bin/bash
say() { local IFS=+;/usr/bin/mplayer -ao alsa -really-quiet -noconsolecontrols "http://translate.google.com/translate_tts?tl=en&q=$*"; }
say $*
Alternatively save from here: [[File:speech.sh]]

Add execute permissions to your script with:
chmod u+x speech.sh

Test it using:
./speech.sh Look Dave, I can see you're really upset about this.

== Recommendations ==

I hope this guide has given you some ideas of how you can make use of speech output in your own project. As to which speech package to recommend, Festival works well enough, Espeak is clearer and so easier to understand and the Google engine gives super quality but is useless if you internet connection goes down. Maybe implement a speech function which first does a ping to Google before deciding whether to use Google or Espeak as its output engine?

All comments/suggestions welcome! Let me know for what you have used speech on you Pi - StevenP on the official Raspberry Pi Forum.

RPi Text to Speech (Speech Synthesis)

2012-10-14T06:07:05Z

StevenP:

This guide shows you three easy methods of getting your Raspberry Pi to talk, and describes the pros and cons of each.

== Why use Text to Speech? ==

It’s very easy add to your program - just output a string to the speech function instead of the screen.
You don’t need an expensive/complicated LCD or monitor for your project - just use any old mp3 player loudspeaker or PC loudspeaker which you have probably got lying around - or even an earphone works well for debugging purposes too.

You could use speech output for:
(i) status messages - e.g. internet connection made or IP address on a headless RPi;
(ii) user interface - e.g. speak the mode selected or station name with button presses on an RPi internet radio;
(iii) main functionality - e.g. tell the time and read the weather forecast on your RPi alarm clock.

== Install supporting packages ==

Speech output requires a few audio software packages to be installed on your RPi. They may be already there but it does no harm to try to install these listed below anyway. The installer will let you know if the package is already present on your RPi. The instructions below are based on the Raspbian distribution (August 2012).

Firstly I recommend updating your Raspbian distribution if you have not recently already done so. Speech did not work for me until I did this. This may take 30 - 60 minutes depending on your connection speed etc. To do this:

sudo apt-get update
sudo apt-get upgrade

If you do not already have sound on your RPi then you will need the alsa sound utilities:
sudo apt-get install alsa-utils
and edit the file /etc/modules using:
sudo nano /etc/modules
to have line:
snd_bcm2835
If this line is already there then leave the file as is!

Install the mplayer audio/movie player with:
sudo apt-get install mplayer
To sort out the mplayer error message, edit file /etc/mplayer/mplayer.conf using:
sudo nano /etc/mplayer/mplayer.conf
to add line
nolirc=yes

== Festival Text to Speech ==

The first speech package I tried was Festival. It worked fine and produces a voice like a rough sounding robot. This may be just what you need if you are adding speech to your RPi robot project.

Install Festival with:
sudo apt-get install festival

Try out Festival with:
echo “Just what do you think you're doing, Dave?” | festival --tts
or to speak RPi’s IP address:
hostname -I | festival -tts

== Espeak Text to Speech ==

Espeak is a more modern speech synthesis package than Festival. It sounds clearer but does wail a little. If you are making an alien or a RPi witch then it’s the one for you! Seriously it is a good allrounder with great customisation options.

Install Espeak with:
sudo apt-get install espeak

Test Espeak with:
English female voice, emphasis on capitals (-k), speaking slowly (-s) using direct text:-
espeak -ven+f3 -k5 -s150 "I've just picked up a fault in the AE35 unit"

== Google Text to Speech ==

Google’s Text to Speech engine is a little different to Festival and Espeak. Your text is sent to Google’s servers to generate the speech file which is then returned to your Pi and played using mplayer. This means you will need an internet connection for it to work, but the speech quality is superb.

I used used ax206geek’s bash script to access the Google Text to Speech engine:

Create a file speech.sh with:
nano speech.sh

Add these lines to the file and save it (in nano editor use CTRL-O writeOut)
#!/bin/bash
say() { local IFS=+;/usr/bin/mplayer -ao alsa -really-quiet -noconsolecontrols "http://translate.google.com/translate_tts?tl=en&q=$*"; }
say $*
Alternatively save from here: [[File:speech.sh]]

Add execute permissions to your script with:
chmod u+x speech.sh

Test it using:
./speech.sh Look Dave, I can see you're really upset about this.

== Recommendations ==

I hope this guide has given you some ideas of how you can make use of speech output in your own project. As to which speech package to recommend, Festival works well enough, Espeak is clearer and so easier to understand and the Google engine gives super quality but is useless if you internet connection goes down. Maybe implement a speech function which first does a ping to Google before deciding whether to use Google or Espeak as its output engine?
All comments/suggestions welcome! Let me know for what you have used speech on you Pi! (StevenP on the official Raspberry Pi Forum)

RPi Text to Speech (Speech Synthesis)

2012-10-14T06:03:01Z

StevenP:

This guide shows you three easy methods of getting your Raspberry Pi to talk, and describes the pros and cons of each.

== Why use Text to Speech? ==

It’s very easy add to your program - just output a string to the speech function instead of the screen.
You don’t need an expensive/complicated LCD or monitor for your project - just use any old mp3 player loudspeaker or PC loudspeaker which you have probably got lying around - or even an earphone works well for debugging purposes too.

You could use speech output for:
(i) status messages - e.g. internet connection made or IP address on a headless RPi;
(ii) user interface - e.g. speak the mode selected or station name with button presses on an RPi internet radio;
(iii) main functionality - e.g. tell the time and read the weather forecast on your RPi alarm clock.

== Install supporting packages ==

Speech output requires a few audio software packages to be installed on your RPi. They may be already there but it does no harm to try to install these listed below anyway. The installer will let you know if the package is already present on your RPi. The instructions below are based on the Raspbian distribution (August 2012).

Firstly I recommend updating your Raspbian distribution if you have not recently already done so. Speech did not work for me until I did this. This may take 30 - 60 minutes depending on your connection speed etc. To do this:

sudo apt-get update
sudo apt-get upgrade

If you do not already have sound on your RPi then you will need the alsa sound utilities:
sudo apt-get install alsa-utils
and edit the file /etc/modules using:
sudo nano /etc/modules
to have line:
snd_bcm2835
If this line is already there then leave the file as is!

Install the mplayer audio/movie player with:
sudo apt-get install mplayer
To sort out the mplayer error message, edit file /etc/mplayer/mplayer.conf using:
sudo nano /etc/mplayer/mplayer.conf
to add line
nolirc=yes

== Festival Text to Speech ==

The first speech package I tried was Festival. It worked fine and produces a voice like a rough sounding robot. This may be just what you need if you are adding speech to your RPi robot project.

Install Festival with:
sudo apt-get install festival

Try out Festival with:
echo “Just what do you think you're doing, Dave?” | festival --tts
or to speak RPi’s IP address:
hostname -I | festival -tts

== Espeak Text to Speech ==

Espeak is a more modern speech synthesis package than Festival. It sounds clearer but does wail a little. If you are making an alien or a RPi witch then it’s the one for you! Seriously it is a good allrounder with great customisation options.

Install Espeak with:
sudo apt-get install espeak

Test Espeak with:
English female voice, emphasis on capitals (-k), speaking slowly (-s) using direct text:-
espeak -ven+f3 -k5 -s150 "I've just picked up a fault in the AE35 unit"

== Google Text to Speech ==

Google’s Text to Speech engine is a little different to Festival and Espeak. Your text is sent to Google’s servers to generate the speech file which is then returned to your Pi and played using mplayer. This means you will need an internet connection for it to work, but the speech quality is superb.

I used used ax206geek’s bash script to access the Google Text to Speech engine:

Create a file speech.sh with:
nano speech.sh

Add these lines to the file and save it (in nano editor use CTRL-O writeOut)
#!/bin/bash
say() { local IFS=+;/usr/bin/mplayer -ao alsa -really-quiet -noconsolecontrols "http://translate.google.com/translate_tts?tl=en&q=$*"; }
say $*
Alternatively save from here: [[File:speech.sh]]

Add execute permissions to your script with:
chmod u+x speech.sh

Test it using:
./speech.sh Look Dave, I can see you're really upset about this.

== Recommendations ==

I hope this guide has given you some ideas of how you can make use of speech output in your own project. As to which speech package to recommend, Festival works well enough, Espeak is clearer and so easier to understand and the Google engine gives super quality but is useless if you internet connection goes down. Maybe implement a speech function which first does a ping to Google before deciding whether to use Google or Espeak as its output engine?

RPi Text to Speech (Speech Synthesis)

2012-10-14T06:01:52Z

StevenP:

This guide shows you three easy methods of getting your Raspberry Pi to talk, and describes the pros and cons of each.

== Why use Text to Speech? ==

It’s very easy add to your program - just output a string to the speech function instead of the screen.
You don’t need an expensive/complicated LCD or monitor for your project - just use any old mp3 player loudspeaker or PC loudspeaker which you have probably got lying around - or even an earphone works well for debugging purposes too.

You could use speech output for:
(i) status messages - e.g. internet connection made or IP address on a headless RPi;
(ii) user interface - e.g. speak the mode selected or station name with button presses on an RPi internet radio;
(iii) main functionality - e.g. tell the time and read the weather forecast on your RPi alarm clock.

== Install supporting packages ==

Speech output requires a few audio software packages to be installed on your RPi. They may be already there but it does no harm to try to install these listed below anyway. The installer will let you know if the package is already present on your RPi. The instructions below are based on the Raspbian distribution (August 2012).

Firstly I recommend updating your Raspbian distribution if you have not recently already done so. Speech did not work for me until I did this. This may take 30 - 60 minutes depending on your connection speed etc. To do this:

sudo apt-get update
sudo apt-get upgrade

If you do not already have sound on your RPi then you will need the alsa sound utilities:
sudo apt-get install alsa-utils
and edit the file /etc/modules using:
sudo nano /etc/modules
to have line:
snd_bcm2835
If this line is already there then leave the file as is!

Install the mplayer audio/movie player with:
sudo apt-get install mplayer
To sort out the mplayer error message, edit file /etc/mplayer/mplayer.conf using:
sudo nano /etc/mplayer/mplayer.conf
to add line
nolirc=yes

== Festival Text to Speech ==

The first speech package I tried was Festival. It worked fine and produces a voice like a rough sounding robot. This may be just what you need if you are adding speech to your RPi robot project.

Install Festival with:
sudo apt-get install festival

Try out Festival with:
echo “Just what do you think you're doing, Dave?” | festival --tts
or to speak RPi’s IP address:
hostname -I | festival -tts

== Espeak Text to Speech ==

Espeak is a more modern speech synthesis package than Festival. It sounds clearer but does wail a little. If you are making an alien or a RPi witch then it’s the one for you! Seriously it is a good allrounder with great customisation options.

Install Espeak with:
sudo apt-get install espeak

Test Espeak with:
English female voice, emphasis on capitals (-k), speaking slowly (-s) using direct text:-
espeak -ven+f3 -k5 -s150 "I've just picked up a fault in the AE35 unit"

== Google Text to Speech ==

Google’s Text to Speech engine is a little different to Festival and Espeak. Your text is sent to Google’s servers to generate the speech file which is then returned to your Pi and played using mplayer. This means you will need an internet connection for it to work, but the speech quality is superb.

I used used ax206geek’s bash script to access the Google Text to Speech engine:

Create a file speech.sh with:
nano speech.sh

Add these lines to the file and save it (in nano editor use CTRL-O writeOut)
#!/bin/bash
say() { local IFS=+;/usr/bin/mplayer -ao alsa -really-quiet -noconsolecontrols "http://translate.google.com/translate_tts?tl=en&q=$*"; }
say $*
Alternatively download speech.sh here: [[File:speech.sh]]

Add execute permissions to your script with:
chmod u+x speech.sh

Test it using:
./speech.sh Look Dave, I can see you're really upset about this.

== Recommendations ==

I hope this guide has given you some ideas of how you can make use of speech output in your own project. As to which speech package to recommend, Festival works well enough, Espeak is clearer and so easier to understand and the Google engine gives super quality but is useless if you internet connection goes down. Maybe implement a speech function which first does a ping to Google before deciding whether to use Google or Espeak as its output engine?

RPi Text to Speech (Speech Synthesis)

2012-10-14T05:58:53Z

StevenP:

This guide shows you three easy methods of getting your Raspberry Pi to talk, and describes the pros and cons of each.

== Why use Text to Speech? ==

It’s very easy add to your program - just output a string to the speech function instead of the screen.
You don’t need an expensive/complicated LCD or monitor for your project - just use any old mp3 player loudspeaker or PC loudspeaker which you have probably got lying around - or even an earphone works well for debugging purposes too.

You could use speech output for:
(i) status messages - e.g. internet connection made or IP address on a headless RPi;
(ii) user interface - e.g. speak the mode selected or station name with button presses on an RPi internet radio;
(iii) main functionality - e.g. tell the time and read the weather forecast on your RPi alarm clock.

== Install supporting packages ==

Speech output requires a few audio software packages to be installed on your RPi. They may be already there but it does no harm to try to install these listed below anyway. The installer will let you know if the package is already present on your RPi. The instructions below are based on the Raspbian distribution (August 2012).

Firstly I recommend updating your Raspbian distribution if you have not recently already done so. Speech did not work for me until I did this. This may take 30 - 60 minutes depending on your connection speed etc. To do this:

sudo apt-get update
sudo apt-get upgrade

If you do not already have sound on your RPi then you will need the alsa sound utilities:
sudo apt-get install alsa-utils
and edit the file /etc/modules using:
sudo nano /etc/modules
to have line:
snd_bcm2835
If this line is already there then leave the file as is!

Install the mplayer audio/movie player with:
sudo apt-get install mplayer
To sort out the mplayer error message, edit file /etc/mplayer/mplayer.conf using:
sudo nano /etc/mplayer/mplayer.conf
to add line
nolirc=yes

== Festival Text to Speech ==

The first speech package I tried was Festival. It worked fine and produces a voice like a rough sounding robot. This may be just what you need if you are adding speech to your RPi robot project.

Install Festival with:
sudo apt-get install festival

Try out Festival with:
echo “Just what do you think you're doing, Dave?” | festival --tts
or to speak RPi’s IP address:
hostname -I | festival -tts

== Espeak Text to Speech ==

Espeak is a more modern speech synthesis package than Festival. It sounds clearer but does wail a little. If you are making an alien or a RPi witch then it’s the one for you! Seriously it is a good allrounder with great customisation options.

Install Espeak with:
sudo apt-get install espeak

Test Espeak with:
English female voice, emphasis on capitals (-k), speaking slowly (-s) using direct text:-
espeak -ven+f3 -k5 -s150 "I've just picked up a fault in the AE35 unit"

== Google Text to Speech ==

Google’s Text to Speech engine is a little different to Festival and Espeak. Your text is sent to Google’s servers to generate the speech file which is then returned to your Pi and played using mplayer. This means you will need an internet connection for it to work, but the speech quality is superb.

I used used ax206geek’s bash script to access the Google Text to Speech engine:

Create a file speech.sh with:
nano speech.sh

Add these lines to the file and save it (in nano editor use CTRL-O writeOut)
#!/bin/bash
say() { local IFS=+;/usr/bin/mplayer -ao alsa -really-quiet -noconsolecontrols "http://translate.google.com/translate_tts?tl=en&q=$*"; }
say $*
[[File:speech.sh]]

Add execute permissions to your script with:
chmod u+x speech.sh

Test it using:
./speech.sh Look Dave, I can see you're really upset about this.

== Recommendations ==

I hope this guide has given you some ideas of how you can make use of speech output in your own project. As to which speech package to recommend, Festival works well enough, Espeak is clearer and so easier to understand and the Google engine gives super quality but is useless if you internet connection goes down. Maybe implement a speech function which first does a ping to Google before deciding whether to use Google or Espeak as its output engine?

RPi Text to Speech (Speech Synthesis)

2012-10-14T05:55:51Z

StevenP:

This guide shows you three easy methods of getting your Raspberry Pi to talk, and describes the pros and cons of each.

== Why use Text to Speech? ==

It’s very easy add to your program - just output a string to the speech function instead of the screen.
You don’t need an expensive/complicated LCD or monitor for your project - just use any old mp3 player loudspeaker or PC loudspeaker which you have probably got lying around - or even an earphone works well for debugging purposes too.

You could use speech output for:
(i) status messages - e.g. internet connection made or IP address on a headless RPi;
(ii) user interface - e.g. speak the mode selected or station name with button presses on an RPi internet radio;
(iii) main functionality - e.g. tell the time and read the weather forecast on your RPi alarm clock.

== Install supporting packages ==

Speech output requires a few audio software packages to be installed on your RPi. They may be already there but it does no harm to try to install these listed below anyway. The installer will let you know if the package is already present on your RPi. The instructions below are based on the Raspbian distribution (August 2012).

Firstly I recommend updating your Raspbian distribution if you have not recently already done so. Speech did not work for me until I did this. This may take 30 - 60 minutes depending on your connection speed etc. To do this:

sudo apt-get update
sudo apt-get upgrade

If you do not already have sound on your RPi then you will need the alsa sound utilities:
sudo apt-get install alsa-utils
and edit the file /etc/modules using:
sudo nano /etc/modules
to have line:
snd_bcm2835
If this line is already there then leave the file as is!

Install the mplayer audio/movie player with:
sudo apt-get install mplayer
To sort out the mplayer error message, edit file /etc/mplayer/mplayer.conf using:
sudo nano /etc/mplayer/mplayer.conf
to add line
nolirc=yes

== Festival Text to Speech ==

The first speech package I tried was Festival. It worked fine and produces a voice like a rough sounding robot. This may be just what you need if you are adding speech to your RPi robot project.

Install Festival with:
sudo apt-get install festival

Try out Festival with:
echo “Just what do you think you're doing, Dave?” | festival --tts
or to speak RPi’s IP address:
hostname -I | festival -tts

== Espeak Text to Speech ==

Espeak is a more modern speech synthesis package than Festival. It sounds clearer but does wail a little. If you are making an alien or a RPi witch then it’s the one for you! Seriously it is a good allrounder with great customisation options.

Install Espeak with:
sudo apt-get install espeak

Test Espeak with:
English female voice, emphasis on capitals (-k), speaking slowly (-s) using direct text:-
espeak -ven+f3 -k5 -s150 "I've just picked up a fault in the AE35 unit"

== Google Text to Speech ==

Google’s Text to Speech engine is a little different to Festival and Espeak. Your text is sent to Google’s servers to generate the speech file which is then returned to your Pi and played using mplayer. This means you will need an internet connection for it to work, but the speech quality is superb.

I used used ax206geek’s bash script to access the Google Text to Speech engine:

Create a file speech.sh with:
nano speech.sh

Add these lines to the file and save it (in nano editor use CTRL-O writeOut)
#!/bin/bash
say() { local IFS=+;/usr/bin/mplayer -ao alsa -really-quiet -noconsolecontrols "http://translate.google.com/translate_tts?tl=en&q=$*"; }
say $*

Add execute permissions to your script with:
chmod u+x speech.sh

Test it using:
./speech.sh Look Dave, I can see you're really upset about this.

== Recommendations ==

I hope this guide has given you some ideas of how you can make use of speech output in your own project. As to which speech package to recommend, Festival works well enough, Espeak is clearer and so easier to understand and the Google engine gives super quality but is useless if you internet connection goes down. Maybe implement a speech function which first does a ping to Google before deciding whether to use Google or Espeak as its output engine?

RPi Text to Speech (Speech Synthesis)

2012-10-14T05:54:44Z

StevenP:

This guide shows you three easy methods of getting your Raspberry Pi to talk, and describes the pros and cons of each.

== Why use Text to Speech? ==

It’s very easy add to your program - just output a string to the speech function instead of the screen.
You don’t need an expensive/complicated LCD or monitor for your project - just use any old mp3 player loudspeaker or PC loudspeaker which you have probably got lying around - or even an earphone works well for debugging purposes too.

You could use speech output for:
(i) status messages - e.g. internet connection made or IP address on a headless RPi;
(ii) user interface - e.g. speak the mode selected or station name with button presses on an RPi internet radio;
(iii) main functionality - e.g. tell the time and read the weather forecast on your RPi alarm clock.

== Install supporting packages ==

Speech output requires a few audio software packages to be installed on your RPi. They may be already there but it does no harm to try to install these listed below anyway. The installer will let you know if the package is already present on your RPi. The instructions below are based on the Raspbian distribution (August 2012).

Firstly I recommend updating your Raspbian distribution if you have not recently already done so. Speech did not work for me until I did this. This may take 30 - 60 minutes depending on your connection speed etc. To do this:

sudo apt-get update
sudo apt-get upgrade

If you do not already have sound on your RPi then you will need the alsa sound utilities:
sudo apt-get install alsa-utils
and edit the file /etc/modules using:
sudo nano /etc/modules
to have line:
snd_bcm2835
If this line is already there then leave the file as is!

Install the mplayer audio/movie player with:
sudo apt-get install mplayer
To sort out the mplayer error message, edit file /etc/mplayer/mplayer.conf using:
sudo nano /etc/mplayer/mplayer.conf
to add line
nolirc=yes

== Festival Text to Speech ==

The first speech package I tried was Festival. It worked fine and produces a voice like a rough sounding robot. This may be just what you need if you are adding speech to your RPi robot project.

Install Festival with:
sudo apt-get install festival

Try out Festival with:
echo “Just what do you think you're doing, Dave?” | festival --tts
or to speak RPi’s IP address:
hostname -I | festival -tts

== Espeak Text to Speech ==

Espeak is a more modern speech synthesis package than Festival. It sounds clearer but does wail a little. If you are making an alien or a RPi witch then it’s the one for you! Seriously it is a good allrounder with great customisation options.

Install Espeak with:
sudo apt-get install espeak

Test Espeak with:
English female voice, emphasis on capitals (-k), speaking slowly (-s) using direct text:-
espeak -ven+f3 -k5 -s150 "I've just picked up a fault in the AE35 unit"

== Google Text to Speech ==

Google’s Text to Speech engine is a little different to Festival and Espeak. Your text is sent to Google’s servers to generate the speech file which is then returned to your Pi and played using mplayer. This means you will need an internet connection for it to work, but the speech quality is superb.

I used used ax206geek’s bash script to access the Google Text to Speech engine:

Create a file speech.sh with:
nano speech.sh

Add these lines to the file and save it (in nano editor use CTRL-O writeOut)
#!/bin/bash
say() {
local IFS=+;/usr/bin/mplayer -ao alsa -really-quiet -noconsolecontrols "http://translate.google.com/translate_tts?tl=en&q=$*"; }
say $*

Add execute permissions to your script with:
chmod u+x speech.sh

Test it using:
./speech.sh Look Dave, I can see you're really upset about this.

== Recommendations ==

I hope this guide has given you some ideas of how you can make use of speech output in your own project. As to which speech package to recommend, Festival works well enough, Espeak is clearer and so easier to understand and the Google engine gives super quality but is useless if you internet connection goes down. Maybe implement a speech function which first does a ping to Google before deciding whether to use Google or Espeak as its output engine?

File:Speech.sh

2012-10-14T05:50:05Z

StevenP: Script to access Google text to speech

Script to access Google text to speech

RPi Text to Speech (Speech Synthesis)

2012-10-05T20:37:12Z

StevenP: Created page with "This guide shows you three easy methods of getting your Raspberry Pi to talk, and describes the pros and cons of each. == Why use Text to Speech? == It’s very easy add to you..."

This guide shows you three easy methods of getting your Raspberry Pi to talk, and describes the pros and cons of each.

== Why use Text to Speech? ==

It’s very easy add to your program - just output a string to the speech function instead of the screen.
You don’t need an expensive/complicated LCD or monitor for your project - just use any old mp3 player loudspeaker or PC loudspeaker which you have probably got lying around - or even an earphone works well for debugging purposes too.

You could use speech output for:
(i) status messages - e.g. internet connection made or IP address on a headless RPi;
(ii) user interface - e.g. speak the mode selected or station name with button presses on an RPi internet radio;
(iii) main functionality - e.g. tell the time and read the weather forecast on your RPi alarm clock.

== Install supporting packages ==

Speech output requires a few audio software packages to be installed on your RPi. They may be already there but it does no harm to try to install these listed below anyway. The installer will let you know if the package is already present on your RPi. The instructions below are based on the Raspbian distribution (August 2012).

Firstly I recommend updating your Raspbian distribution if you have not recently already done so. Speech did not work for me until I did this. This may take 30 - 60 minutes depending on your connection speed etc. To do this:

sudo apt-get update
sudo apt-get upgrade

If you do not already have sound on your RPi then you will need the alsa sound utilities:
sudo apt-get install alsa-utils
and edit the file /etc/modules using:
sudo nano /etc/modules
to have line:
snd_bcm2835
If this line is already there then leave the file as is!

Install the mplayer audio/movie player with:
sudo apt-get install mplayer
Edit file /etc/mplayer/mplayer.conf using:
sudo nano /etc/mplayer/mplayer.conf
to add line
nolirc=yes

== Festival Text to Speech ==

The first speech package I tried was Festival. It worked fine and produces a voice like a rough sounding robot. This may be just what you need if you are adding speech to your RPi robot project.

Install Festival with:
sudo apt-get install festival

Try out Festival with:
echo “Just what do you think you're doing, Dave?” | festival --tts
or to speak RPi’s IP address:
hostname -I | festival -tts

== Espeak Text to Speech ==

Espeak is a more modern speech synthesis package than Festival. It sounds clearer but does wail a little. If you are making an alien or a RPi witch then it’s the one for you! Seriously it is a good allrounder with great customisation options.

Install Espeak with:
sudo apt-get install espeak

Test Espeak with:
English female voice, emphasis on capitals (-k), speaking slowly (-s) using direct text:-
espeak -ven+f3 -k5 -s150 "I've just picked up a fault in the AE35 unit"

== Google Text to Speech ==

Google’s Text to Speech engine is a little different to Festival and Espeak. Your text is sent to Google’s servers to generate the speech file which is then returned to your Pi and played using mplayer. This means you will need an internet connection for it to work, but the speech quality is superb.

I used used ax206geek’s bash script to access the Google Text to Speech engine:

Create a file speech.sh with:
nano speech.sh

Add these lines to the file and save it (in nano editor use CTRL-O writeOut)
#!/bin/bash
say() {
local IFS=+;/usr/bin/mplayer -ao alsa -really-quiet -noconsolecontrols "http://translate.google.com/translate_tts?tl=en&q=$*"; }
say $*

Add execute permissions to your script with:
chmod u+x speech.sh

Test it using:
./speech.sh Look Dave, I can see you're really upset about this.

== Recommendations ==

I hope this guide has given you some ideas of how you can make use of speech output in your own project. As to which speech package to recommend, Festival works well enough, Espeak is clearer and so easier to understand and the Google engine gives super quality but is useless if you internet connection goes down. Maybe implement a speech function which first does a ping to Google before deciding whether to use Google or Espeak as its output engine?

RPi Guides

2012-10-05T20:06:28Z

StevenP: /* Easy */

{{Template:RPi_Learning}}

==Introduction==

This page contains a set of guides to show readers how to do useful tasks. These guides focus on achieving a goal as simply as possible, with the aim to build the confidence of the reader. Hopefully, the reader will also be inspired to learn at the same time.

The Raspberry Pi Forum has a list of [http://www.raspberrypi.org/forum/projects-and-collaboration-general/the-projects-list-look-here-for-some-ideas Project Ideas & Links], to help people get started.

Please add links to your guides (and ones you find interesting).

Fill in each section:
* Guide Title (as a link to the project webpage or connected wiki page)
* Guide Description (including any additional links or information
* Tags (key words related to the project, i.e. LCD Screen, Teaching, Python)
* Author(s) or group who have produced it (also if it is an Open/Community Project for anyone to contribute)
* Guide Status (Not Started/In-Progress/Available).

==Absolute beginners==
Suitable for absolute beginners who have never experimented with Linux before.
{| border="1" style="background:transparent;"
| style="width:15%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Title and Link'''
| style="width:40%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Description'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Tags'''
| style="width:10%; vertical-align:top; border:1px solid #aaa;" |
'''Author'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Status'''
|-
| vertical-align:top; border:1px solid #aaa;" |

===[[RPi Chromium | Installing Chromium web browser]]===
| vertical-align:top; border:1px solid #aaa;" |
Installing the Chromium web browser on Debian.
| vertical-align:top; border:1px solid #aaa;" |
Chromium
| vertical-align:top; border:1px solid #aaa;" |
bredman
| vertical-align:top; border:1px solid #aaa;" |
Ready for testing
|-
|}

==Easy==
Suitable for beginners who are confident typing commands into Linux but need a lot of guidance.
{| border="1" style="background:transparent;"
| style="width:15%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Title and Link'''
| style="width:40%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Description'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Tags'''
| style="width:10%; vertical-align:top; border:1px solid #aaa;" |
'''Author'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Status'''
|-
| vertical-align:top; border:1px solid #aaa;" |

===[[R-Pi NAS | Network Attached Storage]]===
| vertical-align:top; border:1px solid #aaa;" |
Network Attached Storage - Basic concept: A place to save copies of all your important files
| vertical-align:top; border:1px solid #aaa;" |
Samba
| vertical-align:top; border:1px solid #aaa;" |
[[User:bredman | bredman]] - Open Project
| vertical-align:top; border:1px solid #aaa;" |
Tested on Debian, some help needed with Fedora chapter
|-
| vertical-align:top; border:1px solid #aaa;" |

===[[Autoinstall Samba | Connect your RPi to your MS Windows machines]]===
| vertical-align:top; border:1px solid #aaa;" |
The guide above is a full NAS setup - This guide/script just configures and installs a very simple setup to allow you to read/write to your RPi files
| vertical-align:top; border:1px solid #aaa;" |
Samba
| vertical-align:top; border:1px solid #aaa;" |
[[User:SimpleSi | Simon Walters]] - Open Project
| vertical-align:top; border:1px solid #aaa;" |
Tested on Raspbian
|-
| vertical-align:top; border:1px solid #aaa;" |

===[[RPi Debian Python3 | Python 3 on Debian]]===
| vertical-align:top; border:1px solid #aaa;" |
Installing the latest Python 3 and common modules on Debian.
| vertical-align:top; border:1px solid #aaa;" |
Python
| vertical-align:top; border:1px solid #aaa;" |
croston
| vertical-align:top; border:1px solid #aaa;" |
Tested. Needs more modules adding
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi Debian Auto Login | Debian Auto Login/Startx]]===
| vertical-align:top; border:1px solid #aaa;" |
How to launch LXDE without the need of a username/Password in Debian.
| vertical-align:top; border:1px solid #aaa;" |
LXDE, Boot, Login, Auto
| vertical-align:top; border:1px solid #aaa;" |
Ian Hartwell (helpme1986)
| vertical-align:top; border:1px solid #aaa;" |
Early draft.
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPiForked-Daapd]]===
| vertical-align:top; border:1px solid #aaa;" |
How to install Forked-Daapd, an itunes media server
| vertical-align:top; border:1px solid #aaa;" |
Debian, streaming,
| vertical-align:top; border:1px solid #aaa;" |
Greg (pr1sm)
| vertical-align:top; border:1px solid #aaa;" |
Early draft.
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi Setting up a static IP in Debian | Setting up a static IP in Debian]]===
| vertical-align:top; border:1px solid #aaa;" |
How to set-up a static IP in Debian
| vertical-align:top; border:1px solid #aaa;" |
Debian, Static IP
| vertical-align:top; border:1px solid #aaa;" |
sleepy
| vertical-align:top; border:1px solid #aaa;" |
Available
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi Text to Speech (Speech Synthesis) | Text to Speech (Speech Synthesis)]]===
| vertical-align:top; border:1px solid #aaa;" |
Three easy methods of getting your Raspberry Pi to talk
| vertical-align:top; border:1px solid #aaa;" |
Raspbian
| vertical-align:top; border:1px solid #aaa;" |
StevenP
| vertical-align:top; border:1px solid #aaa;" |
Draft
|-
|}

==Medium==
Suitable for beginners who are willing to experiment and only need a little guidance.
{| border="1" style="background:transparent;"
| style="width:15%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Title and Link'''
| style="width:40%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Description'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Tags'''
| style="width:10%; vertical-align:top; border:1px solid #aaa;" |
'''Author'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Status'''
|-
| vertical-align:top; border:1px solid #aaa;" |
===[[R-Pi PXE Server | Classroom Boot Server]]===
| vertical-align:top; border:1px solid #aaa;" |
Classroom boot server - Basic concept: A PXE server to allow cheap computers without hard disks to boot into Windows or Linux.
| vertical-align:top; border:1px solid #aaa;" |
PXE, netboot
| vertical-align:top; border:1px solid #aaa;" |
[[User:bredman | bredman]] - Open Project
| vertical-align:top; border:1px solid #aaa;" |
Lots of random text, needs organisation and testing
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi Ruby on Rails | Installing Ruby on Rails]]===
| vertical-align:top; border:1px solid #aaa;" |
Installing Ruby on Rails and common modules on Debian.
| vertical-align:top; border:1px solid #aaa;" |
Ruby, Rails
| vertical-align:top; border:1px solid #aaa;" |
Erik
| vertical-align:top; border:1px solid #aaa;" |
Partially tested. Still early draft.
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi VNC Server | Share your screen with VNC]]===
| vertical-align:top; border:1px solid #aaa;" |
Installing VNC to allow remote control of the screen from another computer.
| vertical-align:top; border:1px solid #aaa;" |
VNC
| vertical-align:top; border:1px solid #aaa;" |
Simon H
| vertical-align:top; border:1px solid #aaa;" |
Early draft.
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi iSCSI Initiator | iSCSI support and boot]]===
| vertical-align:top; border:1px solid #aaa;" |
Adding iSCSI initiator/target support, setting up iSCSI initiator, and configuring booting from an iSCSI volume.
| vertical-align:top; border:1px solid #aaa;" |
iSCSI, netboot
| vertical-align:top; border:1px solid #aaa;" |
Alex (nidO)
| vertical-align:top; border:1px solid #aaa;" |
Early draft, tested
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi_Email_IP_On_Boot_Debian | Send email containing Pi ip address on boot]]===
| vertical-align:top; border:1px solid #aaa;" |
Send email containing the ip of your Pi so you can access via SSH or other network protocol when your ip changes (moving networks) and you are working headless
| vertical-align:top; border:1px solid #aaa;" |
SSH, email, python
| vertical-align:top; border:1px solid #aaa;" |
--[[User:Geraldcor|Geraldcor]] 03:36, 18 June 2012 (UTC)
| vertical-align:top; border:1px solid #aaa;" |
Early draft, tested
|-

| vertical-align:top; border:1px solid #aaa;" |
===[http://www.penguintutor.com/linux/tightvnc Connecting securely to TightVNC over the Internet]===
| vertical-align:top; border:1px solid #aaa;" |
Guide to installing Tightvnc server on the Raspberry Pi and securing it using ssh to allow connecting over the Internet.
| vertical-align:top; border:1px solid #aaa;" |
VNC, ssh
| vertical-align:top; border:1px solid #aaa;" |
Stewart Watkiss
| vertical-align:top; border:1px solid #aaa;" |
Available
|-

| vertical-align:top; border:1px solid #aaa;" |
===[http://www.penguintutor.com/linux/raspberrypi-webserver Configuring a LAMP webserver]===
| vertical-align:top; border:1px solid #aaa;" |
Guide to configuring the Raspberry Pi as a LAMP (Linux, Apache, Mysql, PHP) webserver.
| vertical-align:top; border:1px solid #aaa;" |
apache, mysql, php
| vertical-align:top; border:1px solid #aaa;" |
Stewart Watkiss
| vertical-align:top; border:1px solid #aaa;" |
Available
|-

| vertical-align:top; border:1px solid #aaa;" |
===[https://github.com/ewindisch/chefiler Storage Filer/NAS via Chef]===
| vertical-align:top; border:1px solid #aaa;" |
Turn-key package to turn a machine into a storage filer / NAS. Developed and tested on a RaspberryPi. Still in early development. Deploys with Chef.
| vertical-align:top; border:1px solid #aaa;" |
samba, nfs, chef
| vertical-align:top; border:1px solid #aaa;" |
Eric Windisch
| vertical-align:top; border:1px solid #aaa;" |
Alpha/early-stage
|-

|}

==Advanced==
Suitable for confident users who want to try something more advanced.
{| border="1" style="background:transparent;"
| style="width:15%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Title and Link'''
| style="width:40%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Description'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Tags'''
| style="width:10%; vertical-align:top; border:1px solid #aaa;" |
'''Author'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Status'''
|-
| vertical-align:top; border:1px solid #aaa;" |
===[[RPi building and installing OpenELEC | building and installing OpenELEC]]===
| vertical-align:top; border:1px solid #aaa;" |
How to build and install OpenELEC,a embedded Multimedia Distro. You can learn (cross)compiling, building packages from source, how buildsystems are working and what is needed to install a OS on a SD-card for Raspberry Pi.
| vertical-align:top; border:1px solid #aaa;" |
XBMC, HTPC, Multimedia, Distro, compiling
| vertical-align:top; border:1px solid #aaa;" |
Stephan Raue
| vertical-align:top; border:1px solid #aaa;" |
Available
|-
| vertical-align:top; border:1px solid #aaa;" |
===[[RPi Using Skypekit | Using Skypekit]]===
| vertical-align:top; border:1px solid #aaa;" |
How to get started using Skypekit to make calls & chat. This is currently only useful for advanced users & developers.
| vertical-align:top; border:1px solid #aaa;" |
Skype, Skypekit
| vertical-align:top; border:1px solid #aaa;" |
Henry Cooke
| vertical-align:top; border:1px solid #aaa;" |
Alpha.
|-

| vertical-align:top; border:1px solid #aaa;" |

===[http://www.penguintutor.com/linux/raspberrypi-headless Pre-configuring SD card with a static IP address]===
| vertical-align:top; border:1px solid #aaa;" |
Guide to pre-configuring a SD image so that it boots with a static IP address. Useful for running headless without needing to know what DHCP address will be allocated.
| vertical-align:top; border:1px solid #aaa;" |
networking, tcpip
| vertical-align:top; border:1px solid #aaa;" |
Stewart Watkiss
| vertical-align:top; border:1px solid #aaa;" |
Available
|-

|}

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]