Recent Sonos update is broken on non-ASCII characters in file names


Userlevel 1
Badge +2

It appears that the recent Sonos update, 13.1, is broken with regards to non-ASCII characters in files when updating the library. I have a job that daily generate 30 playlists, and the format of the name of the playlists is Pnn Artist - Albuim.m3u. They are located on a NAS from Synology that I have had for quite a few years.

For instance, there is a file of which the name is P05 - Järngustav - Tiden läker inga sår.m3u. But in the Windows controller, this appears as P05 - Jrngustav - Tiden lker inga sr.m3u. In the Windows controller I see a square with a cross in instead of the å and the ä. Another example is P23 Cicala Mvta - Live at 磔磔- 結成20周年記念.m3u. Here all Kanji characters comes out as question marks. And it is not only matter of prettiness; when I open the list, there is nothing there, and I can’t put it into the queue.

This was working without problem until yesterday, until it was broken. It obviously needs to be fixed - and fixed soon!

 

Corry P 1 month ago

Hi everyone,

 

Just wanted to let you all know that this issue has been resolved in the latest S2 update (13.3).

 

Please update your players and let us know if you continue experiencing this issue by contacting our customer care team via phone or live chat.

View original

37 replies

Userlevel 1
Badge +2

I made a test and changed the settings for the music library, so that I removed the share for the playlists on the NAS, and instead I mapped the music library to read the playlists from my Windows machine. This changed things to the better, so that file names now appears correctly in the Sonos app, and the files on the playlists are visible.

So it appears that this is only an issue when reading files from Linux, or possibly certainly flavours of Linux.

While this is a workaround for me, I still prefer to have everything on the NAS, which has a higher uptime than the Windows machine.

 

Userlevel 7
Badge +17

Hi @Erland Sommarskog and others!

We are aware of this new issue and are working on a resolution. As yet, we do not have a time-scale for the fix.

This issue is affecting Sonos One SLs only. If you’re unable to index successfully, you may be able to by switching off any SLs. It also only seems to affect NAS shares (or as you’ve discussed in this thread, Linux).

Apologies for any inconvenience.

Userlevel 7
Badge +22

<Rampant speculation> so the SL has a different SMB stack than every other device? Perhaps it is a sign of a “modern” SMB implementation that will eventually support SMBv2 or v3? </RampantSpeculation>

Userlevel 7
Badge +17

<Rampant speculation> so the SL has a different SMB stack than every other device? Perhaps it is a sign of a “modern” SMB implementation that will eventually support SMBv2 or v3? </RampantSpeculation>

 

<RampantIgnorance> No clue. </RampantIgnorance>

Userlevel 7
Badge +17

<Rampant speculation> so the SL has a different SMB stack than every other device? Perhaps it is a sign of a “modern” SMB implementation that will eventually support SMBv2 or v3? </RampantSpeculation>

 

<RampantIgnorance> No clue. </RampantIgnorance>

This is not strictly true, but more humorous than the standard “nothing to share” response. :grin:

Userlevel 2
Badge +2

Thanks for the background. Why would they introduce a 'fix' to only one component?

Not only is this a massive step back in my opinion (as there are ways around the SMBv1 issue) but it now makes a rock solid Sonos experience unwantedly flakey.

I was seriously unimpressed to hear back from Sonos support today to let me know this is a known issue when yesterday the individual was happy to blame my Synology NAS! This individual was unable to give me an timescale for a fix but suggested I re-tag my music library! 

So not only was my time wasted investigating non-existent issues with my NAS but apparently I have to spend further time identifying and changing the metadata for my entire music library!

The main point here is that the way my artists, folders, files etc. are tagged IS CORRECT - Anders Trentemøller's surname is not Trentemoller so why should I re-tag my music to overcome an issue caused by Sonos? This is especially unwelcome advice when Sonos supports the correct character set when the music is not indexed using a One SL as the Associated Product.

Why introduce inconsistency into the ecosystem?  I've invested too much money and time into my Sonos system to 'lose' large chunks of my music library and I don't take being fobbed-off kindly. 

