Posts by chewitt

Quote from sweetthdevil

Hello there,

Thank you for the information and the hard work provided by the libreELEC team!

May I just confirmed that my understanding of the announcement is correct, LE v10 which will run Kodi 19 - Matrix will be available for Wetek Hub (Soc S905-H revision C) done the line?

Also, following the announcement from coreELEC to stop supporting amlogic S905 & S912 due to their kernel not being maintained by amlogic any longer. Is there plan to stop supporting those SOC in the near future?

The statement makes it very clear (or so I thought) that there will be no LE10 release for Amlogic devices. Nightlies exist but mainline kernel support for Amlogic chips is not where it needs to be; there are challenges with hardware coding. I've been poking mainline u-boot support for the older WeTek devices and now have Play2 working well (within the caveats on hardware decoding) but I've been unable to get the Hub to boot so haven't done any work on it in some time - I need to dig up the vendor files and test the hardware with those again. If the status of decoding improves we can release something in the future. S912 is easier since it has more CPU grunt and you can disable problem hardware decoderss and use software decding on 1080p content (forget 4K). Same for newer chipsets with have even more CPU power. There is currently nobody working on the hardware decoding as I don't write code and nobody is funding commercial development. So not likely to see progress anytime soon, but we'll get there at some point. The images in my team share Index of /testing/ are a little more usable then current nightlies due to experimental ffmpeg work. Note - the "box" image is the one to use with any device that uses vendor u-boot.

The Samba change on 26/1 is where fingers naturally point, but I use SMB(2/3) from an assortment of devices in the same share configuration that has not been touched in several years (Synology NAS with SMB shares and SQL) so it's something nuanced and not a general SMB problem.

Start by describing the sharing environment with SW versions, and if Windows is the server target, state the credential types being used.

You probably need to run the Gamestarter image not the default LE image. The error suggests missing compile dependencies so I'd guess the other image has them and our main images don't. NB: I have zero knowledge on the Gatestarter releases.

lx.io sometimes has DB and disk space issues

The only mention of squeezelite that I can find is in the LE repo: Program Add-ons > Multimedia Tools. What you do with that .. I have no idea.

Install the current nightly image from Index of / it will make the upgrade to LE10 final release easier.

Plex is in the Matrix repo but last time I tried it the add-on locked up the box. You might want to check the Kodi forum support thread for the add-on.

Quote from HanSoloDK

Regarding Tiger Lake, then how is the Intel NUC supported ny Libreelec -->

Intel NUC11TNKi3 Tiger Canyon - Core i3-1115G4 - Barebone | Billig

Intel NUC11TNKi5 Tiger Canyon - Core i5-1135G7 - Barebone | Billig

And if they both are fully supported and good for LibreElec, then what is best for 4K. The I3 or I5 ??

I am not a big fan on the PI hardware for mediacenter....

I have no opinion on which one as it's several years since I used Intel hardware. I'm basing the recommendation on the hardware I see being actively used and developed on by the Intel graphics devs who have access to the Kodi team chat. They also still work on Gemini Lake.

I'm not a fan of older Pi hardware as compared to a previous Intel board (Xtreamer Ultra 2) and Amlogic hardware it always felt underpowered. I have no real complaints with RPi4 though.

Quote from HanSoloDK

I asked about that in a other post and was told that it was not supported by LibreElec at all but Kodi Android would support it.

My plan was to get a nVidia Shield Pro but if not supported by LibreElec then that's no godd.

nVidia Shield / Shield Pro is the Team Kodi reference device for Android so in the past we've never bothered to investigate support, and in the future it becomes technically impossible (or complicated beyond the point where it's worthwhile) because the nVidia video driver stack isn't compatible with the GBM/V4L2 direction Kodi is taking for Linux. Android is not without occasional faults in Kodi, but the main issues are vendors not following Google API standards. The shield seems to have fewer quirks and is better maintained (has updates) compared to other devices.

RPi4 .. because while there are many technically superior hardware devices and RPi hardware always has compromises, the level of software support we get from the Pi Foundation developers is second to none; and they care deeply that Kodi runs well on their boards. There are still some feature gaps to plug, but now initial support for HBR audio and HDR are done the number is shrinking quickly and an RPi4 is a solid daily-driver. Or an Intel Tiger-Lake device, as that platform has massive commercial backing and is effectively the reference design for non-ARM things.

Quote from BallerShotCaller

Sorry for this question but did I get this right that the release of LE10 will first be for Generic devices and will be released for other platforms successively after that?

Nope. It will be released simultaneously for Generic, RPi4, and the current roster of Allwinner and Rockchip devices. Everything else is either still in a developmental state or discontinued.

Quote from lameuser99

Can someone elaborate on why support for raspberry pi 1 is discontinued.

RPi0/1 devices need to use the older OMX decoder to run well with recent Kodi versions, and support for OMX (and MMAL) no longer exists in K19. Support was removed as part of the long-term cleanup/removal of vendor-proprietary decoding methods in Kodi. The newer GBM/V4L2 video pipeline needs more than 512MB to run well, so we have discontinued support. You can continue using LE 9.2.

4K60 modes are not supported in the LE10 nightly images. Some optimisation is required to achieve it, and it is being actively worked on.

You've purchased a CM3+ "lite" module. The U7 blank on the right side of the second image is where the RAM chip is (not) soldered.

Common mistake #1 is setting the Kodi smbclient "min" to SMBv1 and "max" to SMBv3 because "that covers all options!" but this means Kodi will connect with SMBv2 which is now the smbclient default (as SMBv1 is considered insecure) which is incompatible with the router which only speaks SMBv1. The only way to force Kodi to use SMBv1 is to set both min and max to SMBv1.

Common mistake #2 is configuring the LE samba (server) share options in the LE settings add-on, which have nothing to do with the Kodi smbclient (client) settings which are in Kodi settings > services > smb client.

ConnMan (the connection manager) will prefer the strongest signal for the SSID that you're connected to, so the solution is not installing drivers (which you cannot do on LE) but ensuring the 5GHz network has a better signal than 2.4GHz. The workaround is forcing the router to use a different SSID for 2.4GHz and 5GHz channels, allowing you to only connect to the 5GHz SSID. There is no way to force it to use 5GHz.

NB: Their instruction is for installing a .deb package which I guess contains drivers, but this will not work on LE because most of the filesystem you look at is expanded at boot-time from two compressed and read-only files, and you cannot install things inside them.

The "community" sections were originally created so there was an area for community builders creating unofficial images (for new unsupported H/W) to encourage their efforts and we organised the forum by SoC type to contain things. Over time some of those unofficial efforts became official but the threads didn't relocate and the categories are now sort-of wrong. At some point we need to clean things up a bit

"take note that CODA driver (imx6) is missing the read-back of parsed SPS (I think Philipp never reversed that) and as a side effect, it cannot implement the SOURCE_CHANGE event used to sync after a seek. You'll notice that seeking works reliably on CODA with GStreamer, but that's only made possible as we do hold some workaround implemented by Pengutronix folks (used on Zodiac in-flight systems)"

^ This is from one of the Collabora engineers who maintains GStreamer. So lack of seeking is known but needs some non-trivial changes in the drivers to enable it. Half the fun with iMX6 is all the documentation and BSP code is under an oppressive NDA, so despite being one of the best-documented SoCs available you have to reverse-engineer everything under clean-room conditions.