Are you using adjust-refresh and whitelisted modes to play media at native resolution/refresh or forcing everything to 60Hz? I'm not seeing any issues from a current TVH setup and my server is 6,000Km away down a WireGuard tunnel (this generally encourages any latent issues to show up).
Posts by chewitt
-
-
I'd recommend whitelisting the 3840x2160 modes as it's a more accurate match for broadcast media. The 4096x2160 modes can result in vertical black bars being shown.
-
WARNING Incorrect checksum calculated on downloaded file: got e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 wanted e13f6f118cfbbdc0b6e0edd5e3504abd96a8d0e33dc67cba31c6942c449f77a
^ The SHA256 checksum for the package has changed on the server end (it happens sometimes) so you need to edit the package.mk file and either correct the PKG_SHA256 value or null it by setting PKG_SHA256="" and then validation will be skipped.
-
Add-ons > Install from repository > Kodi Add-on Repository > Look and feel > Languages > Italian
No idea about the World Live TV add-on, this does not appear to be from the Kodi repo. I suggest you contact the add-on author.
-
How can I switch to YCbCr 4:4:4 and 10bit or YCbCr 4:2:0 and 8bit?
You need to play media with those properties on hardware that has software (driver) support for them.
-
There's a bug somewhere in the boot process. It's known but unresolved. First boot will succeed. Second will fail. Third and all future boots will succeed fine. So no need to examine SD cards or check PSU's, just power up the board again.
-
No idea. You'll need to experiment with the available device-trees and see what works.
-
I wouldn't hold breath. Ask me again this time next year..
-
-
Read the release notes https://libreelec.tv/2023/07/20/libreelec-nexus-11-0-3/ and adjust expectations.
-
Indeed, watch live stalls fairly quickly. I rarely watch live streams.
-
Really no clue about what you did, what the box did, what file file might be

-
FWIW, I've not seen any issues with stalls and the iPlayer add-on; using an RPi5 not RPi4 but that shouldn't make any difference.
-
Old hardware + Old unsupported release = Not our recommendation to anyone these days
-
If you look around there are some user-created scripts to check for DDNS changes and stop/modify/restart the connection; put into a systemd service on a timer or as a cron task so it's persistent.
-
^ This needs to be an IP address (as stated in https://wiki.libreelec.tv/configuration/wireguard) - it will not auto-resolve an FQDN.
-
Does the server end at least show an active connection from the client?
-
cmdline.txt NOT config.txt, and "on the same line" as all the other boot params NOT on a different line in the same file