No worries Jnan, we all started somewhere. (I’m still basically there).
This thread is about using a Raspberry Pi as an HQ Player Network Audio Adapter. HQ Player is a high quality software upsampler (among other things) that can be used as a Roon zone. When HQP is selected as a zone then it handles the output and the NAA is how it sends audio over Ethernet or Wi-Fi.
RoonBridge enables Roon to send audio over Ethernet or Wi-Fi to the device on which it is installed. It enables the device to be a Roon Output.
All Roon architectures require a Core and at least one Control and Output. The Core can have it’s own outputs directly from it. The main Roon program is all three; Core, Control and Output. Remotes (Further installations for Windows, Mac on other computers) are Control and Output. iOS is Control only. Android is Control and Output. RoonServer is Core and Output. RoonBridge is Output only.
RoonBridge can be installed on a Pi3 and it can then be chosen as a Zone in Roon and send USB to a DAC.
Excellent succinct instructions Rene. Thanks. I’ve also got a HiFiBerry Digi+ with a RPi2.
Everything went well for me until the final step of “apt-get install ./networkaudiod_3.1.1-27_armhf.deb” where I get heaps of lines saying:
“Note, selecting ‘…’ for regex ‘.’”
followed by
“Release ‘networkaudiod_3.1.1-27_armhf.deb’ for ‘…’ was not found”
(where the … is replaced by hundreds of different package names)
I also tried using wget and apt-get install for the newest networkaudiod package but same issue.
Does anyone know how I can fix this?
*edit: Actually I discovered an answer is already here. Installed the prebuilt image by Jussi from Signalyst and just edited the config.txt file adding dtoverlay=hifiberry-digi (opening it with textedit on my mac as the build isn’t accessible via ssh)
Now to try and get my head around the combinations of filter and dither options…
As a complete Linux novice I’m enjoying wonderful results with Rpi’s on Roonbridge with various HATs thanks to Rene’s wonderful instructions on the Armv7 thread. Flushed with this success, I thought to try HQP with NAA on a Pi. However, the pre-built Rpi images linked in this and other threads are coming up 404. Would you recommend I roll my own otherwise where can I find these?
@jussi_laako’s download server for NAA related stuff appears to be down for the moment. As this is this place where you’d get both the images and the packages, I’m afraid you’ll have to postpone your plans a bit.
The image versions are optimised for particular hardware and are stand alone when written to an SD. They overwrite anything on the SD. You can’t log in to the image version and install anything else.
NAA needs Debian Stretch to install/run; so you’ll need to upgrade Your Debian Jessie (or solve the required dependencies manually);
NAA and Roon Bridge do not coexist peacefully, as they both need to access Alsa. After playing HQP, NAA does keep its grip, so Roon Bridge cannot gain access (note: I have tried this with earlier versions, not 3.4), so you’ll need to manually stop and start roonbridge.service and networkaudiod.service.
Depending on your comfort level in Linux, flashing the prefab image to a different card may be easier.
I burned the image naa-340-raspberrypi3 image to a fresh SD card & added the overlay for my Dig+. HQP 3.13.3 on Mac sees the NAA and the Digi+ & all is sweetness & light until the music is paused in Roon. The NAA disappears and HQP is unresponsive. Force quit & reboot machine brings it back. Gets a little taxing after a bit.
Which daft thing have I done - any ideas?
Marty
For long time NAA releases the devices when not used. But you need to close HQPlayer, the device is reserved as long as HQPlayer is running to avoid runtime failures.
I had clicks and digital noise with a Raspberry 2 streaming DSD256 to an Ifi Micro iDSD.
I got a Raspberry 3 and all Noise and Clicks are gone. Now streaming DSD 256 is pure pleasure.
Is streaming DSD 512 with a Raspberry 3 as NAA possible? I will get a skylake 6700 based setup in July and want to organise the right NAA tool.
Is the Pi3 connected to your network via cable or wireless? I assume you are using the USB out connected to your iDSD? Any issues with drop outs due to the wired ethernet and usb being on the same bus?