Roon Vs jriver

[Cebolla]

On 3/24/2018 at 11:39 PM, One and a half said:

RAAT though has it all over Jriver stuck with DLNA. Hardware support from quite a few big name vendors is Roon's strength, it's a far better protocol than DLNA could ever be

Is that because you are using RAAT with synchronised multiple endpoint devices? Otherwise, why are you saying RAAT is a far better protocol than standard UPnP/DLNA? It certainly can't be because of the RAAT endpoint vs UPnP renderer hardware support count!

 

Incidentally, you can get Roon to play to any standard UPnP/DLNA renderer, despite Roon's (strange) lack of official support for the UPnP streaming protocol, by using the UPnPBridge/squeeze2upnp Logitech Media Server plugin to act as the go between. This is because Roon also supports the Slim/Squeezebox streaming protocol (in addition to RAAT,  HQPlayer & AirPlay). The UPnPBridge just needs to be configured as a standalone application (ie, no LMS required) and can then be run on any networked machine, including the one running Roon.

http://forums.slimdevices.com/showthread.php?103728-Announce-UPnPBridge-integrate-UPnP-DLNA-players-with-LMS-(squeeze2upnp)

 

 

On 3/24/2018 at 11:39 PM, One and a half said:

I don't use Tidal any more, but there should be a facility like that in Jriver since quite a few people use Tidal. Not going to happen though.

Windows JRiver users can use TIDAL's Desktop app and output the audio bit perfectly to JRiver's playback engine, via its WDM Driver. So this would include 'first unfold'/MQA core audio decoded from MQA Masters tracks. However, when using the JRiver WDM Driver as its input, the JRiver playback engine cannot be used for streaming over the network to UPnP/DLNA renderers and also there's no equivalent JRiver audio input driver for OS X and Linux JRiver users.

 

 

On 3/24/2018 at 11:39 PM, One and a half said:

As far as support is concerned Jriver has their interact forum and the wiki. The wiki is good for product five years ago, was never the full bottle. Interact is not necessarily interactive, more 'our way or the highway'.

Agreed. The JRiver Wiki's description of its UPnP/DLNA configuration is particularly poor.

 

[Cebolla]

8 hours ago, One and a half said:

23 hours ago, Cebolla said:

Is that because you are using RAAT with synchronised multiple endpoint devices? Otherwise, why are you saying RAAT is a far better protocol than standard UPnP/DLNA? It certainly can't be because of the RAAT endpoint vs UPnP renderer hardware support count!

 

I don't know which devices you've used on DLNA, I've tried two, a BD Player and Tuner. The object was to find audio tracks on a DLNA server and play them. Both failed, either the file couldn't be read, perhaps a 96/24 or it took that bloody long to find the file in the first place. When Roon recognises a network end point, selection of that zone is two mouse clicks, and the rest to search and play. DSD, 192, 96 all play from the word go.

 

Ok, so you were not actually comparing the RAAT vs UPnP/DLNA as protocols and were only having a moan at some supposed DLNA compliant devices, a BD Player & a 'Tuner' (a TV set top box/PVR, perhaps?), that you 'tested' in the past. So not really the specialised audio dedicated devices, ie, the UPnP/DLNA supporting network audio file renderers of the type most would recognise on these forums, that you could fairly compare with Roon endpoint devices.

 

From your description of the 'failures' , it appears the devices you tested were DLNA Digital Media Players (DMPs), as opposed to DLNA Digital Media Renderers (DMRs), which means you could not have controlled them from JRiver anyway - so completely off topic!

[Cebolla]

On 3/28/2018 at 11:58 AM, One and a half said:

 

The tested Onkyo Tuner Model T-4070 can be controlled from Jriver, also from Roon, so in essence a renderer, and still on topic, as the discussion is Jriver versus Roon, not renderers alone.  

Fair enough - though it's a relatively old 1st gen UPnP/DLNA renderer ~2010, so basics like gapless playback support also likely to be lacking.