HifiBerry Digi2 Pro

[traderyoda]

How did you sort it in the end?

I might experience the same issue on my build. I have a Pi4 running pCP with a Digi2 Pro. I noticed that pins 3 and 5 are used by the HiFiBerry board. In my case those two GPIO pins are used by my PiSugar UPS. I'm planning to use a power-off/power-on pushbutton but figured I couldn't add another potential conflict to the 3 and 5 pins so started to look at using 39 and 40, but Digi2 Pro is connected to 40 as well. The folks at HiFiBerry warn about sharing pins but don't mention how to get around sharing issues.

[JdL]

I have found the issue.
I am using a Pushbutton to shutdown PiCoreplayer and this gpio-shutdown setting is causing Squeezelite not recognizing the Digi2-Pro.



And now Aplay-L shows my Digi-pro:


I was not aware of the use of GPIO-5 by Digi2-Pro.

[bpa]

Need some time to figure this out.
What bugs me is that playback through the standard headphone jack of the Pi itself is without any issue.......?

Could powersupply be of influence?
I don't have the official Raspberry Pi power, but one sold to me as compatible. (2.5A)

Less power will not slow down audio - it is a clocking setting that is at fault.


The point of the questions is to eliminate different aspects and so you can home in on the problem area.

Wrong speed can result from many sources including.
1. Hardware issue (e.g. faulty clock)
2. ALSA device associated error
3. Squeezelite errors - possibly due to ALSa possibly due to command line options
4. LMS issues - either resampling not happening or incorrectly resampling.

Trying lots of different changes at the same time is often not efficient and may complicate things if the changes are not undone after a test.

Get the details from alsacap - that will confirm what speeds are ALSA thinks are supported and which is relayed back to LMS.
Hopefully other users of the board may be able to confirm whether the Alsacap details are "normal" (i.e rule out h/w issue)

Exactly how much is the audio being slowed down - this can point to likely source (e.g. 50% slowdown can be the result of mono / stereo mixup whereas 10-12% is usually a 44.1 vs 48 kHz issue)

[JdL]

Need some time to figure this out.
What bugs me is that playback through the standard headphone jack of the Pi itself is without any issue.......?

Could powersupply be of influence?
I don't have the official Raspberry Pi power, but one sold to me as compatible. (2.5A)

[bpa]

Not sure how to find other 48kHz files.

Most common case of stream sounding slow is when a 48kHz stream is played at 44.1Khz.
A ripped CD will be at 44.1kHz so to make it sound slow is unusual.
Knowing exactly how slow it is being played might provide a clue - compare expected track duration against how long it takes to play through the player.

For alsacap to work - nothing else must be using the device as this will prevent it being opened. So when running alsacap make sure squeezelite is stopped.

IIRC BBC station live through BBC Sounds (not shoutcast) or Radio France France Musique AAC streams are 48Khz.

[RobbH]

Using a Digi+ Pro, I have some additional Squeezelite settings in pCP:

Max sample rate: 32000-192000

Upsample setting: E


I don't necessarily think these are likely to help you, but should be easy enough to try.

[JdL]

This is my current setting:


I use CD-ripped FLAC files.
Not sure how to find other 48kHz files.




Joost

[bpa]

Don't get me wrong.
The card does work. I am getting sound, but too slow.
Both Optical as well as coax.
Headphone playback on the Pi itself is at correct speed.

The issue could be the card is reporting wrong speed capability to squeezelite (via ALSA)

What is the format of your test streams/files ?
Is the sound slow for both 44.1kHz stream and 48kHz files/streams these are sample rates not bit rate ?

What does alsacap say about the capabilities of the alsa device you are using ?

[kidstypike]

Don't get me wrong.
The card does work. I am getting sound, but too slow.
Both Optical as well as coax.
Headphone playback on the Pi itself is at correct speed.

Which output setting are you using?

[JdL]

Don't get me wrong.
The card does work. I am getting sound, but too slow.
Both Optical as well as coax.
Headphone playback on the Pi itself is at correct speed.

[JdL]

Whatever I choose in the Squeezelite settings page "HifiBerry Digi and Digi+" or "HifiBerry Digi+ Pro", playback is still too slow.
Config.txt shows correct settings as "dtoverlay=hifiberry-digi" or "dtoverlay=hifiberry-digi-pro" depending on my choice of course.
But APLAY-L only shows "device0: HifiBerry Digi Hifi" etc. no difference between the 2.



Joost

[Man in a van]

And this is from https://github.com/raspberrypi/firmw...verlays/README

Name: hifiberry-digi-pro
Info: Configures the HifiBerry Digi+ Pro and Digi2 Pro audio card
Load: dtoverlay=hifi

There was a problem with this board when it was released; the rpi foundation changed the pin order on rpi4b and the board was not recognised by the software.

https://support.hifiberry.com/hc/en-us/community/posts/4408904936209-DIGI2-Pro-not-playing-

to the OP, does the board show in the boot log and dmesg?

Try the hifiberry OS to check if it works

ronnie

[cliveb]

I concur with kidstypike. I use a DIGI2 Pro (on a RPi2). The Digi & Digi+ option works fine:

[kidstypike]

Playback of my recently acquired DIGI2-PRO v2.2 board is too slow.
It is like playback of a 45rpm record at a 33rpm speed.
I am using the PiCorePlayer v8.2.0/Squeelite/LMS platform.
Playback by the standard Raspberry Pi 3B+ headphone jack is correct.
On another Pi 3B+ playback over USB is also without any issues.

I just can't get the driver settings working correct.
Aplay-l command doesn't show "DIGI PRO"....?
Any ideas?

Mines a Digi+, settings below, may help?

[Man in a van]

Check your config file.

From the data sheet

Configuration


Overlay for config.txt:
dtoverlay=hifiberry-digi-pro

ronnie

Edit: I coud not read your screenshots clearly but it would appear the correct overlay is used. It's sometimes better to copy and past the text between code tags
what out put choices are listed on the Sqeezelite Settings page (expand the red word more)