Thanks for raising this @anon94274355. Improving Radio is absolutely a priority for us, and everyone on the team would agree that the current algorithm needs work.
A huge amount of work has been happening over the last few months and we’re really, really excited to deliver new functionality and improvements across the app. The changes we’re working on are wide-ranging, but one of our main focuses has been improving Roon’s metadata infrastructure based on the huge spectrum of feedback we’ve received since we launched.
These changes lay the groundwork for the kind of full-scale overhaul Radio needs. We’ve thought about this quite a bit and are considering a number of possibilities. We’re hoping to kick off work on these changes soon, but first we need to ship 1.3 – with this many changes in progress, a team our size really can’t afford to re-architect Radio twice.
I don’t want to get into too much detail about how we’re looking to improve Radio after 1.3, since the plans are fluid and could still change. I can tell you we think an important source will be what we capture about how people are already using Radio. We’re now at a point where we have a critical mass of users generating this data, and 1.3 will contain client-side functionality to help us gather that data before it’s analyzed in the cloud.
We’re also actively talking to new data providers about the kinds of data we can license to ensure Radio is making the best possible selections in your library, and in the wider world of TIDAL.
There’s no question it would be great to have Radio improvements now, but we don’t want to put a band-aid on this – we intend to treat this piece of the product in a truly first class way. While changes to Radio won’t be part of 1.3, rest assured that we absolutely intend to address these shortcomings, and will provide updates to this community as things firm up after this release.
Thanks @anon94274355!