Posts by chewitt

2GB or 4GB shouild deliver an identical experience with LE, so no harm to swap them over.

There are no software differences between models, and nothing to be set. I'm not seeing HEVC issues with my own 8GB board so it's more likely to be something environmental or media related on your end. If it's something that you can consistently reproduce, please provide Kodi debug logs so we can investigate.

Well done. Commit the changes and push them to GitHub so others can follow in your footsteps later.

Standard problems are poor quality HDMI cables and inadequate PSU.

tomaszc The upstream kernel audio drivers are completely different (as with most upstream things) so while the card name is different, I know this is not the issue. The alsa card conf associated with the card may be more to blame, but why and how to fix it are the challenge.

No logs = No problem. Oh well.

You wait patiently until 10/12-bit support has been added. Until then you can watch 10-bit content downsampled to 8-bit output, which works fine with the 10.0.0 release.

In short, there is no list, because it would be a full-time job to maintain and we're all unpaid volunteers. The upstream kernel sources are the best thing to check. If you find Hauppague (or other) drivers there the hardware is much easier for us to support.

The official Raspberry Pi OS shouldn't be far behind LE in terms of playback; the Pi Foundation devs use LE as a testbed for media things and then backfil the required firmware, kernel and ffmpeg changes once things are proven. If they are lagging behind you should also be able to self-update key packages to use the same source versions/patches that LE runs .. to achieve a similar experience.

NB: It's not impossible to develop things with LE, but the workflow of updating sources, updating a package, rebulding the image, updating the OS .. is less intuitive to developers who are often used to fiddling with code, building, and then running code in-situ.

Simple test is to stop Kodi, rename /storage/.kodi/userdata/guisettings.xml to guisettings-old.xml and restart Kodi. This will give you clean defaults to see if that's the issue. You can always rename back to revert the change.

The 10.80.0 URL is correct, it means we can step through pre-Alpha, Alpha, Beta, RC and then finally 11.0.0 as the release version. However we are still in the process of merging a large backlog of package change for LE11 (master branch) so we didn't build and publish add-ons yet.

Quote from Rens

is it also possible to run C programs

Sure, you can run C programs. You won't be able to compile them on the box though as there are no compile tools in the OS. I suggest you read https://wiki.libreelec.tv/development-1/build-basics and familiarise yourself with how our distro is packaged. If you want to develop things we are probably not the distro you're looking for

tomaszc Most GXM devices have the headphone outputs wired up in device-tree, but I'm pretty clueless about alsa so the images are prob. using an incorrect alsa conf that prevents its use. Or you might need to install alsamixer to unmute things and switch the outputs around. I'm not really sure how all the plumbing fits together so I'm not sure what to advise, sorry.

LE 9.80.11 was a pre-Alpha version, so now we have a full LE10 release some cleanup has been done to remove old add-ons from pre-Beta stages that are not being maintained and use disk. Use the 10.0 release and you will have add-ons again. Or you have to self-compile them for the old version you're using.

Things that run over the network are generally a good idea as it means you can run whatever you want as a client device with (if needed) a different known-good combination of OS + drivers + firmware on the back end. Hauppague are good. HDHomeRun devices also seem to get good press.

Kodi only checks HDMI properties at start, so if you boot without the HDMI cable attached you'll probably get output on-screen, but with some sort of default kernel resolution like 1024x768 not 1080p.

Quote from Forage

It should be TBS upstreaming their work in that repository to the kernel, but for some raison they don't.

TBS has a love/hate relationship with upstreaming. All the people trying to use their devices and/or sustain support in distros are in favour of upstreaming and a couple of years ago they caved into the pressure and started releasing on GitHub which provided a consistent/common source for them. At the same time this has made it easier for cheap Chinese knock-offs of their boards to be produced so part of their team would like to revert to the less accessible "download tarballs via website" approach they had in the past. I'm not sure what the solution is, and it's a hard problem for a small manufacturer so I'm not sure they do either, so I wouldn't expect much change. Most of the drivers are rather messy anyway so the upstreaming process would need a ton of patience and persistence.

LE runs "ash" from busybox, not "bash" (or dash) so shell differences could be the problem.