Waypoints and voice guidance
-
I have noticed that voice guidance seems to be affected by closeness to waypoints.
This week, I travelled a preplanned routes (ie with waypoints) and I noticed that voice guidance was not given if there is a waypoint near to a turning, either before or after it. I expected this if a waypoint is placed BEFORE a turning, as I read in comments on the forum that announcing waypoints takes precedence over voice guidance (even if waypoint announcements are not selected), but I was surprised that this also occurred even if the waypoint is placed AFTER the turning. When there were no waypoints nearby voice guidance approaching junctions etc was given correctly.
On the return journey I simply put in the destination ie an A tp B route with no waypoints. And voice guidance was consistent at each turning.
So I am wondering if this explains why voice guidance appears to be inconsistent? Is it because waypoint announcements are masking them?
-
@David-Bonner yes, could very well be!
If waypoints are present, they are announced by the HERE navigation. Eg: “You’ve reached your waypoint, it’s on the right”.Turn instructions are also completely taken care of by HERE. If turns and waypoints are close together, a choice needs to be made (by HERE). It makes sense that waypoint announcements are chosen as they are created by the user.
However, if you’ve turned off waypoint audio notifications, the turn instruction isn’t magically fetched. Resulting in no audio at all
I’ll have a look at the configuration options and see if anything is possible but I think this is just a really thing to deal with (sadly).
-
@Corjan-Meijerink Would an answer to this problem for both visual and voice guidance at turnings be to not display waypoints in the top left information box?
-
@David-Bonner unfortunately not!
-
@Corjan-Meijerink Thought it might not be that simple
but I am sure you will come up with an elegant solution.
Enjoy the rest of your break -
@Corjan-Meijerink said in Waypoints and voice guidance:
I’ll have a look at the configuration options and see if anything is possible but I think this is just a really thing to deal with (sadly).
Can you then scientifically determine how far waypoints shall be placed from these road occurrences?
Manks bu'j te bange.
-
@StefanHummelink No clue
-
@Corjan-Meijerink then we shall do it all empirically haha. Test route with successively placing the wp further from the junctions hehe
-
@StefanHummelink, That could well be dependent on the length of the voice guidance that remains unspoken, and therefore also dependent on your speed (just a hunch).
I am not affiliated with MyRoute-App. The help I am offering is entirely voluntary.
I am just an enthusiastic user, and hope you will be one too!Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
-
@Con-Hennekens Would be my guess as well. Hopefully Corjan can find some workarounds.
Waypoint announcement, or anything regarding waypoint(specifically waypoint, and not viapoint) should be lowest in hierarchy imho.
Turn instructions should definitely be of higher priority than anything waypoint related. In fact, I feel like the app should not do anything with the waypoints, except for using them to shape the route and show them.Manks bu'j te bange.
-
If only I could get access to the SDK source code
-
@StefanHummelink, Depends... Often you get directions 2 or 3 km in advance. I'd say they don't need te be high priority. Also a user generated message (what a waypoint really is) would be of higher priority than anything auto-generated. I think it would be a tricky discussion. But I understand what you mean.
@Corjan-Meijerink said in Waypoints and voice guidance:
If only I could get access to the SDK source code
I guess you would really like that!
