Hi!
I use the zip attached.
For the dac, I commented bcmxxx in modules. I also added dtoverlay=iqaudio-dacplus in /boot/config.txt. Not sure the second one is useful but now it is ok.
Remains the problem with dev version of volumio. Afte plugin install it canât boot anymore. And at a very early stage of boot, before screen initialisation - so no message.
Well that was my question a bit, it depends on your receiver really. I use Kodi with passthru, so the sound over HDMI should not be tampered with and my receiver will decode the sound. Meaning I use the add-on board for Volumio and passthru for movie watching.
I cannot really find an answer to the question: is passthru really lossless and should a good DAC sound as good (or better, depending on quality obviously) as using for example a hifiberry board?
Yes I meant to ask if the delay changes upon reinstalling/reimaging volumio. To save time I wanted to make a toggle switch (off = no delay, on = delay) on the config page.
Iâve been tinkering all day now, finally I think I got it right⌠Adding either the .asoundrc or asound.conf did change the default ALSA output device (is this what they call the âsinkâ?). I tested this using the following command:
aplay -D default /volumio/app/startup.wav
But Kodi only seemed affected by changing the alsa.conf, it almost seemed as if Kodi loads itâs output settings from that file only. Adding the asound.conf as mentioned on many sites does give an extra option (ALSA default), but playback is sent to HDMI nonetheless.
However the contents were not right for our situation, the asound.conf does in fact override settings from the alsa.conf. So all we need to do it put those exact settings in the override file:
asound.conf
defaults.pcm.card 1
defaults.ctl.card 1
I have checked the code in locally, will upload to github later tonight.
Updates:
Added the ALSA override (also in the installscript, if you upgrade you need to write the asound.conf once).
Added the delay (as a toggle switch) for the Kali reclocker for Kodi.
After successful installation and reboot you need to âstartâ the plugin. You can do this on the plugins page, just âflick the switchâ.
If you are using a Pi3 it might take a few seconds (some wifi errors can occur).
If you really doubt it you can SSH into the pi and type âsystemctl start kodiâ.
It sounds like installation failed, did you wait the installation out? Thereâs a bug in the plugin-installer that causes another âpop-upâ to show, you need to wait 'till the top one shows âinstallation successfulâ.
The close button should not be visible, this will be fixed later on obviously, instead just refresh the page (this causes the pop-ups to disappear), donât do this during installation though!
The correct sequence should be:
Flash the SD-card
Configure volumio (select a DAC and so on)
Install the Kodi plugin â wait it out, this might take a few minutes
Reboot the Pi
If need be reconfigure using the plugin settings page, updating the hdmi/gpu settings will need another reboot, the rest just needs a restart of Kodi
Can you check if the kodi executable is there?
volumio@volumio:~$ ls -al /usr/bin/kodi
kodi kodi-standalone
volumio@volumio:~$ ls -al /usr/bin/kodi-standalone
-rwxr-xr-x 1 root root 2003 May 1 2016 /usr/bin/kodi-standalone
volumio@volumio:~$
If not, then installation failed. The last step in the script is creating the systemd unit, the following command should output text:
âcat /etc/systemd/system/kodi.serviceâ
The process tree should show Kodi when the plugin is activated:
Q: How do I start Kodi?
A: Just start the plugin in Volumio
Q: The plugin doesnât install properly, help?!
A: This is a known issue in the latest image (2.041), just let it run until the âinstalled successfullyâ message appears, reboot and youâre good to go.
Q: What settings require a reboot?
A: gpu_mem and hdmi_force_hotplug require a reboot, the other settings just require Kodi to be restarted.
Q: Why must I configure the DAC before installing the Kodi plugin?
A: Because Volumio rewrites the /boot/config.txt, meaning all changes are lost, the most important settings is gpu_mem, 16MB is far from enough.
Q: Does this plugin run on my BBB/rPiB(+)?
A: It should run, but donât expect it to run smoothly, I gave up on testing on the Pi1 some months ago due to performance issues.
Q: Can I use my DAC for both Volumio and Kodi?
A: Yes, but I advise you to turn off the keep-alive in Kodi (as a matter of fact I will try to do this in the next version of the installation script).
Q: I keep getting the first use pop-up in Kodi, is this normal behavior?
A: Yes and no, exiting Kodi once using the exit button should fix this problem, if not check the logs, you might not have enough rights to write the setting.
[code]volumio@volumio:~$ cat /etc/systemd/system/kodi.service
[Unit]
Description = Kodi Media Center
# if you don't need the MySQL DB backend, this should be sufficient
After = systemd-user-sessions.service network.target sound.target
# if you need the MySQL DB backend, use this block instead of the previous
#After = systemd-user-sessions.service network.target sound.target mysql.service
#Wants = mysql.service
[Service]
User = kodi
#Group = root
Type = simple
#PAMName = login # you might want to try this one, did not work on all systems
ExecStart = /usr/bin/kodi-standalone -- :0 -nolisten tcp vt7
Restart = on-abort
RestartSec = 5
[Install]
WantedBy = multi-user.target[/code]
The fact that the script is there should point towards successful installation. Are there any crash logs in /home/kodi/? And are more created every time you stop and start the Kodi plugin?
Hi
With a small modification in install script I managed to install the plugin on pine64 (aarch64 CPU). It fails to start because it canât find libEGL . Maybe it is missing in the last version? I have no time now to investigate. But it may be a issue for the problem above.
Hereâs what I got. Seems like thereâs no crash logs generated?
volumio@volumio:/home/kodi$ ls -a
. .. .kodi
volumio@volumio:/home/kodi$ cat /home/kodi/kodi_crashlog-yyyyMMdd_hhmmss.log
cat: /home/kodi/kodi_crashlog-yyyyMMdd_hhmmss.log: No such file or directory
Hi Saiyato. Iâve placed this endeavour on hold for now as I was intending to use volumio as a dlna renderer. To simplify things Iâm using a diet pi / kodi setup now which achieves the same with kodi as a dlna renderer.
I am helping another Friend with his volumio / kodi setup and will post the results in due course.
After some successful tests I think itâs now ready to be used, the problem with the new images (2.092/2.096) should be fixed. I also added new settings which were needed to solve the problem:
gpu_mem_1024 (rpi 2b and higher)
gpu_mem_512 (rpi a+, b, b+ and zero)
gpu_mem_256 (rpi a)
Great news Saiyato. The new plugin works and kodi launches. Great job and thanks.
However now the kodi plugin settings in volumio does not show options to choose sound card audio output. Itâs just a blank page when selecting plugin settings. So kodi only works on HDMI audio out for now.
Did I miss something here? The sound card output was set to iqa dac+ before installing the plugin.
Great job Saiyato,
Do you plan to use plugin option to setup choose sound card audio output for Kodi ? Iâm currently using Hifiberry DAC for Volumio and HDMI for Kodi as I donât want to share the same audio output for both ?
Thanks fai! Did you use the latest version I uploaded? You might need to wait a bit, if the plugin was installed seconds ago the pi can still be quite busy.
Attached you will find the plugin settings screen, please note that I made some last minute translation changes, these will be in the next release.
Hi, this should work out-of-the-box. Because that is exactly my setup at the moment. Same goes for you, if you go into the settings page you will find the setting âEnable DAC output for Kodiâ, if that setting it set to false you will have HDMI output for both video and sound.