Hmm. I’m not convinced by that Qobuz statement. Past experience points to a situation where Roon Labs have been knocking on a door that was kept firmly closed by Qobuz. They may be just stringing us all along, as usual…
I’ve been auditioning Qobuz over the last few weeks. I like the presentation/recommendations over Tidal’s native apps (once a few genre filters are set, it feels more like home) – but I don’t think it would much difference if it were integrated in Roon.
I dislike the API integrations (Bluesound, Audirvana), but this looks promising in the native app (quite buggy still, but hey – UPNP):
Unfortunately Roon does not support UPnP Renderer mode, also many devices out there are don’t offer UPnP due to lack of gapless playback. There’s a possibility Roon can considered OpenHome based UPnP stack to develop on their app; this has cross compatibility to UPnP mode.
I think Qobuz should considered adding ‘Qobuz Connect’ similar to Spotify Connect. A code is embedded as a form of a firmware inside the device while the app will instruct the device to connect to the streaming servers. In this way, one no need to keep the app(e.g. Spotify app) on all the time. Music will still continue to playback even the app is closed. The advantage of this is device manufacture or may be Roon don’t have to spend considerable of R&D time of integrating the UI, all it needed is the proper coding on the receiver end(e.g. devices or software like Roon), while we can continue to use existing streaming service apps to control the music playback.
There’s another thing here, it seems these days not many streaming partners want to have their UI integrated into devices or software. The reason; they want their apps to be unique, proprietary and have full control at their disposal. If this the case Roon should considered this option. Having multiple service partners are very important to the survival as we are entering the age of music streaming.