Vault Rebooting and Losing Playlists
Not only does my Vault keep spontaneously rebooting since the recent updates, but it seems to have damaged playlists. Attempting to rectify/repair/edit/add music the playlists appears to trigger the unit rebooting. Among the issues:
1) Music added to playlists has been removed/disappeared from the playlists
2) Playlists will say something like "71 songs in Playlist" but only 30 songs appear.
3) On certain playlists, clicking "Play All" or "Shuffle" results in only one song showing in the Playlist.
Anyone else having this issue or found a workaround?
-
Offizieller Kommentar
Thank you all for your feedback.
As always, please contact the Support Crew by selecting Settings, Send Support Request in the BluOS App so we can investigate further. Our team however has taken the liberty of escalating you already. Our Support Crew will be in touch very shortly via e-mail.
I can confirm your Playlists are intact. With the release of BluOS 4.10.x a major rewrite was performed to modernise and update portions of very old code (some in excess of 12 years on older outdated language) and went through over 12 months of testing. Unfortunately, in such major redesign projects, as much as we try not to let it happen, one or two embarrassments slip pass the goalie. We do realise this 'unfortuante' situation absolutely upends your enjoyment of our product. We do apologise for that.
The "missing" tracks were not converted properly but the original still sits in your Player(s). Please sit tight and do not overwrite your existing Playlists. I cannot comment on the why (mostly because we are unsure as to the why) but in speaking with both our Quality Assurance Team and our Product Development Team, we are currently testing a fix which we will be releasing in the coming days for all to get back up and #LivingHiFi.
In the meantime, our Support Crew will be in touch. -
Please stop pushing this update to payers until it is stable/resolved.
1 -
Having seen all issues reported here in the 4.10.x builds I blocked the update server in my router:
upgrade.nadelectronics.com0 -
That’s a great idea, but one that shouldn’t be necessary. A company shouldn’t continue to disseminate knowingly flawed updates until they are fixed.
0 -
Until the time that Bluesound allows to downgrade to an earlier (working) firmware, I have no other option than to blacklist the upgrade server. As a Linux user I ALWAYS have the possibility to revert to a working former kernel, to assure my system keeps functioning in the event of a botched upgrade. This is how upgrades should be implemented. It's painful to see the same problems resurface after every upgrade of the V4.0 firmware series, all I want is a working streamer. Now I'll just have to wait and see and hope that one day the bugs get killed.
0 -
Unfortunately, it is not only the firmware. The controller apps are also plagued by bugs by the dozens that never get fixed.
My BluOS system is on outdated firmware, outdated Android app (1.5 years old) and outdated desktop app (1 year old). Just so I can keep sort of using my Node, without the crap introduced thereafter.
I cannot recall I have had to deal with a software developer as bad as this in 45 years. It is disgraceful. There is not the slightest effort to fix the endless series of bugs that have been introduced by updates breaking previously existing functionalities. There is no functional QA/QC either.
0 -
When it gets like this, the vendor ends up spending too much time fixing things that they have just broken or things that they have implemented when not ready, and not enough time enhancing their applications.
In short their current working practices are causing them to trip themselves up.
Quite a while back, I was involved in implementing a third party proprietary warehouse management system the concept and design of which were phenomenal. The vendor's execution was, however, poor, and we staggered from one failing release to another.
They did eventually get it right, however, by slowing things right down. They started rigorously testing and retesting each piece of new or amended software, and they also regression tested the application to ensure that what had just been added to the build didn't also break any existing functionality in the way that new BluOS releases seem to be doing right now.
So we went from twice-daily new feature and bug fix releases that consistently failed to waiting for more than two weeks while they did things more thoroughly. Then we got a slow one-by-one flow of bug fixes and enhancements that worked properly and actually improved the product, and gradually we got the fabulous application that we had been promised.
When I saw the application in full swing and watched the warehouse operating around me like a complex machine it was a wondrous moment.
And in that wondrous moment is where Bluesound should be right now. Instead, however, a series of releases largely involving fixes for broken core functionality and faulty new functionality suggests that they aren't in that moment, which is sad since I dearly wish that they were.
1 -
Thank you all for your feedback.
As always, please contact the Support Crew by selecting Settings, Send Support Request in the BluOS App so we can investigate further. Our team however has taken the liberty of escalating you already. Our Support Crew will be in touch very shortly via e-mail.
I can confirm your Playlists are intact. With the release of BluOS 4.10.x a major rewrite was performed to modernise and update portions of very old code (some in excess of 12 years on older outdated language) and went through over 12 months of testing. Unfortunately, in such major redesign projects, as much as we try not to let it happen, one or two embarrassments slip pass the goalie. We do realise this 'unfortuante' situation absolutely upends your enjoyment of our product. We do apologise for that.
The "missing" tracks were not converted properly but the original still sits in your Player(s). Please sit tight and do not overwrite your existing Playlists. I cannot comment on the why (mostly because we are unsure as to the why) but in speaking with both our Quality Assurance Team and our Product Development Team, we are currently testing a fix which we will be releasing in the coming days for all to get back up and #LivingHiFi.
In the meantime, our Support Crew will be in touch.0 -
STILL waiting for the 4.10.13 update errors to be resolved. In addition to the problems noted above, I'm now discovering several music purchases -- added to my Vault before the current debacle -- have disappeared from the "New" category. And new CD rips wind up in the "Unknown CD" folder sans metadata. Finding a custom playlist to enjoy is akin to searching through an unalphabetized telephone directory.
I used to love my Vault and recommended it wholeheartedly to fellow audiophiles. With all the disruptive updates over the last two years, I'm afraid to update the firmware ever again. Now I tell friends to avoid Bluesound products unless they enjoy listening to music with a headache.1
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
9 Kommentare