I also reject the implication by Sonos support that my time is of little importance of value and that I should spend it changing my music library so it works with a poorly regression-tested software release.

 

 

Userlevel 7
Badge +22

What codepage are your playlists in? Is there a BOM on it? Was there a Synology update recently (I ask because I’d be surprised if Sonos changed something as frozen-in-time as imported playlists).

Userlevel 7
Badge +22

I applied an update to Sonos yesterday. It was over a month since I last applied an update to the NAS.

I believe the NAS is running Linux, so I would expect file names to be in UTF-8. I would not expect there to be BOMs in the file names. (The playlists are actually created on a Windows system, and then copied to the NAS. Thus, the names are originally in UTF-16LE, but that is not a concern to Sonos, as Sonos does not know about the Windows system. And, yes, I did check the names on the NAS before I made my post.)

The issue is not isolated to Playlists, but names are broken when I check the Folders node as well. In fact, here is also some extra confusion, because some artists with non-ASCII characters appear multiple times.

So it seems to be a general problem in how file names are read and stored.

I misunderstood, I thought the problem was with paths in playlist files, hence my speculation regarding BOMs.

I know nothing about Linux, but I do know that Sonos generally uses UTF-8 for its strings, as that is how UPnP works. I assume other clients of this NAS see those files correctly?

Could Sonos have finally updated the Samba client in S2 to no longer need SMBv1 and introduced this bug? That is the only reason I can think of they would touch this code with a 10ft barge-pole.

You should probably create a diagnostic and submit it to Sonos support, and also share what NAS you are using for others to chime in.

Badge

It is equally broken if your NAS share is a Windows Server 2019 box.

 

FYI from debugging what filename the One SL is requesting, my guess is that it is scanning/indexing correctly in UTF-8 but sending the encoded name request as (I’m guessing) ANSI, which the fileserver perfectly reasonably cannot then find.

 

The work around is to start music on another (non-SL) speaker and bring the SLs into that group. The other speaker will be group leader and will request the correct filenames. You can then zero the volume on that speaker, leaving the SLs playing the music as desired but within that group.

Userlevel 7
Badge +17

When the app opens or reconnects, it says “Hello?” and whichever player responds “Hello” back first is the associated player. If the wired unit is busier than another player with other tasks (likely), then it may not be first responder.

Userlevel 2
Badge +2

I've experienced the same issue where the artists and albums containing non-English characters e.g. Scandinavian we're not appearing in my music library, despite having been visible previously.  After lots of testing I can confirm that the issue has nothing to do with my Synology NAS and relates to Sonos systems where the Associated Product is a One SL.

I have 2x One SL in my system and one of these was my Associated Product. Each time I updated the music library I had lots of missing artists & their albums from artists such as Trentemøller.

After some testing, the following work around resolved the issue for me:

1. I powered off both One SL and restarted the Sonos Controller which forced a change to the Associated Product.

2. I then powered on both One SLs and manually updated my music library and the missing Artists and albums reappeared.

It is disappointing that this issue has been known about for a couple of months and Sonos have not yet provided a fix. Hopefully a fix will be provided very shortly.

I have contacted Sonos to ask them to let me know when this issue will be fixed or to arrange to replace my One SLs with Ones.

I hope this helps others in the short term and that Sonos provide a long-term fix.

Userlevel 7
Badge +22

The One SL has  different SMB stack than every other Sonos device. The speculation is that this is to finally fix the SMBv1 problem that NAS users complain constantly about for years.

Moral: be careful what you ask for.

This new stack is clearly broken, and as I assume Sonos did not create it, they have to wait for the owners of whatever package they picked up to fix it (I assume it is Samba, the old stack came from them and what a pain that was to integrate into the build system).

Or they could put back the old SMBv1-required stack.

Userlevel 1
Badge +2

