Started by Menion, September 03, 2013, 12:47:55
0 Members and 1 Guest are viewing this topic.
Quote from: menion on October 24, 2013, 17:54:30ah yes, this is correct. Whole TTS system is based on TomTom voices. And in these voices is only 50, 80, 100, 200, ... distances. And I use same system also for TTS.So problem is not incorrect distance above 50 m, but just incorrect spoke distance below 50 m? Then I'll fix it to next version, not a problem.
Quote from: tommi on October 26, 2013, 14:38:10I just prepared a test track (with brouter).Then I started the navigation test and it calculated the navigation.But not until the end of the input track. Only for the first 200 points of the input track.Is there such a limit in Locus?
Quote from: Joachim Buhl on October 27, 2013, 12:05:23Hi MenionI do not understand your edit. Did you find the problem we describe? Did you solve it? What did you fix?
Quote from: menion on October 27, 2013, 11:26:40About distance below 50 m - I wrote "hmm it will be worst, because texts have to be in text files". Currently you should hear notifications without distance for order 0 - 30 m before, for 30 - 65 m you should hear "50 m", for 65 - 90 m "80 m", 95 - 150 you should hear "100 m", etc ...I'm aware that is should be better (more precise), on second side I still do not have working solution for updating TTS navigation files