<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The ReadSpeaker Blogtext-to-speech &#187; The ReadSpeaker Blog</title>
	<atom:link href="http://blog.readspeaker.com/tag/text-to-speech/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.readspeaker.com</link>
	<description>A blog about speech-enabling online content</description>
	<lastBuildDate>Mon, 06 Feb 2012 10:37:15 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
		<item>
		<title>Pronunciation corrections in online text to speech</title>
		<link>http://blog.readspeaker.com/2011/09/20/pronunciation-corrections-in-online-text-to-speech/</link>
		<comments>http://blog.readspeaker.com/2011/09/20/pronunciation-corrections-in-online-text-to-speech/#comments</comments>
		<pubDate>Tue, 20 Sep 2011 20:46:21 +0000</pubDate>
		<dc:creator>roylindemann</dc:creator>
				<category><![CDATA[Online Text to Speech]]></category>
		<category><![CDATA[Speech synthesis]]></category>
		<category><![CDATA[Text to Speech Online]]></category>
		<category><![CDATA[online text to speech]]></category>
		<category><![CDATA[text-to-speech]]></category>

		<guid isPermaLink="false">http://blog.readspeaker.com/?p=563</guid>
		<description><![CDATA[Although text-to-speech technology has made a lot of progress, it can sometimes stumble on certain terms such as acronyms, abbreviations, date formats or number representations to name a few. We have some customers where the pronunciation needs fine-tuning such as in the pharmaceutical sector for example where it is even more important that each term is [...]]]></description>
			<content:encoded><![CDATA[<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="standard" count="1" href="http://blog.readspeaker.com/2011/09/20/pronunciation-corrections-in-online-text-to-speech/"></g:plusone></div><p><a title="Moving World Artwork showing acronyms, Heathrow Terminal 5, London." href="http://www.flickr.com/photos/brighton/2520503925/"><img src="http://farm3.static.flickr.com/2048/2520503925_1010b8ae3b.jpg" alt="Moving World Artwork showing acronyms, Heathrow Terminal 5, London." width="500" height="322" /></a></p>
<p>Although <a href="http://blog.readspeaker.com/2010/09/09/a-brief-history-speech-synthesis-text-to-speech/">text-to-speech technology</a> has made a lot of progress, it can sometimes stumble on certain terms such as acronyms, abbreviations, date formats or number representations to name a few. We have some customers where the pronunciation needs fine-tuning such as in the pharmaceutical sector for example where it is even more important that each term is perfectly well read.</p>
<p>Every account that we open comes with a specific dictionary for the customer. We provide a <a href="http://blog.readspeaker.com/2011/05/13/how-readspeaker-ensures-your-web-pages-are-well-read/">service</a> to each of our customers that helps them with pronunciation issues when they exist. Some of the pronunciation corrections will only be relevant to the dictionary of a particular customer, but in some instances the corrections can also be used for the default dictionary and benefit our entire customer base. We have a very knowledgeable network of linguists that can help our customers in many parts of the world when they encounter pronunciation difficulties.</p>
<p>We have prepared a few <a href="http://demo.readspeaker.com/?p=exp.pronunciation&amp;l=en-us">online text to speech demos</a> that show the before and after effect of our work on some types of words that can get mispronounced by speech synthesis.</p>
<p>Photo Credit: <a href="http://www.flickr.com/photos/brighton/2520503925/">Jim Linwood</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.readspeaker.com/2011/09/20/pronunciation-corrections-in-online-text-to-speech/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How text to speech is made</title>
		<link>http://blog.readspeaker.com/2010/09/10/how-text-to-speech-is-made/</link>
		<comments>http://blog.readspeaker.com/2010/09/10/how-text-to-speech-is-made/#comments</comments>
		<pubDate>Fri, 10 Sep 2010 08:51:28 +0000</pubDate>
		<dc:creator>roylindemann</dc:creator>
				<category><![CDATA[Speech synthesis]]></category>
		<category><![CDATA[TTS]]></category>
		<category><![CDATA[ReadSpeaker]]></category>
		<category><![CDATA[text-to-speech]]></category>

		<guid isPermaLink="false">http://blog.readspeaker.com/?p=343</guid>
		<description><![CDATA[Following yesterday&#8217;s post about a brief history of text to speech, today we list some of the techniques involved in creating speech synthesis. Articulatory synthesis In an articulatory synthesis, models of the human articulators (tongue, lips, teeth, jaw) and vocal ligament are used to simulate how an airflow passes through, to calculate what the resulting [...]]]></description>
			<content:encoded><![CDATA[<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="standard" count="1" href="http://blog.readspeaker.com/2010/09/10/how-text-to-speech-is-made/"></g:plusone></div><p>Following yesterday&#8217;s post about a <a href="http://blog.readspeaker.com/2010/09/09/a-brief-history-speech-synthesis-text-to-speech/">brief history of text to speech</a>, today we list some of the techniques involved in creating speech synthesis.</p>
<h2>Articulatory synthesis</h2>
<p>In an articulatory synthesis, models of the human articulators  (tongue, lips, teeth, jaw) and vocal ligament are used to simulate how  an airflow passes through, to calculate what the resulting sound will be  like. It is a great challenge to find good mathematical models and  therefore the development of articulatory synthesis is still in  research. The technique is very computation-intensive but memory  requirements is almost nothing.</p>
<h2>Formant</h2>
<p>The synthesis is a sort of source-filter-method that is based on mathematic models of the human speech organ.<br />
The  approach pipe is modelled from a number of resonances with resemblance  to the formants (frequency bands with high energy in voices) in natural  speech.<br />
The first electronic voices Voder, and later on OVE and PAT,  were speaking with totally synthetic and electronic produced sounds  using formant synthesis. As with articulatory synthesis, the memory  consumption is small but CPU usage is large.</p>
<h2>Concatenating synthesis</h2>
<p>A concatenating synthesis is made of recorded pieces of speech  (sound-clips) that is then unitized and formed to speech. Depending on  how long sound-clips that are used it become a diphone or a polyphonic  synthesis. The later in a more developed version is also called a Unit  Selection synthesis, where the synthesizer has access to both long and  short segments of speech and the best segments for the actual context is  chosen.</p>
<h2>Diphone</h2>
<p>For a diphone synthesis the elements from the recorded speech are very small.<br />
The  strength in this case is that almost any sentence or expression may be  read but quite often there are errors in the pronunciation and if the  model used for prosody is not good, or modelling is difficult, the  speech may sound a bit monotonic.<br />
A diphone synthesis doesn&#8217;t work  that well in languages where there is a lot of inconsequence in the  pronunciation rules (English, Swedish etc) and in special cases where  letters is pronounced differently than in general. The diphone works  better for languages that have large consistencies in the pronunciation  (Spanish, Finnish etc.) Another advantage is that the prosody, the  intonation, can be described in very much detail.</p>
<h2>Unit selection</h2>
<p>The greatest difference between a Unit selection and a diphone voice  is the length of the used speech segments. There are entire words and  phrases stored in the unit database. this implies that the database for  the Unit selection voices are many times bigger than for diphone voices.  Thus, the memory consumption is huge while the CPU consumption is low.</p>
<p>The  most important issue is to still get a natural and smooth prosody. This  is hard because the units contain both intonation and pronunciation  since entire phrases are used almost directly from the recorded data.  Since the first Unit selection voice was released, over eight years ago,  there has been much improvements for each new voice with every release.  This is by far the most widely used technique among our providers.</p>
<h2>HMM synthesis</h2>
<p>A quite new technology is speech synthesis based on HMM, a  mathematical concept called Hidden Markov models. It is a statistical  method where the text-to-speech system is based on a model that is not  known beforehand but it is refined by continuous training. The technique  consumes large CPU resources but very little memory. This approach  seems to give a better prosody, without glitches, and still producing  very natural sounding, human-like speech. We collaborate with providers  offering this technique as well.</p>
<h2>Customizations and improvements</h2>
<p>On top of using the best voices available we also add our own layer  of improvement, both general and customer specific customizations. We  have linguists with long experience of speech synthesis working with  transcriptions to tweak the pronunciation and reading of the spoken  text. Therefore we can greatly help our customers that want to optimize the quality of the text to speech on their web pages.  Sometimes it is enough to do a quality control of a couple of hours  listening to your website and correct the errors we find. In other cases some of our customers have industry specific words (think of the pharmaceutical industry for example) where it is very important that they are pronounced correctly.</p>
<p>One of the largest  customizations we have made so far was for a customer who sent us a  list of over 3000 words that had to be quality controlled. Another  customization was for a site with about 200 000 pages where the same  acronym or abbreviation had to be expanded differently depending on at  what part of the site it was mentioned in. Many users wonder why the same  voice reads so much better when it is used in our services compared to  when the same voice, or text-to-speech system, is used for reading  similar, or the same, content with other softwares or services. The  answer is the above mentioned customizations.</p>
<p><em>Thanks to <a href="http://www.ling.su.se/staff/hartmut/" target="_blank"><span style="color: #4334b2;">Professor Hartmut Traunmüller, Dept. of Linguistics at the University of Stockholm</span></a> for a lot of the facts, the picture and the sound samples on this page.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.readspeaker.com/2010/09/10/how-text-to-speech-is-made/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>A brief history of speech synthesis (text to speech)</title>
		<link>http://blog.readspeaker.com/2010/09/09/a-brief-history-speech-synthesis-text-to-speech/</link>
		<comments>http://blog.readspeaker.com/2010/09/09/a-brief-history-speech-synthesis-text-to-speech/#comments</comments>
		<pubDate>Thu, 09 Sep 2010 10:16:14 +0000</pubDate>
		<dc:creator>roylindemann</dc:creator>
				<category><![CDATA[Speech synthesis]]></category>
		<category><![CDATA[ReadSpeaker]]></category>
		<category><![CDATA[text-to-speech]]></category>
		<category><![CDATA[TTS]]></category>

		<guid isPermaLink="false">http://blog.readspeaker.com/?p=339</guid>
		<description><![CDATA[Behind all our services there is a server-based software performing the speech synthesis, called text-to-speech software. The voices we use are provided by different providers but the technique behind the different voices has many similarities. Therefore we like to tell you briefly about the development of speech synthesis and its history. The history of speech [...]]]></description>
			<content:encoded><![CDATA[<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="standard" count="1" href="http://blog.readspeaker.com/2010/09/09/a-brief-history-speech-synthesis-text-to-speech/"></g:plusone></div><p>Behind all our services there is a server-based software performing the  speech synthesis, called text-to-speech software. The voices we use are  provided by different providers but the technique behind the different  voices has many similarities. Therefore we like to tell you briefly  about the development of speech synthesis and its history.</p>
<p><span id="more-339"></span></p>
<h2>The history of speech synthesis</h2>
<p>Over  the last few years there has been a great development of the quality of  the speech produced with text to speech. Many people think that  synthetic speech as it is also called sounds like robots from older movies. The truth is  though that some voices almost sound like recorded speech and due to  that we have seen a very strong growth of user groups for our services  the last years.<br />
When we invented the talking web in 2001 the target group  was people with reading difficulties but now we see that the user group  is much broader.</p>
<p>What you maybe don&#8217;t know is that the first synthetic speech was  produced as early as in the late 18th century. The machine was built in  wood and leather and was very complicated to use generating audible  speech. It was constructed by <a title="About von Kempelen at Wikipedia" href="http://en.wikipedia.org/wiki/Wolfgang_von_Kempelen" target="_blank"><span style="color: #4334b2;">Wolfgang von Kempelen</span></a> and  had great importance in the early studies of Phonetics. The picture to the right is the original construction as it can be seen at the  Deutsches Museum (von Meisterwerken der Naturwissenschaft und Technik)  in Munich, Germany.</p>
<p><img class="alignright size-medium wp-image-341" title="Original construction of Von Kempelen's speech synthesis machine" src="http://79.136.80.205/newblog/wordpress/wp-content/uploads/2010/09/kempln31-224x300.gif" alt="Von Kempelen's speech synthesis machine" width="224" height="300" /></p>
<p><a title="Sample wav-file 776 kB" href="http://www.heise.de/ct/projekte/sprachsynthese/kempelen.wav" target="_self"><span style="color: #4334b2;">Here&#8217;s an audio sample of the synthetic speech the machine produced (WAV-file 776 kB)</span></a> .</p>
<p>(First  there is a human that says a sentence and then the machine tries to say  the same. This was made by a re-construction of Kempelens machine.)</p>
<p>In  the early 20th century when it was possible to use electricity to  create synthetic speech, the first known electric speech synthesis was  &#8220;Voder&#8221; and its creator Homer Dudley showed it to a broader audience in  1939 on the world fair in New York.</p>
<p><a title="Sound sample of speech synthesis Voder WAV 381 kB" href="http://www.ling.su.se/staff/hartmut/ljud/voder.wav" target="_blank"><span style="color: #4334b2;">Here&#8217;s an audio sample of Voder, the first electronic speech synthesis ever (WAV-file 381 kB)</span></a></p>
<p>One of the pioneers of the development of speech synthesis in Sweden  was Gunnar Fant. During the 1950s he was responsible for the development  of the first Swedish speech synthesis OVE (Orator Verbis Electris.) By  that time it was only Walter Lawrences Parametric Artificial Talker  (PAT) that could compete with OVE in speech quality.</p>
<p><a title="sample of Speech synthesis OVE WAV-file 77 kB" href="http://www.ling.su.se/staff/hartmut/ljud/Ove.wav" target="_self"><span style="color: #4334b2;">Here&#8217;s a sample of OVE speech synthesis (WAV-file 77 kB)</span></a>.</p>
<p><a title="sample of speech synthesis PAT WAV-file 117 kB" href="http://www.ling.su.se/staff/hartmut/ljud/Pat.wav" target="_blank"><span style="color: #4334b2;">and here&#8217;s a sample of the PAT speech synthesis (WAV 117 kB)</span></a>.</p>
<p>OVE and PAT were text-to-speech systems using Formant synthesis.</p>
<h2>Speech synthesis becomes more human-like</h2>
<p>The greatest improvements when it comes to natural speech were during  the last 10 years. The first voices we used for ReadSpeaker back in  2001 were produced using Diphone synthesis. The voices are sampled from  real recorded speech and split into phonemes, a small unit of human  speech. This was the first example of Concatenation synthesis. However,  they still have an artificial/synthetic sound. We still use diphone  voices for some smaller languages and they are widely used to  speech-enable handheld computers and mobile phones due to their limited  resource consumption, both memory and CPU.</p>
<p>It wasn&#8217;t until the  introduction of a technique called Unit selection, that voices became  very naturally sounding. this is still concatenation synthesis but the  used units are larger than phonemes, sometimes a complete sentence. We  use different providers for different languages to always assure we can  offer the best voices available for that language.</p>
<p>In a next post we will cover the different techniques behind speech synthesis.</p>
<p><em>Thanks to <a href="http://www.ling.su.se/staff/hartmut/" target="_blank"><span style="color: #4334b2;">Professor Hartmut Traunmüller, Dept. of Linguistics at the University of Stockholm</span></a> for a lot of the facts, the picture and the sound samples on this page.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.readspeaker.com/2010/09/09/a-brief-history-speech-synthesis-text-to-speech/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
<enclosure url="http://www.ling.su.se/staff/hartmut/ljud/voder.wav" length="100011" type="audio/x-wav" />
<enclosure url="http://www.ling.su.se/staff/hartmut/ljud/Ove.wav" length="19357" type="audio/x-wav" />
<enclosure url="http://www.ling.su.se/staff/hartmut/ljud/Pat.wav" length="30673" type="audio/x-wav" />
		</item>
		<item>
		<title>Speech-enabling for the long-tail</title>
		<link>http://blog.readspeaker.com/2009/01/21/speech-enabling-for-the-long-tail/</link>
		<comments>http://blog.readspeaker.com/2009/01/21/speech-enabling-for-the-long-tail/#comments</comments>
		<pubDate>Wed, 21 Jan 2009 18:08:37 +0000</pubDate>
		<dc:creator>niclasbergstrom</dc:creator>
				<category><![CDATA[TTS]]></category>
		<category><![CDATA[Web Accessibility]]></category>
		<category><![CDATA[services]]></category>
		<category><![CDATA[Talking web]]></category>
		<category><![CDATA[text-to-speech]]></category>
		<category><![CDATA[VoiceCorp]]></category>

		<guid isPermaLink="false">http://blog.readspeaker.com/2009/01/21/speech-enabling-for-the-long-tail/</guid>
		<description><![CDATA[As you might have remembered when I wrote a post about From birth of the talking web and into the future. I owed you a follow-up note so here it is! As I had discussed, we started out by having a focused approach on which customers we should approach and which end-users would most benefit [...]]]></description>
			<content:encoded><![CDATA[<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="standard" count="1" href="http://blog.readspeaker.com/2009/01/21/speech-enabling-for-the-long-tail/"></g:plusone></div><p>As you might have remembered when I wrote a post about <a href="http://blog.readspeaker.com/2008/10/09/from-birth-of-the-talking-web-and-into-the-future-part-1/">From birth of the talking web and into the future</a>. I owed you a follow-up note so here it is! As I had discussed, we started out by having a focused approach on which customers we should approach and which end-users would most benefit from a server-side speech-enabling solution for web sites. On the user side we have seen that the usages of our technology have increased over the past years making it appealing to a greater number of users. On the customer side, we also witnessed a greater variety of sectors interested in speech-enabling their web content ranging from public sites to banks, insurance companies, non-profit organisations and many others.<br />
 <br />
Now over the past months another change happened. We started getting an increasing amount of incoming leads from much smaller web sites and blogs also interested in speech-enabling their content. This could range from the mom and pop store with a web site to the blogger interested in space technology. These are typically 1 to 10 people organisations. Some of them are purely personal initiatives ie someone interested in a hobby while others might be freelancers, consultants, designers or any other small company or non-profit organisation. Since our company is set up to deal with mid-sized and bigger organisations we needed to see how we could propose an easy way for all these smaller web sites and blogs to speech-enable their content. The idea here was to really get a grasp on the <strong>essential</strong> features that matter to this segment and not throw in all the bells and whistles that serve no purpose at all. Then we thought how to make the implementation process as easy as possible so that all these new small customers could simply integrate our solution as a no-brainer either by using plug-ins we have developed for some popular CMS and blog platforms or either as a simple copy &amp; paste of our HTML code directly into the source code of the page. The last point was to create a new web shop where both personal web sites and blogs as well as small companies and organisations could easily choose the most suitable package for their needs, sign-up and subscribe as seamlessly as possible.<br />
 <br />
We are now proud to announce that we are ready to launch this new venture! Our new product for this segment is called webReader and you can find out all about it by going to <a href="http://www.readspeaker.com/">www.readspeaker.com</a>. We hope you will enjoy this new service and find it useful and we will dedicate our maximum attention to support you in the best way possible. We are starting off with American and British English, Swedish and French voices and will be adding more very shortly.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.readspeaker.com/2009/01/21/speech-enabling-for-the-long-tail/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Good article on text-to-speech</title>
		<link>http://blog.readspeaker.com/2009/01/08/good-article-on-text-to-speech/</link>
		<comments>http://blog.readspeaker.com/2009/01/08/good-article-on-text-to-speech/#comments</comments>
		<pubDate>Thu, 08 Jan 2009 14:01:02 +0000</pubDate>
		<dc:creator>niclasbergstrom</dc:creator>
				<category><![CDATA[TTS]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[text-to-speech]]></category>

		<guid isPermaLink="false">http://blog.readspeaker.com/2009/01/08/good-article-on-text-to-speech/</guid>
		<description><![CDATA[My colleague and co-blogger Daniel Erkstam has just published a good article about the history of text-to-speech technology. Click here to read the full article about the history of TTS.]]></description>
			<content:encoded><![CDATA[<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="standard" count="1" href="http://blog.readspeaker.com/2009/01/08/good-article-on-text-to-speech/"></g:plusone></div><p style="line-height: 15.6pt"><span style="font-family: Georgia" lang="EN-GB">My colleague and co-blogger Daniel Erkstam has just published a good article about the history of text-to-speech technology. <a target="_blank" href="http://www.voice-corp.com/en/Examples/text-to-speech/">Click here to read the full article about the history of TTS</a>.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.readspeaker.com/2009/01/08/good-article-on-text-to-speech/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Speech enabling for the masses!</title>
		<link>http://blog.readspeaker.com/2008/11/26/speech-enabling-for-the-masses/</link>
		<comments>http://blog.readspeaker.com/2008/11/26/speech-enabling-for-the-masses/#comments</comments>
		<pubDate>Wed, 26 Nov 2008 15:57:27 +0000</pubDate>
		<dc:creator>niclasbergstrom</dc:creator>
				<category><![CDATA[Web Accessibility]]></category>
		<category><![CDATA[services]]></category>
		<category><![CDATA[text-to-speech]]></category>
		<category><![CDATA[VoiceCorp]]></category>

		<guid isPermaLink="false">http://blog.readspeaker.com/2008/11/26/speech-enabling-for-the-masses/</guid>
		<description><![CDATA[In the past couple of months we have been getting an increasing number of requests from smaller personal or business web sites and blogs that are interested in speech-enabling their web content using the award winning ReadSpeaker text-to-speech services, but that we just simply could not dedicate enough time to present and sell our applications [...]]]></description>
			<content:encoded><![CDATA[<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="standard" count="1" href="http://blog.readspeaker.com/2008/11/26/speech-enabling-for-the-masses/"></g:plusone></div><p>In the past couple of months we have been getting an increasing number of requests from smaller personal or business web sites and blogs that are interested in speech-enabling their web content using the award winning ReadSpeaker text-to-speech services, but that we just simply could not dedicate enough time to present and sell our applications to. To meet their needs we have decided to open up a dedicated web shop in the next coming days and sell our new application called webReader at either affordable monthly or yearly rates or for a free ad-financed version.</p>
<p>Please stay tuned as we will announce the launch on the blog soon now.</p>
<p>If you want to be contacted as soon as webReader is available, please register at <a href="http://www.rspeak.com/wr_signup/">http://www.rspeak.com/wr_signup/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.readspeaker.com/2008/11/26/speech-enabling-for-the-masses/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Knol &#8211; now with text-to-speech</title>
		<link>http://blog.readspeaker.com/2008/10/08/google-knol-now-with-text-to-speech/</link>
		<comments>http://blog.readspeaker.com/2008/10/08/google-knol-now-with-text-to-speech/#comments</comments>
		<pubDate>Wed, 08 Oct 2008 07:22:54 +0000</pubDate>
		<dc:creator>niclasbergstrom</dc:creator>
				<category><![CDATA[TTS]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[text-to-speech]]></category>

		<guid isPermaLink="false">http://blog.readspeaker.com/2008/10/08/google-knol-now-with-text-to-speech/</guid>
		<description><![CDATA[A few days ago Google announced that they begin to experiment with text-to-speech on their &#8220;Knol&#8221;. Quote from their site: &#8220;We are experimenting with Audio Playback as an option for some knols, starting with a handful of English language featured knols. You can listen using our Flash player, or by downloading an mp3 file and [...]]]></description>
			<content:encoded><![CDATA[<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="standard" count="1" href="http://blog.readspeaker.com/2008/10/08/google-knol-now-with-text-to-speech/"></g:plusone></div><p>A few days ago Google announced that they begin to experiment with text-to-speech on their &#8220;Knol&#8221;.</p>
<p>Quote from their site: &#8220;We are experimenting with Audio Playback as an option for some knols, starting with a handful of English language featured knols. You can listen using our Flash player, or by downloading an mp3 file and using any mp3 player.&#8221;</p>
<p>If a listen-button is shown next to the &#8220;print&#8221; and &#8220;share&#8221; button, you know that the Knol is available also as audio.</p>
<p>Read all about it and try it out here: <a href="http://knol.google.com/k/knol-help/knol-audio-playback/">http://knol.google.com/k/knol-help/knol-audio-playback/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.readspeaker.com/2008/10/08/google-knol-now-with-text-to-speech/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Listen function as Universal design</title>
		<link>http://blog.readspeaker.com/2008/10/03/listen-function-as-universal-design/</link>
		<comments>http://blog.readspeaker.com/2008/10/03/listen-function-as-universal-design/#comments</comments>
		<pubDate>Fri, 03 Oct 2008 06:14:46 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Web Accessibility]]></category>
		<category><![CDATA[text-to-speech]]></category>
		<category><![CDATA[Universal Design]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://blog.readspeaker.com/2008/10/03/listen-function-as-universal-design/</guid>
		<description><![CDATA[The other day I was standing in the hotel bar watching the TV. The volume was turned down completely but thanks to the real-time captioning I was able to follow the news broadcast. The day after, I was spending some hours waiting for my delayed flight at Heathrow airport to get ready for departure. There was [...]]]></description>
			<content:encoded><![CDATA[<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="standard" count="1" href="http://blog.readspeaker.com/2008/10/03/listen-function-as-universal-design/"></g:plusone></div><p><font size="2">The other day I was standing in the hotel bar watching the TV. The volume was turned down completely but thanks to the real-time captioning I was able to follow the news broadcast. The day after, I was spending some hours waiting for my delayed flight at Heathrow airport to get ready for departure. There was a TV on the waiting area, again with the volume turned down. This time there was no captioning. However, they did have a sign-language narrator in the bottom right corner of the screen. That didn’t help me much since I can’t understand sign language. I was experience &#8220;Situational Disability&#8221;. In this case, text would have helped everybody that could read.</font><font size="2">Now, what about Audio? There are a great number of reasons why audio version of the text is as universal as text version of audio. Take reading a news article as an example. It is fairly difficult (not to say dangerous) to read today’s edition of the International Herald Tribune when driving a car. Text just simply doesn’t do very well in that situation. Reading it on a small mobile display is also not the best way to consume the article. If you have some kind of disability that makes it difficult to read ANY text you are in about the same situation. The fact that we want to consume written text in a situation when that is not possible (or convenient) somehow makes us all disabled. It is the situation that creates the handicap, not necessarily our abilities.</p>
<p>There are many people that are helped by speech function integrated on a website. I would dare to say that being able to listen to a web page is Universal Design.<font size="2"> </font></p>
<p>The last years more and more websites subscribe to our ReadSpeaker services that speech enable the websites for anyone that rather listens than reads. We are currently working very hard to make the services more usable in any kind of situation, and regardless of what device you happen to use. It is both a question of usability and mobile user experience. ReadSpeaker is in itself completely device independent since it is a server side service, and we are now finalizing our new implementation instructions that will ensure that it works on any computer, handheld, mobile phone and whatever device that could possibly have a web browser installed. The amount of people using the mobile phone to browse the Internet is increasing dramatically and within the next 2-3 years analysts expect that almost 3 billion people will have web access through their mobile phones. It is time to get ready for this. First, to create websites that work in all these devices and also, since we would probably not see any 17 inch displays on these, speech enable the sites. For everybody that rather listens than reads.</p>
<p></font></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.readspeaker.com/2008/10/03/listen-function-as-universal-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Official San Francisco Website, now talking to you!</title>
		<link>http://blog.readspeaker.com/2008/08/02/the-official-san-francisco-website-now-talking-to-you/</link>
		<comments>http://blog.readspeaker.com/2008/08/02/the-official-san-francisco-website-now-talking-to-you/#comments</comments>
		<pubDate>Sat, 02 Aug 2008 12:38:00 +0000</pubDate>
		<dc:creator>niclasbergstrom</dc:creator>
				<category><![CDATA[Customers]]></category>
		<category><![CDATA[ReadSpeaker]]></category>
		<category><![CDATA[text-to-speech]]></category>
		<category><![CDATA[VoiceCorp]]></category>

		<guid isPermaLink="false">http://blog.rspeak.com/2008/08/02/the-official-san-francisco-website-now-talking-to-you/</guid>
		<description><![CDATA[  VoiceCorp has done it again! The official website for the City of San Francisco is one of the latest web sites to make their content more accessible by adding the ReadSpeaker read-aloud text-to-speech service to their web pages. Most of the pages on the website now have a ”Listen” button in the tool bar [...]]]></description>
			<content:encoded><![CDATA[<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="standard" count="1" href="http://blog.readspeaker.com/2008/08/02/the-official-san-francisco-website-now-talking-to-you/"></g:plusone></div><p><img border="0" align="top" width="124" src="http://tbn0.google.com/images?q=tbn:SQrntGX-n9JVkM:http://bp3.blogger.com/_cV0JAYhz-pc/R9hQTMvZHGI/AAAAAAAAAK0/gRNB225mDmM/s400/moon_over_san_francisco.jpg" alt="City of San Francisco by night" height="93" /> </p>
<p style="margin-bottom: 0cm"><span lang="en-US">VoiceCorp has done it again! The official website for the City of San Francisco is one of the latest web sites to make their content more accessible by adding the ReadSpeaker read-aloud text-to-speech service to their web pages. Most of the pages on the website now have a ”Listen” button in the tool bar right next to the ”Print”, ”Text Only” and ”Font size” functions. Listen for yourself at <a href="http://www.sfgov.org/site/mayor_index.asp">http://www.sfgov.org/site/mayor_index.asp</a></span></p>
<p style="margin-bottom: 0cm"><span lang="en-US"></span></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.readspeaker.com/2008/08/02/the-official-san-francisco-website-now-talking-to-you/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Guest blogger: Speech syntheses – one for each purpose</title>
		<link>http://blog.readspeaker.com/2008/06/02/guest-blogger-speech-syntheses-%e2%80%93-one-for-each-purpose/</link>
		<comments>http://blog.readspeaker.com/2008/06/02/guest-blogger-speech-syntheses-%e2%80%93-one-for-each-purpose/#comments</comments>
		<pubDate>Mon, 02 Jun 2008 18:20:18 +0000</pubDate>
		<dc:creator>niclasbergstrom</dc:creator>
				<category><![CDATA[TTS]]></category>
		<category><![CDATA[Guest blogger]]></category>
		<category><![CDATA[text-to-speech]]></category>

		<guid isPermaLink="false">http://blog.rspeak.com/2008/06/02/guest-blogger-speech-syntheses-%e2%80%93-one-for-each-purpose/</guid>
		<description><![CDATA[This is a post from todays guest blogger: Daniel Erkstam, Nordic Sales Director for VoiceCorp.   The pictures shows two robots. The left one is an industrial robot from ABB that probably is used to build cars or something similar. The right one is one of the most advanced AI robots that can be found today. It [...]]]></description>
			<content:encoded><![CDATA[<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="standard" count="1" href="http://blog.readspeaker.com/2008/06/02/guest-blogger-speech-syntheses-%e2%80%93-one-for-each-purpose/"></g:plusone></div><p><em>This is a post from todays guest blogger: Daniel Erkstam, Nordic Sales Director for VoiceCorp.</em></p>
<p> <img border="0" src="http://www.storvreta.nu/bilder/we-are-the-robots.JPG" hspace="5" alt="Two robots" /></p>
<p>The pictures shows two robots. The left one is an industrial robot from ABB that probably is used to build cars or something similar. The right one is one of the most advanced AI robots that can be found today. It is possible to converse with it and it is very human like.</p>
<p>Both robots serve their purpose and do it well. And it is the same with speech syntheses.</p>
<p>When we launched the first speaking web services back in 2001 the only available voices was very robotic ones and became kind of boring listening to on longer texts. Today we use voices made in a complete different technique and the quality become closer and closer to recorded speech.</p>
<p>But the thing is that the older voices is still used by a lot of people and is even preferred compared to the newer ones for some purposes. For example people with visual impairment often prefer the older voices for screen-reading software&#8217;s like Jaws. The reason is that the older voices are more consequent on how they read the text and you can get used to the odd and robotic character of the voice. The older voices also read out the text in a more detailed way. The voices we use today are a lot more human like but also more &#8220;forgiving&#8221; when it comes to spelling errors and some words from foreign languages etc. The secret behind that is many times bigger database with the phonemes.</p>
<p>We know that the smaller need a person have for a synthetic speech, the harder judge he/she will be. We who doesn’t have reading difficulties or visual impairment can see/read the text and compare that to the voice speaking. Then we react on every little slight error in the pronouncing by the synthesis.</p>
<p>We put a lot of effort to make the reading as good as possible by making a lot of customizations so that the speech syntheses pronounce the current website&#8217;s vocabulary as good as possible. Because we know that there is a strong connection between how good it sounds and how many people that will use the service.</p>
<p>Back to the robots again: They might both serve their purposes well. But I guess it would be an easy choice which one you would pick to serve visitors at the reception desk, right?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.readspeaker.com/2008/06/02/guest-blogger-speech-syntheses-%e2%80%93-one-for-each-purpose/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

