Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 32

Thread: Audio Problem

  1. #21
    Senior Member
    Join Date
    Dec 2010
    Location
    It's nice!
    Posts
    101
    Rep Power
    24

    Default

    Modifying WinCE Loquendo voices is easily done through the .lex file in the TTS_LOQ folder. While in Android the changes seem to have to be modified in the voice file since the NUANCE folder doesn't have a .lex file.

  2.    Advertissements


  3. #22
    Super Member
    Join Date
    Nov 2014
    Location
    USA
    Age
    43
    Posts
    197
    Rep Power
    48

    Default

    Understood. I'm actually talking about Nuance voices here - not Loquendo. In WinCE, a Nuance voice file with the same line in the config_transforms.lua file says "1st" properly - even if that line above is not commented out. That's why I'm saying that the root cause must actually be because of a difference in the Android Nuance TTS engine - not the voice file.

    Strange how the Nuance TTS driver acts differently between WinCE and Android.

    EDIT: I was actually testing with the same voice on WinCE (Ira). I think the only difference is the "tts_engine" parameter in the .ini file.

    Sent from my HP SlateBook 10 x2 PC using Tapatalk
    Last edited by jtrosky; 23rd December 2015 at 21:40.

  4. #23
    Senior Member
    Join Date
    Dec 2010
    Location
    It's nice!
    Posts
    101
    Rep Power
    24

    Default

    I actually took the Ira voice from WinCE and developed it for Android. So it will look kinda similar for both engines. The change was in the info.ini. I see you mentioned the .ini file after I posted this [I re-read your post] but it took a little more than just the tts_engine part. Not much more though.
    Last edited by chas521; 23rd December 2015 at 23:04.

  5. #24
    Important User

    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Farside of the Sun
    Posts
    2,645
    Rep Power
    638

    Default

    @jtrosky I believe there is more than one way to fix this problem. I'm willing to bet the changes was ported and not completed in many voice files using that logic. If it works correctly without the line uncommented, it might be picking up "1st" from another place (search all files for it) Would you post the WinCE voice file that works without the uncommented line? I'm using VocalizerEx (so it's Nuance) on android; but I don't think that matter because Primo on android is designed to use whatever voice engine the android device is set to.

    @chas521 I had installed VocalizerEx (English Allison voice) so when I use your male (Ira voicefile) it sounded female On android, I don't think all parameters under .ini are used (or can be used) I even tried to mod the speech rate and it doesn't work. Speech rate can only be changed under Android setting and not in .ini
    Last edited by osiris4isis; 24th December 2015 at 00:46.

  6. #25
    Senior Member
    Join Date
    Dec 2010
    Location
    It's nice!
    Posts
    101
    Rep Power
    24

    Default

    And Ira voice with my NUANCE sounds male.

  7. #26
    Important User

    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Farside of the Sun
    Posts
    2,645
    Rep Power
    638

    Default

    On WinCE it should be correctly as male since the settings are for a Nuance male profile. But like I said for android, since Primo uses the voice engine from android OS and since I had VocalizerEx Allison, it will sound female

  8. #27
    Super Member
    Join Date
    Nov 2014
    Location
    USA
    Age
    43
    Posts
    197
    Rep Power
    48

    Default

    The "WinCE" voice file that I was testing with was the Ira voice from this archive:

    [Only registered and activated users can see links. ]

    However, I also just tested with @chas521's Android voice file (with a few entries changed in info.ini to make it work in WinCE) and it worked fine as-is - without any changes to any files other than info.ini. I didn't compare the .lua files line by line, but I know the line in question is present and un-commented and the voice file works fine in WinCE. So I still think there is a TTS engine difference that is the root cause here, since it works fine in WinCE with that line present in config_transforms.lua.

    Let me know what you find out. I'm just kinda curious, that's all (not that it really matters - all that really matters is that it's working for @chas521!). Just learning a little about TTS engine differences between Android and WinCE.

    Also, I did see a few quoting issues in the Android voice file from @chas521 (in the info.ini file). I did correct those when I modified the info.ini for use in WinCE. Not sure if that made any difference or not though. It might have been like that on purpose to make it work in Android - not sure.
    Last edited by jtrosky; 24th December 2015 at 03:06.

  9. #28
    Important User

    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Farside of the Sun
    Posts
    2,645
    Rep Power
    638

    Default

    Ok, I took original voice file posted from chas521 and you're right, it does work (without any uncommenting)...Weird, maybe it has to do with the voice engine correctly interpreting it. I'm sure I had tested it without the changes first and it didn't pronounced correctly. But now it pronounced correctly regardless of the changes. Man, this is like [Only registered and activated users can see links. ]

  10. #29
    Senior Member
    Join Date
    Dec 2010
    Location
    It's nice!
    Posts
    101
    Rep Power
    24

    Default

    Like I said, the voice is male and I'm very happy. It works and that's all I can ask for. If it ain't broke don't fix it.

  11. #30
    Super Member
    Join Date
    Nov 2014
    Location
    USA
    Age
    43
    Posts
    197
    Rep Power
    48

    Default

    I completely agree that the main problem here has been resolved for you, @chas521 - but the conversation we're having is still a worthwhile conversation to have, just so we can better understand how things work in order to resolve future issues. And we're also not 100% sure that commenting that one line from the voice file won't have any negative results at some point.

    That being said, unless we can change things in the Nuance TTS engine files, there really isn't much we can do about the differences between the WinCE and Android Nuance TTS engines.

    Obviously, the TTS engines must be handling things differently if the same voice file behaves differently in Android and WinCE.

    By the way, when I test this stuff, instead of trying to plan routes that use the street names you are trying to test, you can simply put what you want to test right in the "testsound" parameter in info.ini. Then, just selecting the voice in iGo will say the word/phrase you want to test. For example, to test these street name issues, I just change the testsound to "1st 2nd 3rd 107th" to see how the voice says the different street names. Much easier than trying to plan a route that touches the streets you want to test! :-) I did the same thing when diagnosing the US/USouth issues I was having. Makes testing these type of voice changes really quick and easy!

    I have tons of Android devices, I guess I should setup iGo on one of them, just for testing purposes - would come in handy.

    Sent from my HP SlateBook 10 x2 PC using Tapatalk

 

 
Page 3 of 4 FirstFirst 1234 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.