Skip to main content

Sonos Controller - Duplicate Album Titles

  • October 20, 2025
  • 81 replies
  • 992 views
Show first post

81 replies

U
Forum|alt.badge.img+6
  • User117655
  • Prodigy I
  • February 14, 2026

This obviously has nothing to do with tags or metadata. This has been shown over and over again. If you rename a folder (a FOLDER!) on the nas and then re-index, a different set of albums will show this anomaly. The albums that showed this problem no longer do, and a DIFFERENT set of albums now do. That would indicate to any competent tech support person or software engineer that metadata is not involved in this problem.

 

EXACTLY!

I have seen this again and again! Even 'fixed' tags (not actually required as already compliant) for compilation albums - no change what so ever... Desktop app (and Phonos) ✔️ though 🤷🏼‍♂️

    A
    Forum|alt.badge.img+4
    • Anthony_6
    • Collaborator II
    • February 15, 2026

    This obviously has nothing to do with tags or metadata. This has been shown over and over again. If you rename a folder (a FOLDER!) on the nas and then re-index, a different set of albums will show this anomaly. The albums that showed this problem no longer do, and a DIFFERENT set of albums now do. That would indicate to any competent tech support person or software engineer that metadata is not involved in this problem.

     

    EXACTLY!

    I have seen this again and again! Even 'fixed' tags (not actually required as already compliant) for compilation albums - no change what so ever... Desktop app (and Phonos) ✔️ though 🤷🏼‍♂️

    I totally agree. I first reported this in October 2025 & here we are no further forward. Sonos broke it & but don’t seem to have a clue how to fix it.

    Anthony
      R
      Forum|alt.badge.img+1
      • RogerWF
      • Author
      • Enthusiast I
      • February 16, 2026

      I received the following request from Sonos support:  “Roger, Can you check to see if there is an inconsistency between tracks in the albums that currently show up as duplicates?  The tracks should all either have the compilation flag or not have the flag.  Let me know what you find.”

       

       

      This is example of clueless support. This obviously has nothing to do with tags or metadata. This has been shown over and over again. If you rename a folder (a FOLDER!) on the nas and then re-index, a different set of albums will show this anomaly. The albums that showed this problem no longer do, and a DIFFERENT set of albums now do. That would indicate to any competent tech support person or software engineer that metadata is not involved in this problem.

       

      Understood and agreed. You are preaching to the choir. But as long as they are paying attention, I’m going to cooperate, and I am just reporting events here.

      But just to magnify your point:  if you remove a folder, rename it, and add it back with the new name, you see the different results as you described. But if you then remove that folder again, rename it back to its original name, and add it back, you still get a totally different set of ‘duplicates’ from those on the original album list.

      Maybe this is what you were implying, but I just wanted to clarify.

      And I have made these points with them via email, but they seem intent on pursuing their own line of investigation. Perhaps you would have responded differently to them, but I’d like to keep communication with them open and provide whatever they request.

      Thank you.

        K
        • kdowling
        • February 16, 2026

        I received the following request from Sonos support:  “Roger, Can you check to see if there is an inconsistency between tracks in the albums that currently show up as duplicates?  The tracks should all either have the compilation flag or not have the flag.  Let me know what you find.”

         

         

        This is example of clueless support. This obviously has nothing to do with tags or metadata. This has been shown over and over again. If you rename a folder (a FOLDER!) on the nas and then re-index, a different set of albums will show this anomaly. The albums that showed this problem no longer do, and a DIFFERENT set of albums now do. That would indicate to any competent tech support person or software engineer that metadata is not involved in this problem.

         

        Understood and agreed. You are preaching to the choir. But as long as they are paying attention, I’m going to cooperate, and I am just reporting events here.

        But just to magnify your point:  if you remove a folder, rename it, and add it back with the new name, you see the different results as you described. But if you then remove that folder again, rename it back to its original name, and add it back, you still get a totally different set of ‘duplicates’ from those on the original album list.

        Maybe this is what you were implying, but I just wanted to clarify.

        And I have made these points with them via email, but they seem intent on pursuing their own line of investigation. Perhaps you would have responded differently to them, but I’d like to keep communication with them open and provide whatever they request.

        Thank you.

        I commend you for sticking with it. I don’t have the patience for it. I’m hoping they will eventually come to an understanding of what is actually happening and fix the problem. I mean, it did work correctly. And then there was a system update and this problem was introduced. But if they keep pursuing this as a tag problem, it may never get fixed. I hope I’m wrong.

          I
          • Ian_S
          • Prodigy III
          • February 16, 2026

          One of the albums I highlighted is not a compilation and doesn’t have the compilation flag set. You’d have thought that the fact one speaker can index it and another can’t would lead them down a different path to compilation flag meta-data… 

          A
          Forum|alt.badge.img+4
          • Anthony_6
          • Collaborator II
          • February 16, 2026

          One of the albums I highlighted is not a compilation and doesn’t have the compilation flag set. You’d have thought that the fact one speaker can index it and another can’t would lead them down a different path to compilation flag meta-data… 

          Yes, I quite agree, they seem transfixed on it being a metadata problem. Yet, as you may remember, I pointed out that scanning the library using the server name rather than using the IP address of the server gave different results, my server (running Unraid) has a fixed IP address, whether that makes a difference I don't know. That was repeatable, as it was always the same six albums or the same one album as I flipped between IP or name. So I really can't believe that is meta data related. It's the same with folder name changes, although that isn't repeatable. As each time you do it you will get differing albums misbehaving or if you're really lucky none. I need to change the genre of two albums but I afraid to do it as I'll have to re scan the library. At the.moment I only have one album showing the problem & it isn't one I listen too that often. So I am leaving well alone, but I really shouldn't have to worry about that.

          I think that they would like it to be a metadata problem so they can blame the user. But then, why didn't the problem always exist, this is a fairly recent problem.

          It's good that they are looking into it. We can only hope that one day it will be fixed.

          Anthony
            Terms & ConditionsCookie settingsAccessibility statement