Timing/Speed of voice commands
Hi,
I'm using Locus Pro some 2months now exclusively for navigation on imported GPX cycling tracks.( using bluetooth headset and without having visual information as the phone is in my jacket) The results are improving after getting the settings right. During my last navigation tour I still had few situations were I unintentionally got off track / felt abandonned :-). According to my opinion, the main reason was that on the one hand the speed of playing the voice command is to slow. If it starts saying that 'in 50meters you should turn right' ( +/- 4-5seconds... ) and you are going downhill 40km / hour, you might get to the point were you should turn but became unsure because of the voice command timing ( especially if multiple turn options are close one to another ). In addition to this ( as compared to my familiar car GPS ) it's missing the 'turn NOW' command. The last time it informs is 50m ahead... Ideally the voice commands come as little as possible ( sometimes on a lonely street , it says things like 'over 50meters follow right' were that's only a mild curve in the same road with no other roads in sight...), but as frequent enough to keep you comfortable and concentrate on cycling ( e.g. it never says 'continue straight ahead' even not if you are already several KM on the path when crossing much bigger roads where 'naturally' you expect guidance ). I'm unsure if this behaviour can be influenced by settings or could be caused by lack of quality in the gpx file. PS It also didn't bring me back 'best effort' --nearest point ? -- to the track after a miss. I had to manually get back on track and then choose 'nearest point / navigatte ' to restart further track navigation. But I now activated the option 'recalculate automatically according to route priority'. I didn't remember that setting when I searched it last time... ) Regards
Dirk
The same question
wow - lot of words but where is the idea?
wow - lot of words but where is the idea?
I updated to 'question'. Better fit for starters. Might endup as idea :-)
I updated to 'question'. Better fit for starters. Might endup as idea :-)
I suggest the advance notification could be based rather on time interval, than on distance. As the constant distance is too long for walkers, while too short for cars. E.g turning could be announced in 20 and 5 seconds.
With addition the time reference point would relate to end of message. So if the message lasts 3 seconds, it would start 23 or 8 seconds before the estimated time of reaching turning point.
I suggest the advance notification could be based rather on time interval, than on distance. As the constant distance is too long for walkers, while too short for cars. E.g turning could be announced in 20 and 5 seconds.
With addition the time reference point would relate to end of message. So if the message lasts 3 seconds, it would start 23 or 8 seconds before the estimated time of reaching turning point.
I mean, in 20 and 5 sec before turning point, it would say either time left, or the distance left to the turning point.
E.g. it would announce - eventually rounded to 5 or 10 m precision
500 m and 125 m for a car going 90 km/h
cca 110 m and 28 m for a bike going 20 km/h
cca 28 and 7 m for a walker going 5 km/h
It would be probably usable for TTS only, not sure if for recorded voice as well, if not possible to say general numbers.
I mean, in 20 and 5 sec before turning point, it would say either time left, or the distance left to the turning point.
E.g. it would announce - eventually rounded to 5 or 10 m precision
500 m and 125 m for a car going 90 km/h
cca 110 m and 28 m for a bike going 20 km/h
cca 28 and 7 m for a walker going 5 km/h
It would be probably usable for TTS only, not sure if for recorded voice as well, if not possible to say general numbers.
hi guys,
setting of navigation commands timing in seconds can be done in the config.cfg file that you can find in Locus root directory. It is a very advanced option that would meaninglessly complicate "common" in-app navigation settings, therefore we left this option outside.
hi guys,
setting of navigation commands timing in seconds can be done in the config.cfg file that you can find in Locus root directory. It is a very advanced option that would meaninglessly complicate "common" in-app navigation settings, therefore we left this option outside.
I see. But in that case it would definitely make sense to have independent config profiles for car / bike / walkers.... As one suit does not fit all, with cars 20-30 times faster than pedestrians.
I see. But in that case it would definitely make sense to have independent config profiles for car / bike / walkers.... As one suit does not fit all, with cars 20-30 times faster than pedestrians.
How does configured distance for advance notification, e.g. 100 m , exactly relate to below 15|35|300s ?
For a single value. e.g. 15s, I would understand it as whatever comes first 100m to turn or 15s to turn.
But what about all 3 values ? Or, does it apply to the last=smallest time value ?
As it is not mentioned in manual:advanced:customization:config
# NAVIGATION
# --------------------------------
# times before command, when Locus notify (in seconds), default is: 15|35|300
navigation_announcements_times=15|35|300
How does configured distance for advance notification, e.g. 100 m , exactly relate to below 15|35|300s ?
For a single value. e.g. 15s, I would understand it as whatever comes first 100m to turn or 15s to turn.
But what about all 3 values ? Or, does it apply to the last=smallest time value ?
As it is not mentioned in manual:advanced:customization:config
# NAVIGATION
# --------------------------------
# times before command, when Locus notify (in seconds), default is: 15|35|300
navigation_announcements_times=15|35|300
I'm not sure where in this discussion comes any "distance" values. Locus do not work with any distances during navigation. All is based on defined times (value from config.cfg) and average device speed ...
I'm not sure where in this discussion comes any "distance" values. Locus do not work with any distances during navigation. All is based on defined times (value from config.cfg) and average device speed ...
Well, I am sorry, you are right, my memory has confused me. :-D
I remember all the Locus GUI configuration is about distances. It is also true there are 2 distances in navigation ( recalculation + off the track trigger ) + 1 distance of in advance notification for guidance.
I have mixed it somehow, remembering wrong the advanced navigation notification is distance based as well.
So if, then it would have a limited application to guidance only. But as guidance is not usually used for cars, single common distance is acceptable for bikers and walkers.
I withdraw statements related to distances in navigation context, keeping just idea of independent navigation profiles.
Well, I am sorry, you are right, my memory has confused me. :-D
I remember all the Locus GUI configuration is about distances. It is also true there are 2 distances in navigation ( recalculation + off the track trigger ) + 1 distance of in advance notification for guidance.
I have mixed it somehow, remembering wrong the advanced navigation notification is distance based as well.
So if, then it would have a limited application to guidance only. But as guidance is not usually used for cars, single common distance is acceptable for bikers and walkers.
I withdraw statements related to distances in navigation context, keeping just idea of independent navigation profiles.
Replies have been locked on this page!