TTS problems on One 3rd edition

I am running Bootloader 5.5136 and Navcore 9.205 in x50 emulation with vocalizer (tom).
I couldn't get any of the v7 Loquendo voices to work. It seems to work ok except if i have it speaking street names it will say "language en" on almost every street. Is there a fix for this?

Use NC8. If you want NC9, you could also try 9.024. It seems that NC is the only NC9 one that does not have the pronunciation problem. For some more suggestions, have a look at this topic (post #3): http://www.navitotal.com/forums/showthread.php?1133-TTS-Vocalizer-voices-(also-Dutch-Italian-and-German) .

I have found a solution, sorta. With my current setup (US & Canada 860.3128), I couldn't get the tts pronunciation to work correctly. When I tried a different map (US & Canada 860.3127) and then on startup re-selected my vocalizer voice (Tom), and then re-selected my map, and turned off my tomtom and turned it back on, everything appears ok.

Q: does 9.024 navcore work and look just like 9.205?

ludespeedny wrote:Q: does 9.024 navcore work and look just like 9.205?

They are so close, you won't tell much, if any, difference

ludespeedny wrote:I have found a solution, sorta. With my current setup (US & Canada 860.3128), I couldn't get the tts pronunciation to work correctly. When I tried a different map (US & Canada 860.3127) and then on startup re-selected my vocalizer voice (Tom), and then re-selected my map, and turned off my tomtom and turned it back on, everything appears ok.

What NC were you using here?

I am running 9.205se navcore

I'll try that and see how it works.

tendriver wrote:They are so close, you won't tell much, if any, difference

ludespeedny wrote:I'll try that and see how it works.

If you solved your problem, why change?

I have another issue I want to see if it will fix, with the poi's showing the info instead of the "call" button

The trick with reselecting the voice and map and rebooting the device did not work for the US & Canada 860.3128 map?

ludespeedny wrote:I have another issue I want to see if it will fix, with the poi's showing the info instead of the "call" button

I thought I answered this question here: Navcore differences 9.101> 9.2

Megalos wrote:The trick with reselecting the voice and map and rebooting the device did not work for the US & Canada 860.3128 map?

It did not work for me either when I had that map, try switching to 860.3127 map or maybe just switch the "cphoneme.dat" but I have not tested that yet.

Yes you did, and appreciate it. But now I am just being anal and want to figure everything out related to poi's and the so I can use some programming skills in the future to help people out. I have made a little progress so far with the crpoi.dat file, but still trying to figure out how it all works together.

tendriver wrote:I thought I answered this question here: Navcore differences 9.101> 9.2

Megalos wrote:The trick with reselecting the voice and map and rebooting the device did not work for the US & Canada 860.3128 map?

ludespeedny wrote:It did not work for me either when I had that map, try switching to 860.3127 map or maybe just switch the "cphoneme.dat" but I have not tested that yet.

Megalos is asking you a question, not stating that he has the same problem.

No, LOL, I was not referring to my situation (I don't even have any USA maps, I live in the Netherlands), I was just curious about your situation. I'm trying to find a solution to the problem of the weird pronunciation, as a lot of people have this. Apparently this solution does not work with every map, I just wanted you to confirm that. But thanks anyway ;-).