<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments for testing simon</title>
	<atom:link href="http://spirit.blau.in/simon/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://spirit.blau.in/simon</link>
	<description>my first steps with the simon speech recognition software</description>
	<lastBuildDate>Fri, 26 Feb 2010 08:17:17 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Configuring incomplete, errors occurred by Peter Grasch</title>
		<link>http://spirit.blau.in/simon/2010/02/26/configuring-incomplete-errors-occurred/#comment-272</link>
		<dc:creator>Peter Grasch</dc:creator>
		<pubDate>Fri, 26 Feb 2010 08:17:17 +0000</pubDate>
		<guid isPermaLink="false">http://spirit.blau.in/simon/?p=2494#comment-272</guid>
		<description>If your system is up to date it looks like KUbuntu still doesn&#039;t provide packages for KDE 4.4.0 (afaik 4.3.95 is a release candidate).

Technically KDE 4.3.95 works too but IMHO it is nicer to check for major version.

If a someone uses KDE 4.3.5 and sees a message that at least KDE 4.3.90 is required he might search for updates to KDE 4.3.x instead of looking for KDE 4.4. This way the message is more clear. If at the point of release, KDE 4.4 is still not wildly available, we will have to work around it anyways (disable some functionality if KDE 4.4 is not found) but I really doubt that...


