Jerry33:
I was just out running errands in my MS, with my USB music playing as it generally does. Within the first 10 minutes, I had 2 instances of the infamous studdering problem... The frequency of those problems have been increasing in recent days. To resolve, both times it took me switching away from USB music and back to it -- with a very-slow-to-respond 17" in-between... so thinking about our back-and-forth here, I rebooted the 17" while driving... And voila.... After the USB reloaded the folder/track structure, music started playing again and I didn't have a single failure for the 20+ minute journey home. Could be coincidence and is far from a definitive test, but sure sounds like the age-old memory corruption problems we've known with older Windows releases for years and early drops of new OS where a big 'ol CTRL-ALT-DEL or "IPL" fixes things. ...oh, and just because I was a bit shocked, my MS remembered which track was playing on that USB stick and starting playing the same track again after the re-boot -- when the crazy thing doesn't always do it in normal use.
ArtInCT:
Thx for the thoughts. As I've played with 8GB, 16GB, 128GB and now something over that on my 256GB USB stick, I'm not running into the problem you or your friend had with MS not seeing or remembering the tracks... They are all there -- it's just playback of tracks have intermittent challenges. ...and there are other Media Player problems with even FM just stopping for a second or two every now and then -- not static, very much like MS was off attending to something more important than pump FM though the audio software...
I did see the discussion about Nav History - Thx - and cleared mine out just-in-case a few days ago when that new tidbit appeared here on TMC. I'm still having the odd 17" slowdowns, and of course the USB music problems I've had since day 1 of ownership. My previous Lexus and MBZ both allowed unlimited number of tracks with native iPod/iPhones, but IIRC with USB music sources documented a maximum number of folder/subfolder depth as well as total max number of tracks allowed. Tesla documents nothing, so, well...
Perhaps some of these pieces are falling into place as a new theory however... We know MS has some fixed amount of memory... Fine. Everything does. There are also definate bugs with USB support (plugging in a device shouldnt cause MS to go screwy as some other threads suggest) and some of us have recreatable bugs that Tesla also acknowledges as issues requiring a future firmware fix that has no ETA. IF Tesla's Linux OS though isn't robust enough to deal with memory fragmentation, or how to prevent memory leakage issues between their own apps, or they have not quite got down some of the task prioritization things that need to be very carefully managed under-the-covers, and some of their apps are not doing a perfect job limiting a maximum number of things that consume memory (Nav history, USB tracks?), well, what we're seeing as some of these issues and how a reboot at least for a while fixes things sure point to those being problems that Tesla needs to resolve. They are certainly not sexy things that will gain positive press if resolved, but in my experience many years ago helping debug some early virtual machine and mainframe OS multitasking development, if Tesla does not step up to the plate, as they enhance and add functionality to the apps they have, the warts will show themselves even more. (Which is what seems to be happening to me... I most always listen to USB music, but it seems the frequency of failures is increasing since I've taken delivery -- and I'm now on my 4th firmware level -- each doing a lot more than the one before it. Hummm.). My experience was problems unfortunately compound in these areas and they are some of the worst bugs to shoot and then resolve. I hope it's a lot easier than that for everyone's sake -- and just a Media Player App that made its way to market before it was really ready, and needs to be brought up to snuff. It would probably also help if Tesla would simply document in their owners manual what USB device types and music sources, bit rates, etc that they wrote their code to support, vs all the trial and error some owners are going through and perhaps causing problems doing things Tesla never intended.
Interesting though, isn't it? I think Elon really does need some good engineers, and not just to work on Autopilot.
===
I'll give some thought to limiting tracks and folders on my USB stick and see if that improves my situation. (
Sure hate being a Systems Engineer again -- and for free with something I paid top-dollar for. I thought I gave up that techie life long ago!)