Some will know me as @menzies , a former lifetime user who gave everything up with Roon due to issues that affected my use of their product. Issues that didn’t seem to take priority. I’m still happy I did this, but still love the full concept of Roon.
At the beginning of the year, In a brief exchange of messages between the current day to day head at Roon it was mentioned they were focussing on fixing issues. Longstanding issues and in my mind, making the core rock solid (pun intended).
Rightly or wrongly I took this as Roon increasing staff levels across the board on support through to the developers. In part that seems true.
I have seen a number of issues get fixed over the past 9 months, but most of these were for newly created bugs when another fix was implemented. That does seem to be the Roon way. Some bugs reported in EA made it through to production. Why?! How?!
There should be a point to feedback, and my point is that Roon is still failing in my eyes ![]()
Basic select, play etc works, but there are issues that affect some differently than it does to others.
Over a month ago (exact timeframe unknown, around Nov 3rd) it became impossible to use the share function with unidentified albums. It was reported on the 3rd. Roon wrote on Nov 5th words to the effect that a fix it would be rolled out shortly in EA. There have been several EA releases in this time. No fix yet. Is this timeframe too long. I think so.
On the Nov 3rd Jamie dropped the dangling carrot of a new feature. The donkey has bolted now and the interest with it I feel.
To some, fixing the share function is more important than introducing support for Nugs.net. A feature request that was started 5 years ago and only got 18 votes. I appreciate new features could help boost Roon user numbers, but for long time users of Roon, their patience is wearing thin.
I created a thread the other day because the original thread created on Nov 3rd had closed for the share issue. Roon did not update the thread for over 30 days and it closed automatically. Granted, it’s marked [ticket in]. There are a good number of threads marked as this. Some are several years old.
There are more
So when some (longstanding) issues go without an update by Roon, users could be left wondering “What’s the point of using Roon?”
Back to my new thread reporting, confirming the share function is broken. You get a reply like the below from Roon support. I appreciate English may not be Vadim’s native language, but the use of clearly placed bold type, the wording and punctuation really annoyed me.
Usually these situations would see the original thread reopened and a merge of threads take place.
A message to Roon, @danny @Jeff_P @brian
Fix the stuff that’s reported (and reproduced) as broken quicker. Bugs from more than 6 months ago must be made a priority. These issues should be targeted before new features hit the top of the pile.
We know you’re passionate about Roon and music. We also know you’re in this to make a few $’s so you can live and feed your families. Your customers are spending their money for that to be possible.
It’s been over 30 days since the new feature hint was dropped. Either something has gone wrong, the deal isn’t finalised or something else, so put that to the side for now. Focus on fixing some big bugs before the holidays. A new feature now will likely bring new bugs, resurrect old bugs and all during the festive holidays when the Roon support and dev teams are having a well deserved special time with their loved ones.
Please take stock of things.
This forum used to be a thriving music loving community. A mix of users sharing musical experience, what they’re listening to and battling head to head. The past year there has been a decline to the spirit of the community. Even Roon staff have dropped off the radar and reduced the amount they take part in community discussions.
I’ll leave it there.
I finish work today and have 16 days of festive family time ahead.
Happy holidays everyone ![]()
![]()
Peace and love to you all ![]()
![]()