[Testing] Kodi 18.0 Leia beta versions now available for RetroPie!
-
@cebix No debug log, no problem. This is not reproducible on a clean installation so it is probably a combination of some non default settings or some incompatible addon. Try moving/removing /home/pi/.kodi
-
@Rascas I somehow missed your debug post - I tried to make one now but once I reverted back to the Estuary skin the problem doesn't exist anymore... So changing the skin back fixed it I guess and I can't reproduce the problem again.
-
Hello, everybody. First of all thank you for this great opensource work.
Second, I recommend to warn that it is necessary to have RetroPi in Stretch version in order to upgrade to Kodi 18. Due to dependencies.
For this upgrade, "first modify the files /etc/apt/sources.list and /etc/apt/sources.list.d/raspi.list. In both files: change every occurrence of the word jessie to stretch
And next, the classic: sudo apt-get update && sudo apt-get -y dist-upgrade
I tested this version of the thread, version 18 beta4 in rpi3.
I recommend them. And sincerely it looks and persive just as stable as the (now old) version 17.3.
I could make Amazon Prime Video (https://forum.kodi.tv/showthread.php?tid=331136) go, after a long way, (Input, Wevine, EULA, etc etc) works fluid in 640p in a Raspi3, in 720p unfortunately the audio of the video is offset, this probably blame the DRM.
I haven't been able to run the Netflix ascidisco kodinerds plugin (https://forum.kodi.tv/showthread.php?tid=329767) , there's an error after the installation, and I haven't been able to check the debug yet.
Thank you for this version, it's a advance.
-
@manu3l Thanks for the warning about Raspbian Stretch, yes it is true, it won't work on Jessie and RetroPie versions earlier than 4.4. I thought that was already in the first post, it was not and I added that info.
About the netflix/amazon prime max resolutions, the Raspberry Pi is not a DRM device authorized from Netflix/Amazon, so everything works by software decoding. The PI 2 can do about 480p max, the Pi 3B, about 640p, but can do 720p with some slight overclocking. The Pi 3B+ can do 720p without changes.
About the recent problems about the Netflix addon, it is already fixed in the addon, but I think it needs an updated inputstream.adaptive addon also. I will do that tomorrow. -
Also dist-upgrade to Stretch broke EmulationStation, giving this error: "while loading shared libraries: libboost_date_time.so.1.55.0: cannot open shared object file: No such file or directory"
Fix with sudo ./retropie_setup.sh and update from Source ?
-
@manu3l That is something unrelated to Kodi. But maybe you can fix it running the retropie_setup.sh scripts, updating it and reinstalling Emulation Station.
-
@manu3l If you upgrade in place from Raspbian Jessie to Stretch, the next step is to update all packages from binary, including Emulationstation, from the RetroPie-Setup script.
-
@mitu I try, but installing the EmulationStatio binary fails S:
-
I try some times, update from binary... no works... but after reboot EmulationStation is back :D
Thanks
-
Kodi 18 RC 1 available for update
Changelog:
-https://kodi.tv/article/kodi-v18-leia-rc1-new-hopeRaspbian/RetroPie specific:
-Added various missing binary addons like pvr.zattoo, pvr.teleboy, vfs-sacd, etc
-All binary addons updated. Netflix works again if updated. -
Thanks. I have tested the new version. I am still having the issue with the on screen controls with estuary not displaying and the kodi interface breaking.
I switched on debug logging (which also shows the on screen memory usage etc), and then it worked fine! This is reproducable - switch off debug logging and the on screen menu won't show. The screen just dims - if you stop the video, the kodi interface no longer displays so it seems it's related to GPU somehow.
There is nothing useful I could see in the non debug log.
https://paste.ubuntu.com/p/pmKw9RM9ZY/
Here's the debug log (which may not be of any use since it works when debug log is on)
https://paste.ubuntu.com/p/pcQwGFQTkF/
Note this problem doesn't happen using a skin like Confluence.
-
I have managed to work around the issue - seems related to "overscan_scale=1" - if I removed that from
/boot/config.txt
the on screen controls display correctly.So either a firmware issue or a compatibility issue with Kodi and this option.
-
@Rascas How can you update to RC1? The first post instructions only get me the v4 beta. Thanks.
-
@cebix said in [Testing] Kodi 18.0 Leia beta versions now available for RetroPie!:
@Rascas How can you update to RC1? The first post instructions only get me the v4 beta. Thanks.
In RetroPie-Setup go to Configuration Tools -> Raspbian Tools -> Upgrade Raspbian packages
Or in terminal do:sudo apt-get update sudo apt-get dist-upgrade -y
-
@BuZz said in [Testing] Kodi 18.0 Leia beta versions now available for RetroPie!:
I have managed to work around the issue - seems related to "overscan_scale=1" - if I removed that from
/boot/config.txt
the on screen controls display correctly.So either a firmware issue or a compatibility issue with Kodi and this option.
That might be it! In all the RPis that I tested I have that line commented, don't remember why. I know what it does theoretically, but I don't need it on my Pis. Can you tell why is it needed in RetroPie ?
I also took a look at Raspbian and LibreELEC and they do not come with that enabled. Since this probably is not much tested, the newer firmwares might have a bug. -
@Rascas explained here - https://github.com/RetroPie/RetroPie-Setup/wiki/Overscan#the-console-looks-good-but-the-picture-is-off-for-emulationstationretroarchetc
basically on some screens that require overscan settings, without this ES can render offscreen.
This is only a problem with Kodi 18 though on the latest firmware. Kodi 17.x is ok.
-
@BuZz I just tested with overscan_scale=1 and I still cannot reproduce de problem. But it can be that in conjunction with something else like yours overscan_bottom=X, etc. Also, do you use some videoplayer at RetroPie boot ? I cannot see any related errors in your Kodi logs...
-
@BuZz Well, I can reproduce it now with overscan_scale=1 and without disable_overscan=1 (I have disable_overscan=1 in all my Pis). So it is most likey a problem/bug with Kodi 18 and overscan scale.
Correct me if I am wrong, overscan_scale=1 and overscan enabled are the default RetroPie settings right? -
@Rascas yes. Those are the defaults.
-
@BuZz Can you please check this thread ?
https://forum.kodi.tv/showthread.php?tid=338052
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.