Comments on: Speech synthesis on the OS X command line http://dowhatimean.net/2006/10/speech-synthesis-on-the-os-x-command-line Richard Cyganiak's Weblog Fri, 12 Mar 2010 02:00:50 +0000 http://wordpress.org/?v=2.6.3 By: Matthew Elvey http://dowhatimean.net/2006/10/speech-synthesis-on-the-os-x-command-line#comment-302304 Matthew Elvey Mon, 08 Mar 2010 23:16:15 +0000 http://dowhatimean.net/2006/10/speech-synthesis-on-the-os-x-command-line#comment-302304 <p>Thanks! I'm trying to use this to run meetings:</p> <p>say "Hello, and welcome to the meeting. We begin with announcements. 10 minutes. Begin" sleep 540 say "9 minutes have passed" sleep 60 say "ok, Time up" say "What's next?" say "Items we will discuss for 5 minutes. Ready?" say "Item 1: Widget output. Yes, I can even read the agenda items to us. If I do that, it could help keep us on track..."</p> Thanks! I’m trying to use this to run meetings:

say “Hello, and welcome to the meeting. We begin with announcements. 10 minutes. Begin” sleep 540 say “9 minutes have passed” sleep 60 say “ok, Time up” say “What’s next?” say “Items we will discuss for 5 minutes. Ready?” say “Item 1: Widget output. Yes, I can even read the agenda items to us. If I do that, it could help keep us on track…”

]]> By: Tom Anderson http://dowhatimean.net/2006/10/speech-synthesis-on-the-os-x-command-line#comment-216808 Tom Anderson Sat, 13 Sep 2008 17:04:28 +0000 http://dowhatimean.net/2006/10/speech-synthesis-on-the-os-x-command-line#comment-216808 <p>Oops that should have been:</p> <p>say -o plugh.aiff "plugh"</p> Oops that should have been:

say -o plugh.aiff “plugh”

]]> By: Tom Anderson http://dowhatimean.net/2006/10/speech-synthesis-on-the-os-x-command-line#comment-216807 Tom Anderson Sat, 13 Sep 2008 17:03:24 +0000 http://dowhatimean.net/2006/10/speech-synthesis-on-the-os-x-command-line#comment-216807 <p>It turns out that unix is perfect: the > symbol just redirects standard output from the terminal to a file. So it should make an empty file.</p> <p>If you want to send the output an aiff file use:</p> <p>say "plugh" -o plugh.aiff</p> <p>you can see this an more with</p> <p>man say</p> It turns out that unix is perfect: the > symbol just redirects standard output from the terminal to a file. So it should make an empty file.

If you want to send the output an aiff file use:

say “plugh” -o plugh.aiff

you can see this an more with

man say

]]>