From mrmarge at cs.cmu.edu Wed Jun 8 11:11:01 2011 From: mrmarge at cs.cmu.edu (Matthew Marge) Date: Wed, 8 Jun 2011 11:11:01 -0400 Subject: [Olympus developers 301]: Sorry for the spam Message-ID: Hi All, I apologize for some of you that received several messages today, I had to clear out some of the pending emails held back by the server. For those of you that are new to the olympus developers list, welcome! I am an administrator now, welcome to the list. We hope that you can contribute to topics that may come up with people using Olympus. Cheers, Matthew Marge From gparent+ at cs.cmu.edu Fri Jun 17 17:02:26 2011 From: gparent+ at cs.cmu.edu (Gabriel Parent) Date: Fri, 17 Jun 2011 17:02:26 -0400 Subject: [Olympus developers 302]: raw file vs wav file, is there a good reason? Message-ID: <4DFBC0E2.7050409@cs.cmu.edu> All, what was the initial reason for writing the utterance and system audio file as raw file versus wav file. Is the main reason to save disk space? Gabriel From Alex.Rudnicky at cs.cmu.edu Sat Jun 18 12:41:00 2011 From: Alex.Rudnicky at cs.cmu.edu (Alex Rudnicky) Date: Sat, 18 Jun 2011 12:41:00 -0400 Subject: [Olympus developers 303]: Re: raw file vs wav file, is there a good reason? In-Reply-To: <4DFBC0E2.7050409@cs.cmu.edu> References: <4DFBC0E2.7050409@cs.cmu.edu> Message-ID: <9C0D1A9F38D23E4290347EE31C22B0AF042E775C@e2k3.srv.cs.cmu.edu> The reasons were not very good ones: 1) at the time everything we were doing in interactive systems was 8kHz, so this was "understood" to be the format. (Or, you just "knew" what your data were.) 2) there was no really universally-accepted file format in ASR (except maybe for .sph). 3) to do it correctly, at the end of the recording you needed to fseek to the top of the file and put in the right numbers in the header (ie length). This was thought to impact speed (maybe a dubious proposition). 4) various other resource-constraint related reasons, none of which I believe are still operative. The right thing to do at this time would be to write a standard RIFF header (.wav). This would make the files readers by pretty much all tools out there; also, the format is flexible enough so that specialized information can easily be included in a data block without breaking anything. Alex -----Original Message----- From: olympus-developers-bounces at mailman.srv.cs.cmu.edu [mailto:olympus-developers-bounces at mailman.srv.cs.cmu.edu] On Behalf Of Gabriel Parent Sent: Friday, June 17, 2011 5:02 PM To: olympus-developers at mailman.srv.cs.cmu.edu Subject: [Olympus developers 302]: raw file vs wav file,is there a good reason? All, what was the initial reason for writing the utterance and system audio file as raw file versus wav file. Is the main reason to save disk space? Gabriel From gparent+ at cs.cmu.edu Sat Jun 18 17:31:53 2011 From: gparent+ at cs.cmu.edu (Gabriel Parent) Date: Sat, 18 Jun 2011 17:31:53 -0400 Subject: [Olympus developers 304]: Re: raw file vs wav file, is there a good reason? In-Reply-To: <9C0D1A9F38D23E4290347EE31C22B0AF042E775C@e2k3.srv.cs.cmu.edu> References: <4DFBC0E2.7050409@cs.cmu.edu> <9C0D1A9F38D23E4290347EE31C22B0AF042E775C@e2k3.srv.cs.cmu.edu> Message-ID: <4DFD1949.3060305@cs.cmu.edu> Ok. It will be much more convenient for me to write directly to .wav file (instead of doing some post-processing). So I will make the change to my branch, and once I see it works well, I will merge the modifications to the trunk. Gabriel Alex Rudnicky wrote: > The reasons were not very good ones: > > 1) at the time everything we were doing in interactive systems was 8kHz, > so this was "understood" to be the format. (Or, you just "knew" what > your data were.) > > 2) there was no really universally-accepted file format in ASR (except > maybe for .sph). > > 3) to do it correctly, at the end of the recording you needed to fseek > to the top of the file and put in the right numbers in the header (ie > length). This was thought to impact speed (maybe a dubious proposition). > > 4) various other resource-constraint related reasons, none of which I > believe are still operative. > > The right thing to do at this time would be to write a standard RIFF > header (.wav). This would make the files readers by pretty much all > tools out there; also, the format is flexible enough so that specialized > information can easily be included in a data block without breaking > anything. > > Alex > > > > -----Original Message----- > From: olympus-developers-bounces at mailman.srv.cs.cmu.edu > [mailto:olympus-developers-bounces at mailman.srv.cs.cmu.edu] On Behalf Of > Gabriel Parent > Sent: Friday, June 17, 2011 5:02 PM > To: olympus-developers at mailman.srv.cs.cmu.edu > Subject: [Olympus developers 302]: raw file vs wav file,is there a good > reason? > > All, > > what was the initial reason for writing the utterance and system audio > file as raw file versus wav file. Is the main reason to save disk space? > > Gabriel > From gparent+ at cs.cmu.edu Mon Jun 27 17:50:01 2011 From: gparent+ at cs.cmu.edu (Gabriel Parent) Date: Mon, 27 Jun 2011 17:50:01 -0400 Subject: [Olympus developers 305]: Re: raw file vs wav file, is there a good reason? In-Reply-To: <9C0D1A9F38D23E4290347EE31C22B0AF042E775C@e2k3.srv.cs.cmu.edu> References: <4DFBC0E2.7050409@cs.cmu.edu> <9C0D1A9F38D23E4290347EE31C22B0AF042E775C@e2k3.srv.cs.cmu.edu> Message-ID: <4E08FB09.9010507@cs.cmu.edu> If yinz look at the svn log, you'll see I just committed some changes to the main trunk of Olympus. Here is the svn comments: .wav files are now written instead of .raw files. 3 helper functions have been added to libOlympusUtility (e.g., Writing header, closing header), and AudioRecorder/AudioRecorderVoIP as well as AudioServer and Kalliope have been modified to use those helper functions when creating files. The function WriteWavHeader defaults to use a sample rate of 8000, but other sampling rate can be passed to it. Right now, the byte size (e.g., 2 for 16 bits sample) is hardcoded. An extra argument could be added if needed. Gabriel Alex Rudnicky wrote: > The reasons were not very good ones: > > 1) at the time everything we were doing in interactive systems was 8kHz, > so this was "understood" to be the format. (Or, you just "knew" what > your data were.) > > 2) there was no really universally-accepted file format in ASR (except > maybe for .sph). > > 3) to do it correctly, at the end of the recording you needed to fseek > to the top of the file and put in the right numbers in the header (ie > length). This was thought to impact speed (maybe a dubious proposition). > > 4) various other resource-constraint related reasons, none of which I > believe are still operative. > > The right thing to do at this time would be to write a standard RIFF > header (.wav). This would make the files readers by pretty much all > tools out there; also, the format is flexible enough so that specialized > information can easily be included in a data block without breaking > anything. > > Alex > > > > -----Original Message----- > From: olympus-developers-bounces at mailman.srv.cs.cmu.edu > [mailto:olympus-developers-bounces at mailman.srv.cs.cmu.edu] On Behalf Of > Gabriel Parent > Sent: Friday, June 17, 2011 5:02 PM > To: olympus-developers at mailman.srv.cs.cmu.edu > Subject: [Olympus developers 302]: raw file vs wav file,is there a good > reason? > > All, > > what was the initial reason for writing the utterance and system audio > file as raw file versus wav file. Is the main reason to save disk space? > > Gabriel > From apapangelis at iit.demokritos.gr Wed Jun 29 06:25:56 2011 From: apapangelis at iit.demokritos.gr (apapangelis@iit.demokritos.gr) Date: Wed, 29 Jun 2011 13:25:56 +0300 (EEST) Subject: [Olympus developers 306]: CMake question Message-ID: <239455fcc33f3d9d19cbece11ca83ad1.squirrel@webmail.iit.demokritos.gr> Hello, I've been trying to install Olympus on my system, Windows 7 64bit - SP1. I have installed everything, including cmake 2.6.4 and I keep getting an error that cmake was not found. I've tried later versions as well and nothing works. I've also checked the Path variable and it contains the cmake path. Am I doing something wrong? The log is: BUILD_CONF... Release BUILD_TYPE... Build OLYMPUS_ROOT... . BUILD_LOG... build.log CMAKE_PARAMS... LOGIOS_ROOT... Tools\logios Detecting platform in use... Windows Searching for File::Spec Perl Module... Found Searching for File::Copy Perl Module... Found Searching for IPC::Open3 Perl Module... Found Searching for IO::Handle Perl Module... Found Searching for Getopt::Long Perl Module... Found Searching for Win32 Perl Module... Found Searching for Win32::API Perl Module... Found Searching for Win32::TieRegistry Perl Module... Found Searching for Windows SDK 6.1 (for Windows Server 2008) or newer... Found v7.0 Searching for the SimpleAudio SAPI Example Project... Not Found Could not find the SimpleAudio DLL SAPI Example Solution. Did you install the Win32 examples when installing the SDK for Windows 7? Searching for Microsoft SAPI SDK... Found Copying SAPI SDK Fixup... Can't copy SDK fixup Do you have permission to write to C:\Program Files\Microsoft SDKs\Windows\v7.0\? Cannot find the Microsoft SAPI SDK 5.1 or newer. Install the SAPI 5.3 SDK by installing the Microsoft Windows SDK for Windows 7, along with the included Win32 samples, from http://msdn.microsoft.com/en-us/windows/bb980924.aspx Creating bin\x86-nt directory for build output... Done Searching for TortoiseSVN... Found Checking if the project is using CMake... Yes Searching for CMake 2.6 or higher... Not Found KitWare key: The handle is invalid Did you install CMake? http://www.cmake.org/cmake/cmake/resources/software.html Searching for maximum valid Visual Studio version... Not Found Please install Microsoft Visual Studio 2005 or 2008. Searching for Sun Java JDK... Found Searching for Apache Ant... Found Error during configure stage. Please fix and run the script again. ********************************************************************* SUMMARY: Could not find the SimpleAudio DLL SAPI Example Solution. Did you install the Win32 examples when installing the SDK for Windows 7? Can't copy SDK fixup Cannot find the Microsoft SAPI SDK 5.1 or newer. Install the SAPI 5.3 SDK by installing the Microsoft Windows SDK for Windows 7, along with the included Win32 samples, from http://msdn.microsoft.com/en-us/windows/bb980924.aspx KitWare key: The handle is invalid Did you install CMake? http://www.cmake.org/cmake/cmake/resources/software.html Please install Microsoft Visual Studio 2005 or 2008. Error during configure stage. Please fix and run the script again. Total Build Time: 0:00 ********************************************************************* Thank you for your help, Alexandros Papangelis From gparent+ at cs.cmu.edu Wed Jun 29 14:01:03 2011 From: gparent+ at cs.cmu.edu (Gabriel Parent) Date: Wed, 29 Jun 2011 14:01:03 -0400 Subject: [Olympus developers 307]: Re: CMake question In-Reply-To: <239455fcc33f3d9d19cbece11ca83ad1.squirrel@webmail.iit.demokritos.gr> References: <239455fcc33f3d9d19cbece11ca83ad1.squirrel@webmail.iit.demokritos.gr> Message-ID: <4E0B685F.7010406@cs.cmu.edu> That's weird, it really looks like you are missing Windows SDK, Visual Studio and CMake. Did you restart your computer in between the install of those and running the build script? I'm not sure how the scripts looks for those dependencies (whether it's a registry look-up, or uses the environment variable PATH), but that's probably what I would look into if I were you. I know of people who successfully installed Olympus on Win 7 64 bits machine, so it's doable. Gabriel apapangelis at iit.demokritos.gr wrote: > Hello, > > I've been trying to install Olympus on my system, Windows 7 64bit - SP1. I > have installed everything, including cmake 2.6.4 and I keep getting an > error that cmake was not found. I've tried later versions as well and > nothing works. I've also checked the Path variable and it contains the > cmake path. Am I doing something wrong? The log is: > > BUILD_CONF... Release > BUILD_TYPE... Build > OLYMPUS_ROOT... . > BUILD_LOG... build.log > CMAKE_PARAMS... > LOGIOS_ROOT... Tools\logios > Detecting platform in use... Windows > Searching for File::Spec Perl Module... Found > Searching for File::Copy Perl Module... Found > Searching for IPC::Open3 Perl Module... Found > Searching for IO::Handle Perl Module... Found > Searching for Getopt::Long Perl Module... Found > Searching for Win32 Perl Module... Found > Searching for Win32::API Perl Module... Found > Searching for Win32::TieRegistry Perl Module... Found > Searching for Windows SDK 6.1 (for Windows Server 2008) or newer... Found > v7.0 > Searching for the SimpleAudio SAPI Example Project... Not Found > Could not find the SimpleAudio DLL SAPI Example Solution. > Did you install the Win32 examples when installing the SDK for > Windows 7? > > Searching for Microsoft SAPI SDK... Found > Copying SAPI SDK Fixup... Can't copy SDK fixup > Do you have permission to write to C:\Program Files\Microsoft > SDKs\Windows\v7.0\? > Cannot find the Microsoft SAPI SDK 5.1 or newer. > Install the SAPI 5.3 SDK by installing the Microsoft Windows SDK for > Windows 7, along with the included Win32 > samples, from http://msdn.microsoft.com/en-us/windows/bb980924.aspx > > Creating bin\x86-nt directory for build output... Done > Searching for TortoiseSVN... Found > Checking if the project is using CMake... Yes > Searching for CMake 2.6 or higher... Not Found > KitWare key: The handle is invalid > Did you install CMake? > http://www.cmake.org/cmake/cmake/resources/software.html > Searching for maximum valid Visual Studio version... Not Found > Please install Microsoft Visual Studio 2005 or 2008. > Searching for Sun Java JDK... Found > Searching for Apache Ant... Found > > Error during configure stage. Please fix and run the script again. > ********************************************************************* > SUMMARY: > Could not find the SimpleAudio DLL SAPI Example Solution. > Did you install the Win32 examples when installing the SDK for > Windows 7? > > Can't copy SDK fixup > Cannot find the Microsoft SAPI SDK 5.1 or newer. > Install the SAPI 5.3 SDK by installing the Microsoft Windows SDK for > Windows 7, along with the included Win32 > samples, from http://msdn.microsoft.com/en-us/windows/bb980924.aspx > > KitWare key: The handle is invalid > Did you install CMake? > http://www.cmake.org/cmake/cmake/resources/software.html > Please install Microsoft Visual Studio 2005 or 2008. > Error during configure stage. Please fix and run the script again. > > Total Build Time: 0:00 > ********************************************************************* > > > Thank you for your help, > Alexandros Papangelis > > From joana.paulo.pardal at l2f.inesc-id.pt Wed Jun 29 16:51:31 2011 From: joana.paulo.pardal at l2f.inesc-id.pt (Joana Paulo Pardal) Date: Wed, 29 Jun 2011 21:51:31 +0100 Subject: [Olympus developers 308]: Skype API chat and call Message-ID: <7655149B-6402-4928-9127-E5EFC2CE58A6@l2f.inesc-id.pt> Hi. The new version of Skype API was released. Apparently it is much easier to use. http://developer.skype.com/ I was wondering if are there any plans to develop a audio server connection that would interact with Skype via voice / video / chat. Thanks, ~ Joana P Pardal