[Olympus developers 144]: Re: Problem regarding Olympus

Mon Aug 17 01:53:40 EDT 2009

Hi Ben

Thanks for your response. I resolved that problem. In fact, Vista prevented
my login account to access some system files. After I ran it with admin
privilege, the problem was disappeared. Now, I'm studying your code to
understand how you implemented the system. Once again thanks for your kind
helping.

Tran Anh Dung

From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
Frisch
Sent: Monday, 17 August, 2009 1:31 PM
To: Tran
Cc: olympus-developers at loganberry.srv.cs.cmu.edu
Subject: Re: [Olympus developers 138]: Re: Problem regarding Olympus

Hi Tran,

  Sorry for the delay in getting back to you.  I have been away for the past
week days, with sporadic 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 "Unable to create SAPI SpAudioPlug instance.", but
I 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 "C:\Program Files\Microsoft
SDKs\Windows\v6.1\Samples\winui\Speech\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.  

  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.

Thanks,

Ben Frisch

On Thu, Aug 13, 2009 at 11:35 PM, Tran <tanhdung at i2r.a-star.edu.sg> wrote:

Hi Ben,

I managed to compile simpleaudio successfully. I forgot to run the SDK
Configuration Tool. That's why the issue happened.

However, when I run the MeetingLine or tutorial 1, the Kalliope crashed.
Here is the log of Kalliope I found on the GUI

KALLIOPE 2.0. Compiled on Aug 11 2009, at 15:09:35.

[GXI at 11:32:56.441] _GalSS_init_server called.
[GXI at 11:32:56.441] Reading configuration file KalliopeSAPI.cfg
[STD at 11:32:56.441 (9447345)] required_voice_attributes = Age=Adult
[STD at 11:32:56.441 (9447345)] optional_voice_attributes = Gender=Male
[STD at 11:32:56.441 (9447345)] speech_rate = 0
[STD at 11:32:56.441 (9447345)] volume = 100
[STD at 11:32:56.441 (9447345)] audio_format = 22
[STD at 11:32:56.441 (9447345)] log = true
[STD at 11:32:56.441 (9447345)] log_audio = false
[ERR at 11:32:56.847 (9447751)] Unable to create SAPI SpAudioPlug instance.
======================================

-----Original Message-----
From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
Frisch

Sent: Wednesday, 12 August, 2009 2:17 PM
To: Tran
Cc: olympus-developers at loganberry.srv.cs.cmu.edu

Subject: Re: [Olympus developers 138]: Re: Problem regarding Olympus

Hi Tran,

  So I encountered the reference to the non-existent
