Same issue here, almost all my Qobuz albums have disappeared in the last days.
It would be great if the Roon team can focus on stability and reliability instead of adding new features. I don’t need new features but I do need the software to be reliable.
Please impress us and spend an entire update cycle optimising the stability of your software. No new features, just fixing bugs and improving the stability. I can asure you ALL of your users would rather have stable software instead of new features.
I think it would also help to have less frequent updates and to test new updates thoroughly for some time before rolling them out. I don’t want to be a beta tester.
Can’t agree more. Always have said when they switched release their model it would be problematic and it constantly is. When we had quarterly updates it was far more stable I don’t remember any major problems apart from the switch to 1.8 and server meltdown. The odd bug still got through but not big ones like we get today.
So we waited a bit longer for new toys but got a much more stable platform overall.
Also since it’s it gone down EA route to spot all the issues, it does seems that no prior testing is now done by beta/alpha testing before before releasing to EA and a more general audience. Hope I am wrong but it feels this way.
I agree. I’m sure I’m out of sync with the world of rapid release software, but I don’t understand this obsession with new features. Maybe if you’re catering for teens and twentysomethings, but that’s hardly Roon’s demographic. Stability should be the at the heart of Roon’s software. Whatever has happened with the Qobuz outage it has revealed, yet again, that there is a fragility to Roon that just isn’t there with other providers.
Totally agree with @SukieInTheGraveyard here : “Whatever has happened with the Qobuz outage it has revealed, yet again, that there is a fragility to Roon that just isn’t there with other providers” . i dont want to be a beta tester, nor do i really want to be a member of an audiogeek community, I just want to be a satisfied and respected customer/user/subscriber, enjoying my rights to the functionnal and functioning product/service that i need when i am paying for it.
I agree that stability is the base for customer satisfaction when it comes to software. I personally would welcome new features if they do not make the product overly complicated or more unstable. Particularly browsing and curating features which have been introduced recently (like ´Listen later´ or dynamic playlists) absolutely improve the roon experience and I do not think the stability was suffering therefore.
Would support that if it would be realistic. But seemingly a lot of problems originate from local networking or computing capabilities and are very difficult to reproduce. I am not sure it is doable to send all roon developers to working with 15yo wi-fi gear having old castle walls between router and endpoint, activating all energy-saving routines and firewalls on outdated iOS and MacOS devices just to ensure the software would provide stability under such conditions.
The other important question if the userbase would be agreeing to tailoring the software for sub-par conditions remains unanswered. Stability in many cases also comes from decreasing quality, snappiness and versatility of features. I am not sure people would be happy with an ARC like standard the moment they use Wi-fi.
Personally I would do it the other way round. That says a lot about the diverse wishes of the community.
By improving stability I meant fixing bugs, improving code quality and improving code maintainability. So the codebase is cleaner, more structured and easier to maintain and less prone to bugs.
I feel like Roon management told the team to spend too much time on new features, while too little time is spend on improving code quality and stability of existing code. This is not as sexy as working on new features, but is very important. New features are welcome of course, but a slower pace is preferred, so enough time is allocated to keep the code stable. Apparently there are bugs which keep popping up again months or a year later.
The playback stability is actually rock solid for me.
My Roon Server and Roon Bridges are wired, only my Roon Remotes use Wi-Fi.
And I have a dedicated pc for Roon Server.
I think it would be good if Roon can re-evaluate their software release life cycle. It feels like steps are skipped and the production releases feel like beta releases…
It would also be great if Roon can make their software release notes more detailed.
Currently everything is listed under “Changes”.
I would like to suggest to use the following sub categories under Changes:
What’s New
Resolved Issues
Known Issues
Bug free software does not exist. It would be helpful to list the fixed bugs and known bugs for a release.