Posts by chewitt
-
-
Code
kodi-send --action=PlayerProcessInfo kodi-send --action=PlayerDebug -
"dmesg | paste" and "lspci -nn | paste" and share the URLs here
-
And with v7.90.005? .. there was a fix for an OOM issue in Kodo 17b1 (but no guarantee it's the same issue).
-
a) The error message is just a warning, it can be ignored
b) The 7.0.3 build you are using is not official (we stopped at 7.0.2) so who knows what mixed up extra commits it contains -
PlayerProcessInfo .. and yeah it's fcuking annoying
-
FWIW, nouveau works well enough on my revo ION1 box, most issues crop up with live tv, progressive scan content works without problems.Do you have the nouveau changes in a git repo anywhere?
-
It normally depends on the device (the GPU in use) and what's in the HDMI chain. It's simple to test without the AVR inline.
-
There's a Hyperion add-on in our add-on repo that's pre-compiled and tested to work on LibreELEC, but that would require you to be on an 8.0/Krypton build and most of the S905 things in circulation appear to be 7.0 based - some builders provide add-ons, others don't.
-
autostart.sh is the wrong approach; read /storage/.config/system.d/openvpn-on-boot.sample
-
Current "normal" versions of Ubuntu/Fedora/CentOS are used by various team members so the workaround is to use a proper Linux distro and not the frankenversion that's running under Win10. You're probably the first person who's attempted this, and I doubt any of the devs are interested to spend time adding support when easy alternatives that require zero/little effort exist.
-
You should track-down escalade and see what efforts can be combined; he's also been experimenting with PMS things. And welcome
-
The error says the certificate notAfter time is invalid, so either there is bad data in the certificate (unlikely if the same cert works on 7.0.2) or maybe the device date/time is incorrect which causes an odd result.
-
I'd have done it within a single script but there's always four ways to do something in bash, and if it works, it works
-
Random suggestion .. take the HDMI cable used between PS3/Projector and try it with HTPC/Projector. Any different?
-
Yes, and No
We are working on overall support for Amlogic devices. There are at least 4-5 different kernels in use among different community builders and a dogs breakfast of Kodi patches that are poorly attributed and frequently hacked in device specific (not always reusable) ways. To make progress we need to get people working around a common kernel and patch set. It would be nice to have a Generic S905 build, and we are planning to move @kszaq's work to our main repo alongside the WeTek Hub (S905-H rev.c) and Odroid C2 (S905) to encourage community contribution, but the hardware reality of the general S905 (and now S905X + S912) landscape is not simple and little differences that are not significant to individual S905 devices are collectively very complex to handle in a single codebase. It may be the case that we act as a central focal point for development, but leave releases to community builders who work as part of our extended team and support the specific devices they have a personal interest in. So, there are plans, but not crystal clear plans, and with Kodi team starting to wrap-up Krypton development there is still a lot of do on the Amlogic side of the house; to the point where it's possible LE v8.0 might release with full support for Generic x86 and Raspberry Pi hardware, and "beta" support for Amlogic things.
-
Pi devices are amazing for what they are, but they are also a $30 hobby board with limited CPU. Some visualisations are OpenGL and will be handled nicely through GPU decoding. Others require CPU and will be challenging on low-spec hardware. Most Kodi devs use mid-range x86 hardware with a lot more CPU power for development so it's not too surprising that some Kodi eye-candy puts a Pi board beyond its limits - it was never the design target. The easy option for a small speed bump is moving from RPi2 to RPi3 but that may not be enough and the real step-up requries to you move beyond Pi to something more capable. You don't always need to look at the latest/greatest (most expensive) kit; it depends on your media playback needs. I'm still using an older Atom/nVidia box as my main player device. It's nearing 5-years old and is up for replacement as it can't handle newer HEVC/1080p/4k content that I need to test with now, but it still has 3.5x the CPU grunt of an RPi3 and plays H.264 content perfectly.
Which specific visualisations are you trying to use?
-
Have you installed the IMDB scraper add-on and configured Kodi to exclusively use that scraper?