I called Sonos support to report the issue, but lo and behold: they had a solution! In my NAS (a Synology DS213), I was told to go to the Control Panel, and then select File Services. There is a tab SMB/AFP/NFS. In this tab, select Advanced. In this UI there is “Max SMB-protocol” and “Min SMB-protocol”. They should be set to SMB2 and SMB1 respectively. I applied these changes and restored the setting for the music library to use the NAS for the playlists - and now things are working properly. Well, almost. Folder names with non-ASCII names are still broken, but that is less of an issue, since I don’t use folders that much, and it is still possible to get to the tracks.

 

Hats off for Sonos Support!

Userlevel 7
Badge +17

Hi everyone,

 

Just wanted to let you all know that this issue has been resolved in the latest S2 update (13.3).

 

Please update your players and let us know if you continue experiencing this issue by contacting our customer care team via phone or live chat.

I’m having the exact same problem, with Sonos One SLs (but older devices work fine) and a Synology DS218. I’m indexing manually, and any songs with non-ASCII characters show up, but cannot be played.

 

Userlevel 1
Badge +2

After the update that came a few days I go, I don’t see this problem. Hopefully, this means that the issue has been fixed. But since it was only Sonos One SL that was affected, and I got a few more other players, it could also be that the scheduled updated moved to a different player after the installation of the new version.

After the update that came a few days I go, I don’t see this problem. Hopefully, this means that the issue has been fixed. But since it was only Sonos One SL that was affected, and I got a few more other players, it could also be that the scheduled updated moved to a different player after the installation of the new version.

 

Sonos confirmed in another thread that the recent update fixed this bug.

Userlevel 1
Badge +2

I applied an update to Sonos yesterday. It was over a month since I last applied an update to the NAS.

I believe the NAS is running Linux, so I would expect file names to be in UTF-8. I would not expect there to be BOMs in the file names. (The playlists are actually created on a Windows system, and then copied to the NAS. Thus, the names are originally in UTF-16LE, but that is not a concern to Sonos, as Sonos does not know about the Windows system. And, yes, I did check the names on the NAS before I made my post.)

The issue is not isolated to Playlists, but names are broken when I check the Folders node as well. In fact, here is also some extra confusion, because some artists with non-ASCII characters appear multiple times.

So it seems to be a general problem in how file names are read and stored.

 

 

Userlevel 1
Badge +2
 

I misunderstood, I thought the problem was with paths in playlist files, hence my speculation regarding BOMs.

...

You should probably create a diagnostic and submit it to Sonos support, and also share what NAS you are using for others to chime in.

The contents of the playlists files themselves is utterly dull. The entries are just 01.lnk.mp3 and so on.

 

Yeah, maybe I should have taken the occasion and called Sonos support today, as it is a day off due to Ascension Day. On the other hand, sitting the telephone queue to Sonos is not particularly entertaining. The exact model of the NAS is a DS213 and the version of the OS is DSM 6.2.3-25426 Update 3.

I also have this problem. When will it be fixed?

Sonos doesn’t release any dates for fixes, which makes sense, as sometimes tracking down obscure issues doesn’t respond to calendar dates.

We know about them if/when they give release notes to us. Or if our personal testing confirms it’s been fixed, which has been more the case since the change last year in the person/policy regarding release notes. The new regime thinks less is more. 

Userlevel 1
Badge +2

Now I have gotten two updates to Sonos since this thread - alas the problem is still there. I can work around by requesting a manual update of the music library - for some reason the scheduled one runs on one of the One SL. Too bad for those who only Sonos One SL and no other player.

I have a DS218 too and its version is DSM 6.2.4-25556.

And yours ?

 

I still have the problem even after automatic and manual re-indexing :sob:

ok, thanks for communication. We waiting :grin:

Userlevel 1
Badge +2

Thanks Corry for the update! I already had the One SL as the prime suspect. Based on snm18’s post, I disconnected the One SL last night, and this night the music index was updated completely. I had planned to do a few more tests to verify that they are the culprits, but thanks to you update I don’t need to.

As it happens, I don’t use my One SL much as they are in the kitchen where I don’t play that often. But nevertheless I’m looking forward to the next update which I hope will have the fix. (Based on the assumption that it is a regression. But maybe it is not? I only got my SLs a month ago, and maybe they became masters of indexing after the upgrade because of some shakeup.)

Reply