DMCore/Events/PhoenixInput.h on my computer.  You can fix it by
removing #include "DMCore/Events/PhoenixInput.h" on line 67 of
Libraries/RavenClaw/DMCore/Agents/CoreAgents/InteractionEventManagerAgent.cp
p.
It was replaced by DMCore/Events/GalaxyInteractionEvent.h, and I guess
it was not automatically rebuilt after the deletion. (PhoenixInput.h
was removed as part of the fix for
http://trac.speech.cs.cmu.edu/olympus/ticket/52 .)  I apologize for
the inconvenience.  I'll try to get that fix committed by tomorrow.
 The other errors in building Olympus look exactly like
http://trac.speech.cs.cmu.edu/olympus/ticket/87 , which was fixed by
upgrading to Visual Studio 2005 SP1.  Send me your build.log if the
build is still not successful, and if there is an unexpected fatal
error, hang, or crash with the trunk, please send me the log file that
corresponds to the agent with the problem.  I'll do my best to try to
fix or help fix what is wrong.

Thanks,
Ben

On 8/11/09, Tran <tanhdung at i2r.a-star.edu.sg> wrote:
> Hi Ben,
>
> The attached is the build log. The line 114 is the first error, which
causes
> subsequent errors.
>
> Thanks,
> Tran Anh Dung
>
> -----Original Message-----
> From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
> Frisch
> Sent: Wednesday, 12 August, 2009 2:41 AM
> To: Tran; olympus-developers at loganberry.srv.cs.cmu.edu
> Subject: [Olympus developers 133]: Problem regarding Olympus
>
> Hi,
>   Can you send me your build.log, and I'll take a look.
>
> Thanks,
> Ben
>
> On Tue, Aug 11, 2009 at 3:59 AM, Tran <tanhdung at i2r.a-star.edu.sg> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi Ben,
>
>
>
> Sorry for the late reply. I was in the ACL conference last week.
>
>
>
> Thanks for your informative email. As the problem in Vista, I
> recompiled the Olympus on Windows XP. The tutorial 1 & 2 are working fine.
> Thanks for your great effort. There is only a minor issue about speech
> recognition due to my accent. But I guess it should be improve if I
provide
> more training data.
>
>
>
> On Windows Vista, I downloaded the trunk source code to compile.
> But it seems not to work. There were error while compiling as in attached
> image. I did some preliminary checking and found that some files are
missing
> such as
>
Libraries\RavenClaw\DMCore\Agents\CoreAgents\InteractionEventManagerAgent.cp
> p.
> This file causes error while compiling RavenClaw. I don't know what is the
> exact reason, but I think you are still doing on those source code and it
> might
> cause the problem.
>
>
>
> Once again, thanks for your help.
>
>
>
> Tran Anh Dung
>
>
>
>
>
> From: bfrisch at gmail.com
> [mailto:bfrisch at gmail.com] On Behalf Of Benjamin Frisch
> Sent: Tuesday, 4 August, 2009 7:42 AM
> To: Tran
> Cc: Olympus Developers
> Subject: Re: [Olympus developers 133]: Problem regarding Olympus
>
>
>
>
>
> Hi Tran,
>   Kalliope is configured in Configurations/Desktop-SAPI/KalliopeSAPI.cfg
> inside of your example system directory to use the first adult male voice
it
> finds.  You could change the male to female in that configuration file,
> and it will use the first female voice it finds, which will probably be
Anna
> in
> your case.  This will probably cause Kalliope to synthesize correctly, as
> if the SAPI example run time application runs into an error with the male
> voices, then Kalliope would as well.  I'm not sure why the voices seem to
> be corrupted, but it could be a problem with the SAPI 5.1 SDK, which was
> originally made for Windows xp, running on Windows Vista.  The current
> Olympus trunk will detect the installation of the Windows SDK 6.1 "for
> Windows Server 2008" which includes the SAPI 5.3 SDK.  I am also
> sorry to hear that PocketSphinxEngine is crashing.  The PocketSphinxEngine
> in the Olympus trunk was largely rewritten to support PocketSphinx 0.5.
>   In light of the PocketSphinxEngine and Kalliope issues, and your use of
> Windows Vista, I'd recommend that you try to use the Olympus trunk.  We
> are probably a couple of weeks away from an Olympus 2.5 release from the
> Olympus trunk.  As such the trunk is generally stable now.  You can
> download the Windows SDK for Windows Server 2008, which includes SAPI
> 5.3 from
>
http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-
> 9BE5-FA919850BDBF
> .  You will also need to install CMake via the Win32 Installer from
> http://cmake.org/cmake/resources/software.html
> .  The build scripts currently cause CMake to generate the Visual Studio
> solution files in the Build/cmake directory off of the Olympus Root and
off
> the
> root of the MeetingLine and soon to be added Madeline example system.
>    Let me know if KalliopeSAPI ends up working with SAPI 5.3
> SDK.  If it still doesn't work (but doesn't crash), then I recommend that
> you use the new KalliopeFlite support in the Olympus trunk instead, which
> you
> can use by running OlympusRebuildFlite.pl in your Olympus trunk root and
> then
> running SystemRunFlite.bat rather SystemRun.bat.  While I haven't recently
> encountered a crash while running one of our systems for a while with the
> trunk, if anything crashes for you or is not working, let me know so I can
> do
> my best to fix it before the release.
>    Thank you for sending in your changes to the grammar generation
> scripts in the Tutorials.  I committed your changes, and I am sorry for
> the trouble.
>
> Thanks,
> Ben Frisch
> CMU Speech Lab Undergraduate Research Assistant for Summer 2009
>
>
>
> On Thu, Jul 30, 2009 at 11:53 PM, Tran <tanhdung at i2r.a-star.edu.sg>
> wrote:
>
>
>
>
>
> Hi Benjamin,
>
>
>
> I managed to run the TTY
> version of MyBus successfully. It was very good. However, for the SAPI
> version,
> there was error. When I init_session, the console output "Welcome to
> MyBus", but there is no voice from the system. I guess it is because of
> the Kalliope has some problems with speech synthesis. After sometimes,
> PocketSphinx crashes. I don't know what is the cause. I ran an example of
> Microsoft Speech. It can talk with Anna voice, but Mary and Mike voice has
> error. Could that be a problem with the voice configuration in Kalliope?
> Please
> help me on this. Thanks
>
>
>
> I also found that, the source
> code on SVN cannot compile correctly if you don't make some changes in
> the perl script. I attach a change log file for your reference. It is nice
> if
> you make these changes on the source to minimize the effort of other
> developers.
>
>
>
>
>
> Regards,
>
> Tran Anh Dung
>
> Research Officer
>
> Human Language Technology Department
>
> A*, Singapore
>
>
>
>
>
>
>
>
>
> From: bfrisch at gmail.com [mailto:bfrisch at gmail.com] On Behalf Of Benjamin
> Frisch
>
>
>
>
>
> Sent: Thursday, 30 July, 2009 9:44 AM
> To: Tran
> Cc: Alex Rudnicky
>
>
>
> Subject: Re: [Olympus developers 133]: Problem
> regarding Olympus
>
>
>
>
>
>
>
>
>
> Hi Tran,
>
>
>
>   At least from picture, it looks like you forgot to start the
> session first.  Just enter init_session and MyBus should start.
>  Let's us know if you have further questions.
>
>
>
>
>
>
>
>
>
>
>
> Thanks,
>
>
>
>
>
> Ben
>
>
>
> On Wed, Jul 29, 2009 at 9:40 PM, Tran <tanhdung at i2r.a-star.edu.sg>
> wrote:
>
>
>
>
>
> I forget to attached in previous email.
>
>
>
>
>
>
>
> From: Alex Rudnicky [mailto:Alex.Rudnicky at cs.cmu.edu]
>
> Sent: Thursday, 30 July, 2009 9:26 AM
> To: Tran; olympus-developers at cs.cmu.edu
> Cc: Benjamin Frisch
> Subject: RE: [Olympus developers 133]: Problem regarding Olympus
>
>
>
>
>
>
>
>
>
>
>
> These systems are pedagogical and
> follow the tutorial material.
>
> Have you tried to compile and use one
> of the example systems, such as MeetingLine?
>
>
>
>  - Alex Rudnicky
>
>
>
>
>
>
>
>
>
> From: olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu
> [mailto:olympus-developers-bounces at LOGANBERRY.srv.cs.cmu.edu] On
> Behalf Of Tran
> Sent: Wednesday, July 29, 2009 9:18 PM
> To: olympus-developers at cs.cmu.edu
> Subject: [Olympus developers 133]: Problem regarding Olympus
>
>
>
>
>
>
>
> To whom it may concerns,
>
>
>
> We are doing research on Dialogue Management System. We found that Olympus
> is an interesting system. We downloaded and manage to compile the source
> code
> and tutorial 1/2 successfully. However, when we run it, there seems to be
> nothing happens (no interaction from system, no response while we
talking).
> We
> do not know how to operate it. Hence, could you be able to help us to
> instruct
> how to use the system? We look forward to hear from you
>
>
>
> Regards,
>
> Tran Anh Dung
>
> Research Officer
>
> Human Language Technology Department
>
> A*, Singapore
>
>
>
> PS: all the source code is downloaded as instructed on the Olympus wiki
> page. The downloaded version is 2.2 (not the development version)
>
>
>
> 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."
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> 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."
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> 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."
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> 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."
>
> 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."
>

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."

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."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/olympus-developers/attachments/20090817/4d152cb7/attachment-0001.html