I wasn’t effected by this issue, but it obviously stopped a number of users from using Roon at all.
For what it is worth, I echo the calls for such issues to be treated as a top priority in the future. The fix should be rolled out as soon as possible, and not as part of a larger build release including other issues, that while inconvenient, do not stop the most basic of Roon functionality from working: playback of users’ music libraries.
If all QA resources had been diverted to this issue 15 days ago, a fix likely would have been available before the release of build 778.
There is a world of difference between this issue and the issues with 1.8 that I have been collating into this list:
I took a bit of constructive criticism for not including this issue in the main listing - my definition of what issues were to be included was already somewhat blurry; and didn’t include specific user configurations.
The posts linking back to/discussing this issue served the main purpose of the list - letting users know Roon was investigating an issue, and if anything, gave the issue more visibility than just being another item in a list.
But if anyone effected by this issue feels that my list should have been based on priority, with this issue at top of the listing; I feel that I need to apologise - you were right.
If I had to start the list again, it would be based on priority, rather than the blurry definations of restoring functionality/bugs (support) and feature requests, loosely based on the current forum sections.
Going forward to the next major release, I hope that Roon work on a new system for keeping users informed of their plans for addressing issues - it shouldn’t be left to users like myself.
My suggestion is that during each major release the forum has a persistant banner (as used during outages or Nucleus/sub offers) linking to an online service like Trello, where each issue is listed under priority; with details of impact on functionality; a link back to the original forum topic for discussion; and a very rough outline of the phase it is in: investigation/recreated/fix/QA, even without a ETA on the fix being released it would be helpful to users.
Even better, if the issue tracking system Roon uses internally also has a user-facing interface?
The forum structure also needs to be improved.
Another reason I created the list was in an attempt to reduce the amount of times the same issue is being reposted. Additionally, support issues posted to the feedback topics on specific build(s) get buried under tens, if not hundreds, of general discussion posts.
Perhaps a general posting/staging section where mods would review new support topics and move into a specific section as appropriate or confirm with the poster that the issue had already been reported, then unlist the topic from the forum.
Users would only be able to create topics in the general support section, and only post to topics mods had created in the specific support sections.