Unable to play certain albums via Albums option
Beantwortet
I’ve had my Bluesound Node 2i since February 2020. All my music is in FLAC format stored on a NAS drive. A Synology DS220+ 4Tb in RAID1. The share works perfectly on both an Android app and an iPad one.
Since an upgrade to the firmware last June I cannot play certain albums from the Albums tab. Individual tracks from the Songs and Artist options work fine. I can even select a song on one of the affected albums, tap the three dots to the right and select Go to Album and the whole album is available to play.
But if I select Albums - Gladiator - for example, I get the message saying “Couldn’t load content. Please try again”. It simply will not play. There are at least 10 Albums affected.
I raised a ticket with support four months ago and the issue is still not fixed. Even after I described how to get access to the Album via Songs. Surely it can’t be that difficult to fix.
The same happens on a five year-old Android smartphone and a two year old 5th Gen iPad. I really do want this fixing. Am I alone in having this problem?
-
Yes, shall do that.
0 -
Ray, link to new post below. I am on 4.2.4 and 4.8.17. The app 4.2.4 is not affected by the bugs reported in my new post, nor was it affected by the bug discussed in this thread (Unable to play certain albums via Albums option).
0 -
Pinot, I had a look at your post and checked my ripped CD of The Nutcracker. 24 tracks and I see a progress bar in Now Playing and Play Queue mode. The elapsed and remaining time only shows on Now Playing mode.
If it’s any help I first raised the issue in this topic last June. It dragged on for a few months with no progress. But after posting here it did eventually get resolved. Good luck!
0 -
I've updated to iOS app 4.8.1 and BluOs 4.8.17 and all of my albums that previously triggered "can't load content" now open properly.
1 -
Ray, it is not so much about the progress itself, but about some indicator showing which track is playing in the album track list.
The play queue is useless for this, because it does not show the work nor the composer. Track list often consist of multiple works by different composers. Furthermore, track lists in classical can be very long.
0 -
@Pinot Gris, a screenshot might help us understand your problem. I suggest a new topic is required as it’s a different problem to this one which I now consider resolved.
0 -
Ray, I was responding to your Nutcracker comment, had the impression it referred to the link I posted.
Resuming:
1. The album not opening seems finally resolved after 8 months
2. The currently playing track not being highlighted in an album's tracklist, follow link above to post, remains unresolved for more than 8 months
0 -
Pinot, okay. Today I’ve switched to an iPhone so should I have any more issues with the app it will be in the Apple section. Good luck getting things sorted.
0 -
Thanks. Until BluOS fixes this bug I shall just remain on the outdated app v4.2.4 which has been immune to both the album opening and track highlighting issues.
0 -
Node & Nano , using IOS (16.7.10) controller on IPAD
I still have the issue of "Content could not be shown" on most classical Albums, it seems like there is an corrolation with the metadata issue with Colon : in album name as all the albums with problems have that feature (my standard tagging for classical albums are "Composer: Album"), however it's not 100% conssitent as a few classical albums with : in the album actually works.
So "Beethoven: Violin Concerto - Haitink" cannot be show whereas "Arvo Pärt: Serenity - The Beauty of Arvo Pärt" works fine , both albums have the same artist and albumartist for all tracks.
1 -
Ran a quick test with the precise titles you mentioned, both open fine. All my albums with a colon in the albumtitle open fine as well. So not able to reproduce.
Have you tried whether the Haitink album opens, if you remove the colon from the albumtitle for each track, without changing anything else?
1 -
Just checked the software update on my NODE and there was a new version available ( i was on 4.8.7 and the new was 4.8.21) i used to get a push information on new versions but not this time. I ran the update and thereafter both albums opens fine.
I then checked my NANO which also was on 4.8.7 and there the issue still existed, after an update there the issue was solved as well, so i can confirm that this issue (which has been there for quite some time) is solved in the newest version
0 -
I am so glad I found this thread - I have the same issue on some albums, and it was driving me crazy. I ended up using MP3Tag to simply delete the album artist entries on the affected albums. I do hope this is fixed in the future, though. Thanks to the posters who helped to identify the issue!
0 -
I am having the same issue with Classical Albums. I can use the 'browse to folder' method as a work around but it would be good to have this fixed.
Using a Node: BluOS version 4.10.19
0 -
I started fixing these by using MP3Tag to convert the album artist entries to match the artist entries. I think I'm done - I found 24 albums in a library of about 6000 that needed this. Easier than the other work arounds, I think. Still, I continue to hope for a fix.
0 -
Yes I am still having this issue also. I have an album with the same Artist and Artist Name but I can only get to the tracks in Song view.
"Couldn't Load Content. There was a problem loading your content. Please try again."
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
76 Kommentare