Sonos Controller - Duplicate Album Titles

Found it, it looks a pretty decent piece of kit for storage of audio. I don't think I'll buy one just to see if it fixes the duplicate album problem though.

​@Anthony_6 

They ain’t cheap.  I bought mine from a friend who uses cloud servers now.

Isn’t that solved by changing tags, that Sonos not sees as a problem (so they are not going to solve it)?

Sounds about right.  Never been a huge fan of systems that require library indexing.  Find myself listening to Dolby Atmos from Apple or Amazon most of the time.  Still…. I have not found any duplicate albums in my library for some reason.  Don’t know why.

Some of the file and path lengths are related to the SMB protocol, not Sonos choices.

Same with character usage limitations.

Sonos may further restrict both, no good way to tell other than building test data and trying it.

Shame the support section here doesn't have a detailed list of the requirements, the forum might but searching them is frustrating.

Whatever the (unspecified) requirements are, they must not be the same as S1. Because my S1 system is using the same library on my NAS and this problem does not exist on S1.

Or, more likely, there is a bug that got introduced last September and Sonos can’t find it. This problem didn’t exist prior to that update. All this discussion about tags and path lengths being the problem is crazy. This problem DIDN’T EXIST prior to that update last September.

Yes, I hear you loud and clear, all we're doing is trying to hide the problem that Sonos should be fixing. But as I and others have said I don't think enough of us are using Sonos this way any more. Sonos seem to be more interested in home cinema setups or streaming from the likes of Spotify etc.They've certainly forgotten their roots of a high quality stereo home audio system for primarily listening to music.

I really wish I'd hadn't got rid of my original zone players when Sonos made the awful decision to brick them. Yet another Sonos disaster situation.

Yes I saw the price.

The Samba module, what Linux uses to provide the SMB protocol, was given a huge re-write. The new version of the module was too big for the original Sonos devices which is why they stayed with SMB v1 for so long and a major incentive for the S1 to S2 split. Allowing devices with adequate memory resources to run the new code while keeping the older devices usable.

So yes the old and new SMB versions have many differences, since I don't use SMB outside Sonos I haven't  kept up with the details.

While all true, that doesn’t explain why this problem started with an S2 update in September when it was already using SMB v2/v3 prior to that.

We’ve been discussing this problem since last October. See Anthony_6’s thread for a refresher:

Albums have suddenly started to behave strangely.

I was addressing kdowling's S1 S2 changes post up few.

I'm well aware of the duplicate issue. Have it here and wasted a lot of time trying to sort it out.

Until the programmers at Sonos get a better handle on the codebase we are going to keep seeing issues like this and they are going to be hard to get fixed.

Been there, done that at past jobs when management decided to "fix" the development department and lost control of the process.