Roon Endpoint Streamers - Direct Comparisons between Current Offerings?


Have any of you directly compared sound quality between any of the current offerings of streamers when used solely as a Roon endpoint/streamer? This assumes Roon core and any local music file storage is being operated on a separate device (i.e., a separate server).

I have listed several of the current options below and while a few of those offer additional features, such as server capabilities, hosting of local file storage, or operating players unique to their manufacturers (i.e., other than Roon), I am interested in their performance solely as a Roon endpoint/streamer. Other suggestions not listed below are welcome, but please consider a $5K -$10K price range.

Streamers

  • Sonore Signature Rendu SE optical v3.0 - $5,350
  • Auralic Aries G2.2 - $6,099
  • Innuos Pulsar - $7,999

Server/Streamers

  • Aurender N200 - $6,300
  • Antipodes K22 - $9,000
mitch2

I know this is $2,500 above your specified budget, but I would be remiss if I didn't mention the wonderful Grimm MU1 streamer ($12,500 w/o storage, $300 additional with 2TB storage). Sonically the best I've heard!      

As I understand it, your streamer uses a Pi; not sure how Mesttum implements the Pi, but in its freestanding form, the pi has been measured as having more noise than a few other relatively inexpensive alternatives, such as the iFi Zen, the Volumio Rivo, the Holo Red, and the Pro-Ject S2 Ultra.  Not sure how immune from noise your dac is, but here’s an excerpt of a post by John Westlake, the S2 Uktra designer, regarding the Pi and his implementation:

“As a co-designer (with Jarek) I can help answer some questions about the ProJect Streambox S2 Ultra - ProJect is our 3rd OEM “customer” for our streamer solution :)

The roots of this design is based on our own internal requirement for a streaming solution for a crowd funded DAC I've been developing for the past few years. The crowd funded group consists of about 150 development sponsors – so I have to be creative to maximise the limited funding resources.

One requirement for the DAC was for a Streaming solution that allowed HiRes Bit Accurate (no data manipulation), DSD support and allowed the DAC to be Audio Clock master. With our limited 150pcs to 200pcs DAC production – nobody was interested in supplying a streaming solution so I was forced by such circumstances to turn to an open source software.

The Open Source community is very active in this area, but the hardware solutions are based on non optimised off-the-shelf computer hardware. While the Raspberry Pie is a great low cost computer hardware – however it’s been designed with cost as the primary objective and understandably not with audio optimisation anywhere near an important consideration.

So while there is zero chance we have the resources to develop / support the streaming software for our small volume group sponsored project, we can develop the hardware with our eyes closed shut.

It became apparent that Volumio offered the best feature set (just missing SBT / LMS support) – but as an old school turntable / CD user I struggled with its UI. I needed to find a way to have a customised version of Volumio, but with only 150 to 200 potential units there is no way we could afford to directly pay for the customised software development.

So, as our requirements where rather desirable for HiFi manufactures (Bit Accurate HiRes (no data manipulation), DSD support and allowed the DAC to be Audio Clock master) I developed a plan to offer our streamer hardware solution to a few select customers I’d worked with in past (who all struggled to find a decent streaming solution).

Now with a rather large carrot (the potential of large OEM sales) – I was able to convince Volumio’s founder Michelangelo that he could make a nice little business from developing a custom OEM version of his software that would work with our hardware platform – in exchange we would get a supported software solution for our 150 – 200 group funded DAC :)

After several false starts (BeagleBone, and a few other cheap Chinese SBC’s) we about gave up on the streamer side of the project when the raspberry Pie foundation released the long promised Quad Core industrial version of the RPi3. This industrial version of the RPi3 called the CM3 module allows us to optimise the streamer hardware (PSU, RF and Clocking) while maintaining software compatibility with RPI. An important goul of our streamer solution is that we wanted an optimised “audio” streaming solution while not limiting the customer to a single software solution – for those skilled in software they can install any of the RPI based media players (Moode, LMS and even Kodi) etc.

Another important advantage of the RPi based CM3 module is the use of onboard eMMC memory thereby removing reliability issues (and speed) when using “External” SDcards.



In answer to “why the extra cost” over the standard RPi3 – it’s required to give a basic explanation of the RPi3 weakness WRT high end audio applications (remember is designed as a lowest cost computer platform NOT a highend audio streamer). These weakness in no way are a criticism of the RPi3 – but rather its design limitation from my perspective as an audio designer.


Basically its weakness are all based on Clock Phase Noise (Jitter) and local PSU noise (which directly impacts the Jitter performance) and also the resultant local RF emissions:-



1. The USB HUB / LAN IC is clocked by the CM3 SoC which has significantly higher jitter then an external Clock oscillator. More detrimental is that fact that clock phase noise is heavily correlated with the SoC software processing – resulting in Data correlated jitter.



2. The USB HUB / LAN IC PLL clock circuits are powered from the switching supply rail that also powers the SoC Memory, so as data is “processed” though the memory this causes modulation of the PSu Rail directly correlated with the Data patterns which then modulates the critical PLL in the USB HUB / LAN which is used as our USB “source” via this noisy PSU rail.



3. As one would expect little care has been taken with the quality of the 5V rail for USB DAC power – in fact its really pretty poor by “Audio” standards.




4. There are multiple “free running” switching regulators on the RPi PCB – whose clocks are not related to the USB clock Rate so there switching products are free to induced multiple / complex RF and Ground noise spurie in the system.



I could list more weakness, but you can start to appreciate the “Deficiencies” (not unexpected) of the simple Rpi3.



1. The little ProJect streamer tackles these issues by making the USB 24MHZ clock the system “Clock master” and cleanly generating the LAN’s 25MHz clock and the multiple local switching supply’s operating from a divided down synchronised frequency of this 24MHz.



2. Great care has been taken with the internal PSU’s – I count 8 low noise PSU’s of the top of my head.



3. The USB host signal from the CM3 is RF filtered and USB “Detoxed” (the poor Phase noise of the CM3 USB Host controller) is attenuated by two Cascoded USB Hub bridges (and RF filter) resulting in a much attenuated USB Jitter on the “DAC” USB output.



4. The DAC 5V feed has a very low noise regulator – whose voltage and current can be monitored via the streamer software.



5. The DAC 5V USB voltage output can be disabled via software for DAC’s that don’t require 5V.



6. An external USB bypass to the DAC USB output is proved, this bypass “Detox’s” the external USB signal in the same manor as applied to the RPi CM3 USB Host output.



7. 16GB onboard eMMC is available for OS / software & local files.”
 

@ddgtt

+1 Grimm MU1

I think it is worth the money. I have had one in my system for a while. While it is not as good as my Aurrender W20SE nor is its price. I think it a good choice… or an Aurrender N20. Which I have not heard head to head… but I would wager on the N20… but no Roon for the N20.

Isn’t the Grimm MU1 a server/streamer combination? Any sonic advantage to using it in the streamer, or Roon endpoint, capacity only?

I like the Holo Audio Red as a Roon endpoint.  Well engineered with very low jitter.  Why spend $5K to $10K on something that is built to be a streamer with custom software etc. and then just using it as an endpoint?  Put the money you save into another component that will level up your sound in a more significant way.  Just my 2 cents.