![]() On the flip side, however, we often find albums on Tidal, Spotify, Apple Music and Deezer that aren't available on Qobuz at all – which we would argue is a far bigger issue. Numbers rarely tell the whole story, but we regularly find hi-res albums on Qobuz that are available in only CD-quality on Tidal. Recent figures put the total number of hi-res tracks at over 2m, while Tidal claims 'only' over 1m. Amusingly, Android has such easy to use API for developers to play music gaplessly.Qobuz's comparatively high price has always been partly justified by its exhaustive library of hi-res music (FLAC 24-bit up to 192kHz). Google doesn't give a shit about gapless as long as Google Play Music mp3's can somewhat be played gaplessly (MSE supports mp3 and it is believed Google used it for their Google Music receiver). But writing such receiver will not be trivial, if at all possible. There is hope that at some point html5 Media Source Extensions (MSE) will support FLAC decoding, allowing to make a gapless FLAC receiver running on the Chromecast. And it has some drawbacks such as requiring the device generating the continuous stream running, and using more battery if playing FLAC or whatever format that must be decoded to PCM (not a problem on a desktop computer or NAS). Having the controlling software send a continous stream (such as HiFi Cast) is *not* an easy solution for developers, although it is the only one possible for now. Having gapless supported on the receiver side in a standard way (eg on the standard receiver made by Google) would make it easy for app developers to take advantage of it for ubiquitous and easy gapless playback. Instead the integration has become a constantly moving phantom.Ĭhromecast Audio. The issue would go away, if the integration of Qobuz into Roon would finally become a reality. But I guess that is what we are increasingly becoming.Ĭan someone enlighten me, if there is a target date, by when the Google Chromecast Audio issues will be fixed? I cannot imagine this to be rocket science. This really makes me feel like an RGU (revenue generating unit), not a customer. ![]() No indication on the website that there are issues. Qobuz does neither, yet treats Chromecast like a fully supported endpoint. Whatever Roon do in RoonCore to enable this, Qobuz would be able to do in the server that originates the Qobuz stream. Roon manages to stream to Google Chromecast Audio at 96kHz without issues and to stream gapless. Customers expect Chromecast to work without issues. They have been described in Qobuz' answers to customers' questions).ĭLNA in the Qobuz app has been declared Beta. Gapless playback using Chromecast is also not possible (I know there are technical hurdles. Looking through this thread, the Chromecast issues at 96kHz seem to be a widely known issue. Until I tried to stream 24/96 through my Google Chromecast Audio. In return I can now stream hires albums in hires, without purchasing them first. So I now have the pleasure of paying 50% more for my subscription. Not quite out of free will, but because Qobuz is cancelling the sublime product and will only have Studio and sublime+ going forward, both of which are more expensive than sublime was. I have recently upgraded my (France) sublime subscription to sublime +.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |