PDF version - Nerd Vittles
Contents
1. Like Festival user types can be added to the cst_vals In Festival this can be done on the fly but because this requires the updating of some list when each new type is added this wouldn t be thread safe Thus an explicit method of defining user types is done in src utils cst_val_user c This is not as neat as defining on the fly or using a registration function but it is thread safe and these user types wont changes often lt gt lt lt Vp gt gt Top Contents Index _ 7 APIs Flite is a library that we expected will be embedded into other applications Included with the distribution is a small example executable that allows synthesis of strings of text and text files from the command line T lt gt lt lt Up gt gt Top Contents Index 2 7 1 flite binary The example flite binary may be suitable for very simple applications Unlike Festival its start up time is very short less that 25ms on a PII SOOMHz making it practical on larger machines to call it each time you need to synthesize something flite TEXT OUTPUTTYPE If TEXT contains a space it is treated as a string of text and converted to speech if it does not contain a Space TEXT is treated as a file name and the contents of that file are converted to speech The option t specifies TEXT is to be treat as text not a filename and f forces treatment as a file Thus flite t hello will say the word hello while flite hello wil2. palm pocore I believe CodeWarrior has better support for this but in this case we rolled our own though help from other open source examples was important We manage the m68k ARM interface through PEAL which is basically a linker for ARM code and calling mechanism from m68k PEAL deals with globals and spliting the code into 65K chunks automatically Flite does however have a number of large data segments in the lexicon and the voice database itself PEAL can deal with this but it loads large segments by copying them into the dynamic heap which on most Palm device is less than 2M This isn t big enough Thus we changed Flite to restrict the number of large data sgements it used and also did some new compression on them The five segments the Its rules the lexical entries the voice LPC coefficients the voice residuals and the voice residual index are now treated a data segments that are split into 65400 sized segments and loaded into feature memory space which is in the storage heap and typically much bigger This means we do need about 2 3 megabyte free on the device to run We did look into just indexing the 65400 byte segments directly but that looked like being too much work and we re only going to be able to run on 16M sized Palms anyway there aren t any 8M ARM Palms with audio expect maybe some SmartPhones Using Flite from m68k land involves getting a flite_info structure from flite_init This contains a bunch of fields th
3. Top Contents Index _ Flite a small fast speech synthesis engine 1 Abstract initial comments 2 Copying How you can copy and share the code 3 Acknowledgements List of contributors 4 Installation Compilation and Installation 5 Flite Design 7 APIs Standard functions 8 Converting FestVox Voices building flite voices from FestVox ones lt gt lt lt UVp gt gt Top Contents Index 2 1 Abstract This document provides a user manual for flite a small fast run time speech synthesis engine This manual is nowhere near complete Flite offers text to speech synthesis in a small and efficient binary It is designed for embedded systems like PDAs as well large server installation which must serve synthesis to many ports Flite is part of the suite of free speech synthesis tools which include Edinburgh University s Festival Speech Synthesis System http www cstr ed ac uk projects festival and Carnegie Mellon University s FestVox project http festvox org which provides tools scripts and documentation for building new synthetic voices Flite is written in ANSI C and is designed to be portable to almost any platform including very small hardware Flite is really just a synthesis library that can be linked into other programs it includes two simple voices with the distribution an old diphone voice and anb example limited domain voice which uses the newer unit selection techniques we have been devel
4. that will be used in flite to ensure that a consistent order is given bin build_flite idx All the necessary C files should now have been built in flite and you may compile them by cd flite make This should give a library and an executable called flite that can run as flite Hello World Assuming a general voice For Idom voices it will only be able to say things in its domain This flite binary offers the same options as standard the standard 1ite binary compiled in the Flite build but with your voice rather than the distributed voices Almost certainly this process will not run smoothly for you Building voices is still a very hard thing to do and problems will probably exist This build process does not deal with customization for the given voices Thus you will need to edit flite VOICE c to set intonation ranges and duration stretch for your particular voice For example in our cmu_us_sls_diphone voice a US English female diphone voice We had to change the default parameters from feat_set_float v gt features int_f0 target_mean 110 0 feat_set float v gt features int 0 target _stddev 15 0 feat_set_float v gt features duration_stretch 1 0 to feat_set_float v gt features int_f0 target _mean 167 0 feat_set float v gt features int 0 target _stddev 25 0 feat_set_float v gt features duration _stretch 1 0 Note this conversion is limited Because it depends on the C compiler to do t
5. will eventually build sufficient C code in flite that can be compiled with the constructed flite Makefile to give you a library that can be linked into applications and also an example flite binary with the constructed voice built in You can run all of these stages except the final make together by running the the build script with no arguments bin build_flite But as things may not run smoothly we will go through the stages explicitly The first stage is to build the LPC files this may have already been done as part of the diphone building process though probably not in the Idom clunit case In our experience it is very important that the records be of similar power as mis matched power can often cause overflows in the resulting flite and sometimes Festival voices Thus for diphone voices it is important to run the power normalization techniques described int he FestVox document The Flite LPC build process also builds a parameter file of the ranges of the LPC parameters used in later coding of the files so even if you have already built your LPC files you should still do this again bin build_flite lpc For Idom and clunit voices but not for diphone voices we also need the Mel frequency Cepstral Coefficients These are assumed to have been cleared and are in mcep as they are necessary for running the voice in Festival This stage simply constructs information about the range of the mcep parameters bin build_flite mc
6. LUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS IN NO EVENT SHALL CARNEGIE MELLON UNIVERSITY NOR THE CONTRIBUTORS BE LIABLE FOR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE DATA OR PROFITS WHETHER IN AN ACTION OF CONTRACT NEGLIGENCE OR OTHER TORTIOUS ACTION ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE J Ls Le lt lt Upg gt gt Top Contents Index _ 3 Acknowledgements The initial development of flite was primarily done by awb while travelling perhaps the name is doubly appropriate as a substantial amount of the coding was done over 30 000ft During most of that time awb was funded by the Language Technologies Institute at Carnegie Mellon University Kevin A Lenzo was involved in the design conversion techniques and representations for the voice distributed with flite as well as being the actual voice itself Other contributions are e David Huggins Daines dhd cepstral com much of the clunits code porting to multiple platforms substantial code tidy up and configure autoconf guidance e Cepstral LLC http cepstral com For supporting DHD to spend time on flite and passing back the important fixes and enhancements including SAPI support e Willie Walker lt william walker sun com gt and the Sun Speech Group lots of low level bugs and fixes e Portuguese Foundation for Science and Technology FC
7. M simulator under Windows it never really contributed to the development The POSE m68k emulator though was use to develop the flop application itself T lt gt lt lt Up gt gt Top Contents Index 2 4 3 1 Some notes on the PalmOS port Throughout the PalmOS developer documentation they continually remind you that a Palm device is not a full computer its an extention of the desktop But seeing devices like the Treo 600 can easily make one forget and want the device to do real computational work PalmOS is designed for small light weight devices so it is easy to start hitting the boundaries of its capabilities when trying to port larger aplications PalmOS5 0 still has interesting limitations in the m68k domain int s are 16 bit and using memory segments greater than 65K require special work Quaint as these are they do significantly affect the port At first we thought that only the key computationally expensive parts would be in ARM so called armlets but trying to compile the whole flite code in m68k with long short distinctions and sub 64K code segment limitations was just too hard Thus all the Flite code USEnglish Lexicon and diphone databases actually are compiled in the ARM domain There is however no system support in the ARM domain so call backs to m68k system functions are necessary With care calls to system functions can be significantly limited so only a few call backs needed to be written These are in
8. T Praxis XXI program The SAPI interface provided by Cepstral LLC was partially funded by the above program Henry Spencer For the regex code University of Edinburgh for releasing Festival for free making a companion runtime synthesizer a practical project much of the design of flite relies on the architecture decisions made in the Festival Speech Synthesis Systems and the Edinburgh Speech Tools The duration cart tree and intonation accent and FO models were derived from the models in the Festival distribution which in turn were trained from the Boston University FM Radio Data Corpus e Carnegie Mellon University The included lexicon is derived from CMULEX and the letter to sound rules are constructed using the Lenzo and Black techniques for building LTS decision graphs e Craig Reese IDA Supercomputing Research Center and Joe Campbell Department of Defense who wrote the ulaw conversion routines in src speech cst_wave_utils c lt lt lt Vp gt gt Top Contents Index 2 4 Installation Flite consist simple of a set of C files GNU configure is used to configure the engine and will work on most major architectures In general the following should build the system tar zxvf flite XXX tar gz cd flite XxXx configure make However you will need to explicitly call GNU make gmake if make is not GNU make on your system The configuration process build a file config config which under some circumstances
9. _phones const char phones cst_ voice voice synthesize the given phones with the given voice and returns an utterance from it for further processing and access J lt gt lt lt I Up gt gt Top Contents Index 2 8 Converting FestVox Voices As of 1 2 initial scripts have been added to aid the conversion of FestVox voices to Flite In general the conversion cannot be automatic For example all specific Scheme code written for a voice needs to be hand converted to C to work in Flite this can be a major task Simple conversion scripts are given as examples of the stages you need to go through These are designed to work on standard English diphone sets and simple limited domain voices The conversion technique will almost certainly fail for large unit selection voices due to limitations in the C compiler more discussion below Conversion is basically taking the description of units clunit catalogue or diphone index and constructing some C files that can be compiled to form a usable database Using the C compiler to generate the object files has the advantage that we do not need to worry about byte order alignment and object formats as the C compiler for the particular target platform should be able to generate the right code Before you start ensure you have successfully built and run your FestVox voice in Festival Flite is not designed as a voice building debugging tool it is just a delivery vehicle for finaliz
10. at be set and sent to the ARM domain Flite synthesizer proper within which other output fields may be set and returned This isn t a very general structure but is adequate Note the necessary byte swapping for the top level fileds is done for the this structure before calling the ARM native arm_flite_synth_text and swapped back again after returning Display playing audio pointy clicky event thingies are all done in the m68K domain m lt gt lt lt Up gt gt Top Contents Index 2 4 3 2 Using the PalmOS There are three basic functions that access the ARM flite functions fLite_init flite_synth_text and flite_end Le Le Lee Up gt Top Contents Index _ 5 Flite Design T lt gt lt lt Up gt gt Top Contents Index _2 5 1 Background Flite was primarily developed to address one of the most common complaints about the Festival Speech Synthesis System Festival is large and slow even with the software bloat common amongst most products and that that bloat has helped machines get faster have more memory and large disks still Festival is criticized for its size Although sometimes this complaint is unfair it is valid and although much work was done to ensure Festival can be trimmed and run fast it still requires substantial resources per utterance to run After some investigation to see if Festival itself could be trimmed down it became clear because there wa
11. ate computationally efficient and well proven Thus both because HRGs have such a background and that Flite is to be compatible with voices and models developed in Festival Flite uses HRG s as its basic utterance representation structure Most of a synthesizer is in its data lexicons unit database etc the actual synthesis code it pretty small In Festival most of that data exists in external files which are loaded on demand This is obviously slow and memory expensive you need both a copy on the data on disk and in memory As one of the principal targets for Flite is very small machines we wanted to allow that core data to be in ROM and be appropriately mapped into RAM without any explicit loading This can be done by various memory mapping functions in Unix its called mmap and is the core technique used in shared libraries called DLLs in some parts of the world Thus the data should be in a format that it can be directly accessed If you are going to directly access data you need to ensure the byte layout is appropriate for the architecture you are running on byte order and address width become crucial if you want to avoid any extra conversion code at access time like byte swapping At first is was considered that synthesis data would be converted in binary files which could be mmap ed into the runtime systems but building appropriate binaries files for architectures is quite a job However the C compiler does this in a standard way Theref
12. con and letter to sound rules o Unit database and voice definition T lt gt lt lt Up gt gt Top Contents Index 2 6 1 cst_val This is a basic simple object which can contain ints floats strings and other objects It also allows for lists using the Scheme Lisp car cdr architecture as that is the most efficient way to represent arbitrary trees and lists The cst_val structure is carefully designed to take up only 8 bytes or 16 on a 64 bit machine The multiple union structure that it can contain is designed so there are no conflicts However it depends on the fact that a pointer to a cst_val is guaranteed to lie on a even address boundary which is true for all architectures I know of Thus the distinction between between cons i e list objects and atomic values can be determined by the odd evenness of the least significant bits of the first address in a cst_val In some circles this is considered hacky in others elegant This was done in flite to ensure that the most common structure is 8 bytes rather than 12 which saves significantly on memory All cst_val s except those of type cons are reference counted A few functions generate new lists of est_val s which the user should be careful about as they need to explicitly delete them notably the lexicon lookup function that returns a list of phonemes Everything that is added to an utterance will be deleted and or dereferenced when the utterance is deleted
13. e dk code flite htm which includes full sources The system as distributed does compile under the gcc arm wince pe toolchain available from http win ce voxware com 28575 Development 20Tools but Flite is currently not properly integrated with the WinCE audio device so although the binary runs it can t play any audio only generate it to files I lt gt lt lt Up gt gt Top Contents Index _ 4 3 PalmOS Support Starting with 1 3 we have initial support for PalmOS using the free development tools The compilation method assumes the target device is running PalmOS 5 0 or later on an ARM processor Following convention in the Palm world the app that the user interacts with is actually a m68k application compiled with the m68 gcc cross compiler the resulting code is interpreted by the PalmOS 5 0 device The core flite code is in native ARM and hence uses the ARM gcc cross compiler An interesting amout of support code is required to get all this work properly The user app is called flop FLite on Palm and like most apps written by awb is functional but ugly You should not let a short sighted Scotsman who still thinks command line interfaces are cool design a graphical app But it does work and can read typed in text memos and text files The armflite ro resources are designed with the idea that proper applications will be written using it as a library The flop prc application is distributed separately
14. ed voices so you should first ensure you are satisfied with the quality of Festival voices before you start converting it for Flite The following basic stages are required Setup the directories and copy the conversion scripts Build the LPC files Build the MCEP files for Idom clunits Convert LPC MCEP into STS short term signal files Convert the catalogue diphone index Compile the generated C code The conversion assumes the environment variable FLITEDIR is set for example export FLITEDIR home awb projects flite The basic flite conversion takes place within a FestVox voice directory Thus all of the conversion scripts expect that the standard files are available The first task is to build some new directories and copy in the build scripts The scripts are copied rather than linked from the Flite directories as you may need to change these for your particular voices SFLITEDIR tools setup flite This will read etc voice defs which should have been created by the FestVox build process except in very old versions of FestVox If you don t have a etc voice defs you can construct one with y y festvox src general guess_voice defs in the Festvox distribution or generate one by hand making it look like FV_INST cmu FV_LANG us FV_NAME ked_timit FV_TYPE clunits FV_VOICENAME SFV_INST SFV_LANG SFV_NAME FV_FULLVOICENAME SFV_VOICENAME SFV_TYPE The main script build building the Flite voice is bin build_flite which
15. ep The next stage is to construct the STS files Short Term Signals STS are built for each pitch period in the database These are ascii files one for each utterance file in the database with LPC coefficients and ulaw encoded residuals for each pitch period These are built using a binary executable built as part of the Flite build f lite tools find_sts bin build_flite sts Note that the flite code expects waveform files to be in Microsoft RIFF format and cannot deal with files in other formats Some earlier versions of the Edinburgh Speech Tools used NIST as the default header format This is likely to cause flite and its related programs not work So do ensure you waveform files are in riff format ch_wave info wav will tell you the format And the following fill convert all you wave files mv wav wav nist mkdir wav cd wav nist for iin wav do ch_wave otype riff o wav Si i done The next stage is to convert the index to the required C format For diphone voices this takes the dic est index files for clunit Idom voices it takes the festival clunit VOICE catalogue and festival trees VOICE tree files This process uses a binary executable built as part of the Flite build process lite tools flite_sort to sort the indices into the same sorting order required for flite to run Using unix sort may or may not give the same result due to definitions of lexicographic order so we use the very same function in C
16. he final conversion into binary object format a good idea in general for portability you can easily generate files too big for the C compiler to deal with We have spent a some time investigating this so the largest possible voices can be converted but it is still too limited for our larger voices In general the limitation seems to be best quantified by the number of pitch periods in the database After about 100k pitch periods the files get too big to handle There are probably solutions to this but we have not yet investigated them This limitation doesn t seem to be an issue with the diphone voices as they are typically much smaller than unit selection voices I lt gt lt lt Up gt gt Top Contents Index _ 8 1 Lexicon Conversion As of 1 3 the script for converting the CMU lexicon as distributed as part of Festival is included make_cmulex will using the version of CMULEX unpacked in the current directory to build a new lexicon Also in 1 3 a more sophisticated compression technique is used to reduce the lexicon size The lexicon is pruned removing those words which the letter to sound rule models get correct Also the letters and phones are separately huffman coded to produce a smaller lexicon j lt gt lt lt Up gt gt Top Contents Index _2 8 2 Language Conversion This is by far the weakest part as this is the most open ended There are basic tools in the flite tools director
17. ilers are released A second problem with C is the size and efficiency of the code produced Proponents of C may rightly argue that Festival and the Edinburgh Speech Tools aren t properly designed but irrespective if that is true or not it is true that the size of the code is much larger and slower than it need be for what it does Throughout the design there is a constant trade off between elegancy and efficiency which unfortunately at times in Festival requires untidy solutions of copying data out of objects processing it and copying back because direct access particularly in some signal processing routines is just too inefficient Another major criticism of Festival is the use of Scheme as the interpreter language Even though it is a simple to implement language that is adequate for Festival s needs and can be easily included in the distribution people still hate it Often these people do learn to use it and appreciate how run time configurability is very desirable and that new voices may be added without recompilation Scheme does have garbage collection which makes leaky programs much harder to write and as some of the intended audience for developing in Festival will not be hard core programmers a safe programming language seems very desirable After taking into consideration all of the above it was decided to develop Flite as a new system written in ANSI C C is much more portable than C as well as offering much lower level control of
18. l say the content of the file hello Likewise flite hello world will say the words hello world while flite f hello world will say the contents of a file hello world If no argument is specified text is read from standard input The second argument OUTPUTTYPE is the name of a file the output is written to or if it is play then it is played to the audio device directly If it is none then the audio is created but discarded this is used for benchmarking If ouTPUTTYPE is omitted play is assumed You can also explicitly set the outputtype with the o flag flite f doc alice o alice wav i lt gt lt lt Up gt gt Top Contents Index 2 7 2 C example Each voice in Flite is held in a structure a pointer to which is returned by the voice registration function In the standard distribution the example diphone voice is cmu_us_kal Here is a simple C program that uses the flite library include flite h cst_voice register_cmu_us_kal int main int argc char argv i cst_voice v if argc 2 i fprintf stderr usage flite_test FILE n exit 1 flite init v register _cmu_us_kal flite file to _speech argv 1 v play Assuming the shell variable FLITEDIR is set to the flite directory the following will compile the system with appropriate changes for your platform if necessary gcc Wall g o flite test flite_test c ISFLITEDIR include LSFLITEDIR 1lib lflite_cm
19. may need to be edited e g to add unusual options or dealing with cross compilation On Linux systems we also support shared libraries which are useful for keeping space down when multiple different application are linked to the flite libraries For development we strong discourage use of shared libraries as it is too easy to either not set them up correctly or accidentally pick up the wrong version But for installation they are definitely encouraged That is if you are just going to make and install they are good but unless you know what LD_LIBRARY_PATH does it may be better to use static libraries the default if you are changing C code or building your own voices configure enable shared make This will build both shared and static versions of the libraries but will link the executables to the shared libraries thus you will need to install the libraries in a place that your dynamic linker will find them cf etc Id so conf or set LD_LIBRARY_PATH appropriately I lt gt lt lt Up gt gt Top Contents Index 2 4 1 Windows Support J lt gt lt lt Up gt gt Top Contents Index 2 4 2 Window CE Support Flite has been successfully compile by a number of different groups under Windows CE The system should compile under Embedded Visual Studio but we not have the full details If you look are the net it is possible to find precompiled versions for Windows CE including http www vikso
20. ong felt that research in speech and language should have an identifiable link to ultimate commercial use In providing a platform that can be used in consumer products that falls within the same framework as our research we can better understand what research issues are actually important to the improvement our work In considering small useful synthesizers it forces a more explicit definition of what is necessary in a synthesizer and also how we can trade size flexibility and speed with the quality of synthesized output Defining that relationship is a research issue We are also advocates of speech technology within other research areas and the ability to offer support on new platforms such as PDAs and wearables allows for more interesting speech applications such as speech to speech translation robots and interactive personal digital assistants that will prove new and interesting areas of research Thus having a platform that others around us can more easily integrate into their research makes our work more satisfying T lt gt lt lt Up gt gt Top Contents Index 2 5 2 Key Decisions The basic architecture of Festival is good It is well proven Paul Taylor Alan W Black and Richard Caley spent many hours debating low level aspects of representation and structure that would both be adequate for current theories but also allow for future theories too The heterogeneous relation graphs HRG are theoretically adequ
21. opi Top fover top of document Coments Contents fable of comes Tinder index eoneeptindex F 21 About r SSS where the Example assumes that the current position is at Subsubsection One Two Three of a document of the following structure e 1 Section One 0 1 1 Subsection One One 1 2 Subsection One Two 1 2 1 Subsubsection One Two One 1 2 2 Subsubsection One Two Two 1 2 3 Subsubsection One Two Three lt Current Position a 1 2 4 Subsubsection One Two Four 1 3 Subsection One Three 1 4 Subsection One Four 0 0 0 This document was generated by Nerd Vittles on May 9 2006 using texi2html
22. oping Neither of these voices would be considered production voices but server as examples new voices will be released as they are developed The latest versions comments new voices etc for Flite are available from its home page which may be found at http cmuflite or lt lt lt Vp gt gt Top Contents Index 2 2 Copying Flite is free software It is distributed under an X11 like license Apart from the few exceptions noted below which still have similarly open lincenses the general license is Language Technologies Institute Carnegie Mellon University Copyright c 1999 2005 All Rights Reserved Permission is hereby granted free of charge to use and distribute this software and its documentation without restriction including without limitation the rights to use copy modify merge publish distribute sublicense and or sell copies of this work and to permit persons to whom this work is furnished to do so subject to the following conditions 1 The code must retain the above copyright notice this list of conditions and the following disclaimer 2 Any modifications must be clearly marked as such Original authors names are not deleted 4 The authors names are not used to endorse or promote products derived from this software without specific prior written permission w CARNEGIE MELLON UNIVERSITY AND THE CONTRIBUTORS TO THIS WORK DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INC
23. ore the mode of operation for data within Flite is to convert it to C code actually C structures and use the C compiler to generate the appropriate binary structures Using the C compiler is a good portable solution but it as these structures can be very big this can tax the C compiler somewhat Also because this data is not going to change at run time it can all be declared const Which means in Unix it will be in the text segment and hence read only this can be ROM on platforms which have that distinction For structures to be const all their subparts must also be const thus all relevant parts must be in the same file hence the unit databases files can be quite big Of course this all presumes that you have a C compiler robust enough to compile these files hardware smart enough to treat flash ROM as memory rather than disk or an operating system smart enough to demand page executables Certain popular operating systems and compilers fail in at least one of these respects and therefore we have provided the flexibility to use memory mapped file I O on voice databases where available or simply to load them all into memory T lt gt lt lt Up gt gt Top Contents Index _2 6 Structure The flite distribution consists of two distinct parts e The flite library containing the core synthesis code e Voice s for flite These contain three sub parts o Language models text processing prosody models etc o Lexi
24. pring 3 1H4 1 noarch rpm We also need the prc tools to know which SDK is available palmdev prep In addition we use Greg Parker s PEAL http www sealiesoftware com peal ELF ARM loader You need to download this and compile and install it yourself so that peal post1link is in your path Greg was very helpful and even added support for large data segments for this work though in the end we don t actually use them Some peal code is in our distribution which is valid under his licence but if you use a different version of peal you may need to ensure they are matched by updating the peal code in palm We used version peal 2004 12 29 The other palm specific function we require is par http www djw org product palm par which is part of the pre tgz distribution We use par to construct resources from raw binary files There are other programs that can do this but we found this one adequate Again you must compile this and ensure par is in your path Note no part of par ends up in the distributed system Given all of the above you should be able to compile the Palm code and the flop application configure target arm palmos make The resulting application should be in palm flop flop pre which can then be installed on your Plam device pilot xfer i palm flop flop pre Setting up the tools and getting a working Linux Palm conduit is not particularly easy but it is possible Although some attempt was made to use the Simulator PalmOS 5 0 AR
25. s a core set of functions that were sufficient for synthesis that a new implementation containing only those aspects that were necessary would be easier than trimming down Festival itself Given that a new implementation was being considered a number of problems with Festival could also be addressed at the same time Festival is not thread safe and although it runs under Windows in server mode it relies on the Unix centric view of fast forks with copy on write shared memory for servicing clients This is a perfectly safe and practical solution for Unix systems but under Windows where threads are the more common feature used for servicing multiple events and forking is expensive a non thread safe program can t be used as efficiently Festival is written in C which was a good decision at the time and perfectly suitable for a large program However what was discovered over the years of development is that C is not a portable language Different C compilers are quite different and it takes significant amount of work to ensure compatibility of the code base over multiple compilers What makes this worse is that new versions of each compiler are incompatible and changes are required At first this looked like we were producing bad quality code but after 10 years it is clear that it is also that the compilers are still maturing Thus it is clear that Festival and the Edinburgh Speech Tools will continue to require constant support as new versions of comp
26. so it can be used without having to install all these tools But if you want to PalmOS development here is what you need to do to compile Flite for PalmOS and the flop application There are number of different application development environments for Palm here I only describe the Unix based one as this is what was used You will need the PalmOS SDK 5 0 from palmOne http www palmone com us developers This is free but does require registration Out of the lots of different files you can get for palmOne you will eventually find palmos sdk 5 0r3 1 noarch rpm install that on your linux machine rpm i palmos sdk 5 0r3 1 noarch rpm You will also need the various gcc based cross compilers http prc tools sourceforge net prc tools 2 3 1 i386 rpm prc tools arm 2 3 1 i1386 rpm prc tools htmldocs 2 3 1 noarch rpm The Palm Resource compiler http pilrc sourceforge net pilrc 3 1 1 1386 rpm And maybe the emulator http www palmos com dev tools emulator pose 3 5 2 i386 rpm pose skins 1 9 1 noarch rpm pose skins handspring 3 1H4 1 noarch rpm Though as POSE doesn t support ARM code Simulator does but that only works under Windows POSE is only useful for debugging the m68k parts of the app Install these rpm i prc tools 2 3 1 1386 rpm rpm i prc tools arm 2 3 1 1386 rpm rpm i prc tools htmldocs 2 3 1 noarch rpm rpm i pilrc 3 1 1 i386 rpm rpm i pose 3 5 2 1386 rpm rpm i pose skins 1 9 1 noarch rpm rpm i pose skins hands
27. the size of the objects and data structure it uses Flite is not intended as a research and development platform for speech synthesis Festival is and will continue to be the best platform for that Flite however is designed as a run time engine when an application needs to be delivered It specifically addresses two communities First as a engine for small devices such as PDAs and telephones where the memory and CPU power are limited and in some cases do not even have a conventional operating system The second community is for those running synthesis servers for many clients Here although large fixed databases are acceptable the size of memory required per utterance and speed in which they can be synthesized is crucial However in spite of the decision to build a new synthesis engine we see this as being tightly coupled into the existing free software synthesis tools or Festival and the FestVox voice building suite Flite offers a companion run time engine Our intended mode of development is to build new voices in FestVox and debug and tune them in Festival Then for deployment the FestVox format voice may be semi automatically compiled into a form that can be used by Flite In case some people feel that development of a small run time synthesizer is not an appropriate thing to do within a University and is more suited to commercial development we have a few points which they should be aware of that to our mind justify this work We have l
28. u_us_kal lflite_usenglish lflite _cmulex lflite lm lt gt lt lt Up gt gt Top Contents Index _2 7 3 Public Functions Although of course you are welcome to call lower level functions there a few key functions that will satisfy most users of flite void flite init void This must be called before any other flite function can be called As of Flite 1 1 it actually does nothing at all but there is no guarantee that this will remain true cst_wave flite text _to wave const char text cst_voice voice Returns a waveform as defined in include cst_wave h synthesized from the given text string by the given voice float flite file _to_speech const char filename cst _voice voice const char outtype synthesizes all the sentences in the file filename with given voice Output at present can only reasonably be play or none float flite text_to_speech const char text cst _ voice voice const char outtype synthesizes the text in string point to by text with the given voice outtype may be a filename where the generated waveform is written to or play and it will be sent to the audio device or none and it will be discarded The return value is the number of seconds of speech generated cst_utterance flite synth _text const char text cst_voice voice synthesize the given text with the given voice and returns an utterance from it for further processing and access cst_utterance flite synth
29. y that include Scheme code to convert various Scheme structures to C include CART tree conversion and Lisp list conversion The other major source of help here is the existing language examples in flite lang usenglish lt gt lt lt Up gt gt Top Contents Index _ 9 Porting to new platforms byte order unions compiler restrictions lt gt lt lt Up gt gt Top Contents Index _2 10 Future developments Top Contents Index _ Table of Contents 1 Abstract 2 Copying 3 Acknowledgements 4 Installation 4 1 Windows Support 4 2 Window CE Support 4 3 PalmOS Support 4 3 1 Some notes on the PalmOS port 4 3 2 Using the PalmOS 5 Flite Design 5 1 Background 5 2 Key Decisions 6 Structure 6 1 cst val 7 APIs 7 1 flite binary 7 2 C example 7 3 Public Functions 8 Converting FestVox Voices 8 1 Lexicon Conversion 8 2 Language Conversion 9 Porting to new platforms 10 Future developments Top Contents Index _ Short Table of Contents 1 Abstract 2 Copying 3 Acknowledgements 4 Installation 5 Flite Design 6 Structure 7 APIs 8 Converting FestVox Voices 9 Porting to new platforms 10 Future developments Top Contents Index _ About this document This document was generated by Nerd Vittles on May 9 2006 using texi2html The buttons in the navigation panels have the following meaning Fur e Tr
Download Pdf Manuals
Related Search