Doctor Glyndwr wrote:
We're not going to get much further without data. Ideally we'd need to establish some correlations, e.g.
1) played to x min y seconds: resumed fine
1) played to a min b seconds: resumed at c min d seconds
The questions are: for what maximum value of x:y does it go wrong, and what can we deduce from how a:b maps to c:d?
Well it's not the 59m59s thing, otherwise it'd simply refuse to handle tracks longer than that, or not display the elapsed time correctly, as it clearly does on my video earlier in the thread.
(Interestingly, the aftermarket Dension kit I had fitted to the Merc could only display 59m59s and then rolled over to 00m00s, but nonetheless it remembered which 'chunk' of 59m59s it was on, so clearly was recording an extra parameter somewhere behind the scenes. From the track in the video for example, it would display 73m11s as 13m11s, but would in fact resume play correctly from 73m11s.)
Thinking on further with the behaviour I've observed, on the first occasion I noticed it occur it actually resumed from the last but one point
in the previous track it had played. i.e. I turned the car on and it should have resumed playback from near the start of the track 'Voices of Autumn', but what it actually did is go back to near the end of 'Neverending Melodies', which is the track that had been playing the last but one time I turned the car off. So it's not even like it just went right back to the start of Voices of Autumn as it can't go further back than 00m00s in a track, so it was definitely storing the previous value of its last but one shutdown point, and resumed from there. (i.e. It doesn't just go back a certain distance in the current track, but retrieves both the track and position from a previous shutdown, changing to that track if required.)
As for collecting the data you correctly identify as being required to take this further, that's not realistically going to happen with just me using the car for pretty much identical commutes the vast majority of the time, and with the intermittent nature of the problem it'd be hard to conclude if the bug occurred in a 50 minute track but not in a 40 minute track, that the 50 minute duration was definitely the issue, as it might just have behaved itself properly for the 40 minute track by random chance but the problem could still occur on a 40 minute track in the future.
We need more people with 2010 Audis fitted with the MMI-3G 'High' system, running the same software revision as mine, to perform further testing. That would possibly be overkill.
Attachment:
trackerso.JPG
Register
Calendar
FAQ
Search
