Skip to main content
Enthusiast II
November 18, 2021

Sonos no longer recognizing folder.jpg for cover art?

  • November 18, 2021
  • 126 replies
  • 7238 views

After the most recent upgrade to Sonos 13.4 (S2), I don’t see much cover art in the Sonos controller. More precisely, it seems that I see cover art if it is embedded into the MP3 file, but not if the cover art in a separate file called folder.jpg. In my collection, most albums have a folder.jpg, and only a minority of albums have embedded cover art. There are two reasons for this:

  • Albums that originally had on CD, cassette or vinyl.
  • For several years, Sonos was not able to display cover art that was embedded into the MP3 files that I bought, so I had to extract them to folder.jpg and remove them from the MP3 file.

Is any one else seeing this? Or is this just some accident on my system?

 

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

126 replies

AjTrek1
November 29, 2021

Hi

@Airgetlam makes a valid point about  “bugs” and how they are discovered and subsequently resolved. It’s important to understand that when dealing with multiple types of end-user hardware; testers look at general realities that cover most scenarios in the real world. There will always be those one-off scenarios that weren’t covered.

For example…writing code to auto alphabetize common last names that works 99.9 % of the time; but fails when a hyphenated last name is introduced. That’s a bug that the code writer didn’t take into account and therefore must enter a “what-if” line to fix the bug encountered by the end-user of the software. 

As mentioned by @Airgetlam …that’s probably the case here-in-point. 

Together Everyone Achieves More = T.E.A.M.
Airgetlam
November 29, 2021

One of the issues on teams I’ve worked on is that often people forget to make allowances for what are considered in the US “non-standard” characters, such as many languages around the world actually use, and are considered “standard” there. 

Not sure whether that’s the case here, just an example of unintentional bias that might not be caught by the assumed “small” number of beta testers.

On the other hand, I think they knew there were potential issues and decided not to make a public announcement. There were many a time when I was unaware of issues, and made the announcement in public about the feature, only to be inundated with “but it doesn’t work on my machine” from many customers. My guess is that’s why there’s currently silence. They, at the last moment, figured out there were issues, and it was too late to pull back the release, but they were able to not make a public announcement around the feature. 

All of that blows up as soon as the phone folks have told people about the feature, as indicated in previous posts, but, at least in orgs I’ve been in, CS is a different group than forum support folks, so there could have been a message that got lost between the various groups as to whether or not to talk about it.

This is all speculation on my part, mind you, based on several decades of software experience. It could be something much more nefarious….but I just have a hard time believing Sonos would be intentionally screwing its customers. It’s bad business to do that. 

Bruce
Enthusiast II
November 29, 2021

One of the issues on teams I’ve worked on is that often people forget to make allowances for what are considered in the US “non-standard” characters, such as many languages around the world actually use, and are considered “standard” there. 

Not sure whether that’s the case here, just an example of unintentional bias that might not be caught by the assumed “small” number of beta testers.

I can’t really see that this the issue in this case. But interesting enough, the issue I ran into in May was exactly that. Sonos One SL players botched non-ASCII characters when they indexed the music library. But for folder problem, I have not see any such correlation.

el rubio
November 29, 2021

I get the feeling that we are ‘guinea pigs’ and used as an extended test group across different continents to escalate which features are mostly not working

 
 
salu2.eu
Enthusiast I
December 1, 2021

Contacted chat support to add my case to the growing body of issues. Support asked for new diagnostics, submitted 547048099. Keeping my original thread up-to-date as well.

Got another confirmation that the issue is related to SMB2/SMB3, and that engineers are working on a solution with an unknown ETA.

World-Class Superstar
December 7, 2021

I'm happy to report that my system just updated to 13.4.1 and my cover art has returned. 

Enthusiast I
December 7, 2021

Can confirm @beynym's update: update 13.4.1 was offered (Android controller, Windows controller, and system). Album art still erratic though. Slow to load and far from complete in the Android controller, very slow to load but eventually complete, apparently, in the Windows controller. 

It may be significant that my Windows controller is connected to the Beam, which lies in close proximity to my router, while the Android controller insists on being connected to the One, which is much further away.

Enthusiast II
December 7, 2021

Sounds promising! I will have to find a spot for upgrading the system. That is, I need to close down stuff on my Windows machine, in case the upgrade decides to reboot Windows. Which it often does - without asking.

 

Enthusiast I
December 7, 2021

Album art issue is definitely still present in 13.4.1. Also, Sonos no longer switches to Dark Mode to match Android, and the Appearance setting that's supposed to control this has vanished. Thus far, not impressed with 13.4.1.

Enthusiast II
December 7, 2021

Yes, I see cover art after the update. Now, the past weeks it has been on and off, so it may be a bit too early to say for sure. However, I also see cover art when browsing albums, which I never did with 13.4 (unless I disabled SMB2/3 on the NAS). But as florismk notes, the cover art is coming quite slowly. I don’t have any issue with dark mode on my Andriod phone.

 

And, yes, the installation of the Windows controller rebooted Windows, without giving a warning.