![]() I used this tutorial to download the Kodi source and compile/configure it: You need to download the source of kodi, patch the file xbmc/cores/AudioEngine/Sinks/AESinkALSA.cpp and compile it on your own. OpenElec is too stripped down, so i can not use "apt-get" or so. Yes, because I want to do more with the Pi than Kodi. # uncomment to increase signal to HDMI, if you have interference, blanking, or # uncomment to force a HDMI mode rather than DVI. # uncomment to force a specific HDMI mode (this will force VGA) # uncomment if hdmi display is not detected and composite is being output By default it will be display's size minus # goes off screen, and negative if there is too much border # uncomment the following to adjust overscan. # and your display can output without overscan # uncomment this if your display has a black border of unused pixels visible # uncomment if you get no picture on HDMI for a default "safe" mode # Some settings may impact device functionality. snd-hifiberry-digi sound: wm8804-spdif 3f203000.i2s mapping cat /etc/nf platform sound: Driver snd-hifiberry-digi requests probe deferral snd-hifiberry-digi sound: snd_soc_register_card() failed: -517 snd-hifiberry-digi sound: ASoC: CPU DAI (null) not registered I would like to use passthrough, because my decoder can handle AC3 and dmesg | grep snd When I installed Openelec on the Pi, I could select "ALSA: Default (snd_pri_hifiberry_digi S/Pdif)". In Kodi I can select "ALSA: Default (snd_pri_hifiberry_digi Analog)", but I cant change the passthrough to the HifiBerry soundcard - it is greyed out to "PI: HDMI". Karte 0: sndrpihifiberry, Gerät 0: HifiBerry Digi HiFi wm8804-spdif-0 **** Liste der Hardware-Geräte (PLAYBACK) **** LD_PRELOAD=/usr/lib/libGL.I have installed a fresh Raspbian on my Pi with the HifiBerry Digi+ card. For now, I have shortcuts in Kodi Favorites and working audio. ![]() To get around this I hardcoded the options, which is not a long term solution becasue this might be overwritten with a future update. Which is a problem if you need to use a custom audio device to get sound. But in this case all the chrome_OPTS variables are not loaded. Thus the chrome-start of your add-on is called on opening of a url. As I found out if you use a custom path to Chrome, which is needed with your Chrome addon, the script.sh is completely skipped. So I started to check the chrome-launcher files to see if I could find a starting point to begin fixing this. I have tested the live-usb, no audio when used on my NUC. If not, it probably has to do with the custom audio. I'm going to run this live-usb on my NUC tonight to see if it works. I have it running now on my laptop (live usb) which does have an analog output, I made no custom config or script changes. Maybe I should to try to stop and start pulseaudio like it is in /storage/.kodi/addons/browser.chrome/bin/chrome-start. So I select the actual Chrome location, thus al the tweaks in chrome-start are not carried over. So I have to manualy tell it where it is, but /storage/.kodi/addons/browser.chrome/bin/chrome-start is not recognised as chrome. I think the problem lies in the Chrome-launcher addon, it does not recognize the location of Google-Chrome. If I am correct, the value that I put in the custom audio field is directly loaded in the $ALSA_DEVICE variable. But when I use Chrome-launcher these options seem to be overriden. These options get loaded when /storage/.kodi/addons/browser.chrome/bin/chrome-start is started. It is the custom audio option of the CHrome add-on settings.
0 Comments
Leave a Reply. |