PI5 with Raspberry Pi OS (64bit) and AMP2 - audio with only half the speed

michael

January 30, 2024 16:33

None

I just got my Pi 5 and installed my working AMP2 on it and read the documentation. The AMP2 works, but the playback is in slow-motion (half the speed).

My setup looks like this:

Pi5 + original Pi Fan + GPIO Extension (6.2mm from Berrybase) + Hifiberry AMP2

The config looks like this:

/boot/firmware/config.txt

dtoverlay=vc4-kms-v3d,noaudio
dtparam=audio=off
dtoverlay=hifiberry-dacplus,slave
force_eeprom_read=0

/etc/asound.conf

pcm.!default {
type hw card 0
}
ctl.!default {
type hw card 0
}

aplay -l

card 0: sndrpihifiberry [snd_rpi_hifiberry_dacplus], device 0: HiFiBerry DAC+ HiFi pcm512x-hifi-0 [HiFiBerry DAC+ HiFi pcm512x-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0

And audio-Playback:

MPlayer UNKNOWN-12 (C) 2000-2023 MPlayer Team
do_connect: could not connect to socket
connect: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing /home/pi/sound/doorbell.mp3.
libavformat version 59.27.100 (external)
Audio only file format detected.
Load subtitles in /home/pi/sound/
==========================================================================
Opening audio decoder: [mpg123] MPEG 1.0/2.0/2.5 layers I, II, III
AUDIO: 44100 Hz, 2 ch, s16le, 40.0 kbit/2.83% (ratio: 5000->176400)
Selected audio codec: [mpg123] afm: mpg123 (MPEG 1.0/2.0/2.5 layers I, II, III)
==========================================================================
AO: [pulse] Init failed: Connection refused
Failed to initialize audio driver 'pulse'
AO: [alsa] 44100Hz 2ch s16le (2 bytes per sample)
Video: no video
Starting playback...
A: 2.0 (01.9) of 4.0 (04.0) 0.1%

Exiting... (End of file)

pigpiod is disabled as someone wrote it could mess up the audio, but was preinstalled.

Please help me, as i´m out of ideas and the Board worked flawlessly on my Pi3b a day ago.

Thank you

Date Votes

24 comments

0

michael January 31, 2024 05:00

I think it has something to do with the clock signal of the Pi.

This is in dmesg:

[ 1377.329927] pcm512x 1-004d: No SCLK, using BCLK: -2
[ 3130.506369] pcm512x 1-004d: No SCLK, using BCLK: -2
[ 3131.385633] pcm512x 1-004d: No SCLK, using BCLK: -2
[ 4931.200285] pcm512x 1-004d: No SCLK, using BCLK: -2
[ 4932.073795] pcm512x 1-004d: No SCLK, using BCLK: -2
[ 5873.030276] pcm512x 1-004d: No SCLK, using BCLK: -2
[ 5873.902939] pcm512x 1-004d: No SCLK, using BCLK: -2
[ 6138.682193] pcm512x 1-004d: No SCLK, using BCLK: -2

Comment actions Permalink
1

HiFiBerry team January 31, 2024 07:14

The clock messages are perfectly normal. We can't see this issue here, but there are probably still some bugs in HBOS64. Please open a bug report here:
https://github.com/hifiberry/hifiberry-os/issues

Also check if you can reproduce the issue with other sources.

Comment actions Permalink
0

michael January 31, 2024 07:34

I do not use hifiberry-os. I use the official Raspberry Pi OS (64 bit).

Comment actions Permalink
0

michael January 31, 2024 07:38

As many have suggested with previous versions of the Pi there could be an issue with a wrong configured gpio (PCM / PWN) and i have no idea how to check for the correct setting.

Comment actions Permalink
1

HiFiBerry team January 31, 2024 08:07

Have you upgraded to the latest kernel version? Make sure you update the kernel as there is still a lot of work on the Pi kernel and you might have one with a bug.

This is a plain installation with no additional software installed - right?

Comment actions Permalink
0

michael January 31, 2024 11:43

Yes, the system is fully updated with the following Kernel and no additional software besides nut, lm-sensors, lnav, mplayer installed:

Linux rpi-og 6.1.0-rpi8-rpi-2712 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 (2024-01-25) aarch64 GNU/Linux

Comment actions Permalink
1

HiFiBerry team January 31, 2024 13:46

God new: You're right.
Bad news: It's a bug. This means it'll take a bit until it's fixed.

It seems there was a change mode in the Pi 5 kernel in December that might have caused. This. We don't know yet, but we'll work with the Raspberry Pi guys to get it fixed.

There is a potential workaround. If you can force your application to use 32bit sample format, it'll play at normal speed as this bug affects only 16bit samples.

With sox you can easily check the difference:

play -n -b 16 synth sine 1000
play -n -b 32 synth sine 1000

Comment actions Permalink
0

michael January 31, 2024 13:59

Perfect, thank you. I use mplayer and i dont think theres an option to force it to 32bit sample format. But i check with the "play" command at home and get in touch again.

Comment actions Permalink
0

michael January 31, 2024 15:50

It works now :) i used the "-format s32le" option with mplayer to force it to 32bit sample format and it now works flawlessly.

Thank you so much :)

Comment actions Permalink
2

HiFiBerry team February 02, 2024 09:09

Strangely, this isn't a new bug, but a very old one. It just never created a problem on older Pi's. The bugfix has been merged into the Raspberry Pi kernel sources yesterday. It should be available with the next Pi kernel update (probably in the next 1-2 weeks).

