Audio Asylum Thread Printer
Get a view of an entire thread on one page
|For Sale Ads|
In Reply to: RE: Roon Ready? posted by Isaak J. Garvey on June 08, 2017 at 19:55:45
>> does your new digital hub, or any other component run Roon? <<
Yes, the Ayre QX-5 Twenty is "Roon Ready". What happens is this - an Ethernet input requires a medium-powered microprocessor to connect to the Ethernet - typically running some version of Linux modules. Obviously there is no need to support things like keyboards, displays, mice, and so forth. Instead it mostly just needs to handle the internet connection.
In addition the base Linux code can be modified to interface with other software. The module used by Ayre has "hooks" for Roon, Tidal, Spotify Connect, and Qobuz. Roon has the most rigorous test program and requires a complete unit sent to their test labs to both certify proper operation and then remain there so that they can both test new Roon releases and also verify other future compatibility issues.
This is one reason that setting up a Roon-based system is typically easier than setting up a UPnP-based system. While UPnP standards exist, there is no certifying body that enforces the standards. When setting up a UPnP-based Ethernet sytem, JRiver is one of the most robust pieces of software I've found and rarely has any compatibility issues with any hardware.
Strictly my own opinions, and not necessarily those of my employer or AI-enhanced life-sized doll.
Thanks. Great info.
The one thing I do admire about Roon is they take into account user feedback and they have continually, without deviation, improved the product.
I agree with you that JRiver is stable and robust and, in many ways, is flexible enough for almost anyone. One significant issue is that running it with a UpnP network client bypasses the DSP engine so that employing bass management and EQ is not possible. One must use a directly connected DAC.
OTOH, using Roon with a Roon Ready device allows the user to employ all the features of Roon including convolutions and other signal DSP.
Strictly my own opinions, and not necessarily those of my employer or Charles Hansen. ;-)
Thanks for the additional information. Could you please clarify something which is still fuzzy for me? Are you saying that Roon's DSP capabilities are more powerful than those in JRiver, or that Roon's architecture allows the use of additional 3rd party software that JRiver's architecture does not? (Or perhaps both?) Thanks!
Both have identified clear differences between the capabilities of Roon and JRiver - at least as they currently stand. For audio users, Roon may be advantageous. On the other hand JRiver also supports video devices and formats, which would likely tip the scales for home theater users. (But this is the Audio Asylum, isn't it?)
I was not distinguishing between their internal DSP capabilities since I have not really gotten a handle on that yet.
What I was referring to is that JRiver can apply the DSP to wired (local) output devices (e.g., via S/PDIF, AES/EBU, USB, etc.) but not to networked output devices (via ethernet or WiFi). The latter limitation can be bridged with an appropriate ASIO driver such as is supplied by Merging Technology for the NADAC.
OTOH, Roon can output DSP-processed signals to any connected device, local or networked.
Roon is able to stream to the HQPlayer; something JRiver cannot do.
While Roon's and JRiver's DSP capabilities are good, many folks prefer the HQPlayer for converting files to DSD.
Post a Message!
This post is made possible by the generous support of people like you and our sponsors: