BalenaSound with hifiberryAmp100

Product support
,
1

Hi everyone, I was wondering if it will be possible to use balena sound with the new hifiberry amp100 board.
Thank you in advance for your response.

Nathan

4

Hi,

Here is the list of supported DACs for BalenaSound https://sound.balenalabs.io/docs/audio-interfaces/#dac-boards, please give it a try and let us know if your board is not in the list. It’s simple to add support for a new DAC.

6

Hi,

I checked this document before posting, i saw that you use the same project for a lot of different hifiberry cards : hifiberry-dac.
Is it safe to use this project with my new hifiberry-amp100 board?

Nathan,

7

Hey Nathan,

From Hifiberry’s website, it looks like the dtoverlay for that board is hifiberry-amp100 which we don’t currently support on balenaSound. I would try hifiberry-amp as your BALENA_HOST_CONFIG_dtoverlay setting. It won’t hurt the DAC if it’s wrong, it just won’t produce sound. :slight_smile:

If that doesn’t work, and you need support for the correct overlay, let us know and we’ll raise an issue on the sound github repo.

Phil

9

After a glance over the Amp100 datasheet and product info, it looks to me like you need to use the hifiberry-dacplus DT overlay. The product page says it’s a combination of a DAC+ Pro and a 100W amp. Most of the DAC+ and DAC2 line use hifiberry-dacplus, including the Amp2. Another option to try is hifiberry-dacplushd, in case they used the higher-end DAC chip on that board.

10

Thank you really much for your answers :pray:!

11

I will keep you informed of the results.

13

Hi everyone, so i tried all the different BALENA_HOST_CONFIG_dtoverlay variables :

  • hifiberry-dac
  • hifiberry-dacplus
  • hifiberry-dacplushd
  • hifiberry-amp

What i did is that i took downloaded v2.58.3+rev 1 development version on you website, flashed it on a USB key.
1/Boot the rbpi
2/Changed the BALENA_HOST_CONFIG_dtoverlay variable
3/Shutdown the pi
4/Unplug power
5/Boot again and check results ( I basically send audio through spotify airply & bluetooth)

I tried to disabled Multiroom audio but i still did not get any sound, do you have any idea if i missed something ? The board seems to be detected which is a good sign though…

14

I checked the logs, the result is the same for all the different variables :
09.01.21 13:09:49 (+0100) audio>
09.01.21 13:09:49 (+0100) audio> — Audio —
09.01.21 13:09:49 (+0100) audio> Starting audio service with settings:
09.01.21 13:09:49 (+0100) audio> - Pulse log level: NOTICE
09.01.21 13:09:49 (+0100) audio> - Default output: AUTO
09.01.21 13:09:49 (+0100) audio>
09.01.21 13:09:49 (+0100) audio> Detected audio cards:
09.01.21 13:09:49 (+0100) audio> 0 ALSA bcm2835_alsa-bcm2835ALSA
09.01.21 13:09:49 (+0100) audio> 1 sndrpihifiberry HifiberryDacp-snd_rpi_hifiberry_dacplus
09.01.21 13:09:49 (+0100) audio>
09.01.21 13:09:49 (+0100) audio>
09.01.21 13:10:05 (+0100) audio> Waiting for sound supervisor to start
09.01.21 13:10:05 (+0100) audio> Setting audio routing rules. Note that this can be changed after startup.
09.01.21 13:10:05 (+0100) audio> Routing ‘balena-sound.input’ to ‘snapcast’.
09.01.21 13:10:05 (+0100) audio> Routing ‘balena-sound.output’ to ‘alsa_output.dac.stereo-fallback’.
09.01.21 13:10:06 (+0100) audio> W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified).
09.01.21 13:10:08 (+0100) audio> W: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
09.01.21 13:10:08 (+0100) audio> W: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

18

Hi Nathan,

Can you tell us more about your setup? What device are you using (e.g. Raspberry Pi 3) and are you using a 32-bit or 64-bit OS on it?

Phil

20

@nathanh did you ever manage to get the Hifiberry Amp100 running with balenaSound?

22

Hi everyone, hifiberry seems to have introduced a new dtoverlay specific to this device, called hifiberry-amp100
Anyway i managed to realize what i wanted to do with their own os…
Thank you really much for your help!

24

hifiberry-amp100 is the correct setting. I’ve tested it. And you should also remove “vc4-kms-v3d” dt overlay setting.

Refer to this setting https://www.hifiberry.com/docs/data-sheets/datasheet-amp100/ and https://www.hifiberry.com/docs/software/configuring-linux-3-18-x/