Pages: 1 2 3 4 5 6 7 8 9 10
(8th Nov, 2014 07:26 PM)Skywatch Wrote: [ -> ] (31st Oct, 2014 04:14 AM)zkiifreak Wrote: [ -> ]Question:
Will this work DD5.1/DTS output (aka passthrough) in XBMC (XBian blend of course)? Or only stereo?
I have not tried this yet, but I have noticed that the DAC only plays music and streaming audio. When a video is played the sound reverts to the HDMI output somehow and I have not yet found a setting to change this (XBMC has the DAC set as output under settings but I can't see anything else that overrides this).
DD5.1 (AC3) output would be good for me too and I will have a play with this next week, time allowing.
Skywatch.
Video is handled by omxplayer. So far only paplayer and dvdplayer can use ALSA audio system but not omxplayer.
I just found out, the dvdplayer program is preinstalled in Xbian. It's available in the context menu, great! I just have to find out how to make it to standard player. I would like to suggest that alsa-tools would be preinstalled in future version of Xbian, cause using Raspi only makes sense with having a DAC or something like hifiberry. Thanks.
EDIT: Some corrections, cause misunderstoodments and cause I've got new information.
What Do i have to Do to User hifiberry digital with xbian???
I usw Kernel 3.17......
Thanks sirloc
(10th Feb, 2015 05:14 AM)Sirloc Wrote: [ -> ]What Do i have to Do to User hifiberry digital with xbian???
I usw Kernel 3.17......
Thanks sirloc
I have merged your thread into this one as same topic is discussed. Please read through and discuss here if needed. Thank you
hi there, i cant find any help....isnt there a how to... as far as i know the modules are already in the actual kernel. i have kodi and kernel 3.17... please
thanks sirloc
I am in the same situation as Sirloc. I have hifiberry Digi+ and latest stable version of the xbian. Needed to update from 24/1/2015 image becouse the newest and the second newest images stuck on "loading..." when using them.
So now i have the latest stable version kernel (3.17) and installed alsa-utils, alsa-base and xbian-package-xbmc-alsa.
my modules file looks like this:
snd_soc_bcm2708
bcm2708_dmaengine
snd_soc_hifiberry_digi
No sound cards detected when using aplay -l. Also no ALSA in audio output, only HDMI and analog.
What to do next? I saw that there were some snc_soc_hifiberry files on the latest stable image root. Not sure are they when it is updated from later versions?
It would be really nice to have some sort of guide to these hifiberry stuff, now there is just messages that someone got it work but the infos are missing :/
Thanks in advance
(11th Feb, 2015 05:12 PM)samu_88 Wrote: [ -> ]I am in the same situation as Sirloc. I have hifiberry Digi+ and latest stable version of the xbian. Needed to update from 24/1/2015 image becouse the newest and the second newest images stuck on "loading..." when using them.
So now i have the latest stable version kernel (3.17) and installed alsa-utils, alsa-base and xbian-package-xbmc-alsa.
my modules file looks like this:
snd_soc_bcm2708
bcm2708_dmaengine
snd_soc_hifiberry_digi
No sound cards detected when using aplay -l. Also no ALSA in audio output, only HDMI and analog.
What to do next? I saw that there were some snc_soc_hifiberry files on the latest stable image root. Not sure are they when it is updated from later versions?
It would be really nice to have some sort of guide to these hifiberry stuff, now there is just messages that someone got it work but the infos are missing :/
Thanks in advance
Hi samu, I remember having difficulty with setting it up, mine's not a digi but here are my modules and blacklists, might help:
Terminal
root@xbian:/home/xbian# cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.
ipv6
snd_soc_bcm2708
bcm2708_dmaengine
snd_soc_pcm5102a
snd_soc_hifiberry_dac
snd_soc_bcm2708_i2s
Terminal
root@xbian:/home/xbian# cat /etc/modprobe.d/xbian.conf
blacklist spi_bcm2708
blacklist i2c_bcm2708
blacklist leds_gpio
blacklist snd_soc_bcm2708_i2s
alias char-major-89 i2c-dev
blacklist imx2_wdt
blacklist evbug
Thanks for your Post now i See i hat the wrong blacklist folder......
It Works now great..
Thank u
It was not the wrong blacklist......i check it again, xbian has two blacklists.....one xbian and one rpi.....
Does it still work sirloc? I remembered that I fixed mine by using the crazy-audio script that checks your system for necessary modules.
Hi there,
I can't get my digi+ to be detected with last xbian stable release (kernel 3.18.5+).
Did some changes cause a regression since last messages here? In that case, which was the latest build known to work with hifiberry hardware?
Regards,
Tom
Look into using device tree.
Hi everyone,
since yesterday I'm a proud owner of a HifiBerry Digi+. I'm running Xbian on a Raspberry Pi2,
Terminal
xbian@mumepc ~ $ uname -a
Linux mumepc 4.1.2+ #41 SMP PREEMPT Tue Jul 21 06:43:56 CEST 2015 armv7l GNU/Linux
Following the
HifiBerry Guide, I first checked the blacklists...
Terminal
xbian@mumepc ~ $ cat /etc/modprobe.d/xbian.conf
alias char-major-89 i2c-dev
blacklist evbug
...which does not seem to include anything relevant to sound.
I then added "dtoverlay=hifiberry-digi" to my /boot/config.txt, and even added the (probably not needed) asound.conf.
But alsa doesn't find any soundcards. Checking dmesg...
Code:
[ 1.615914] ALSA device list:
[ 1.615925] No soundcards found.
and then some lines later...
Code:
[ 5.063652] snd-hifiberry-digi sound: ASoC: CPU DAI (null) not registered
[ 5.063682] snd-hifiberry-digi sound: snd_soc_register_card() failed: -517
[ 5.073955] snd-hifiberry-digi sound: ASoC: CODEC DAI wm8804-spdif not registered
[ 5.074011] snd-hifiberry-digi sound: snd_soc_register_card() failed: -517
[ 5.115021] bcm2708_i2c 3f804000.i2c: BSC1 Controller at 0x3f804000 (irq 79) (baudrate 100000)
[ 5.115344] snd-hifiberry-digi sound: ASoC: CODEC DAI wm8804-spdif not registered
[ 5.115368] snd-hifiberry-digi sound: snd_soc_register_card() failed: -517
[ 5.123494] snd-hifiberry-digi sound: ASoC: CODEC DAI wm8804-spdif not registered
[ 5.123520] snd-hifiberry-digi sound: snd_soc_register_card() failed: -517
[ 5.429259] init: failsafe main process (105) killed by TERM signal
[ 5.618847] random: nonblocking pool is initialized
[ 5.765804] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
[ 15.080847] snd-hifiberry-digi sound: ASoC: CODEC DAI wm8804-spdif not registered
[ 15.080871] snd-hifiberry-digi sound: snd_soc_register_card() failed: -517
1) Shouldn't these error messages appear *before* ALSA tries to come up with a device list?
2) Does anyone else have an error like this? Any explanation? What can I do?
Earlier, I tried adding the modules manually, which seemed to "work", as in: modprobing them worked without error, however, the card did not. Unfortunately I don't have dmesg logs from then.
What's the state of the xbian-package-alsa-xbmc packet?
Thanks everyone!
I don't own a digi+ but have a few dacs that I use on different pi's.
You don't need the xbian-package-alsa-xbmc any more, just use the latest version of Xbian from the download site.
At the moment the 4.1.2+ kernel doesn't work at all for me on a pi2 with I2S and your results confirm it's not just me having the problem. Try installing the 4.1.0 RC8 and see if that helps (it did the trick for me). You can even try 3.18.8 as that too worked on Pi2.
Also, you can try adding dtparam=i2s=on to your config.txt. You never know it might make a difference.
There is ongoing work on a 4.1.3 kernel that might solve the issue for pi2, hopefully we'll be testing that soon...
Update.... kernel 4.1.3 tested last night and works on Rpi2 - so that's your solution (make sure to also get the latest 2.3.0 firmware installed first).
Skywatch.
(29th Jul, 2015 08:26 PM)Skywatch Wrote: [ -> ]Update.... kernel 4.1.3 tested last night and works on Rpi2 - so that's your solution (make sure to also get the latest 2.3.0 firmware installed first).
Great!
(Tested the i2s dtparam in the meantime, which did not do the trick.)
Uuuuuhm... Feeling a bit stupid to ask this, but can't I get the update from the (unstable?) repository? (I'm a genuine apt-get fan...)
Pages: 1 2 3 4 5 6 7 8 9 10