Was testing for 1.8 adequate?

Well, that’s the thing, it’s not that it broke another feature, rather that in broke a specific workflow with respect to that feature. Tagging still works, it just works differently in 1.8, and in a way that’s broadly incompatible with the ways in which some people used it in the past.

1 Like

Mods have temporarily slowed this thread to prevent inappropriate tit for tat argument.

6 Likes

the crash of the settings page on ipads and on Windows PC was discovered and reported by several invitees after the first hour or so of this late „beta testing experience“. Same for the issues with composer/conductors. The latter surely impacted less people in a lesser way, but still.
it seemed not to be a known issue and it was not fixed before release.
The problem with tags was not discussed in these last couple of days, if I remember correctly. Which tells me that there might not have been a problem with amount of testers but with their selection in terms of their use cases. It makes no sense to blame testers. They test according to their use cases unless they work to execute a predefined test script. So it would have been the responsibility of the Roon team to select testers based on use case profiles. One could guess that this was not done.

2 Likes

I’m not convinced that testing is the issue. Maybe functionality is more the issue. Testing is there to try and break it, not judge whether it is any good or easy to use or intuitive or better/worse than 1.7.

From what I’ve seen here and personally experienced thus far with Roon the problem is the UI. I’ve always suspected that the Roon interface was/is designed by programmers. It feels like new stuff has been crow-barred into earlier UI iterations (which weren’t that good in the first place) by coders, who are rarely any good at interface design.

Maybe it’s time Roon invested in a high quality experienced specialist GUI designer with the freedom to start again. A good UI designer thinks like a user and is largely detached from the vagaries of coding.

If I’m wrong and Roon do employ professional UI designers, maybe it’s time to consider a change? The 1.8 tagging issues are unforgivable!

2 Likes

I believe Danny said in another thread that there weren’t many tag users. I’m not sure how he knows that, but it seems like the majority of users that participate in this forum use tags. Most of them were broken with 1.8. I only had three tags, but I used them quite a lot. One of my tags failed to completely migrate with the new library, so it became useless.

Yep, I’m not sure how he would know that either. In my case the fallout wasn’t too drastic - a couple of bookmarks failed to behave as expected - but from what I’ve read quite a large number of people have lost what they would consider to be basic functionality. All that said, and whichever way you look at it, tags are now harder to use and less effective than they were in v1.7. I’m not sure why Roon would take this retrograde step, but I’m hoping they’ll walk this one back.

Analytics data gathered by Roon Labs software

Roon captures information about how and where you use the software, and statistical reports about this information are stored on our servers for analysis. The data is transmitted and stored without any reference to your personal information. The purpose of the analytics data is to help us understand our members and how they use Roon.

Information about how you use Roon. In order to understand our members and their needs better, we capture data about the features you use, how often you use Roon, statistics about your collection, geographic location, number of outputs (devices you stream to), and streaming technologies used (Roon Ready players, AirPlay devices, Squeezebox players, HQplayer, etc.).

1 Like

We don’t know who does what, but we know overall. We can’t tie it to individuals, so it’s impossible to know how community users use Roon differently from non-community users.

Had I dredged my memory a bit more thoroughly I wouldn’t have asked how you know, because I’ve seen that info before. Putting that aside, I’m still puzzled by what seems like a backwards step with tags. Even if only a limited number of people use them, I can’t see the rationale for a) changing the way they work, and b) making them harder to use. I know you’ve acknowledged the negative feedback elsewhere, and that we can expect some changes in future updates, but I’m still baffled by the change. It would be interesting to hear the rationale.

I don’t know, but I updated my core ( on a Synology NAS), remote on iMac, iPad, fire table and Samsung phone with only a slight issue on Fire tablet .