Bug in displaying indexed data?

Answered

Bjørn Ulvik

Hi-Res

• July 24, 2020 08:42

Windows App: 3.8.3 BluOS: 3.8.17

Library - Albums - Sort by A -> Z
Ok (screenshot 1)

Library -  Artists - Artist name - Albums, show all - Sort by A -> Z
Not ok (screenshot 2), wrong year and total number of tracks.

This only happens when you have two or more albums in the library with the exact same album name.

Displayed track information is from "correct" album, but year and total number of tracks is from an album from a different artist.
In this case Shania Twain instead of Slade. Shania is the first in alphabetic order. A few test folders confirm that.

1

• Official comment

  

  Sam R.

  • July 24, 2020 17:38

  Hello Bjørn,

  Thank you very much for this detailed report. 

  I have been able to replicate it to some degree here, so I will forward this to our development team to look into further.

  Regards,
  Sam R.
• 

  Bjørn Ulvik

  Hi-Res

  • March 14, 2023 11:57

  Issue is still present.

  0
• 

  Permanently deleted user

  • January 19, 2024 13:37

  Just letting you know I've now raised an official support ticket about this, and the other related thread we've been commenting on over the last 3+ years. I'm completely fed-up with Bluesound's utter lack of action on this bug, but I don't know if anyone has ever raised a proper support ticket about it, or if we'd assumed that it was already on their "to-do" list (as both threads imply that it had been passed on to the development team).

  Hopefully this will spur them on a bit? Or maybe they'll just continue to ignore it for another 3 years...

  0
• 

  Bjørn Ulvik

  Hi-Res

  • February 14, 2024 12:00

  This is ridiculous!

  0
• 

  Permanently deleted user

  • February 14, 2024 19:23
  • Edited

  There is some possible good news though. After I'd raised the support ticket I got this response a few weeks later, so I guess it's officially in the system now! Hopefully it will be resolved sooner rather than later, especially as it was originally reported by multiple people back in 2020 (and based on the official response you received back then, was also passed on to the dev team but seemingly ignored...)

  After speaking with our engineering team regarding your specific issue they have been able to replicate it here in our labs. Our engineering team will be looking into this further and be providing a fix for this issue in a future firmware update.
   
  Unfortunately, we here in technical support are not provided a timeline on future development and releases so I can not say for certain when this update will become available. However, rest assured that our engineering team will be doing everything they can to resolve this issue as soon as possible.

  0

Please sign in to leave a comment.