Noch keine Lösung und auch keine Antwort

[Peter Schiefer]

schon mit beta 304 beschrieb ich ein Problem zu meiner 8 km Testrunde zum Gym.
Habe heute, um vielleicht selbst Ursachen zu finden ein paar Änderungen vorgenommen.
Hinweis: Gelbe und grüne WPs sind so attributiert, dass sie angesagt werden, ebenso klar das Ziel als roter WP. Tatsächlicher Start ist vor WP1 grün.
Blaue WPs enthalten Ziffern, keinen Infotext und werden somit nicht angesagt.
Route hin zum Gym
Bild Hier

WP 8 etwas vorgezogen, somit nun genug „Zeit“ um den WP als auch die folgende Abbiegeanweisung anzusagen. Zuvor war der WP nach der Abbiegung vor dem Kreisverkehr und es fehlten Ansagen.
Auch im Krriesverkejr „Nehmen sie die 2. Ausfahrt ist korrekt, Car mode im setting

Alles somit, unter wohl notwendiger Beachtung von Entfernungen, in Ordnung. All notwendigen Ansagen wurden genannt, die blauen WP, sind ohne Ansage

Jetzt Bild der Rückfahrt identische Strecke.

Alles beginnt wie erwartet und ist richtig bis zur angesagten Abbiegung nach angesagtem WP4
Zu WP5 bis 7 erfolgt keine Ansage. Erst die Zielankunft wird ab 1000 Meter zuvor angekündigt.

Corjan, was funktioniert da nicht? Das ist unbefriedigend.

[RetiredWingMan]

@Peter-Schiefer waypoints 5, 6 & 7 won't be announced as they contain numbers.

[M. Schrijver]

Ich habe das gleiches problem. Deine einstellung fur ansagen steht auf alle, nicht nur auf "Via"?

Wann ich die einstellung auf "alle" eingestelt ist. functioniert das ansagen auch niet correct bei mir. Wann die einstellung auf "Via" steht is alle schon gut bei mir.

[M. Schrijver]

What you mentioned about MRA Next confirms what i found.
When i have a Viapoint with a note. I set a shaping point a few hunderd meters (300-500) before the Viapoint just like you do.

What happened to me was:
I tried it once for a section of a trip and the behaviour of MRA Next was very bad.
Around 70% of the shaping point were announced as "next stop" or something like that (i don't know english translation of the dutch announcement).
Most direction changes (crossings, etc) were not announced anymore.
Autoskip behaviour was a mesh.

My mood was pretty bad right now. So i switched from "All" to just "Via" for the announcements.
Everything was nice and silent around shaping points
I did get direction changes announcements again
Autoskip was pretty much back at a level as it should be.

For me:
I don't want to touch the screen anymore after i start the route. The software needs to fix all the shit what comes along when i'm riding. No input from me what so ever should be needed. Just riding and follow the route as best a i can. The Software must do his job to make sure i can follow the original route as good a possible.

I don't like Viapoints because you need to skip them manually when you missed one for what ever reason. But i like the functionality of it. So setting "Waypoint Messages" to "All" would be the solution for me. But this creates a lot of other shit.

MRA does have some work to do.

[M. Schrijver]

For me. Every point i need skip manually is 1 too many. Because i need stop to skip it properly.

Nearly all my routes i created are for myself. Which i ride with my wife and/or a few friends. Therefore i don't need to plan lunchstops etc. I stop when i see a nice spot. Usually every 1-1.5 hours. In the meantime i demand from my navigation software that it guides me, so i can drive the route as intended during planning.
When i take another direction for whatever reason. I expect from the software it brings me back to the original route without any nagging of complaining. Nothing more, nothing less. Every time again and again.
When the software is constant telling me i do something wrong. Then software is doing something wrong. It just need to shut up and guide me.

I like to drive and i like to enjoy the scenery. Because of these 2 things i don't have the time and i don't want to fiddle with the navigation software when driving.
As you can see. I do not require a lot of features but the things i use needs to be 100% perfect in operation.

Because The Netherlands is a pretty densed country with a lot of roads. A route over the backroads with a length of approx 250 km requires around 70 points to get a good reliable route which can be shared with others.

[Con Hennekens]

Forgive me if I have not read all details above. I just want to handout some thoughts.

• Voice announcement for VIA points will take place 2000 mtrs before you reach it
• Voice announcement for SHAPING points will take place 750 mtrs before you reach it
• The above two rules ONLY apply when there are NO other shapingpoints within that distance. If there are, the announcement will take place AFTER passing that shaping point.
• Waypoint announcements take precedence over navigational instructions. Therefore it can happen that those are limited. This is especially the case in test scenarios where waypoints are usually closer than in normal scenic routes.

[Con Hennekens]

@M-Schrijver said in Noch keine Lösung und auch keine Antwort:

When i take another direction for whatever reason. I expect from the software it brings me back to the original route without any nagging of complaining. Nothing more, nothing less. Every time again and again.

The app cannot read minds. It does bring you back on the route. You can not choose to "disobey" and then blame the app for it. And it does not nag, but keeps giving you suggestions.

I do not require a lot of features but the things i use needs to be 100% perfect in operation.

That will not ever happen in a less than perfect world

[Con Hennekens]

@Peter-Schiefer said in Noch keine Lösung und auch keine Antwort:

A voice announcement vor a VIA Point 2000 m before set point on the road only once is absolute bad.

I agree with you that this is a rather long distance. The idea behind it is probably that especially VIA points are most important to be announced in due time, also at higher speeds. We do however have enough tools to limit that distance to a self chosen one, by placing a shaping point. in advance.

As to why in some circumstances it does not work like you expect, I really have no idea ;-). I have been testing this feature some time ago, and I must say it never let me down. Maybe some things have been tweaked in the meantime. I'll try and test again.

[Bouke Ent]

i see that every person has it own idea about his way of planning and travel. i do understand all sides but that does not mean that it would fit in everybodies world of planning and travel. there will always pros and cons. peter is looking for his ideal cabrio software and maybe MRA will give him 90% of his wanted functionality. I hope he will use MRA and will be able to find solutions that work for him.

[M. Schrijver]

@Con-Hennekens
The Via and SP announcements can interfer with direction announcements. If you know this. You can overcome this upto a certain level in the routeplanner.

But.......
What happened at this moment. Because of this interference between Waypoint announcements and direction announcement. It causes that sometimes direction announcements will be gone for a longer period. Even when there are no waypoint announcements planned ahead.

[Con Hennekens]

@Peter-Schiefer said in Noch keine Lösung und auch keine Antwort:

So, for 2 km you have 1 minute and more to react on this announcement. This is real a to long time to have your eyes on the counter too while driving or at the CarPlay screen

Well, Information about "must-stops" (that's what VIA points are!) is VERY welcome in due time, and 1 minute is nothing too soon at all, since often you have to look out for a safe place to stop. Besides, you should not drive with your eyes on the counter.

It's your calculation, but I think it is pretty perfect as it is.

[Con Hennekens]

@Peter-Schiefer, I am sorry, but it is difficult to decipher what you mean exactly. To be honest I don't think your argumentation is less weak than mine. Also not many members have posted the same suggestion, which I think you are persevering too strongly. Devs are reading along and will make up their own mind about it. Maybe you will get lucky. But for now let's agree to disagree.