The better advice would have been to update to an LE12 nightly that has the same fix included. You are now on LE13 so while Kodi database file are currently same-version (we haven't bumped to Kodi P in master branch yet) the LE and Kodi-binary add-ons are numerically bumped to LE13 and will need to be removed and reinstalled if you want to downgrade to the next stable LE release (12.0.1) when it arrives. Note that removal/reinstall doesn't mean you lose settings.
Posts by chewitt
-
-
-
The old methods require OMXplayer/MMAL decoding and these were removed from Kodi (c.2018) in a purge of vendor proprietary decoding methods as Kodi moved forwards with open standards (GBM/V4L2, VAAPI, VDPAU). RPi devs have reimplemented the video pipeline for older RPi0/1/2/3 boards using GBM/V4L2, but the end goal of that effort was to upstream all their kernel driver code instead of hoarding ever-more in the downstream RPi kernel fork. The CPU+GPU approach, while clever, was always a big hack that would never be allowed upstream, and as it would be architecturally hard to reimplement (rewriting from scratch) under GBM/V4L2 the work has never been done. Around the same time RPi4 also launched bringing native HEVC decoding. There was no intent from RPi devs to "drive RPi4 upgrades" by not reimplementing the CPU+GPU approach, but it did reduce the need.
Having never used PINN, I can't really say whether downgrades are possible, but going back to 9.2.8 (or I think 9.2.6 for RPi3 as 9.2.8 was a respin solely for RPi4 support) is a big jump, so best to reimage and start over clean.
-
Read: https://wiki.libreelec.tv/hardware/amlogic .. it will probably boot with the Q201 device-tree.
-
The meson-gxm-q200.dtb device-tree should work, assuming the boot loop isn't caused by flashing the wrong ROM to the device resulting in broken u-boot (can only be diagnosed with a UART cable attached to show what u-boot is doing .. or not).
Also read this first as the boot process changed: https://wiki.libreelec.tv/hardware/amlogic
-
Two probable scenarios:
a) You're using an under-spec PSU (something less than 5V/3A) and this causes power/stability issues.
b) The SD card has gone terminal and needs replacing.
I'd image another card and see how that works first, before thinking about anything else.
-
RPi3B+ supports H264 hardware decode. It does not support HEVC hardare decode. Older LE releases (up to LE 9.2) have patches to share the decoding effort between CPU and GPU to improve HEVC decoding. It is normally possible to play low-bitrate 1080p files.
After LE10 the RPi3B is using a newer GBM/V4L2 display pipeline and this does not support the CPU+GPU decoding method. The board can still software decode HEVC, but without the GPU offload the maximum resolution is reduced to SD and 720p media.
Your options are:
a) Use handbrake/ffmpeg to re-encode files from HEVC to H264 ($0).
b) Use handbrake/ffmpeg to re-encode files to SD or 720p ($0).
c) Use an older LE 9.2.8 release ($0).
d) Change the RPi3 for something that supports native HEVC decode, e.g. RPi4, or RPi5 ($$).
-
As Linux does not support HDR10+ or Dolby Vision, your choicees for Kodi are an AppleTV or an nVidia Shield, and further discussion is best done in the Kodi forums as neither of those devices are supported here.
-
LE 9.2.8 is the last image to support "display_rotate" in config.txt, but this will not boot on current RPi5 hardware (only the original boards) as newer hardware requires newer firmware. This is not impossible to solve, but LE 9.2.8 is starting to look old now and most RPi5 boards won't boot LE 9.2.8 without some effort. LE 10/11/12 use a completely different display pipeline which does not currently support display rotation.
-
How To Update Libreelecletmegooglethat.com
-
I have noticed that it happens when Radarr or Sonarr attempts to run a library update after a new file is downloaded.
I'll remind you of forum rules, and wish you good luck in finding someone to help you (in some other forum).
-
You probably need to enable HDR modes for specific HDMI sockets. Something like "Enhanced Mode" or "Deep Colour Mode" or such (there is no standard term).
-
The original developer of the add-on hasn't been around for a while now, so all add-on maintenance is crowd sourced and we're lucky that it doesn't appear to need much effort. The only documentation is "prior art" in the code and if you'd like to see a new feature; it's your resposibilty to either code it or find someone to code it. The project staff can usually find someone to review any changes that are submitted but we don't really have the resources to handle requests.
-
It appears the original add-on (in the Kodi repo) is now unmaintained and changes to some of the upstream sites that radio feeds are sourced from mean it's no longer working. In some cases a little manual tweaking to add-on files can get things working. In others more invasive changes are needed. There are also forks or replacement/alternative add-ons appearing, though none are in the Kodi repo at the moment (and that may not happen based on the whims of individual developers. It's best to read the add-on support threads: https://forum.kodi.tv/forumdisplay.php?fid=148 .. for the radio add-on, skip-to/start around page 50.
-
I'd guess the USB-C dock advertises 'monitor' capabilities not AVR/TV capabilities. If you connect direct to the receiver over HDMI do you get the normal resolutions?
-
-
Isn't ASIO specifically a Windows thing - not sure I get how it's related to Linux? Or am I missing something?
ASIO is Windows only. There's no direct equivalent to ASIO on Linux (only good-old ALSA) but I do see folks in the RPi audio distro ecosystem using RT (real-time) kernels because that's supposed to be better juju for your listening experience. Magic
-
"Newly created posts will remain inaccessible for others until approved by a moderator."
It's true (for new registrants with no posting history) but there's about 10x moderators and they're spread over a few timezones so the time between posting and someone approving is never that long.
