LE latest stable: 12.0.1
Rpi5 4 GB version, AARCH64
Posts by soder10
-
-
Dear all,
I have a couple of UHD Blu-ray RIPS, that keep Libreelec crashing
(note: I am somewhat novice to LE/KODI to make the difference between a Kodi application-level crash versus the entire Linux OS rebooting, but if you can give some helping pointers I can understand it)
I uploaded a sample debug log under:
https://paste.libreelec.tv/poetic-marten.log
if anyone can have a look at it. As soon as I press the playback on for example the 2001 space odissey video, the screen goes blank, and I can see the LE logo, as if the whole Pi5 has rebooted.
-
If one could please confirm, if I set up e.g. 512 MB as cache, and I set up read-factor as ADAPTIVE, how does that translate to real-life number (values) in the:
- Audio queue
- Video queue
- Forward... queue?
Please forget the 100Mbit/s NIC config.
-
I appreciate that you updated the title of my thread. But it will mislead other readers thinking we are discussing how to squeeze out the theoretical max from the Pi5 NIC if the negotiated speed is 100Mbit/s full-duplex.
When in fact I desperately ask you guys to give some hints about how the caching in Kodi/LE works?
-
This seems to be the normal speed for that hardware. The NIC specs don't mean you really get it in real life.
If my practical LAN speed maxes somewhat below the theoretical 100Mbit/sec, and the constant bitrate of the 4K UHD videos actually exceeds that value, does it make sense to increase the bufferin Kodi to as large as to possible to delay the buffer underrun as further as possible? If I get buffer underrun 1 or 2 times during an hour, that results is a short 1min pause (during which time the buffer goes up again, and can sustain for yet another hour of plaxback), then I reached my goal.
Only thing I am asking from this forum, why the system does not honor the value set under "caching". If I have plenty of RAM, I would like to utilize it to make the buffering as rare as possible.
I hope it makes sense.
-
Probably a LAN problem.
Yes, the problem is that its not gigabit.
But the questions in my opening post still apply aboutv how exactly does caching work in LE / Kodi, and how to maximize usable cache size up to the free RAM available?
-
Messing about with those cache settings would not make high bitrate 4K videos (UHD BDs?) play smoothly on 100Mbit LAN. You will have to upgrade to Gigabit.
Yep, 4K UHD Blu-ray remuxes.
In general, anything below constant 75Mbit plays nicely. The problem starts with those that are 80-85Mbit, and occasionally peaking at around 100Mbit.
-
Hello all,
I am trying to understand how caching works in Kodi / Libreelec. I am new to Kodi, so did my homework on the Kodi wiki. But I feel there is a LOT of background info missing from that article.
System: Libreelec 12.0.1 official, on Pi5, stock skin, no add-on apart from the ones available after a fresh install.
I try to play very high bitrate 4K videos (constant 85+Mbit/sec) on Pi5 4GB / Pi5 2GB, and have serious and annoying buffering issues. I use Pi5 wired LAN interface, but it is running only on 100Mbit/sec, not Gigabit. The video source is on an SMB windows box.
I checked the Kodi wiki: "caching" article.
--> Buffering mode is set as: Buffer all filesystems, including local files
--> Memory size: I tried changing to various hardcoded values (128MB, 256MB). Its unclear, if I need to reboot, or the change gets applied immediately?
--> Read factor: Adaptive. But I also tried 4x, 10x as well.
--> Cache Chunk size: I set it to 1 MB. Neither the UI help text nor the wiki article is really clear about what protocols do indeed honour that setting? How about SMB protocol? Does it benefit from the large chunk size, if I want to playback both giant 4K HEVC files and ordinary H.264 files over LAN?
How about the chunk size setting under the other location: Services \ SMBclient? Does it affect the same behavior as the caching chunk size described in the previous pharagraph? The UI help text is very unclear whether SMB client honours chunk size setup under which settings-location?
After all of this, I checked Kodi wiki: "Player Debug Info":
I see the following behavior: at the start of the video playback, Aq and Vq goes slowly up to @99%, and when it reaches 99%, "forward" starts to increase from 1MB and goes up to max at 95MB. Even if I set up 256MB, it doesnt go above 95MB. The percentage shows 100% for the 95MB cache value, which doesnt really make sense to me.
Under 3-4 minutes of continuous playback, "forward" slowly goes down under 1 MB. Then slowly the Vq goes down from 99% to 0%, and then the playback stops. Then the Aq+Vq starts increasing from 0% to 99%, and then playback starts again. But "forward" does not go up to 95MB, it stays around the same roughly 1 MB size. Then vq slowly goes down to 0%, playback stops and the cycle repeats ad infinitum.
My goal to cache slightly more agressively on both the 4GB and the 2GB Pi5, so that these high bitrate 4K videos can be played back from start to finish without buffering stops.
-
(Sorry to hijack your thread) I am new to Kodi.
Since day1 with a brand new RPi5 + wired gigabit LAN, I experience a similar type of slowness issue. Using LE 12.0.1 and SMB via Windows 10 home server. Folders (even small 1-2 files in it) usually open under 2-3 seconds (which is still somewhat slow, heck its on a gigabit LAN!). But what worries me more, during these 2-3 seconds, basically the UI blocks any other input action. If the delay is more, the UI block is more noticeable. Sometimes the circling happens for a minute (I cannot confirm if its due to the slow SMB or something completely different stuck in the background reason). Then suddenly all inputs I entered in the past 1 minute gets processed in a split second. Looks crazy I can tell you.
Is that something sort of "get used to it, it works like that since xbmc 2001" and normal in the Kodi universe @ 2024? Or Kodi v21 is very new, contains too much experimental and untested stuff?
-
Rpi5 2 GB version has garbled UI output with this release.
Just wanted to warn anyone who bought the new Rpi5 model for Libreelec.
