Prodigy I

Answered

Music Library Compilation Issue under new 16.3 Firmware

Forum|Forum|2 years ago
July 16, 2024
240 replies
12063 views

Today I successfully updated to the latest 16.3 Firmware and Windows Desktop Controller.
I subsequently performed an “Update Music Library Now” from the 16.3 Windows Desktop Controller.
Now any Sonos Controller (including SonoPhone, SonoPad) show multiple entries for each compilation album when viewing Albums.
Just an example shown below...

Does anyone else have this issue?
Ross.

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.

Best answer by Corry P

Hi @rosswells127 et al

I have an update regarding this behaviour.

It is (now) expected behaviour that if you have a compilation album with no Album Artist metadata tagged on an S2 system, it will appear in the album list multiple times. To resolve this issue, please tag all tracks in the album with an Album Artist - if there is no single artist, please tag each track in the album with “Various Artists”. Once an album has a Album Artist tag, it will no longer appear as duplicates in the Album container list.

I hope this helps.

Edit: This thread was automatically closed due to inactivity. I have reopened it.

Show previous replies

R

RayBob

Contributor I

I’m sure most of you have already figured this out, but the “workaround“ is to make certain that every “artist“ listed for every track is exactly the same. If one cares who the artist is for a specific song on a compilation album, you have to type it in with the song title.

A year ago I was considering getting a smart Sonos speaker, but this seems ridiculous in the face of a company/programmers who are not smart!

R

RogerWF

Enthusiast II

So they are now in the final month of their stated improvement plan*, and there is still so much wrong with the current mobile app. I still just use the Windows version, which enables me to better manage the queue, but it’s still problematic. How do you think they are doing?

*”July and August:

Improving the stability when adding new products
Implementing Music Library configuration, browse, search, and play

August and September:

Improving Volume responsiveness
User interface improvements based on customer feedback
Improving overall system stability and error handling

September:

Improving the reliability of Alarm consistency and reliability

September and October:

Restoring edit mode for Playlists and the Queue
Improving functionality in settings”

The New Sonos App and Future Feature Updates | Sonos

S

Schweizermag

Enthusiast I

I reported this when it first happened and indeed I was told I was the first to raise this error. It was indeed back in July. I sent Sonos detailed analysis of the problem with supporting data and screenshots, all of which I still have. I even had a Sonos tech fiddling around in my library for two hours who confimed that they’d never seen this corruption before. I got a call back to tell me that they were working on a solution but since then nothing. Looks like those of us with large personal libraries who don’t stream much are of low interest to Sonos. Looks like just buying the kit doesn’t generate enough revenue to cover the C level salaries.

S

Schweizermag

Enthusiast I

I’m sure most of you have already figured this out, but the “workaround“ is to make certain that every “artist“ listed for every track is exactly the same. If one cares who the artist is for a specific song on a compilation album, you have to type it in with the song title.

A year ago I was considering getting a smart Sonos speaker, but this seems ridiculous in the face of a company/programmers who are not smart!

True enough, but that’s a lot of work for 5000 albums and it wasn’t even a problem three months ago.

R

robokitty

Enthusiast II

It’s poor isn’t it.

They broke something really basic in indexing (on the speaker) that has worked for years and we get treated to some patronising history of meta data tagging.

If it’s something as simple as forgetting to respect an option, why hasn’t it been remedied quickly and WTF do they use as any kind of regression test? Various regressions seem to indicate they have very bad rigour here.

Mid July this started are here we are closing in on mid October….

It’s absolutely insane.

R

robokitty

Enthusiast II

I’m sure most of you have already figured this out, but the “workaround“ is to make certain that every “artist“ listed for every track is exactly the same. If one cares who the artist is for a specific song on a compilation album, you have to type it in with the song title.

A year ago I was considering getting a smart Sonos speaker, but this seems ridiculous in the face of a company/programmers who are not smart!

True enough, but that’s a lot of work for 5000 albums and it wasn’t even a problem three months ago.

Also there is valuable information in the track artist info. One would be crazy to get rid of it just to work around this bug. If one were to nuke that info, then a compilation album would have no artist info at all.

MoPac

Headliner III

I’m sure most of you have already figured this out, but the “workaround“ is to make certain that every “artist“ listed for every track is exactly the same. If one cares who the artist is for a specific song on a compilation album, you have to type it in with the song title.

A year ago I was considering getting a smart Sonos speaker, but this seems ridiculous in the face of a company/programmers who are not smart!

True enough, but that’s a lot of work for 5000 albums and it wasn’t even a problem three months ago.

I wouldn’t mess with compilation tags particularly if I had a lot of them. Sonos, though they are slow, will fix that issue.

R

robokitty

Enthusiast II

Hi @Eejay60

We are aware and are investigating. I have no ETA for a resolution, however.

Could someone remove the “answered” flag from this post. A seemingly simple bug came in months ago, and there has been nothing from Sonos in all this time? This crushingly terrible bug had been with us for months, and no progress at all?

Corry P

Sonos Staff

Hi @robokitty

No. As it stands, that is currently the Best Answer (note that it does not say “solution”) out of all those given here. There are no steps you can take to resolve this (short of altering all of your metadata, but I would not consider that a resolution), so there will be no better answers until this is resolved.

Consider - If I did as you asked, anyone new to this thread would not necessarily see my announcement that we are aware of the issue and assume that it is something that they might be able to work around, thus wasting their time and causing frustration - probably more frustration than you get while looking at that Best Answer that you’re not happy with.

When the issue is resolved, the announcement posted here saying as much will become the new Best Answer.

I hope this helps.

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein

MoPac

Headliner III

Hi @robokitty

No. As it stands, that is currently the Best Answer (note that it does not say “solution”) out of all those given here. There are no steps you can take to resolve this (short of altering all of your metadata, but I would not consider that a resolution), so there will be no better answers until this is resolved.

Consider - If I did as you asked, anyone new to this thread would not necessarily see my announcement that we are aware of the issue and assume that it is something that they might be able to work around, thus wasting their time and causing frustration - probably more frustration that you get while looking at that Best Answer that you’re not happy with.

When the issue is resolved, the announcement posted here saying as much will become the new Best Answer.

I hope this helps.

Why is this so difficult when the older firmware handled compilations correctly? This from a guy that never listens to compilations.

Show more replies

Sign up

Login to the community