Beta Issues Encountered
-
Folks,
I am using Next Beta 3.2.8 - 151 with an iPhone 15 Pro Max. I used it on a ride yesterday and encountered the following issues:
- The app intermittently did not announce turns. I had to use the visual map to see my next turn.
- I ran into a detour. The app continually attempted to re-route me back to the turn that I missed. I would have expected the app to re-route me onto a new route to get me back on my route. No try to re-route me to the missed waypoint/turn.
- When the app announces the next turn, it mutes my music (I'm using my Music app with my local library) which is correct. However, it does not restart the music when it is finished with it's announcement. I have to manually restart the music.
Thanks,
Joe Rebele -
@Joe-Rebele Thanks for the feedback!
- Voice improvements will be further configurable / improved in a later update. Was there any consistency in your issue?
- Were you navigating A-B / a track / a route? That really determines the logic of a recalculation. With A-B it will always calculate a new fastest route when deviating (ofcourse this can still differ with your personal opinion ) - in track navigation the app wants to keep you on the original track as much as possible - for waypoints it always calculates a new route including the waypoints you still need to pass.
- This indeed happens sometimes with different apps / BT device combinations and is something we wish to improve (as with 1.) before the release.
Thanks again for the feedback
-
@Joe-Rebele, for
-
I think the auto-skipping of waypoints could be your problem. That is not functional as yet, and could be the reason it is guiding you back to a turn that is close to that WP.
-
I have not tried yet myself (I love the sound of my boxer too much I guess). Bu I am hoping it will not mute music, but rather lower the volume instead. @Corjan-Meijerink?
-
-
@Con-Hennekens It's called "Audio ducking" - meaning that the phone gets an instruction to lower the volume of other sources as a higher priority voice prompt needs to be played.
After that prompt is finished - the other sources continue playback at the original level.
However, if something goes wrong (due to our app / race conditions of multiple sources or a wrong implementation of the other app - which is possible too) the other sources can remain muted.