![]() ![]() In conclusion, the topics I raise above may not be pertinent to your use, but the other comments above suggest there are indeed Bluesound users to whom they are. Equally, I don’t deny that there’s a role for “integrators” that can bring those services into one app, albeit with less features than the bespoke apps. Suppliers like Bluesound need to support all of these (at full lossless resolution) to stay in the game. I’d also say that the existence of casting mechanisms like Spotify Connect, Tidal Connect, Amazon AlexaCast and hopefully soon Qobuz Connect where users can retain the full feature set offered by streaming services rather than the diminished access thru the APIs offered to third parties is the way ahead. Plus the Heos app was, well, less than optimal. I couldn’t access the playlists I had created over the years in Amazon Music, nor access the tracks I had uploaded to Amazon Music when they offered that service. Nor could I include it in an Alexa multi room group with the echos my wider family use. When I abandoned it for WiiM, it was because it didn’t support lossless casting from the amazon music app nor thru Alexa, being CD quality at best if not indeed just lossy audio. My experience of Amazon Music integration before WiiM was largely thru Heos which is implemented in a similar to Bluesound. The official comment from Bluesound above is rather introverted and shortsighted and needs to be revised as it appears ignorant of the MRM stack. ![]() While the Bluesound interface may well years beyond other implementations, I’d argue by not being implemented using the newer MRM stack (as eloquently explained in the Naim link I provided above), it’s potentially well behind other implementations like WiiM that do use the MRM stack.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |