One thing I can add is that I never listen to vanilla Roon. In every case, there are things that can be done with the DSP to make the sound better (to my ears) including application of convolution filters for specific headphone models, room correction, correction for listening position, and various parametic EQ tweaks to make things sound just right to me (and clearly different from default "flat" DSP) in each case. I use Roon in 6 rooms, on 3 systems, and with 4 different models of headphones. Each of these sound way different without Roon DSP. Now they all sound a lot more similar and "better" to my ears. I target a flat response initially then tweak to personal preference from there. In the case of my good sounding yet highly compromised (on the grand scale of things) desktop system I also invert phase.
Aurender is finally Roon Ready?!
Saw a note on the latest Conductor 4 update that it adds Roon Ready capabilities to N20. I have N200 so I can’t try it yet, but am curious to hear from those with N20 who had tried Roon with it, as I’m assuming and hoping that this update will be made available for the N200 as well.
Here’s a bit about it from Aurender…
https://aurender.com/roon_ready/
- ...
- 40 posts total
I have a couple DSD256 recordings downloaded. Roon settings limit to DSD128. When I played those DSD256 files via Roon on the Aurender N30SA, my DAC’s display showed DSD256. I don’t know what was happening there, but I assume the DAC was displaying the file it was receiving. Why the discrepancy, I have no idea. |
@tvad I streamed DSD and on the N200 display it showed as 32/352.8khz I guess with the N200 implementation they limited streamed bitrate to above whereas on the N30S it’s a straight shot despite the settings that appear to limit it to DSD128. could just be a bug. |
That’s a cool album @tvad ! Thanks for sharing the settings! |
- 40 posts total