Sonos no longer recognizing folder.jpg for cover art?

And now, without restarting anything, I suddenly see the cover art again. What I did do was to the music from from one zone to another as I went into that room and then I moved the music back when I was done. Exactly when the cover art started to appear, I don’t know.

It seems quite obvious that Sonos made some changes, but it is not as simple as that they are ignoring folder.jpg, but something more subtle. Maybe threshold for when to display or ignore has changed?

I'm not entirely sure why this has been marked as answered, or why the answer that has been flagged is even helpful.....

Nor am I. I’m also puzzled that someone else than me (since I started the thread) can mark something as the best answer. I guess that Spunk accidently pressed the wrong button. Since the issue is by no means resolved, is there any chance that you can revert your action?

I've asked the moderators to remove this Best Answer.

No, it wasn’t me. And I would be very surprised if someone other than the thread starter or a moderator could do that.

I suggest that everyone experiencing this issue submit diagnostics and follow-up directly with Support or here.

Pure speculation on my part is that there is a timing issue, probably related to communication delays between controller and player. Check the Associated Product for the controller that you are using as I suggested above. It is possible that one Association is struggling with communication. You do not have much control over which unit will become the the Associated Product.

For systems with only one wired network connection, the communication path can become quite contorted for floder.jpg. For example if ‘A’ is wired and the controller is Associated with ‘D’, it is possible that the communication path to folder.jpg could be: Controller - ‘D’ - ‘C’ - ‘B’ - ‘A’ - folder.jpg - ‘A’ - ‘B’ - ‘C’ - ‘D’ - Controller and I can’t speculate exactly how the controller might connect with ‘D’ or how ‘A’ might connect to folder.jpg.

A communication issue along the path to folder.jpg will introduce delays. Historically, the system has worked through all of this without bothering the user. It’s possible that previous releases had an artwork timeout of ‘x’ and this release has a timeout of ‘x/n’ and the system cannot respond fast enough.

Communication issues leave tracks in the diagnostics.

Another potential variable is how Groups are built. The first member of a Group becomes the Group’s “Coordinator” and all music for the Group passes through the Coordinator. If the Coordinator is struggling with communication, all players in the Group will suffer and overall system data flow will slow -- potentially introducing further delay in folder.jpg fetch. Building the Group in a different order might improve this sort of situation. Again, all of this leaves tracks in the diagnostics.

Same issue here! The artwork loads intermittently in the queue but never in the now playing screen.

Tried different wireless channels and a router reboot but no luck.

Is there any benefit in submitting a diagnostic?

Yes, a diagnostic and follow-up with support creates an ‘incident’. Corporations track incidents and respond by allocating resources to reduce support costs. Plus, the additional diagnostic contributes to a wider variety of cases to study.

But is there any point with sending diagnostics alone? The problem I have with calling support is the time it takes. Here in Sweden there is typical a waiting time of ten minutes or more, and it is only available 10-18, and that’s when I’m at work. Yes, I work from home, but still I’m at work, and I can’t bill my client for talking to Sonos.

Send the diagnostics and post the number here, Support will usually find the issue and respond. If we haven’t seen anything back by Monday we can request that Support staff look at the topic.

I just realized I have an un-updated controller on the Windows box I use for updating the Honda, firing it up now to see what it looks like there. And on Windows the 13.3 controller shows no artwork from the Music Library.

I doubt it is a delay issue here, I have my setup on SonosNet with 2 Wired Beams and a wired Arc. Channel utilization is 20-25% according to my RF monitor. This setup has not changed for many months now.

I have tried both a SonosNet connected Beam as well as an Ethernet wired Beam, both show the same symptoms. The Wired Beam and controllers are all on the same Gigabit switch.

Checking my Linux (non-Sonos) controller shows no artwork on the Music Library either, since it connects to the player directly it points to being a firmware issue on the speakers, not a controller bug.

Running this on a Raspberry Pi: https://github.com/pascalopitz/unoffical-sonos-controller-for-linux