Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 1 of 4 123 ... LastLast
Results 1 to 10 of 32

Thread: Audio Problem

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

    Default Audio Problem

    I have Primo 2.4 on my Samsung S5 phone. It works fine with TTS and everything. Except that it says "1st Street", not "First Street", "2nd Street" and not "Second Street", etc. I made what I thought were the correct changes in the voice config_transform_tables.lua file but I still got 1st and not first. Anyone got an idea? Thanks.

    EDIT: I tried a different version but that didn't work too. Wonder if it's a map thing?
    Last edited by chas521; 20th December 2015 at 15:57.

  2.    Advertissements


  3. #2
    Important User

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

    Default

    You mean it pronounce 1st as "one" "s" "t" instead of "first"?

    The brute force solution is to defined it under dictionary.voice
    [words]
    1st="first"
    2nd="second"
    :
    !_a**="Australia"
    :

    But it is cumbersome especially if you have like hundreds of them. So we need to find a way to defined it via pattern.

    Under config_numbers.lua there is definition for
    ordinals = {
    {L"first", nil, nil},
    {L"second", nil, nil},
    {L"third", nil, nil},
    {L"fourth", nil, nil},
    {L"fifth", nil, nil},
    {L"sixth", nil, nil},
    {L"seventh", nil, nil},
    {L"eighth", nil, nil},
    {L"ninth", nil, nil},
    {L"tenth", nil, nil},
    {L"eleventh", nil, nil},
    {L"twelfth", nil, nil},
    {L"thirteenth", nil, nil},
    {L"fourteenth", nil, nil},
    {L"fifteenth", nil, nil},
    {L"sixteenth", nil, nil},
    {L"seventeenth", nil, nil},
    {L"eighteenth", nil, nil},
    {L"nineteenth", nil, nil},
    {L"twentieth", nil, nil},
    }

    If somehow we can use that definition and pattern like (for all the 'th)
    ;numberTH spacer
    /(?i)([\s,\.]r_art_s.*[\s,\.][1-9]+)([tT][hH][\s,\.].*r_art_e[\s,\.])/-->"\1th"

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

    Default

    You are correct stating my problem.

  5. #4
    Member +
    Join Date
    Nov 2015
    Location
    In my bed
    Posts
    75
    Rep Power
    49

    Default

    Fist of all make sure you have the right words like : second, third in file: config_database.lua
    Probably you use wrong voice file and you have in config_database.lua words like 1st....2nd...
    1st and 2nd lua uses when you gps said: turn at second left or take the third right for example.

    I don't know actually what had you tried...but I think if you mod lua file :config_transform_tables.lua you must resolve your problem...
    Do you have this in this file? :
    module("VOICE")

    transform = {}



    transform.roadname_abbrev_table = TRANSFORM.new({
    {1,L"Tunnl",L""},
    {1,L"Tunls",L""},
    {1,L"Tunl",L""},
    {1,L"Tunel",L""},
    {1,L"Tunnel",L""},
    {1,L"Avnue",L""},
    {1,L"Avn",L""},
    {1,L"Avenu",L""},
    {1,L"Aven",L""},
    {1,L"Ave",L""},
    {1,L"Av",L""},
    {1,L"Cntr",L""},
    {1,L"Cnter",L""},
    {1,L"Center",L""},
    {1,L"Centre",L""},
    {1,L"Centr",L""},
    {1,L"Cent",L""},
    {1,L"Cen",L""},
    {1,L"Ctr",L""},
    {1,L"Strt",L""},
    {1,L"Street",L""},
    {1,L"Str",L""},
    {1,L"St",L""},
    {1,L"unnamed",L""},
    {1,L"unnamed road",L""},
    etc
    ..........................................

    Try more, writting this key words....but writting in front of this package.....
    {1,L"what you are listen",L"What you want to listen"},

    Keep in mind that TTS works in Android extremely in other way from WinCE....no matter what map you are using or if you are using nextgen or igo android...

    Hope you solve the problem

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

    Default

    [Only registered and activated users can see links. ]


    I did this a couple of weeks ago. I kinda know what I'm doing - I think. Still pronounces 2nd and not second.

    EDIT: Does anyone else have the same problem with numbered streets on Primo 2.4 Android? If no problem, what program are you using?
    Last edited by chas521; 20th December 2015 at 22:10.

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

    Default

    Quote Originally Posted by osiris4isis View Post
    You mean it pronounce 1st as "one" "s" "t" instead of "first"?

    The brute force solution is to defined it under dictionary.voice
    [words]
    1st="first"
    2nd="second"
    Tried this; didn't work. I'm sure there's an answer somehow. It's gotta be.

    EDIT: I just ran a simulated trip through Manhattan [New York City] where almost all of the streets are numbered streets. It was fine. For example. 45th Street was said as Forty-fifth Street. I live where a couple of the streets are one-digit numbers. So maybe it's only the small numbers that have the problem - that's now confirmed.
    Last edited by chas521; 21st December 2015 at 22:13.

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

    Default

    I wonder if the maps have the single digit streets as "1<space>st", 2<space>nd", etc... When I was having the "US/USouth" issue, I found that it was "U<space>S" in the maps, which caused the TTS to originally say "U South" instead of "U" "S".

    Have you tried overriding the single digit streets like 1<space>st="first" in the dictionary.voice file instead of 1st="first"? Just a guess...

    Sent from my HP SlateBook 10 x2 PC using Tapatalk

  9. #8
    Important User

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

    Default

    @jtrosky that is a very good point. There are many ways to do this, but unfortunately the easiest is to direct substitute. That is what I did when I tested a 15th Street on MyWay (old voice format) and it works ok. I don't have any street less than 10th in my area to test.

    @chas521 the direct substitution should work, but it will a pain to do for hundred of 'th streets. I think we need to solicits expert on how to do it "correctly" via pattern matching.

    We first have to id where street name are checked. Separate the difference between "direction" and "street name" passed to the TTS engine. Then we have to make sure that it's correct format: <number><st,nd,rd,th><whitespaces><street,drive,...> then substitute correct pattern (1 -> one, 101 -> one hundred and one, etc...)

    Update: I found a voice file that works. It has config_transforms.lua defined
    Code:
    Please Login or Register to see the links
    It uses the following but I commented out the first pattern
    Code:
    Please Login or Register to see the links
    Now I'm trying to figure out how to prevent "N Ave" from being pronounced as "North Ave"
    Last edited by osiris4isis; 22nd December 2015 at 11:37.

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

    Default

    Here's what I tried in the dictionary voice file: 1st="first", 1 st="first" and 1_st="first" and nothing worked. Maybe I just have to live with it. It's not the worst thing but it's not 100% if you know what I mean.

  11. #10
    Important User

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

    Default

    Post your voice file. I modded "Joe 2" voice file (I think originally posted by Mike Hunt) and it seems to work. But it doesn't have alert voice, so I need to see if I can mod "Samantha" (also from Mike Hunt) and see if it works. I'll post it after testing.

 

 
Page 1 of 4 123 ... 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.