windbag

As we have LEDs, which have a much longer lifetime that filament bulbs, we'll probably defer action until MOT in November. If they offered a free update to the maps at the same time, that would be a different matter...

Also checked - we have LEDs, not old school filament bulbs

Yes, our VIN put in that checker flags up that an action is required, consistent with our letter.

Thanks for posting the details. I did the same and yes, ours is subject to the recall. Ours is 2015, though, so maybe just that year?

We got one of these too. Sounds like it could be hassle, as the list given is only full retailers, not down to authorised service centres. If only full retailers, much further away & will be a considerable hassle. Why don't they make it worthwhile & offer to update our maps in the same visit ?

OK, stick with SD cards then; thought that might be the case.

Again, thanks for the info, that is really helpful. I'm a bit concerned it might get silly in how long it takes to deal with (?indexing?) larger cards when content-updated/put in the slot - as even 16 GB takes a while with only 1500 tracks on board. One final thing: do you know the size of the RNS-510 Columbus SSD?

Again, many thanks, that is categoric. I will consider the trade-off of increased mp3 file size vs seeing the play times in the car. Sad that the unit introduces such a need, when no other player I have does 🙁

I haven't a clue. I'm only using a 16GB one as a test, but I'm not going to do a "random buy" test of cards to find out. If someone KNOWS the biggest size a RNS-510 style Columbus unit can take I'm happy to get one, but it will need to be up in the Terabyte size to get everything on in one go. Just changing 16GB disks seem to take the system a while to deal with (index?) - I'm not surprised - how long does it take your Octavia III to be able to use a changed-content 400 GB card?

Many thanks for the decode. But if read your previous post correctly, it can't decode VBR track-lengths ? If so, I can forget trying to change my VBR generation process to enable it to do so.

Thanks, Langers2k, that explains why there is so much variety in he posts I came across. How do I identify which is in my car? If this helps: Skoda Superb MkII HW Vsn H27 SW Vsn 6276

Because: a) it gives a constant quality of coding for each frame rather than just spewing out data where it isn't always needed - I am doing a whole load of spoken word stuff, some with interspersed music - the file size difference is significant. Also true of much of the music I will be converting too. b) I have a LARGE set of files to generate, which won't fit on the max size of card that the Skoda unit will read, so will have to be broken up into related blocks anyway, so file size is very important c) It is my lifestyle choice for all sorts of reasons and to question such is really not the point - either the unit CAN be persuaded to read VBR files and give track-lengths - in which case I'm keen to hear how I might achieve such - or it isn't, and I can just concentrate on all the other mp3 players that do handle such files.

I had noted that these posts from July, 2014: https://www.briskoda.net/forums/topic/321349-different-audio-formats-on-the-sd-card/?do=findComment&comment=3849483 & https://www.briskoda.net/forums/topic/321349-different-audio-formats-on-the-sd-card/?do=findComment&comment=3851948 says "No time displaying problems with vbr", & "It seems this format is ok to handle for the car system" - so was trying to find out what my problem was. Looking here, though, it sort of implies it can't do the track length: https://www.briskoda.net/forums/topic/440051-columbus-questions/?do=findComment&comment=4947470 But this Feb 2017 post https://www.briskoda.net/forums/topic/424233-columbus-unit-not-remembering-last-trackalbum-played/?do=findComment&comment=4814816 shows a display which got VBR track-length right, as well as the progress bar and time left correct, and even displayed the artwork (!) - so I'm confused. I'm looking to generate many VBR mp3s, and would be sad if I later find I could have tweaked my process to enable the VBR track-length to work in the car. If it truly isn't "supported", it would be helpful if it was noted somewhere explicitly, as I've spent a fair bit of time & trouble trying to fix VBR files at my end. So my question still stands; has anyone got the Skoda unit to display the correct track-length for VBR ? - if so, by what encoding route/fixing method ? OR Is VBR track-length explicitly not Skoda supported ? - ie nothing I can do will help

Has nobody found a way to get a VBR mp3 file to show the correct track length? I found a thread on another forum which had a similar issue, but all the fixes suggested: VBRfix (Moonbase update) mp3val Foobar (Utilities/Fix VBR mp3 header) have not changed "VBR" displaying where the correct track-length should be on the Skoda player. In case it helps, I attach a typical mp3-VBR file (1.5 MB) that is doing this (and resisted all "fixing" attempts as described) African Waltz-Johnny Dankworth.mp3

Any tracks with fixed rate show tracklengths fine. It is just a VBR file issue.