Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[tsurkamp]

I'm working on this IdPi build and can't get my HiFiBerry Digi+ to operate. It is an older unit and in the past, has needed it's device tree edited.

I can see my NAS, play through the HDMI on the RPi3, but the optical connector dosen't light (power light is on). The available options for aduio device either don't work for the Digi+ or are the HDMI options.

In an eariler post, someone mentioned they were able to change the device tree.

Being the total linux noob, I can't even get past the mainmenu to a linux prompt. How do I make this happen, please?

Thanks for your help and I look foward to this IdPi upgrading to MC22.

[duncan4791]

I have the same board, here is what you can do.
Shutdown the IdPi and remove the SD card. Put the SD card into a SDcard reader on another PC. Open the cards directory, in the root directory  find Config.txt and open to edit in a text editor. At the end of the file add the line "dtoverlay=hifiberry-digi". If you wish to disconnect onboard audio find the line "dtparam=audio=on" and put a "#" in front. Save the file as text. Install in IdPi and boot up. This should active the HiFiBerry Digi+ driver.

If you read the SD card on a linux machine (put a Rasbian install on the pi and use a usb SDcard reader) you can access the full directory structure. HifiBerry recommends adding the following to /etc/asound.conf :

pcm.!default  {
 type hw card 0
}
ctl.!default {
 type hw card 0
}
This will cause the digi to be default audio device.

All this can be found at https://support.hifiberry.com/hc/en-us/articles/205377651-Configuring-Linux-4-x-or-higher

Hope it helps.

[tsurkamp]

Thank you, Duncan!

I can say "Thanks for sharing!" without sarcasm.

Worked Great!

[duncan4791]

tsurkamp, your welcome.

One addtional point the HiFiBerry Dac+Pro and Digi+ Pro do not work with the IdPi nor with Volumio, Kobo, Rune and most other music servers, that I have tried, unless they have updated recently. The kernel needs to be updated the the latest by JRiver. So there is no point in buying the higher function boards if you are not going to be using them with either Raspian or some other 4.4.19+ kernel.

[tsurkamp]

Back again...

Got my upgrade to MC22 installed and once again my digi+ is not working.

This time the card is recognized as a hifiberry digi+, offers 4 different drivers, music will play with no sound coming out.

There is NO light coming from the optical input.

I have not used your recommendation to make the digi+ the default player because I don't have the usb disc reader nor a SD disc to reboot the Rpi to a Raspian and change the code.

I will get the stuff if this is my only solution.

But since it wasn't needed before, I wonder if there is anything else that I might try do since the upgrade to MC22 is the only change that was made.

Thanks AGAIN for your help.

[bob]

Back again...

Got my upgrade to MC22 installed and once again my digi+ is not working.

This time the card is recognized as a hifiberry digi+, offers 4 different drivers, music will play with no sound coming out.

There is NO light coming from the optical input.

I have not used your recommendation to make the digi+ the default player because I don't have the usb disc reader nor a SD disc to reboot the Rpi to a Raspian and change the code.

I will get the stuff if this is my only solution.

But since it wasn't needed before, I wonder if there is anything else that I might try do since the upgrade to MC22 is the only change that was made.

Thanks AGAIN for your help.

The current Raspbian kernel doesn't support your device.
When the Raspbian jessie repo updates to 4.9 (which is supposedly any day now), we'll look at making that the default kernel.

[tsurkamp]

I'm certainly no expert here, but to be clear I am using a Digi+ that was purchased in 2015. It has been working great until the upgrade to MC22. I am reading ( a post from Duncan elsewhere) that the Digi+ Pro will require the new kernel. I don't have one of those.

Sorry but I am surprised that the old board would not be workable.

If you are right...I have a bone to pick with HiFiBerry.

THX

[bob]

It worked with MC20 on the Id Pi?
Sounds like I got the boards confused then.

What are the Audio Device selections in MC's setup on your Id?
You should be looking for something like
front: blah blah.

You can also do function 10 on the main menu to see what are the installed audio devices the Id sees.

[tsurkamp]

The RPi shows...

