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?
-
Offizieller Kommentar
Hi Ray
Thanks for your feedback. I can't say you are alone, but I can say you do appear to be in a very small minority as we are not seeing wide cases of this. That being said look for us to reach out to you via e-mail as I have asked our Support Crew to re-open your case.
Thanks for your patience...
-
+1
1 -
@Max Dekker, thank you. 👍
0 -
Tony, I’ve had ongoing discussions via email for months. The support case shouldn’t be closed until it’s resolved.
The trouble is the team I liaise with aren’t the people doing the coding. It’s very frustrating.
0 -
Tony,
You do not seem to appreciate how badly this bugs affects the user experience. It affects many albums in my library and breaks the usability of BluOS' library functionality, which has now been utterly unreliable for half a year. BluOS is broken, because this and several bugs that do not get fixed.
Secondly, you seem to be sweeping this under the carpet, many others have complained about it.
Some facts about this bug:
- introduced around 30 May in Android app v4.4.0
- has been present in every Android release after v4.4.0
- is not present in Android app v4.2.4, irrespective of the BluOS release (4.2.x, 4.4.x, 4.6.x)
- reported in detail by me on 13 June (ticket 469537)
- confirmed by your team: "Following discussions with our Engineering team regarding your specific issue, they have replicated the issue in our labs."
- reported by Niels van Hoorn 5 months ago as well as various others (note this thread is about library, but someone hijacked it for an Amazon issue) in:
- reported by Jari Vihanto 3 months ago in:
https://support1.bluesound.com/hc/en-us/community/posts/25439750748311-Service-Unavailable
- reported by JC 2 months ago in:
https://support1.bluesound.com/hc/en-us/community/posts/26548891664151-Bug-in-Node-Library
- remains unresolved after half a year, despite the fact that you have the code that works laying around (Android 4.2.4)
The above suggests that your development team seems to be totally lost.
1 -
Gerben, thanks for your contribution. I had a quick look through the first link you provided where you said this… “ Apparent cause: this happens to albums that have in the metadata
1. An album artist, AND
2. An artist that is the same for each track of the album”I have a couple of manually created albums from DAT recordings and they’ve always been fine until June. One is a single track from “Also Sprach Zarathustra” by the LA Philharmonic conducted by Zubin Mehta. The single track is less than 4 minutes. That also fails to play via Albums.
0 -
I’ve been sent an email with a link to download a test file. It requires me to login using my email address. But having done that I get a message saying “Unable to get login information “.
How are we meant to get access to this site? No option to register.
0 -
Hi Ray, please continue to work with our Support Crew directly. They will be happy to assist.
0 -
I wondered why so many of my classical albums were affected. It’s clear now. All have the same artist for every track. Example is The Nutcracker by Berlin Symphony Orchestra. Conductor is the same. Composer is the same.
I would have thought this would make things simple to fix. Important too because classical music will be disproportionately affected. Have a look at the code prior to the June update. You do keep old copies of the code I trust.
0 -
Another affected album. The Planets, composer Gustav Holst, artist could well be the conductor of The London Symphony Orchestra, Sir Colin Davis. Same for all 7 tracks.
All the metadata is 100% accurate.
0 -
Hi Ray
Please continue to work directly with our Support Crew and update the request with your information. This way they can continue to work directly with our QA team to locate the root cause of your issue and resolve it.
Thanks for your understanding.
0 -
Tony, the information I posted is for the benefit of others experiencing this problem. Please understand this problem has been present for five months with zero progress. It’s only since posting here yesterday I’ve seen some progress.
0 -
Hi Ray,
Indeed the Zarathustra single matches my bug description in the other thread: "Affected are albums containing one or more tracks, thus including singles."
Another user had a correct addition to the bug report: if artist and albumartist are the same, the album opens correctly.
In the meantime I also found that if these albums are accessed through the albums listed under the albumartist, it fails, but if through the albums listed under the artist, the album opens correctly.
The official Bluesound comment above is rather shocking.
The only criterion being a minority is short sighted for various reasons:
- this specific bugs affects especially classical music, which will limit the number of users affected
- maybe a lot of users did not report, but simply resorted to one of the various workarounds suggested by other users
- Bluesound had confirmed this bug to be reproducible;
so it can be expected that every user, who has an album that has the metadata to trigger the bug, is affected - it ignores the severity of the bug;
opening an album is one of the most basic operations a user will perform;
personally, every album I play starts with opening it, which will show me the tracklist and other metadata, followed by hitting "Play all" - not fixing bugs, even if only reported by a smaller number of users, degrades the quality and user experience of the product
- bugs have no place in any decent piece of software
This does not stand on its own. One bug and was reported by me in January and two in June, all three could be replicated by Bluesound, none of the three has been fixed. The same is valid for various issues reported by other users. The "ghost share" bug has been around for years and must have wasted the time of numerous users.
Who is interested in multi-room, hi-res, Dirac, native DSD decoding, VU-meters or whatever, if basic functionalities are broken? I am not, which might make me a minority, which according to Bluesound logic can be ignored. For me, the reputation built by NAD over half a century has been destroyed by BluOS in less than a year.
All above is already bad enough, but it is even worse.
The official comment basically says that BluOS / Bluesound / NAD knowingly, willingly, deliberately choose for not fixing an identified bug, thus accepting that the quality of BluOS degrades and thereby as well degrades the quality and user experience of every Bluesound and NAD equipment that depends on BluOS.
1 -
Hi Gerben. It does appear classical albums are particularly susceptible to this problem. Hence why so few users are affected. We’re a dying breed! But that doesn’t mean it’s okay for the bug to remain.
I’ve also had confirmation a while back that the problem was reproducible. So why hasn’t it been resolved? As you say access to the Album via an alternative source is error free. I suggested they look at that code and use it on the Albums option.
I supplied a zipped version of the soundtrack to Gladiator. Some metadata was changed by Bluesound and I was asked to try it. Unfortunately it didn’t resolve the problem and in some respects was worse as every track was duplicated and played twice.
The reputation of Bluesound is on trial here as far as I’m concerned. The steps to reproducing the problem have been described as has a way of bypassing it. We’ve been extremely patient but patience has its limits.
I expect Bluesound to pull out all the stops now and fix what on the surface appears to be a straightforward problem.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
14 Kommentare