You're absolutely right about car audio configuration making a difference. The time required between decision to instruct and audio playback is extended considerably when the interim must contain a handoff to a Bluetooth handsfree like that.DwarfLord wrote: Conclusions:
1. Car audio configurations can cause a 3-s delay in issuing instructions, which seems enough to lead to URs. Attempting to fix those particular URs by becoming more aggressive with junction-node placement (beyond the wiki standard), adding AGCs, etc. is probably not the best response. Unfortunately we don't know which URs might be due to this behavior.
2. Waze is said to take into account how long it will take to issue a voice instruction and to advance voice timing to compensate. The test showed no evidence that it does so, at least not with any precision. It is possible that Waze instead uses a rough guess at how long the instruction will take that does not differ from voice to voice. If so, one wonders how that affects timing of very long versus very short street names, if at all.
As for 2, Waze does account for that, but I don't think in the way you're thinking. It will start speaking sooner for particularly long phrases, but it won't account for the differences in audio playback methods (Bluetooth vs. phone speaker), I don't think. Perhaps part of the reason for this is that audio routing is typically handled by the OS, not the app itself, and sometimes other apps can sort of inadvertently force Waze to use Bluetooth even if you don't want it to. I would think that Waze could at least see where its audio was being output, but whether or not they've actually programmed to account for that is a different question.
Re: [Page Update] Junction Style Guide