02-13-2021, 10:05 PM
(This post was last modified: 02-13-2021, 10:43 PM by TheOldPresbyope.
Edit Reason: ETA Spotify; PS:
)
@officialsm
So there are three methods to stream Qobuz tracks through a moOde player.
1. Use an official Qobuz mobile app or Web player on some other host and direct the audio output to moOde's Bluetooth or Airplay renderer. The chosen alternative renderer has to be enabled, of course.
2. Use a 3rd party DLNA Media Player / UPnP AV Control Point or OpenHome Player with built-in Qobuz service, again on some other host, and direct the audio output to the moOde UPnP Renderer. The UPnP Renderer has to be enabled as well as its correct service (UPnP AV or Openhome, or both in many cases). BubbleDS is an example of a Qobuz-enabled OpenHome player available for Android devices.
In this method, it is not necessary to enter Qobuz credentials in moOde's UPnP Config page. They are entered into the 3rd party app. One navigates to Qobuz in the cloud, not in a local server.
3. Alternatively, use a 3rd party DLNA Media Player /UPnP AV Control Point / OpenHome Player but with the Qobuz service enabled in moOde's UPnP Config page. In this case, one navigates to Qobuz in the moOde UPNP-mediaserver.
There are essential differences between OpenHome and UPnP AV / DLNA protocols, but I'm not going to discuss them here. Consult your favorite search engine.
Similarly, there are differences among all the 3rd party apps, some of which have caused problems for the upmpdcli developer. Again, I'm not going to discuss them here. Consult the upmpdcli website, which touches on some of the protocol issues as well.
At one time or another I've fiddled with the Bubble apps, with various Linn apps (Kinsky, Kazoo), and also with mconnectLite, either on Android or iOS. For the most part, I don't like any of them and I'm not going to try to walk anyone else through them.
When I listen to a paid streaming service I use the service's bespoke app. I'm so old my ears can't discern the difference between streaming direct to moOde and streaming through Airplay and IMHO my iPad 9.7' is the right-sized handheld for exploring their apps (and the moOde WebUI, for that matter).
I haven't mentioned Tidal here but the principle is the same. Other nice streaming services such as Primephonic and AmazonMusicHD, are accessible only by method #1.
ETA - Spotify is off in its own little world where one has to use method #1 with the audio output directed to the moOde Spotify Renderer, which has to be enabled, of course.
Regards,
Kent
PS - the Qobuz credentials have to be correct for the service level being corrected. I've had some interesting glitches with my credentials not being validated in one app or another (or in the upmpdcli qobuz plugin) and then working another day.
So there are three methods to stream Qobuz tracks through a moOde player.
1. Use an official Qobuz mobile app or Web player on some other host and direct the audio output to moOde's Bluetooth or Airplay renderer. The chosen alternative renderer has to be enabled, of course.
2. Use a 3rd party DLNA Media Player / UPnP AV Control Point or OpenHome Player with built-in Qobuz service, again on some other host, and direct the audio output to the moOde UPnP Renderer. The UPnP Renderer has to be enabled as well as its correct service (UPnP AV or Openhome, or both in many cases). BubbleDS is an example of a Qobuz-enabled OpenHome player available for Android devices.
In this method, it is not necessary to enter Qobuz credentials in moOde's UPnP Config page. They are entered into the 3rd party app. One navigates to Qobuz in the cloud, not in a local server.
3. Alternatively, use a 3rd party DLNA Media Player /UPnP AV Control Point / OpenHome Player but with the Qobuz service enabled in moOde's UPnP Config page. In this case, one navigates to Qobuz in the moOde UPNP-mediaserver.
There are essential differences between OpenHome and UPnP AV / DLNA protocols, but I'm not going to discuss them here. Consult your favorite search engine.
Similarly, there are differences among all the 3rd party apps, some of which have caused problems for the upmpdcli developer. Again, I'm not going to discuss them here. Consult the upmpdcli website, which touches on some of the protocol issues as well.
At one time or another I've fiddled with the Bubble apps, with various Linn apps (Kinsky, Kazoo), and also with mconnectLite, either on Android or iOS. For the most part, I don't like any of them and I'm not going to try to walk anyone else through them.
When I listen to a paid streaming service I use the service's bespoke app. I'm so old my ears can't discern the difference between streaming direct to moOde and streaming through Airplay and IMHO my iPad 9.7' is the right-sized handheld for exploring their apps (and the moOde WebUI, for that matter).
I haven't mentioned Tidal here but the principle is the same. Other nice streaming services such as Primephonic and AmazonMusicHD, are accessible only by method #1.
ETA - Spotify is off in its own little world where one has to use method #1 with the audio output directed to the moOde Spotify Renderer, which has to be enabled, of course.
Regards,
Kent
PS - the Qobuz credentials have to be correct for the service level being corrected. I've had some interesting glitches with my credentials not being validated in one app or another (or in the upmpdcli qobuz plugin) and then working another day.