(under option #10)
Card 0, ID 'sndrpihifiberry', name 'snd_rpi_hifiberry_digi'
    Device 0, ID "HiFiBerry Digi wm8804=spdif=0'        etc.

Under Audio Device
There are four choices...
1. default:CARD=sndrpihifiberry (ALSA) snd_rpi_hifiberry_digi
2. hw:CARD=sndrpihifiberry (ALSA) snd_rpi_hifiberry_digi
3. plughw:CARD=sndrpihifiberry (ALSA) snd_rpi_hifiberry_digi
4. sysdefault:CARD=sndrpihifiberry (ALSA) snd_rpi_hifiberry_digi

nothing that begins with "front".

And it was working great as MC20.

For some reason, MC22 can't turn the Digi+ on - no power light comes on the Digi+.

An aside question...I have during the upgrade process checked 3 times to be sure that I have all of the updates for MC22. First two checks made changes as expected, but when I checked again it ran an update that looked like the 2nd update being repeated. So I did it again and it ran the same update.

I guess I'm thinking  that the update is not recognizing that it has been done. Not that it seems to be causing any problem, but it seems a little strange.

THX

[bob]

The RPi shows...

(under option #10)
Card 0, ID 'sndrpihifiberry', name 'snd_rpi_hifiberry_digi'
    Device 0, ID "HiFiBerry Digi wm8804=spdif=0'        etc.

Under Audio Device
There are four choices...
1. default:CARD=sndrpihifiberry (ALSA) snd_rpi_hifiberry_digi
2. hw:CARD=sndrpihifiberry (ALSA) snd_rpi_hifiberry_digi
3. plughw:CARD=sndrpihifiberry (ALSA) snd_rpi_hifiberry_digi
4. sysdefault:CARD=sndrpihifiberry (ALSA) snd_rpi_hifiberry_digi

nothing that begins with "front".

And it was working great as MC20.

For some reason, MC22 can't turn the Digi+ on - no power light comes on the Digi+.

An aside question...I have during the upgrade process checked 3 times to be sure that I have all of the updates for MC22. First two checks made changes as expected, but when I checked again it ran an update that looked like the 2nd update being repeated. So I did it again and it ran the same update.

I guess I'm thinking  that the update is not recognizing that it has been done. Not that it seems to be causing any problem, but it seems a little strange.

THX

What supported formats and sample rates does menu item #10 show?

Did you notice what packages it was trying to upgrade the 2nd time??

Thanks.

[duncan4791]

Just a note:

Pretty much the same as tsurkamp.

I have an Digi standard so I tried it. The IdPi recognizes it and Media Center can configure for it, but no data gets sent to the device. When the digi gets a bit stream (observed under latest Raspian) the optical transmitter turns on, when the data stops the light turns off. The IdPi does not light up the optical transmitter. Media Center, itself, is happily playing the selected track so the data must be going somewhere.

I am not getting the Default option for some reason.

Things are getting weirder! As a retired software programmer I realize the complexity of your product and supporting it on 8 or 9 platforms. Your doing a good job, as far as I can tell. Good luck figuring it all out.

[bob]

Just a note:

Pretty much the same as tsurkamp.

I have an Digi standard so I tried it. The IdPi recognizes it and Media Center can configure for it, but no data gets sent to the device. When the digi gets a bit stream (observed under latest Raspian) the optical transmitter turns on, when the data stops the light turns off. The IdPi does not light up the optical transmitter. Media Center, itself, is happily playing the selected track so the data must be going somewhere.

I am not getting the Default option for some reason.

Things are getting weirder! As a retired software programmer I realize the complexity of your product and supporting it on 8 or 9 platforms. Your doing a good job, as far as I can tell. Good luck figuring it all out.

There is no way this should be different than in MC 20. I was wanting to see his full output from option 10 to see what the device actually supports.

You might check to see if the volume is set to system or internal (I'd suspect it should be internal) and if the audio mixer option from the main menu shows the device muted or something weird.

[duncan4791]

Hi again.

Taking your suggestion I looked at the alsamixer and found that it was defaulting to S/PDIF Rx instead of Aif. Changing it to the right setting fixed it.

Thanks.
Sent from JRiver IdPi Firefox Browser.

[bob]

Hi again.

Taking your suggestion I looked at the alsamixer and found that it was defaulting to S/PDIF Rx instead of Aif. Changing it to the right setting fixed it.

Thanks.
Sent from JRiver IdPi Firefox Browser.

Nice!
Cute sending from the browser too