![]() ![]() If possible for 64bit.Īll links for that are pointing to hotfiles and long gone.Īnother big problem is finding the correct phonetic disciptions for native names, Australia is hard enough, but I gues NZ will be even harder. Than there's the problem with the versions and "encryption" of the lexicon files.Īccording to Loquendo they are plain text files but most files I could find can't be edited with a normal editor and the same problem when trying it with the Loquendo Lexicon manager.īut at this stage this does not really matter as I would need the current LoquendoTTS director suite including the english voices first. Not sure if anyone realised yet but you never get any definitions when you buy a Loquendo distribution, not even with the voice. This was a complete disaster as the old engine does not support all the changes and is even more restricted than the V7 Kate. So that you understand my frustration: even with a correctly installed voice the TT stays silent for instructions as long as not all files and definitions are correct!Īt this stage I decided to start fresh and with the old version 6 Kate as she should work fine on 32mb devices as well. Result: It started to complain that the original language discriptions are missing! So I transformed all necessary files so that they match the what the TT wanted. YES!!! You do it right and define everything according to Loquendo's specifications and the bloody thing simply overrides it! ![]() ![]() My modified lexicons were loaded, but at a later stage sicarded because the TT tried to load default definitions. The big problems started once I got the error logging and TTS engine logging working. However this is quite an easy task as you can find several. My first approach by deleting this file resolved quite a few issues but I had to create some new exceptions for raod types so that for example the M1 will be spoken as M 1 and not Motorway something. This causes the engine for example to mix street and road types so that a freeway becomes a court in a bad case. Without deleting this file all possible changes to the lexicons and definitions are ignored or their settings overridden by the cphoneme.dat. Loquendo (Now they and Nuance are one company!) uses a very specific folder and discription hirachy and that should have made thing easy as all was working fine on the PC.īut TT simply refuses to accept those rules and specifies their own (undocumented) rules in their modiefied libraries.Īt first I thought this is only to confuse a potential user trying to do some changes but I realised that TT insists on using the cphonme.dat inside the map folder. I finally found some info on error locating in Loquendo and am now on a dead end. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |