[Olympus developers 136]: Re: Problem regarding Olympus

Mon Aug 3 19:41:40 EDT 2009

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