Hi Everybody
I just received a DiGi+ card for installing it on my Raspberry Pi B+, and use it with Openelec 6.0.3. I've followed the process for installing it and it works fine, the device is correctly detected on Openelec and i can select it.
I don't know why but i have no sound at all through the toslink output, and i've also tried the coax i have the same behaviour. If i'm switching the output to PI:HMDI, sound is coming back directly on my TV, but with the DiGi+ selected, my amplifier stays quiet no interface click sounds, no sound in stereo or multichannels...
Here's all the tests i've done :
- Switching to another toslink cable from my PS3 (works fine on my PS3, not on the Pi)
- Testing with the coax of my dvd player (works fine on my DVD, not on the Pi)
- Restarting from a fresh complete new openelec/kodi install
- Using your Test Image, and i have the sound on my AVR (so i assume that if i can hear the sound, it means that the card is perfectly working)
The green led is up, but i noticed a weird thing, when the RBP is off with power plugged, i can see the red laser color into the toslink blank cache, as soon as i'm turning the RBP on, no laser at all, even when i'm trying to read a movie, or if i'm navigating in Kodi's interface.
I probably missed something somewhere, but i didn't found any similar case on HiFiberry and Openelec forum.
Any clue that can help me?
Thanks in advance
11 comments
-
HiFiBerry team What's the output of "aplay -l"?
Best regards
Daniel -
Alexandre Van Roy Hi
Here's what i have
---------------------------------------------------------------------------------------------------------------------
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_digi], device 0: HifiBerry Digi HiFi wm8804-spdif-0 []
Subdevices: 0/1
Subdevice #0: subdevice #0
---------------------------------------------------------------------------------------------------------------------
Hope it'll help!
Regards
-
HiFiBerry team This looks good. Did you select the ALSA sound card in the audio settings? If you did, this should work.
Best regards,
Daniel -
Alexandre Van Roy Yes i did, and i've also applied all the settings with Passthrough etc... (i also tried with the other more simple modes).
Withouth touching any cable, the test image give me a sound on the amplifier
I'm really stuck there, and don't know where the issue can comes from. A tick box somewhere in Kodi? Perhaps it can be usefull to test the Raspbian with automatic detection for checking how it works.
I don't know Raspbian for now (i'm new on Raspberry and linux platforms) but i assume there is a possibility for testing videos / multichannel?
I also noticed on the forums that one or two years ago there was an openelec image already configured for HiFiBerry, but it seems to not be available anymore. It should be good to test it and see how it works.
Regards
-
Alexandre Van Roy Hi,
I've done some tests with the preconfigures raspbian version, and still no sound at all even if the card is correctly detected and that i have the same results than with Openelec if i'm typing the aplay -l command.
During Raspbian loading there is a lot of informations and there is a weird line with a failed: -517 about the sound card. I attached the picture (the fail line is on the top). Anyway it's really weird that i have no sound on two separated systems.
Any clue?
Thanks for your assistance.
-
Alexandre Van Roy Hi,
I've removed my RPi from my home theater for more easy testing. I wanted to check when i can see the laser signal through the white toslink cache.
I can see it in two cases :
- Test image from HiFiBerry site
- When i shutdown Kodi (i initially thought it was the 'keep audio device alive for 1 min', but apparently no, it stays on until i reboot)
For the rest of the time, with Raspbian (preconfigured version) i don't have any signal, under Kodi within the interface or reading a video, i have nothing too.
Here's the details of my Kodi settings :
Can somebody kindly check if the light is blinking when you're navigating in kodi, with GUI sounds activated? I assume we should see a blinking signal at least right?
Thanks in advance for your help!
Alex (cheers from France!) :)
-
HiFiBerry team Hi Alex,
the -517 error is normal. This is a temporary error as the sound card driver hasn't been loaded at this point of the boot process.
It is also normal that the light of the TOSLink output stays on all the time. It also does not blink as the frequencies here are very high (several MHz).
Just checking what you tested:
- the test tone image works fine
- on Kodi you do not hear any sound
- the pre-configured Raspbian detects the card, but you don't hear any sound
Is this correct? This is rather strange as the hardware seems to work fine with the test tone image.Best regards,
Daniel -
Alexandre Van Roy Yes you're right.
Just a remark, for me the toslink port is always OFF, except during the test image and after having kodi turned off
I'll be able to test a pi3 this afternoon with the Digi+ card, but i'm in my office and not at home, i'll not be able to test it directly on my AVR but if the toslink port light is on, i assume it'll be a very good sign.
Is the bluetooth bug has been fixed now for pi3 or should i disable bluetooth in the config.txt for being sure everything works fine for this test?
If the Pi3 is working fine, then it means that the problem is coming from my raspberry (not sure if it's happening very often but... i want to exclude all the options)
Thanks a lot.
-
HiFiBerry team Hi Alexandre,
the bluetooth bug has been fixed more than 3 months ago, but not all distributions have upgraded their kernel yet. However, this isn't the cause of the problem here.
We have seen rare cases of defective RPI GPIOs, so if the Digi+ is working with one RPI, but not with another, the root cause might be a broken RPI.
Best regards,
Daniel -
Alexandre Van Roy I'm using Openelec version 6.0.3 from the 30th of March. I assume this one should be fine.
I'll test with this one, but if you advise me to test another distribution just tell me. I'll keep you posted this afternoon then.
Regards
-
Alexandre Van Roy Good news, with a Pi3 i have the toslink port up as soon as i select it in the settings. All should work correctly with it then.
The problem is really coming from my Pi1 then. I'll relegate it as a test one only.
Thanks for your support, and thanks for your great products! :)
Alex