Sonos no longer recognizing folder.jpg for cover art?

@Stanley_4 all that being on a Synology NAS using SMBv2/v3 ?

I’m using Synology DSM 6.2.4-25556 Update 2 and I can flip between SMB’s without any fuss, even while music is playing. There is no need to re-index my library.

Okay, this is embarassing. The good news: Android controller did switch back to dark mode. The embarassing news: my fully tagged and album-arted mp3 collection wasn't as fully tagged and album-arted as I thought. I’d gone through a major effort to get it all straightened out, and thought it had worked, so all album art issues in the controller were obviously Sonos’ fault.

Discovered yesterday that a significant portion of my files were still a mess, tag- and artwise. Fixed it all, and now… lo and behold… album art loads! I've watched with joy as every single piece of album artwork appeared on its album in the Android controller as I slowly scrolled through the whole list.

With two caveats:

1. It's still very slow, up to a second per album, sometimes more. Starting at the top and scrolling down fast before stopping halfway down the list, album art takes forever to show up. As if the controller insists on loading the album art for all the albums I've speed-scrolled past before loading the albums stationary in my screen.
2. It seems to be highly depended on consistent album-level tagging. Files in a folder don't necessarily have to have all album-level tags filled, but if they are, they must be perfectly consistent: album name, album artist, disc number, artwork, and possibly other fields as well. 

Anywayz, it seems like the issue is really fixed in 13.4.1 (except the slow performance).

One observation, not directly related to album art, but well to SMB2/SM3, and I’m too lazy to start a thread.

I have had some problems lately with adding imported playlists to the queue. I’ve added them, and after some seconds it has said that the last track could not be found, and nothing was entered. I’ve needed a couple of attempts. I’ve had some other problems recently which indicates that more general network problems, so it may not be related to SMB2/SMB3, but it seems that things work better since I re-enabled SMB1 on my NAS. It’s still a little funny, because if I add three albums (i.e playlists), it first says that the queue is only the songs on the first album, but the others shows up later.

Maybe Sonos still have some fine-tuning to do with their SMB2/SMB3 support.

I find that album art fetch is much slower on SMB2 and the SONOS controllers can be impatient. If the controller times out default artwork will be displayed. I don’t use imported playlists and therefor have no experience with missing tracks.

The last missing track could be due a classic programming flub. If items in list ‘A’ are numbered 0-1-2-3-4-5 and list ‘B’ is numbered as 1-2-3-4-5-6, how many itiems are in each list? An obviouls way to determine this is to use the top number as the list length. Unfortunately, this results in list ‘A’ having a length of ‘5’ and list ‘B’ having a length of ‘6’.

maybe I am just lucky or have more patience but I added my 25k tracks music library on my Synology NAS and all album art displayed well - same for the flac and mp3 directories I added - maybe this is because I only use macOS and Apple gear or my Sonos speakers are relatively new

Laughed too soon. No idea why it worked for a little while on Thursday. Problem is back in all its glory today. Even going back to SMB1 doesn't fix it.

Welcome to the “sometimes” club, mine come and go too.

Just to make it more frustrating the queue entries often get images while the currently playing image is blank.

I haven’t done a full-system power off and back on yet, maybe that would help?

Album Art is very erratic for me also. Definitely a controller issue - almost like an afterthought for the software or if it times out displaying simply gives up until there is another input to the controller. Comically my ancient iPad 1 with Sonopad will always display the artwork faithfully (I use this to display the song playing only)

Contacted support again. Issue is known and still under investigation. 13.4.1 was not intended to contain a solution, it seems.

EDIT: And switching back to SMB1 doesn't seem to help any longer.