Greetings,
Peter</description>
		<content:encoded><![CDATA[<p>If your system is up to date it looks like KUbuntu still doesn&#8217;t provide packages for KDE 4.4.0 (afaik 4.3.95 is a release candidate).</p>
<p>Technically KDE 4.3.95 works too but IMHO it is nicer to check for major version.</p>
<p>If a someone uses KDE 4.3.5 and sees a message that at least KDE 4.3.90 is required he might search for updates to KDE 4.3.x instead of looking for KDE 4.4. This way the message is more clear. If at the point of release, KDE 4.4 is still not wildly available, we will have to work around it anyways (disable some functionality if KDE 4.4 is not found) but I really doubt that&#8230;</p>
<p>Greetings,<br />
Peter</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Active vocabulary is gone by Peter Grasch</title>
		<link>http://spirit.blau.in/simon/2010/02/19/active-vocabulary-is-gone/#comment-271</link>
		<dc:creator>Peter Grasch</dc:creator>
		<pubDate>Sat, 20 Feb 2010 10:11:48 +0000</pubDate>
		<guid isPermaLink="false">http://spirit.blau.in/simon/?p=2489#comment-271</guid>
		<description>Please make sure that you can reproduce the problem and report it in more detail (including version numbers, etc.) on our bugtracker on sourceforge.

Thanks.

Greetings,
Peter</description>
		<content:encoded><![CDATA[<p>Please make sure that you can reproduce the problem and report it in more detail (including version numbers, etc.) on our bugtracker on sourceforge.</p>
<p>Thanks.</p>
<p>Greetings,<br />
Peter</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on git pull origin master; Serialize scenarios by Peter Grasch</title>
		<link>http://spirit.blau.in/simon/2010/02/16/git-pull-origin-master-serialize-scenarios/#comment-270</link>
		<dc:creator>Peter Grasch</dc:creator>
		<pubDate>Tue, 16 Feb 2010 20:37:51 +0000</pubDate>
		<guid isPermaLink="false">http://spirit.blau.in/simon/?p=2477#comment-270</guid>
		<description>No, sorry.

Basically, with the new architecture you organize your vocabulary, grammar, commands, etc. in scenario packages. During compilation you serialize those scenarios to the input files for the HTK / Julius tools.

Those buttons in sam provide the same serialization features and are basically &quot;export to HTK/Julius&quot; buttons. They are not meant to be used as &quot;export&quot; features but rather as a way to intervene at a lower level. sam caters to the power user who wants to tweak their model and wants absolute control over it. By providing the option to change the model files directly _after_ simon does its magic, the process becomes much more transparent and power users really do have full control over their models while the average user still profits from the aforementioned &quot;magic&quot; that will automatically try to make the best out of the provided user input.

Moreover, this way the simon files don&#039;t have to take HTK bugs / limitations into account (those issues are dealt with during synchronization) and simond has more control over what to give to HTK. Thanks to the new architecture, simon now deals much better with often accuring errors and acually fixes a lot of problems on the fly.

Greetings,
Peter</description>
		<content:encoded><![CDATA[<p>No, sorry.</p>
<p>Basically, with the new architecture you organize your vocabulary, grammar, commands, etc. in scenario packages. During compilation you serialize those scenarios to the input files for the HTK / Julius tools.</p>
<p>Those buttons in sam provide the same serialization features and are basically &#8220;export to HTK/Julius&#8221; buttons. They are not meant to be used as &#8220;export&#8221; features but rather as a way to intervene at a lower level. sam caters to the power user who wants to tweak their model and wants absolute control over it. By providing the option to change the model files directly _after_ simon does its magic, the process becomes much more transparent and power users really do have full control over their models while the average user still profits from the aforementioned &#8220;magic&#8221; that will automatically try to make the best out of the provided user input.</p>
<p>Moreover, this way the simon files don&#8217;t have to take HTK bugs / limitations into account (those issues are dealt with during synchronization) and simond has more control over what to give to HTK. Thanks to the new architecture, simon now deals much better with often accuring errors and acually fixes a lot of problems on the fly.</p>
<p>Greetings,<br />
Peter</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on shadowvocabulary.xml by Peter Grasch</title>
		<link>http://spirit.blau.in/simon/2010/02/03/shadowvocabulary-xml/#comment-268</link>
		<dc:creator>Peter Grasch</dc:creator>
		<pubDate>Wed, 03 Feb 2010 21:06:15 +0000</pubDate>
		<guid isPermaLink="false">http://spirit.blau.in/simon/?p=2468#comment-268</guid>
		<description>Little tip: Use the file command in the future. It uses (transparent) gzip compression. The file is quite big enough at it is.

For performance reasons, you need to match the indentation / structure of the XML if you want to fiddle with it. or simon will not parse it correctly.</description>
		<content:encoded><![CDATA[<p>Little tip: Use the file command in the future. It uses (transparent) gzip compression. The file is quite big enough at it is.</p>
<p>For performance reasons, you need to match the indentation / structure of the XML if you want to fiddle with it. or simon will not parse it correctly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Static model from Voxforge by Peter Grasch</title>
		<link>http://spirit.blau.in/simon/2010/02/03/static-model-from-voxforge/#comment-267</link>
		<dc:creator>Peter Grasch</dc:creator>
		<pubDate>Wed, 03 Feb 2010 21:02:33 +0000</pubDate>
		<guid isPermaLink="false">http://spirit.blau.in/simon/?p=2463#comment-267</guid>
		<description>Hm let me know what happened if you find out.

Thanks!</description>
		<content:encoded><![CDATA[<p>Hm let me know what happened if you find out.</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Static model from Voxforge by producer</title>
		<link>http://spirit.blau.in/simon/2010/02/03/static-model-from-voxforge/#comment-266</link>
		<dc:creator>producer</dc:creator>
		<pubDate>Wed, 03 Feb 2010 16:26:59 +0000</pubDate>
		<guid isPermaLink="false">http://spirit.blau.in/simon/?p=2463#comment-266</guid>
		<description>Interesting: The file &lt;code&gt;/home/am3msi/.kde/share/apps/simon/model/model.dict&lt;/code&gt; consists only of 4 lines:

&lt;blockquote&gt;&lt;code&gt;0	[]	sil
1	[]	sil
2	[DESIGNER]	d ix z ay n er
2	[DESIGNS]	d ix z ay n z&lt;/code&gt;&lt;/blockquote&gt;

And my 200 words German speech model contains exactly these two words (this demonstrates that english pronunciation is possible with &lt;code&gt;Ralf&#039;s German dictionary&lt;/code&gt; when it comes to foreign words like designer).

It seems that &lt;code&gt;model.dict&lt;/code&gt; is the &lt;a href=&quot;http://en.wikipedia.org/wiki/Intersection_%28set_theory%29&quot; rel=&quot;nofollow&quot;&gt;intersection&lt;/a&gt;  of my previous German active vocabulary with 200 German words and the imported English dictionary from Voxforge.

So something went wrong. I don&#039;t know why the intersection happened. But I think that I should completely delete the following folders:

&lt;code&gt;/home/am3msi/.kde/share/apps/simon
/home/am3msi/.kde/share/apps/simond&lt;/code&gt;

After I have done that, I can import the English Voxforge acoustic model again. Or I could try to restore my 200 words German speech model. Or I could start from scratch with my German speech model. I don&#039;t know what I will do next.</description>
		<content:encoded><![CDATA[<p>Interesting: The file <code>/home/am3msi/.kde/share/apps/simon/model/model.dict</code> consists only of 4 lines:</p>
<blockquote><p><code>0	[]	sil<br />
1	[]	sil<br />
2	[DESIGNER]	d ix z ay n er<br />
2	[DESIGNS]	d ix z ay n z</code></p></blockquote>
<p>And my 200 words German speech model contains exactly these two words (this demonstrates that english pronunciation is possible with <code>Ralf's German dictionary</code> when it comes to foreign words like designer).</p>
<p>It seems that <code>model.dict</code> is the <a href="http://en.wikipedia.org/wiki/Intersection_%28set_theory%29" rel="nofollow">intersection</a>  of my previous German active vocabulary with 200 German words and the imported English dictionary from Voxforge.</p>
<p>So something went wrong. I don&#8217;t know why the intersection happened. But I think that I should completely delete the following folders:</p>
<p><code>/home/am3msi/.kde/share/apps/simon<br />
/home/am3msi/.kde/share/apps/simond</code></p>
<p>After I have done that, I can import the English Voxforge acoustic model again. Or I could try to restore my 200 words German speech model. Or I could start from scratch with my German speech model. I don&#8217;t know what I will do next.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Static model from Voxforge by producer</title>
		<link>http://spirit.blau.in/simon/2010/02/03/static-model-from-voxforge/#comment-265</link>
		<dc:creator>producer</dc:creator>
		<pubDate>Wed, 03 Feb 2010 16:06:23 +0000</pubDate>
		<guid isPermaLink="false">http://spirit.blau.in/simon/?p=2463#comment-265</guid>
		<description>I think that I forgot to use the dictation plugin (&lt;code&gt;Commands&lt;/code&gt; &gt; &lt;code&gt;Manage Plug-Ins&lt;/code&gt; &gt; &lt;code&gt;Add&lt;/code&gt; &gt; &lt;code&gt;Dictation&lt;/code&gt;). Now, with the dictation plugin, I get recognition results. It recognizes only DESIGNER and DESIGN, but at least simon recognizes something. That is a start!

It is really good to see that it is possible to use the &lt;a href=&quot;http://www.repository.voxforge1.org/downloads/Nightly_Builds/AcousticModel-2010-02-03/&quot; rel=&quot;nofollow&quot;&gt;Voxforge English acoustic model&lt;/a&gt; with simon.</description>
		<content:encoded><![CDATA[<p>I think that I forgot to use the dictation plugin (<code>Commands</code> &gt; <code>Manage Plug-Ins</code> &gt; <code>Add</code> &gt; <code>Dictation</code>). Now, with the dictation plugin, I get recognition results. It recognizes only DESIGNER and DESIGN, but at least simon recognizes something. That is a start!</p>
<p>It is really good to see that it is possible to use the <a href="http://www.repository.voxforge1.org/downloads/Nightly_Builds/AcousticModel-2010-02-03/" rel="nofollow">Voxforge English acoustic model</a> with simon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Clear button; improve phoneme by Peter Grasch</title>
		<link>http://spirit.blau.in/simon/2010/02/03/clear-button-improve-phoneme/#comment-264</link>
		<dc:creator>Peter Grasch</dc:creator>
		<pubDate>Wed, 03 Feb 2010 12:52:05 +0000</pubDate>
		<guid isPermaLink="false">http://spirit.blau.in/simon/?p=2436#comment-264</guid>
		<description>Oh and by the way you might enjoy the pronunciation training plugin. It&#039;s great to test the recognition rate &quot;live&quot;.

Greetings,
Peter</description>
		<content:encoded><![CDATA[<p>Oh and by the way you might enjoy the pronunciation training plugin. It&#8217;s great to test the recognition rate &#8220;live&#8221;.</p>
<p>Greetings,<br />
Peter</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Clear button; improve phoneme by Peter Grasch</title>
		<link>http://spirit.blau.in/simon/2010/02/03/clear-button-improve-phoneme/#comment-263</link>
		<dc:creator>Peter Grasch</dc:creator>
		<pubDate>Wed, 03 Feb 2010 12:29:21 +0000</pubDate>
		<guid isPermaLink="false">http://spirit.blau.in/simon/?p=2436#comment-263</guid>
		<description>We have an export scenario button (Manage scenarios) which contains the dictionary.

Greetings,
Peter</description>
		<content:encoded><![CDATA[<p>We have an export scenario button (Manage scenarios) which contains the dictionary.</p>
<p>Greetings,<br />
Peter</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on git pull origin master by Peter Grasch</title>
		<link>http://spirit.blau.in/simon/2010/02/02/git-pull-origin-master/#comment-262</link>
		<dc:creator>Peter Grasch</dc:creator>
		<pubDate>Tue, 02 Feb 2010 22:11:23 +0000</pubDate>
		<guid isPermaLink="false">http://spirit.blau.in/simon/?p=2430#comment-262</guid>
		<description>Hi!

Sorry &#039;bout that, I pushed the fix to the master repository.

As you did see the entry in the voxforge forum you know that there seems to be an issue with the adaption process but you are very welcome to try it...

Sam is working again in this revision (I fixed it today).

The current version also god a desperately needed &quot;Clear&quot; button in the vocabulary menu so you can remove all words from your active / shadow vocabulary with one click (and two confirmation dialogs of course).

All in all you will see mostly fixes for the next two weeks (one major feature pending).

Greetings,
Peter</description>
		<content:encoded><![CDATA[<p>Hi!</p>
<p>Sorry &#8217;bout that, I pushed the fix to the master repository.</p>
<p>As you did see the entry in the voxforge forum you know that there seems to be an issue with the adaption process but you are very welcome to try it&#8230;</p>
<p>Sam is working again in this revision (I fixed it today).</p>
<p>The current version also god a desperately needed &#8220;Clear&#8221; button in the vocabulary menu so you can remove all words from your active / shadow vocabulary with one click (and two confirmation dialogs of course).</p>
<p>All in all you will see mostly fixes for the next two weeks (one major feature pending).</p>
<p>Greetings,<br />
Peter</p>
]]></content:encoded>
	</item>
</channel>
</rss>
