Sorry for the slow response, @Dan_Knight …this was lost in the holiday shuffle.
We don’t have plans to allow Roon Bridge to talk to non hw:X,X devices because a number of things fall apart if we can’t be sure we’re talking to a hardware device.
In many cases, the default device presents “wide-open” hardware capabilities, which interferes with Roon’s ability to make good decisions about sample rate and bit depth conversions. Non-hardware devices sometimes perform faster-than-realtime buffering or pre-loading, which interferes with our clock management and synchronization technologies. Also, having arbitrary downstream DSP undermines the integrity and usefulness of Roon’s signal path display.
As far as EQ is concerned, Roon 1.3 will ship with its own parametric equalizer and will be able to load convolution filters generated by external EQ software.
Makes sense when aiming for highest possible audio quality, and, especially considering 1.3 will have its own built in EQ, looking forward to it!
Any chance we will see the ARMv8 Roon Bridge binaries released to public before/with Roon 1.3? We are keen to add Roon Bridge installation for our Odroid C2/Pine A64 users:
How does one change the name that shows in the device list for networks i.e. FIng from DietPi to something more meaningful like loungepi etc? One of mine is called Raspberry and the other DietPi but no idea how to or where to change them
On a more serious note: you have my utmost respect making Linux manageable for the uninitiated on those SBC’s.
(And on an even more serious note: don’t bother with Cuboxes unless you have serious time to spare, you’re bored and it is raining outside. Mine are doing just fine with Armbian – and with DietPi you appear to be skating where the puck is going to be instead of where it was yesterday. That looks like a good investment, time-wise.)
I have dietpi properly configured with roonbridge on a new RP3 equipped with a HIFIBERRY DIGI+. It’s working fine if I send an audio signal directly from Roon to that roonbridge, but when I attempt to link zones together with my main listening zone the audio quits playing on the RP3/DIGI+. Other than that it’s working fine as a roonbridge for direct playback.
Has anyone a suggestion regarding this behavior? Is this something I need to ask Roon about directly?
Should be fine I link pi3 and pi2 running Dietpi with another RAAT device and its rock solid.
What’s the device? Does it play fine by itself? All hard-wired?
Besides the HifiberryDigi+/RP3, I have both a Win10 laptop in my main listening room and my main gaming pc in another room running roonbridge.
I have a somewhat novel setup on my laptop to allow me the benefit of upsampling, speaker, and room correction in my main listening room. I’m using Reaper DAW mastering software along with FABFILTER, et al. professional VST Plugins to tailor the sound in my main listening room and tame a rising top-end on my horn loaded speakers. Reaper can be configured to allow audio outputted to it’s own ASIO device that roonbridge can see and output audio too. The sound is then manipulated in the digital domain with VST Plugins before being outputted to my USB Benchmark Media DAC2 HGC.
Figured out the problem. Roon was upsampling to Reaper on my laptop because the Reaper app was requesting 96kz from Roon. Once I matched the bit depths and bit rates Roon stopped oversampling and outputted properly to all my zones. When I thought about the problem it occurred to me that this extra upsampling by Roon to only one zone adds latency that makes syncing between zones properly problematic. My main listening configuration is temporary until Roon releases V1.3, but I needed some way to correct my horns rising top end and this convoluted solution accomplishes that and allows me the use of any VST plugins. Thanks for the suggestions.
We were staring down the barrel of this problem when considering the prospect of doing “Roon Bridge Kit”. It’s a lot of work that really only needs to be done once, and not something that vendors like us should be doing in a fragmented way.
I’m looking forward to playing with DietPi when I get a chance to dive into these guys…
Setup a NanoPi Neo with DietPi and it took me less than 10 minutes. I use it in my home office with an Audioquest Dragonfly connected to powered speakers. Works flawlessly and SQ is very good.
In my main rig I have an RPi2 with a Kali Reclocker, also set up with DietPi. Works beautifully as well.
@Dan_Knight Thanks for the great software - easiest Linux install ever.
Is there a particular setting to enable the HifiBerry Digi+ PRO?
DietPi-Config -> Audio Options -> Soundcard settings only lists a “hifiberry-digi” option with a description referring to “HifiBerry DIGI / DIGI+”. It seems to be working fine if I select that option, but I wanted to be sure I’m not missing something.
The Digi+ Pro is autodetected – you can set your soundcard to ‘none’ in dietpi-config.
It will work just fine with the standard Digi driver as well – you can verifiy that the Pro-driver is loaded by issuing ‘aplay -l’. If there’s ‘Pro’ in the string, you’re all set.
.
