Hi Tran,<div> Sorry for the delay in getting back to you. I have been away for the past week days, with <span class="Apple-style-span" style="font-family: Arial; font-size: 13px; border-collapse: collapse; white-space: pre; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; ">sporadic <span class="Apple-style-span" style="border-collapse: separate; font-family: arial; font-size: small; white-space: normal; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; ">e-mail access. I guess Visual Studio 2008's default SDK already had the proper definition's. I'll make sure to document that you need to run the SDK configuration tool with Visual Studio 2005. I'm not sure why you are "<span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse;color:rgb(34, 34, 34)">Unable to create SAPI SpAudioPlug instance.", but I </span><span style="border-collapse:collapse;color:rgb(34, 34, 34)"><font face="arial, helvetica, sans-serif">think it is because the SAPI Audio DLL is not registered with Windows. (It should be registered by the Visual Studio project, but security restrictions on Vista might lead to the registration not working.) Try executing regsvr32 </font></span><span style="border-collapse:collapse;color:rgb(34, 34, 34)"><font face="arial, helvetica, sans-serif">"</font><span style="border-collapse:separate;color:rgb(0, 0, 0);white-space:pre-wrap"><font face="arial, helvetica, sans-serif">C:\Program Files\Microsoft SDKs\Windows\v6.1\Samples\winui\Speech\</font><span style="white-space:normal;border-collapse:collapse;color:rgb(34, 34, 34)"><font face="arial, helvetica, sans-serif">SimpleAudio\Release\SimpleAudio.dll" in a command prompt that you launch with Administrator permissions, and then rerun KalliopeSAPI. If KalliopeSAPI still doesn't work, I recommend that you use Flite instead of SAPi by first running OlympusRebuildFlite.pl (you have to run the rebuild script to clear CMake's build configuration cache when switching between synthesizer APIs), and once that completes successfully, run SystemRunFlite.bat rather than SystemRun.bat in the system directories. </font></span></span></span></span></span></div>
<div><span class="Apple-style-span" style="font-family: Arial; font-size: 13px; border-collapse: collapse; white-space: pre; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; "><span class="Apple-style-span" style="border-collapse: separate; font-family: arial; font-size: small; white-space: normal; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; "><span style="border-collapse:collapse;color:rgb(34, 34, 34)"><span style="border-collapse:separate;color:rgb(0, 0, 0);white-space:pre-wrap"><span style="white-space:normal;border-collapse:collapse;color:rgb(34, 34, 34)"><font face="arial, helvetica, sans-serif"> If you are unhappy with Flite as your synthesizer, you can try changing optional_voice_attributes = Gender=Male to optional_voice_attributes = Gender=Female in KalliopeSAPI.cfg in Configurations/Desktop in all example systems and tutorials except for RoomLine where the configuration file is in Configurations/Desktop-FakeDB and then, run OlympusRebuild.pl in Olympus, and then run a system using KalliopeSAPI via the normal SystemRun.bat script like before. With the previous configuration changes you should end up using Microsoft Anna, which shouldn't have synthesis problems for you with KalliopeSAPI. Let me know how it goes.</font></span></span></span></span></span></div>
<div><font class="Apple-style-span" color="#222222" face="arial, helvetica, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse; "><br></span></font></div><div><span style="border-collapse:collapse;color:rgb(34, 34, 34)"><span style="border-collapse:separate;color:rgb(0, 0, 0);white-space:pre-wrap"><span style="white-space:normal;border-collapse:collapse;color:rgb(34, 34, 34)"><font face="arial, helvetica, sans-serif">Thanks,</font></span></span></span></div>
<div><span style="border-collapse:collapse;color:rgb(34, 34, 34)"><span style="border-collapse:separate;color:rgb(0, 0, 0);white-space:pre-wrap"><span style="white-space:normal;border-collapse:collapse;color:rgb(34, 34, 34)"><font face="arial, helvetica, sans-serif">Ben Frisch</font></span></span></span></div>
<div><br><div class="gmail_quote">On Thu, Aug 13, 2009 at 11:35 PM, Tran <span dir="ltr"><<a href="mailto:tanhdung@i2r.a-star.edu.sg" target="_blank">tanhdung@i2r.a-star.edu.sg</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Ben,<br>
<br>
I managed to compile simpleaudio successfully. I forgot to run the SDK<br>
Configuration Tool. That's why the issue happened.<br>
<br>
However, when I run the MeetingLine or tutorial 1, the Kalliope crashed.<br>
Here is the log of Kalliope I found on the GUI<br>
<br>
KALLIOPE 2.0. Compiled on Aug 11 2009, at 15:09:35.<br>
<br>
[GXI@11:32:56.441] _GalSS_init_server called.<br>
[GXI@11:32:56.441] Reading configuration file KalliopeSAPI.cfg<br>
[STD@11:32:56.441 (9447345)] required_voice_attributes = Age=Adult<br>
[STD@11:32:56.441 (9447345)] optional_voice_attributes = Gender=Male<br>
[STD@11:32:56.441 (9447345)] speech_rate = 0<br>
[STD@11:32:56.441 (9447345)] volume = 100<br>
[STD@11:32:56.441 (9447345)] audio_format = 22<br>
[STD@11:32:56.441 (9447345)] log = true<br>
[STD@11:32:56.441 (9447345)] log_audio = false<br>
[ERR@11:32:56.847 (9447751)] Unable to create SAPI SpAudioPlug instance.<br>
======================================<br>
<div><br>
-----Original Message-----<br>
From: <a href="mailto:bfrisch@gmail.com" target="_blank">bfrisch@gmail.com</a> [mailto:<a href="mailto:bfrisch@gmail.com" target="_blank">bfrisch@gmail.com</a>] On Behalf Of Benjamin<br>
Frisch<br>
</div><div>Sent: Wednesday, 12 August, 2009 2:17 PM<br>
To: Tran<br>
Cc: <a href="mailto:olympus-developers@loganberry.srv.cs.cmu.edu" target="_blank">olympus-developers@loganberry.srv.cs.cmu.edu</a><br>
</div><div>Subject: Re: [Olympus developers 138]: Re: Problem regarding Olympus<br>
<br>
Hi Tran,<br>
</div><div><div></div><div> So I encountered the reference to the non-existent<br>
DMCore/Events/PhoenixInput.h on my computer. You can fix it by<br>
removing #include "DMCore/Events/PhoenixInput.h" on line 67 of<br>
Libraries/RavenClaw/DMCore/Agents/CoreAgents/InteractionEventManagerAgent.cp<br>
p.<br>
It was replaced by DMCore/Events/GalaxyInteractionEvent.h, and I guess<br>
it was not automatically rebuilt after the deletion. (PhoenixInput.h<br>
was removed as part of the fix for<br>
<a href="http://trac.speech.cs.cmu.edu/olympus/ticket/52" target="_blank">http://trac.speech.cs.cmu.edu/olympus/ticket/52</a> .) I apologize for<br>
the inconvenience. I'll try to get that fix committed by tomorrow.<br>
The other errors in building Olympus look exactly like<br>
<a href="http://trac.speech.cs.cmu.edu/olympus/ticket/87" target="_blank">http://trac.speech.cs.cmu.edu/olympus/ticket/87</a> , which was fixed by<br>
upgrading to Visual Studio 2005 SP1. Send me your build.log if the<br>
build is still not successful, and if there is an unexpected fatal<br>
error, hang, or crash with the trunk, please send me the log file that<br>
corresponds to the agent with the problem. I'll do my best to try to<br>
fix or help fix what is wrong.<br>
<br>
Thanks,<br>
Ben<br>
<br>
On 8/11/09, Tran <<a href="mailto:tanhdung@i2r.a-star.edu.sg" target="_blank">tanhdung@i2r.a-star.edu.sg</a>> wrote:<br>
> Hi Ben,<br>
><br>
> The attached is the build log. The line 114 is the first error, which<br>
causes<br>
> subsequent errors.<br>
><br>
> Thanks,<br>
> Tran Anh Dung<br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:bfrisch@gmail.com" target="_blank">bfrisch@gmail.com</a> [mailto:<a href="mailto:bfrisch@gmail.com" target="_blank">bfrisch@gmail.com</a>] On Behalf Of Benjamin<br>
> Frisch<br>
> Sent: Wednesday, 12 August, 2009 2:41 AM<br>
> To: Tran; <a href="mailto:olympus-developers@loganberry.srv.cs.cmu.edu" target="_blank">olympus-developers@loganberry.srv.cs.cmu.edu</a><br>
> Subject: [Olympus developers 133]: Problem regarding Olympus<br>
><br>
> Hi,<br>
> Can you send me your build.log, and I'll take a look.<br>
><br>
> Thanks,<br>
> Ben<br>
><br>
> On Tue, Aug 11, 2009 at 3:59 AM, Tran <<a href="mailto:tanhdung@i2r.a-star.edu.sg" target="_blank">tanhdung@i2r.a-star.edu.sg</a>> wrote:<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> Hi Ben,<br>
><br>
><br>
><br>
> Sorry for the late reply. I was in the ACL conference last week.<br>
><br>
><br>
><br>
> Thanks for your informative email. As the problem in Vista, I<br>
> recompiled the Olympus on Windows XP. The tutorial 1 & 2 are working fine.<br>
> Thanks for your great effort. There is only a minor issue about speech<br>
> recognition due to my accent. But I guess it should be improve if I<br>
provide<br>
> more training data.<br>
><br>
><br>
><br>
> On Windows Vista, I downloaded the trunk source code to compile.<br>
> But it seems not to work. There were error while compiling as in attached<br>
> image. I did some preliminary checking and found that some files are<br>
missing<br>
> such as<br>
><br>
Libraries\RavenClaw\DMCore\Agents\CoreAgents\InteractionEventManagerAgent.cp<br>
> p.<br>
> This file causes error while compiling RavenClaw. I don’t know what is the<br>
> exact reason, but I think you are still doing on those source code and it<br>
> might<br>
> cause the problem.<br>
><br>
><br>
><br>
> Once again, thanks for your help.<br>
><br>
><br>
><br>
> Tran Anh Dung<br>
><br>
><br>
><br>
><br>
><br>
> From: <a href="mailto:bfrisch@gmail.com" target="_blank">bfrisch@gmail.com</a><br>
> [mailto:<a href="mailto:bfrisch@gmail.com" target="_blank">bfrisch@gmail.com</a>] On Behalf Of Benjamin Frisch<br>
> Sent: Tuesday, 4 August, 2009 7:42 AM<br>
> To: Tran<br>
> Cc: Olympus Developers<br>
> Subject: Re: [Olympus developers 133]: Problem regarding Olympus<br>
><br>
><br>
><br>
><br>
><br>
> Hi Tran,<br>
> Kalliope is configured in Configurations/Desktop-SAPI/KalliopeSAPI.cfg<br>
> inside of your example system directory to use the first adult male voice<br>
it<br>
> finds. You could change the male to female in that configuration file,<br>
> and it will use the first female voice it finds, which will probably be<br>
Anna<br>
> in<br>
> your case. This will probably cause Kalliope to synthesize correctly, as<br>
> if the SAPI example run time application runs into an error with the male<br>
> voices, then Kalliope would as well. I'm not sure why the voices seem to<br>
> be corrupted, but it could be a problem with the SAPI 5.1 SDK, which was<br>
> originally made for Windows xp, running on Windows Vista. The current<br>
> Olympus trunk will detect the installation of the Windows SDK 6.1 "for<br>
> Windows Server 2008" which includes the SAPI 5.3 SDK. I am also<br>
> sorry to hear that PocketSphinxEngine is crashing. The PocketSphinxEngine<br>
> in the Olympus trunk was largely rewritten to support PocketSphinx 0.5.<br>
> In light of the PocketSphinxEngine and Kalliope issues, and your use of<br>
> Windows Vista, I'd recommend that you try to use the Olympus trunk. We<br>
> are probably a couple of weeks away from an Olympus 2.5 release from the<br>
> Olympus trunk. As such the trunk is generally stable now. You can<br>
> download the Windows SDK for Windows Server 2008, which includes SAPI<br>
> 5.3 from<br>
><br>
<a href="http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-" target="_blank">http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-</a><br>
> 9BE5-FA919850BDBF<br>
> . You will also need to install CMake via the Win32 Installer from<br>
> <a href="http://cmake.org/cmake/resources/software.html" target="_blank">http://cmake.org/cmake/resources/software.html</a><br>
> . The build scripts currently cause CMake to generate the Visual Studio<br>
> solution files in the Build/cmake directory off of the Olympus Root and<br>
off<br>
> the<br>
> root of the MeetingLine and soon to be added Madeline example system.<br>
> Let me know if KalliopeSAPI ends up working with SAPI 5.3<br>
> SDK. If it still doesn't work (but doesn't crash), then I recommend that<br>
> you use the new KalliopeFlite support in the Olympus trunk instead, which<br>
> you<br>
> can use by running OlympusRebuildFlite.pl in your Olympus trunk root and<br>
> then<br>
> running SystemRunFlite.bat rather SystemRun.bat. While I haven't recently<br>
> encountered a crash while running one of our systems for a while with the<br>
> trunk, if anything crashes for you or is not working, let me know so I can<br>
> do<br>
> my best to fix it before the release.<br>
> Thank you for sending in your changes to the grammar generation<br>
> scripts in the Tutorials. I committed your changes, and I am sorry for<br>
> the trouble.<br>
><br>
> Thanks,<br>
> Ben Frisch<br>
> CMU Speech Lab Undergraduate Research Assistant for Summer 2009<br>
><br>
><br>
><br>
> On Thu, Jul 30, 2009 at 11:53 PM, Tran <<a href="mailto:tanhdung@i2r.a-star.edu.sg" target="_blank">tanhdung@i2r.a-star.edu.sg</a>><br>
> wrote:<br>
><br>
><br>
><br>
><br>
><br>
> Hi Benjamin,<br>
><br>
><br>
><br>
> I managed to run the TTY<br>
> version of MyBus successfully. It was very good. However, for the SAPI<br>
> version,<br>
> there was error. When I init_session, the console output “Welcome to<br>
> MyBus”, but there is no voice from the system. I guess it is because of<br>
> the Kalliope has some problems with speech synthesis. After sometimes,<br>
> PocketSphinx crashes. I don’t know what is the cause. I ran an example of<br>
> Microsoft Speech. It can talk with Anna voice, but Mary and Mike voice has<br>
> error. Could that be a problem with the voice configuration in Kalliope?<br>
> Please<br>
> help me on this. Thanks<br>
><br>
><br>
><br>
> I also found that, the source<br>
> code on SVN cannot compile correctly if you don’t make some changes in<br>
> the perl script. I attach a change log file for your reference. It is nice<br>
> if<br>
> you make these changes on the source to minimize the effort of other<br>
> developers.<br>
><br>
><br>
><br>
><br>
><br>
> Regards,<br>
><br>
> Tran Anh Dung<br>
><br>
> Research Officer<br>
><br>
> Human Language Technology Department<br>
><br>
> A*, Singapore<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> From: <a href="mailto:bfrisch@gmail.com" target="_blank">bfrisch@gmail.com</a> [mailto:<a href="mailto:bfrisch@gmail.com" target="_blank">bfrisch@gmail.com</a>] On Behalf Of Benjamin<br>
> Frisch<br>
><br>
><br>
><br>
><br>
><br>
> Sent: Thursday, 30 July, 2009 9:44 AM<br>
> To: Tran<br>
> Cc: Alex Rudnicky<br>
><br>
><br>
><br>
> Subject: Re: [Olympus developers 133]: Problem<br>
> regarding Olympus<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> Hi Tran,<br>
><br>
><br>
><br>
> At least from picture, it looks like you forgot to start the<br>
> session first. Just enter init_session and MyBus should start.<br>
> Let's us know if you have further questions.<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> Thanks,<br>
><br>
><br>
><br>
><br>
><br>
> Ben<br>
><br>
><br>
><br>
> On Wed, Jul 29, 2009 at 9:40 PM, Tran <<a href="mailto:tanhdung@i2r.a-star.edu.sg" target="_blank">tanhdung@i2r.a-star.edu.sg</a>><br>
> wrote:<br>
><br>
><br>
><br>
><br>
><br>
> I forget to attached in previous email.<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> From: Alex Rudnicky [mailto:<a href="mailto:Alex.Rudnicky@cs.cmu.edu" target="_blank">Alex.Rudnicky@cs.cmu.edu</a>]<br>
><br>
> Sent: Thursday, 30 July, 2009 9:26 AM<br>
> To: Tran; <a href="mailto:olympus-developers@cs.cmu.edu" target="_blank">olympus-developers@cs.cmu.edu</a><br>
> Cc: Benjamin Frisch<br>
> Subject: RE: [Olympus developers 133]: Problem regarding Olympus<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> These systems are pedagogical and<br>
> follow the tutorial material.<br>
><br>
> Have you tried to compile and use one<br>
> of the example systems, such as MeetingLine?<br>
><br>
><br>
><br>
> - Alex Rudnicky<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> From: <a href="mailto:olympus-developers-bounces@LOGANBERRY.srv.cs.cmu.edu" target="_blank">olympus-developers-bounces@LOGANBERRY.srv.cs.cmu.edu</a><br>
> [mailto:<a href="mailto:olympus-developers-bounces@LOGANBERRY.srv.cs.cmu.edu" target="_blank">olympus-developers-bounces@LOGANBERRY.srv.cs.cmu.edu</a>] On<br>
> Behalf Of Tran<br>
> Sent: Wednesday, July 29, 2009 9:18 PM<br>
> To: <a href="mailto:olympus-developers@cs.cmu.edu" target="_blank">olympus-developers@cs.cmu.edu</a><br>
> Subject: [Olympus developers 133]: Problem regarding Olympus<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> To whom it may concerns,<br>
><br>
><br>
><br>
> We are doing research on Dialogue Management System. We found that Olympus<br>
> is an interesting system. We downloaded and manage to compile the source<br>
> code<br>
> and tutorial 1/2 successfully. However, when we run it, there seems to be<br>
> nothing happens (no interaction from system, no response while we<br>
talking).<br>
> We<br>
> do not know how to operate it. Hence, could you be able to help us to<br>
> instruct<br>
> how to use the system? We look forward to hear from you<br>
><br>
><br>
><br>
> Regards,<br>
><br>
> Tran Anh Dung<br>
><br>
> Research Officer<br>
><br>
> Human Language Technology Department<br>
><br>
> A*, Singapore<br>
><br>
><br>
><br>
> PS: all the source code is downloaded as instructed on the Olympus wiki<br>
> page. The downloaded version is 2.2 (not the development version)<br>
><br>
><br>
><br>
> Institute for Infocomm Research disclaimer: "This email is confidential<br>
> and may be privileged. If you are not the intended recipient, please<br>
delete<br>
> it<br>
> and notify us immediately. Please do not copy or use it for any purpose,<br>
or<br>
> disclose its contents to any other person. Thank you."<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> Institute for Infocomm Research disclaimer: "This email is confidential<br>
> and may be privileged. If you are not the intended recipient, please<br>
delete<br>
> it<br>
> and notify us immediately. Please do not copy or use it for any purpose,<br>
or<br>
> disclose its contents to any other person. Thank you."<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> Institute for Infocomm Research disclaimer: "This email<br>
> is confidential and may be privileged. If you are not the intended<br>
> recipient,<br>
> please delete it and notify us immediately. Please do not copy or use it<br>
for<br>
> any purpose, or disclose its contents to any other person. Thank you."<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> Institute for Infocomm Research disclaimer: "This email is<br>
> confidential and may be privileged. If you are not the intended<br>
> recipient, please delete it and notify us immediately. Please do not<br>
> copy or use it for any purpose, or disclose its contents to any other<br>
> person. Thank you."<br>
><br>
> Institute for Infocomm Research disclaimer: "This email is confidential<br>
and<br>
> may be privileged. If you are not the intended recipient, please delete it<br>
> and notify us immediately. Please do not copy or use it for any purpose,<br>
or<br>
> disclose its contents to any other person. Thank you."<br>
><br>
<br>
Institute for Infocomm Research disclaimer: "This email is confidential and may be privileged. If you are not the intended recipient, please delete it and notify us immediately. Please do not copy or use it for any purpose, or disclose its contents to any other person. Thank you."<br>
</div></div></blockquote></div><br></div>