No sound from Pi Zero W + Dac+ Zero

Hi,

I've been unable to get a peep out of my DAC+ zero hooked up to a Raspberry Pi Zero W, want to use this as a spotify client.

Initially I used a hand-soldered header version, but subsequently switched to a replacement with factory-soldered header, so I don't think it's the problem

Followed the instructions here https://www.hifiberry.com/docs/software/configuring-linux-3-18-x and can see the device with aplay -l:

**** List of PLAYBACK Hardware Devices ****

card 0: sndrpihifiberry [snd_rpi_hifiberry_dac], device 0: HifiBerry DAC HiFi pcm5102a-hifi-0 [HifiBerry DAC HiFi pcm5102a-hifi-0]

Subdevices: 1/1

Subdevice #0: subdevice #0

but speaker-test produces no sound. raspotify seems to be working OK but it also produces no sound:

> sudo systemctl status raspotify

* raspotify.service - Raspotify
Loaded: loaded (/lib/systemd/system/raspotify.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2021-04-10 16:00:46 AEST; 10min ago
Process: 451 ExecStartPre=/bin/mkdir -m 0755 -p /var/cache/raspotify (code=exited, status=0/SUCCESS)
Process: 452 ExecStartPre=/bin/chown raspotify:raspotify /var/cache/raspotify (code=exited, status=0/SUCCESS)
Main PID: 453 (librespot)
Tasks: 3 (limit: 881)
CGroup: /system.slice/raspotify.service
└─453 /usr/bin/librespot --name raspotify (zerodac) --device-type speaker --backend alsa --bitrate 160 --disable-audio-cache --enable-volume-normalisation --volume-ctrl linear --initial-volume 100 --username outsider137 --password XXXXXXXXX

Apr 10 16:00:47 zerodac librespot[453]: [2021-04-10T06:00:47Z INFO librespot_core::session] Connecting to AP "gae2-accesspoint-e-hl02.ap.spotify.com:4070"
Apr 10 16:00:48 zerodac librespot[453]: [2021-04-10T06:00:48Z INFO librespot_core::session] Authenticated as "outsider137" !
Apr 10 16:00:48 zerodac librespot[453]: [2021-04-10T06:00:48Z INFO librespot_playback::audio_backend::alsa] Using alsa sink
Apr 10 16:00:48 zerodac librespot[453]: [2021-04-10T06:00:48Z INFO librespot_core::session] Country: "AU"
Apr 10 16:04:17 zerodac librespot[453]: [2021-04-10T06:04:17Z INFO librespot_playback::player] Loading <Swim and Sleep [Like a Shark]> with Spotify URI <spotify:track:1QjiO5JBzztmaZ9lPnt5uE>
Apr 10 16:04:19 zerodac librespot[453]: [2021-04-10T06:04:19Z INFO librespot_playback::player] <Swim and Sleep (Like a Shark)> (165226 ms) loaded

I also had a look at the logs again following the instructions

$ sudo vcdbg log msg
001338.102: brfs: File read: /mfs/sd/config.txt
001338.881: brfs: File read: 1820 bytes
001390.846: HDMI0:EDID error reading EDID block 0 attempt 0
001392.111: HDMI0:EDID error reading EDID block 0 attempt 1
001393.377: HDMI0:EDID error reading EDID block 0 attempt 2
001394.641: HDMI0:EDID error reading EDID block 0 attempt 3
001395.907: HDMI0:EDID error reading EDID block 0 attempt 4
001397.172: HDMI0:EDID error reading EDID block 0 attempt 5
001398.438: HDMI0:EDID error reading EDID block 0 attempt 6
001399.702: HDMI0:EDID error reading EDID block 0 attempt 7
001400.968: HDMI0:EDID error reading EDID block 0 attempt 8
001402.232: HDMI0:EDID error reading EDID block 0 attempt 9
001403.256: HDMI0:EDID giving up on reading EDID block 0
001406.422: brfs: File read: /mfs/sd/config.txt
001407.097: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined
001426.790: brfs: File read: 1820 bytes
001604.220: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined
001604.275: *** Restart logging
001605.019: hdmi: HDMI0:EDID error reading EDID block 0 attempt 0
001606.288: hdmi: HDMI0:EDID error reading EDID block 0 attempt 1
001607.555: hdmi: HDMI0:EDID error reading EDID block 0 attempt 2
001608.824: hdmi: HDMI0:EDID error reading EDID block 0 attempt 3
001610.092: hdmi: HDMI0:EDID error reading EDID block 0 attempt 4
001611.361: hdmi: HDMI0:EDID error reading EDID block 0 attempt 5
001612.628: hdmi: HDMI0:EDID error reading EDID block 0 attempt 6
001613.897: hdmi: HDMI0:EDID error reading EDID block 0 attempt 7
001615.165: hdmi: HDMI0:EDID error reading EDID block 0 attempt 8
001616.434: hdmi: HDMI0:EDID error reading EDID block 0 attempt 9
001617.459: hdmi: HDMI0:EDID giving up on reading EDID block 0
001617.793: hdmi: HDMI0:EDID error reading EDID block 0 attempt 0
001619.062: hdmi: HDMI0:EDID error reading EDID block 0 attempt 1
001620.330: hdmi: HDMI0:EDID error reading EDID block 0 attempt 2
001621.599: hdmi: HDMI0:EDID error reading EDID block 0 attempt 3
001622.867: hdmi: HDMI0:EDID error reading EDID block 0 attempt 4
001624.136: hdmi: HDMI0:EDID error reading EDID block 0 attempt 5
001625.403: hdmi: HDMI0:EDID error reading EDID block 0 attempt 6
001626.672: hdmi: HDMI0:EDID error reading EDID block 0 attempt 7
001627.940: hdmi: HDMI0:EDID error reading EDID block 0 attempt 8
001629.209: hdmi: HDMI0:EDID error reading EDID block 0 attempt 9
001630.234: hdmi: HDMI0:EDID giving up on reading EDID block 0
001630.278: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
001630.301: HDMI0: hdmi_pixel_encoding: 162000000
001630.549: vec: vec_middleware_power_on: vec_base: 0x7e806000 rev-id 0x00002708 @ vec: 0x7e806100 @ 0x00000420 enc: 0x7e806060 @ 0x00000220 cgmsae: 0x7e80605c @ 0x00000000
001636.047: dtb_file 'bcm2708-rpi-zero-w.dtb'
001636.064: Trying Device Tree file 'bcm2708-rpi-zero-w.dtb'
001640.442: brfs: File read: /mfs/sd/bcm2708-rpi-zero-w.dtb
001640.465: Loading 'bcm2708-rpi-zero-w.dtb' to 0x100 size 0x65f5
001650.018: dtdebug: delete_node(/__local_fixups__)
001652.888: brfs: File read: 26101 bytes
001664.908: dtdebug: using platform 'bcm2835'
001667.006: brfs: File read: /mfs/sd/overlays/overlay_map.dtb
001668.357: dtdebug: overlay map loaded
001669.932: dtdebug: /aliases:i2c_vc=i2c0
001674.956: dtdebug: /__symbols__:i2c_vc=i2c0
001678.469: dtdebug: /__overrides__:i2c_vc=i2c0
001685.663: dtdebug: /__overrides__:i2c_vc_baudrate=i2c0_baudrate
001687.222: dtdebug: /aliases:i2c=i2c1
001692.394: dtdebug: /__symbols__:i2c=i2c1
001695.959: dtdebug: /__overrides__:i2c=i2c1
001697.550: dtdebug: /aliases:i2c_arm=i2c1
001702.750: dtdebug: /__symbols__:i2c_arm=i2c1
001706.298: dtdebug: /__overrides__:i2c_arm=i2c1
001713.571: dtdebug: /__overrides__:i2c_baudrate=i2c1_baudrate
001720.858: dtdebug: /__overrides__:i2c_arm_baudrate=i2c1_baudrate
001724.841: dtparam: uart0_clkrate=48000000
001727.599: dtdebug: /__overrides__ has no uart0_clkrate property
001727.615: Unknown dtparam 'uart0_clkrate' - ignored
001727.638: brfs: File read: 1523 bytes
001731.710: brfs: File read: /mfs/sd/config.txt
001732.717: brfs: File read: 1820 bytes
001737.589: dtdebug: Opened overlay file 'overlays/hifiberry-dac.dtbo'
001738.417: brfs: File read: /mfs/sd/overlays/hifiberry-dac.dtbo
001747.819: Loaded overlay 'hifiberry-dac'
001754.708: dtdebug: merge_fragment(/soc/i2s@7e203000,/fragment@0/__overlay__)
001754.734: dtdebug: +prop(status)
001755.314: dtdebug: merge_fragment() end
001755.470: dtdebug: merge_fragment(/,/fragment@1/__overlay__)
001762.126: dtdebug: merge_fragment(/pcm5102a-codec,/fragment@1/__overlay__/pcm5102a-codec)
001762.155: dtdebug: +prop(#sound-dai-cells)
001763.040: dtdebug: +prop(compatible)
001763.845: dtdebug: +prop(status)
001764.704: dtdebug: merge_fragment() end
001764.731: dtdebug: merge_fragment() end
001775.045: dtdebug: merge_fragment(/soc/sound,/fragment@2/__overlay__)
001775.071: dtdebug: +prop(compatible)
001775.398: dtdebug: +prop(i2s-controller)
001776.007: dtdebug: +prop(status)
001776.328: dtdebug: merge_fragment() end
001782.444: brfs: File read: 655 bytes
001784.630: brfs: File read: /mfs/sd/cmdline.txt
001784.665: Read command line from file 'cmdline.txt':
001784.684: 'console=serial0,115200 console=tty1 root=PARTUUID=ba131b2e-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait'
001791.676: dtparam: uart1=off
001794.286: dtdebug: found override uart1
001794.322: dtdebug: override uart1: string target 'status'
003856.009: dtparam: cam0-pwdn=44
003858.617: dtdebug: found override cam0-pwdn

any ideas? thanks

JPT April 11, 2021 10:43

did you try alsamixer?
I read somewhere to press the M key to mute/unmute.

If this doesn't help, then same problem here ;)

Duncan Galloway April 15, 2021 06:15

my alsamixer reports "this sound device does not have any controls" :(

HiFiBerry team April 15, 2021 07:02

speakertest is NOT a good tool for tests. Have a look here:
https://www.hifiberry.com/docs/software/playing-test-sounds/

BTW: The easiest way to get Spotify running for most people is HiFiBerryOS (https://www.hifiberry.com/os)

JPT April 15, 2021 07:11

I found somewhere that the DAC+ zero does not have a hardware volume control. so this is correct. my mistake. use the softvol alsa plugin if you need volume control.

my DAC+ zero works perfectly fine on a different Pi where alsamixer doesn't show any controls either. This is not the source of the problem.

I believe I remember different, but the hifiberry staff tells me that the driver NEVER is loaded automatically. Well... no idea. going to try with a cheap USB sound card.

Duncan Galloway April 19, 2021 07:10

Thanks JPT & team for the feedback

I tried instead installing HiFiBerryOS, and got it up and running, and communicating via the web portal.

However I don't see "Spotify" in the source list. How do I add it?

HiFiBerry team April 19, 2021 07:11

Spotify isn't supported in HBOS for the Pi Zero. Sorry, I didn't think about this before.

Edited by HiFiBerry team April 19, 2021 07:11

Duncan Galloway April 19, 2021 07:43

Really? it's appearing in my Spotify client as an option (although I can't play anything).

And "systemctl status spotify" reports

● spotify.service - Vollibrespot
Loaded: loaded (/usr/lib/systemd/system/spotify.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2020-09-12 12:20:09 UTC; 1min 4s ago
Process: 899 ExecStartPre=/opt/hifiberry/bin/bootmsg Starting Vollibrespot (code=exited, status=0/SUCCESS)
Process: 903 ExecStartPre=/opt/hifiberry/bin/store-volume /tmp/spotifyvol (code=exited, status=0/SUCCESS)
Process: 909 ExecStartPost=/usr/bin/sleep 1 (code=exited, status=0/SUCCESS)
Process: 910 ExecStartPost=/opt/hifiberry/bin/restore-volume /tmp/spotifyvol (code=exited, status=0/SUCCESS)
Process: 919 ExecStartPost=/usr/bin/rm /tmp/spotifyvol (code=exited, status=0/SUCCESS)
Main PID: 908 (vollibrespot)
Tasks: 1 (limit: 795)
CGroup: /system.slice/spotify.service
└─908 /usr/bin/vollibrespot -c /etc/vollibrespot.conf

Sep 12 12:20:05 kitchen systemd[1]: Starting Vollibrespot...
Sep 12 12:20:07 kitchen vollibrespot[908]: vollibrespot v0.2.2 UNKNOWN UNKNOWN (librespot 1a224a3 2020-10-25) -- Built On 2021-02-03
Sep 12 12:20:07 kitchen vollibrespot[908]: Reading Config from "/etc/vollibrespot.conf"
Sep 12 12:20:07 kitchen vollibrespot[908]: [Vollibrespot] : Using Alsa backend with device: default
Sep 12 12:20:09 kitchen systemd[1]: Started Vollibrespot.

Can I not just edit /etc/vollibrespot.conf to include my Spotify credentials, and then stream?

HiFiBerry team April 19, 2021 07:44

It might have been slipped in, but I can't say if this is working at all. It will probably stop working again after the next update.

Duncan Galloway April 19, 2021 08:34

Can confirm it works in the version I have, but the playback is uneven and with frequent interruptions. Bandwidth or processor limitations?

I guess this is why you it's not "officially" included as an option?

HiFiBerry team April 19, 2021 08:37

Hard to say. We generally don't recommend the Pi Zero:
https://www.hifiberry.com/blog/pi-zero-for-audio-projects/

The Node.JS component the the Pi Zero is already unsupported. It it possible that the Pi Zero support in HBOS will be stopped completely at some point in the future.

Duncan Galloway April 19, 2021 09:04

You should probably include these caveats on the product page of the DAC+ Zero – the form factor makes it very appealing to use with the pi Zero https://www.hifiberry.com/shop/boards/hifiberry-dac-zero

HiFiBerry team April 19, 2021 09:05

It has nothing to do with the DAC+ Zero, but with the Pi Zero. And we also know that some people don't agree with our opinion ;-)

No sound from Pi Zero W + Dac+ Zero

12 comments