I have a Servarr stack with Jellyfin which I'm using with Kodi.
This stops our support for your task.
Posts by Da Flex
-
-
We've just added Flatpak package manager on nightly builds. I guess that's the most convenient option.
-
-
You're still doing it wrong:
Code2026-05-17 02:09:07.762 T:2177 info <general>: Disabled debug logging due to GUI setting. Level 0. -
-
Can you ping all involved devices by IP address?
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
No, just compare the release dates of LE and RPi firmware.
-
You have to install LE 9.2.8 for 3D. You probably have to downgrade the RPi firmware to make it work.
-
I guess what he means is the arrangement of the pictures, when you select a different view mode for a streaming provider. Pictures are bigger then, and arranged in a horizontal row. In that case it could really need more RAM, or Kodi is buffering in (non-existing / too small) graphic memory.
-
I don't use kiosk mode, but when multiple links lead to the same object, then it could also be a dead lock. So when using any tools on top of those lists (media scrapers), then it's worth to check them.
-
Thanks. The log looks very good, no critical errors. There is a chance that kiosk mode uses more RAM, and when the second RAM bank gets activated, it might causes an invisible error / freeze (I already had that problem many years ago). So I would take a USB stick, and run MemTest86.
-
Like this?
Yes, it's active after reboot, and results in more log details.
-
Use advancedsettings.xml to increase the log level. Post another log when it happens again.
-
Maybe this procedure helps:
-
There is something wrong with your advancedsettings.xml file, so you're still at log level 0:
Code2026-04-28 21:49:46.726 T:823 error <general>: Error loading special://profile/advancedsettings.xml, no <advancedsettings> node 2026-04-28 21:49:46.726 T:823 info <general>: Default Video Player: VideoPlayer 2026-04-28 21:49:46.726 T:823 info <general>: Default Audio Player: paplayer 2026-04-28 21:49:46.726 T:823 info <general>: Disabled debug logging due to GUI setting. Level 0.PS: Also have a look at this thread:
-
Shall I try to reproduce for a log with the following settings?
<loglevel>3</loglevel>
<setting id="debug.extralogging">true</setting>
<setting id="debug.setextraloglevel">131072</setting>Reproduce the issue with log level 1. Anything else is overkill.
-
After further testing, and hooking the Raspberry Pi straight into my beamer, audio works perfect. (through the beamer speaker)
Please check the LE audio settings in expert mode. The 44.1kHz sampling rate is common, but could be too low for some hi-res audio codecs. So your beamer seems to handle that sampling rate, but the Meridian AVR could have a problem with it.
Code2026-04-18 13:59:22.897 T:1906250624 DEBUG: CActiveAESink::OpenSink - SinkPi Initialized: 2026-04-18 13:59:22.897 T:1906250624 DEBUG: Output Device : HDMI 2026-04-18 13:59:22.898 T:1906250624 DEBUG: Sample Rate : 44100 2026-04-18 13:59:22.898 T:1906250624 DEBUG: Sample Format : AE_FMT_FLOAT 2026-04-18 13:59:22.898 T:1906250624 DEBUG: Channel Count : 2 2026-04-18 13:59:22.898 T:1906250624 DEBUG: Channel Layout: FL, FR 2026-04-18 13:59:22.898 T:1906250624 DEBUG: Frames : 2205 2026-04-18 13:59:22.898 T:1906250624 DEBUG: Frame Size : 8chewitt : Thx for explaining.
