Rpi3/Dac+

Mad Prophet

Before I'm roasted at the stake, I did search and I've read most of the post/replies concerning this topic, but I remain confused.

I'm relatively new to Linux, have several RPi's but I'm still learning and very new to Rune. I'm also completely new to things like SSH.

If I might: Created the card, no problems. Booted my Pi3 (with monitor/kb). It was next to impossible (for me) to use the kb or mouse on the UI. I know it's meant to be used on touch, so no biggie. What was problematic is that nothing I changed would 'stick'. I could scan the available wifi networks, enter the info and...nothing. Then connected ethernet, boom. All works. Able to configure the wlan0 and get share working. Disconnect and move to room with the speakers.

Booted fine and was able to access via runeaudio.local with no problem. Except one: no sound.

My Pi3 has a Hifiberry DAC+ attached, but there's no option for selecting it, thus, no sound.

Going back and forth between forums for the Pi, Hifiberry and Rune, I've seen numerous fixes. I tried running the script found here via SSH and was returned Integer(0). When I tried to run refresh_ao, I was given 'no such command' (or something close to that. So I tried a simple reboot. No joy.

The next fix is to edit the file, uncommenting out the DAC+ entry. Or perhaps adding "dtoverlay=hifiberry-dacplus" tp config.txt as suggested by the Pi forums.

Or do I turn off Bluetooth as one post suggested?

My experience as a programmer (long ago) showed that making a bunch of changes then hoping it still works is unlikely to bear fruit. So wifi is working, the shares are working, the interface is working - only the choice of output devices and, of course, the resulting sound from that device isn't working.

tl:dr?
1) Which fix should I apply? To which file? This part is especially important to me as most references to file changes rarely list the file location. In a recent post I just read about adding access to a Airport Extreme attached USB HDD, it said to add this line and listed the line, but not which file to add the line to. Again, my inexperience is the problem, not the supplied help.
2) Can I simply pull the card, put it in my linux laptop and edit it or should I (which I'd prefer for the knowledge I'd gain) edit it using SSH?
3) Is there a way, using SSH, I can determine if the DAC+ card is working? (It worked in Volumio, but the sound was simply terrible.)

Thanks so much in advance.

hondagx35

Hi Mad Prophet,

there is nothing to fix.
The only thing you have to do is to configure your DAC in /boot/config.txt.

Enabling I2S DACs and digital output boards

A section in /boot/config.txt already includes device tree settings for supported boards, each line preceded by the comment symbol "#". When an I2S dac or an S/PDIF output board is installed, the corresponding device tree overlay has to be enabled by removing the "#" symbol from the corresponding line. Without this step, the OS kernel does not detect the board.

Example, enabling a HiFiBerry DAC+:

# Uncomment one of these lines to enable an audio interface
#device_tree_overlay=hifiberry-dac
device_tree_overlay=hifiberry-dacplus
#device_tree_overlay=hifiberry-digi
#device_tree_overlay=hifiberry-amp
#device_tree_overlay=iqaudio-dac
#device_tree_overlay=iqaudio-dacplus

......

After making the above changes, the Pi can be rebooted with all hardware installed.

When the Pi boots with a DAC board and the correct device tree overlay setting, the output device can be selected in the Rune UI, from a drop down list in Menu > MPD Configuration > Audio Output. The next steps are usually to configure the volume control and other MPD music options.

From here

This can be done via ssh or by putting the sd card in your pc.

Frank

Mad Prophet

I was concerned about doing the SSH editing, but as it turned out, I needn't have been. Super easy. Tried using hardware but it stayed at 100 - which caused my puli to hit the roof barking. Strange...she normally likes Slayer...

Perfect now - and great sound!