Edited by HiFiBerry team February 02, 2024 09:09

Comment actions Permalink
0

michael February 02, 2024 09:21

nice, thank you :)

Comment actions Permalink
0

NicoLapse February 10, 2024 18:16

Hi,
Have the same problem since few weeks.
With a Hifiberry DACplus
Thx.

Comment actions Permalink
0

HiFiBerry team February 12, 2024 07:24

Did you upgrade to the latest kernel using rpi-update?
Unfortunately I can't say when the Pi foundation will release a new kernel via rpi-update, but usually this doesn't take more than 1-2 weeks.

Comment actions Permalink
0

NicoLapse February 12, 2024 16:25

Yes, upgrade done 4 days ago with rpi-update.
Ok, I'll try again in few days !

Comment actions Permalink
1

HiFiBerry team February 12, 2024 20:22

Accoridng to the archive, it was updated 4 days ago:
https://github.com/raspberrypi/firmware

But I see that this is a 6.6 kernel. Try an rpi-update now and let me know what kernel version you get. I'm not sure if they already merged the 6.1 changed into 6.6.

Comment actions Permalink
0

NicoLapse February 12, 2024 20:46

Indeed, I was on version 6.1, and I now see version 6.6 available.
I'll test it tomorrow and I'll let you know !
Thx !

Comment actions Permalink
0

NicoLapse February 13, 2024 18:37

Unfortunately, despite updating the firmware of my Pi5, I still have the same issue. The sound is slowed down: a piece of music that usually lasts 2 minutes will take 3 minutes, and the notes are lower than usual.

Comment actions Permalink

NicoLapse February 20, 2024 01:10

Ok problem solved with the addition of
format "48000:32:2"
in the mpd conf file.

Which give :
audio_output {
        alsa type
        name “My ALSA Device”
        device "hw:0,0"
        mixer_type "software"
        mixer_device "default" # optional
        mixer_control "PCM" # optional
        mixer_index "0" # optional
        format "48000:32:2"
}

Thanks to both of you for the idea to look around 16 or 32 bits.

:)

michael February 23, 2024 21:55

Update: It stopped working without upgrading via rpi-update:

[    5.059789] i2c_designware 1f00074000.i2c: controller timed out
[    6.083780] i2c_designware 1f00074000.i2c: controller timed out
[    6.083803] pcm512x 1-004d: Failed to reset device: -110
[    6.083952] pcm512x: probe of 1-004d failed with error -110
[    6.523505] Adding 102384k swap on /var/swap.  Priority:-2 extents:1 across:102384k SSFS
[    6.585511] input: vc4-hdmi-0 as /devices/virtual/input/input7
[    6.586520] input: vc4-hdmi-1 as /devices/virtual/input/input8
[    7.107786] i2c_designware 1f00074000.i2c: controller timed out
[    7.856855] macb 1f00100000.ethernet eth0: PHY [1f00100000.ethernet-ffffffff:01] driver [Broadcom BCM54213PE] (irq=POLL)
[    7.856866] macb 1f00100000.ethernet eth0: configuring for phy/rgmii-id link mode
[    7.859300] pps pps0: new PPS source ptp0
[    7.859354] macb 1f00100000.ethernet: gem-ptp-timer ptp clock registered.
[    8.131778] i2c_designware 1f00074000.i2c: controller timed out
[   11.944856] macb 1f00100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[   11.944875] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   17.123859] i2c_designware 1f00074000.i2c: controller timed out

Is my Hardware dead? as i cloned the card to my second Pi with another AMP2, which works totally fine.

The Card isn´t detected anymore:

aplay -l
aplay: device_list:274: no soundcards found...

and a reboot doesnt fix it either.

Edited by michael February 23, 2024 21:55

0

NicoLapse February 23, 2024 22:51

It's my config if it can help you :

sudo nano /boot/firmware/config.txt (this file as changed of directory with the last rpi-update)

#dtparam=audio=on

dtoverlay=vc4-kms-v3d,noaudio

[all]

dtoverlay=hifiberry-dacplus,slave

sudo nano /etc/modules

snd_soc_bcm2708

bcm2708_dmaengine

snd_soc_pcm512x

snd_soc_hifiberry_dacplus

sudo nano /etc/asound.conf

pcm.!default {

type hw card 0

}

ctl.!default {

type hw card 0

}

Comment actions Permalink
0

michael February 24, 2024 07:33

Thanks, but it was a hardware problem. Completely disconnecting and reconnecting it from the 24V Power-Source fixed the problem.

Comment actions Permalink
0

Chris Kennedy February 29, 2024 03:48

I have come across this problem too, same hardware RPI5 and amp2 and the slowed down audio etc with pulseaudio selected from the audio settings in raspi-config. Don't seem to have it after reloading the whole lot again but I haven't touched the audio settings yet so presumably it's still set to pipewire. Since debian bookworm all the audio stuff has switched over to pipewire which is kinda mildly annoying when one has gotten use to connecting instruments with Alsa and jack.

Edited by Chris Kennedy February 29, 2024 09:01

Comment actions Permalink
1

HiFiBerry team March 01, 2024 12:52

This is fixed now both in the kernel that comes with Raspberry Pi OS and in the latest 6.6.x kernel that is distributed via rpi-update.

Comment actions Permalink
0

NicoLapse March 08, 2024 18:53

Thanks Hifiberry team, i can now confirm it's work with the new Kernel !
Nice !

Comment actions Permalink

Please sign in to leave a comment.