TTS voice disappeared just like that ...

Started by Marcus Aurelius, July 21, 2015, 14:44:57

0 Members and 1 Guest are viewing this topic.

Marcus Aurelius

Last weeks I was cycling in Mallorca. I used Locus Pro with the BROUTER engine since GraphHopper, seems not to cover the Baleares within the Spain area, but this just beside.
As a TTS, I am using SVOX Classic TTS Nld (a dutch voice, bought). The installing process was perfect, tested it in Belgium.
In Mallorca it worked perfect, nice navigation spoken very clearly. For one reason or another I could just navigate a new route and not just follow a gpx track with spoken commands, but okay, since the waypoints were that close, it was mostly the same route.
But after seven days or so of intensive use, at a certain moment the spoken command just disappear. Instead there came a useless triple beep in place. Whatever I tried, selecting, unselecting, nothing could solve the problem. If I select it, there is a clear signal 'proces succesvol' in dutch, but no commands, just beep-beep-beep ... Has anyone any idea how to solve this issue ?
  •  

Menion

Good day Marcus,

unfortunately from your description, I'm not perfectly sure I may help, but let's try it ...

- "Navigation" in Locus do not use beep signals so what comes on my mind - were you using "Navigation" and not "Guidance"? Because in guidance mode, you may define something like this - three beeps, etc.
- you wrote "not just follow a gpx track" - hmm why this? When you tap on a track and choose "Navigation", nothing happen?

If you are able to simulate it also at home, some screenshots may be useful.
- Official help (ideas, questions, problems): help.locusmap.eu
- Advanced topics, sharing of knowledges: you're here!
- LM 4 Beta download, LM 4 Release download
  •  

Marcus Aurelius

#2
I will try to explain what is my modus operandus. Since I know the isle Mallorca very well, I wanted to make a complete cyling network for the region. I started to design in Basecamp with the implant of the most logical cycling traffic points. (about 400 waypoints) From these points off I made GPX routes in two directions. For instance, Point M005 en point M006, brings up finally two gpx tracks named, M005 to M006 and M006 to M005. All the hard waypoints as well as the gpx tracks I do send them to LOCUS
It would gives me the freedom, as I thought to use as well 'the built in navigate tool'  to go independently directly a KNOT, a hard waypoint, as to guide me along the gpx track. The tools on the gpx track (navigation and guidance) seemed to work fine in the beginning. If i tap on the gpx I have the choice between navigation and guidance. Navigation there seems still to work. (a bit difficult to simulate it at home). Guidance just gives me a few beeps, and I really dont know how I could handle it usefully. But what I mostly did was just hitting the knot waypoint, navigate straight to it, and checking out the accuracy of the route made in Basecamp comparing it to my knowledge and to the route navigation made in Locus to the next point. This was a pretty usefull powerfull tool to check up the real road later on with the initial one. For six days, this worked pretty fine, but then just during a trip, the navigation option to a knot, did not give me spoken commands anymore, just soms useless triple beeps, So, it seems, I still have commands when I tap on a gpx track and use the 'navigate' option. But no commands with the navigation to a knot. Just triple beeps then. Also 'guidance' along a track seems not to work, but I must admit, that I dont know what I may expect of it, since it never worked in a way as I tought it should work, namely with spoken command to along the track. Concerning your issue, about the triple beep, I noticed too that locus could be in a kind of guidance modus inspite I use the normal navigate option, directly to a point. Hope you understand the issue better now. Thanks to help me out.
  •  

Marcus Aurelius

Another test yesterday. There is a weird change in behave now. When I select a gpx track on the screen, it drives me again perfectly to and trough the track even if it's far away. (navigation and not guidance) Only some strange commands occur which I never heard before as '150 m op zeven uur' (150 meter at seven o'clock) But okay can handle that.
But if I select instead a waypoint to navigate to, there is still the triple beep as I mentioned ... And this worked perfectly earlier...
Really dont have a clue what is going on here ...
  •