Bug in Node Library?
Beantwortet
I bought a Node in August 2023, which has worked fine until (I think) the latest software update. I am controlling it with the iOS app on an iPhone 7, and am playing FLAC files shared over my home network from my Windows 10 PC.
There now seems to be a bug with the Library as follows:
- If I go to "Library" then "Album", many albums give this error message when clicking on them: "Couldn't Load Content. There was a problem loading your content. Please try again."
- If I select a problematic album via "Artists" or "Genre", I get the error message above.
- If I select a problematic album via "Composers", I can click on the album without any error...
- Browsing problematic albums via "Folders" also works fine.
I have tried the following, but nothing has helped yet:
- Rebuilding the index from both the "Settings/Music Library" and "Settings/Diagnostics" screens.
- Rebooting the device via the "Settings/Diagnostics" screen, and also by turning off and back on at the mains after 10 minutes.
Closing down the app on my iPhone and relaunching it.
Any ideas?
-
Offizieller Kommentar
Couldn't Load Content. There was a problem loading your content. Please try again." The albums that do work seem to be those that I have played within the last couple of month
Another Bluesound user here.
When I've seen this in the past something has changed in the directory structure or permissions where the files are stored. I was able to resolve it by confirming the files were present and uncorrupted at the storage location then deleting and rebuilding the index.
Failing that I suggest you log a support request with Bluesound.
-
I have also had this issue and found that, using Android(I don't know what the apple interface looks like) that if you click on the 3 dots at the top, the music will play from this.
1 -
To me this looks like the same bug that has been reported 4 months ago:
Please note above thread was polluted by some discussion on another Amazon-related bug, but the original thread as well as my additions to it were about a library issue.
Coincidentally, today I amended the tags of another few dozen albums in my library, as a work-around for this bug, which still has not been resolved after so many months.
1 -
Homesteadric: you're right: tapping the 3 dots beside the album picture will allow me to access the tracks, even when tapping the album itself gives the error message.
I have since tried uninstalling and reinstalling the app, along with a factory reset of my Node. No joy.
Possible related issue: when going to "Settings/Diagnostics/Rebuild index", the process never seems to end. It says, "Index deleted, re-index started. Please wait...", but hasn't finished after 30 minutes. I can return to the previous screen by tapping the back arrow at the top left. In contrast, rebuilding the index from "Settings/Music Library/Reindex music collection" only takes about 1 minute to complete (nearly 3000 tracks). Is there any difference in what these two reindex commands are supposed to do?
I'll submit a ticket shortly if I can't find a solution to my original post.
0 -
Gerben: thank you for that link! Having checked the metadata of the tracks involved, I can see precisely the same problems in the iOS player that you did in the Android player.
My collection is almost entirely classical music, and the albums affected all have the same features in common, just as you described in the other thread, with a small twist in bold below:
- Every track has the same album artist
- Every track has the same artist (but different to the album artist)
For example, an album with "Karajan" as the album artist for all tracks and "BPO; Karajan" as the artist for all tracks gives the error message when it is tapped.
But an album with "Brendel" as both the album artist for all tracks and also the artist for all tracks can be selected without any issues.
Hopefully there's a straightforward software fix for this bug...
P.S. Possible related bug: for an album which can be selected ok, the display fails to show the artist info under track titles where the artist is the same as the album artist. Examples:
- For the second album above ("Brendel" as both artist and album artist), although I can select the album ok, the display does not show the artist info below any of the track titles.
- Another album which can be selected fine has album artist "Curzon" for all tracks, and artist "Cleveland SO; Curzon" for all tracks except the last, where the artist is simply "Curzon". When selecting this album, the display shows the artist info under every track title except the last.
0 -
I'm just speculating here, but I note the semicolon in the "BPO; Karajan" filename. While semicolons are legal for Windows filenames others (on stackexhange) have reported problems using semicolons in *some* cases.I wonder whether altering the semicolon to a dash would resolve the issue.
1 -
Thanks for the suggestion, Brian. I have just tried changing the metadata to remove all punctuation including semicolons, colons, commas, etc. The issue still remains.
But changing the metadata so the artist and album artist are exactly the same for all tracks fixes it. The album can now be selected without an error, although the artist info does not appear under any of the track titles as mentioned above.
0 -
Hi JC,
Thanks for confirming. It seems that after four months of annoying presence in Android this bug has now found its way to iOS as well.
Never looked into same artist for artist and albumartist, as such has little added value. The way I normally get rid of it is by deleting the artist tags.
2
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
8 Kommentare