I noticed that there was judder in sports scenes.
Forcing adjust display refresh rate on start/ stop and "sync playback to display" to off kills all judder effects.
I watch 25 / 50 tv transmissions at 1080i and 1080p.
I've setup kodi more or less as chewitt mentioned above.
I use tvheadend "pass" profile, or one ffmpeg profile that transcodes to 512kbps with libx264 .
Strange:
After the 9.2.3 update I've got
the
"pulse-eight cec adapter" notification stuck on screen.
Always there.
Any idea on how to disable it ?
Have you tried at docker hub ?
there's a lot of openvpn releases. Even with openvpn-as (the web based administration only for x86)
#UPDATED Version 1.0.9 - 27th September 2022
Running with LE11 (and E12)
# UPDATED Version 1.0.6 --- 19th March 2021
Now runs in both LibreELEC 9.X and 10.X
Link update bellow
# INTRO
I've made a small openvpn server that can be installed on LibreELEC running raspberry pi devices (and eventually other arm devices).
The server runs in a small docker image (around 20MB) that is automatically loaded on first start
After first run, you should configure your server address giving its ddns name or wan ip address.
Then, START THE ADDON and go to your ssh CONSOLE and run:
"openvpn-add-server" to:
- create the server config and keys;
- define your router address (so your openvpn clients can get access to your lan).
Note that the keys will take up to 15 minutes to create in a Raspberry Pi 4 (be patient).
Then call:
"openvpn-add-user" to:
- create users and get the ovpn file of each one.
Theses are the files you must give to the client to acess your openvpn server using an openvpn client software.
Restart the add-on and it's done !
### DOWNLOAD HERE
Version 1.0.9 - LE11 & LE12
https://mega.nz/file/EOAhCYDb#WtSj0s5-jXdcuqftXOD0IOUGaBV-UxjhrpF3_T8EsRQ
# TECH STUFF
### The docker is hosted in:
### The git source is:
GitHub - nvdias0/rpi-docker-openvpn: Docker OpenVPN image for Raspberry Pi
it is a fork from olivierguerriat/rpi-docker-openvpn, which in turn is a fork from kylemanna/docker-openvpn with an armhf base image
Look at those links above if you want to know more.
I’m not using 4K.
what kind of tv you have?
What is your resolution in kodi?
Did you enable 4k 60 in your config.txt?
You did not whitelist 4k 23,98 24 50 59,94 60?
So, your RasPi connects directly to the TV, without AV-Receiver?
Could you do me a favor: While judder and frame-dropping...can you switch off the TV (let the RasPi run!) and switch it on after 20 seconds again.
Does this make any difference and the judder is gone for a few minutes? Thanx, Greetings!
That's what happens to me at the moment: First I had the same problems you described in the first post, than I could get rid of it for a few weeks ( algorithmdirtyregions) and now all is back much worse.
I've also tried algorithmdirtyregions. But after some time, all the isswues were back.
The set of setting above is giving the best results.
Note: I've tried your test ith the TV, But I notice no diference - I'm using a Sony Android TV (2016 model) with a Raspberry Pi 4.
I've watched somme movies which had judder with MMAL other without-it.
After some more testing, I've had the most stable video viewing experience using the following set of settings:
Settings
Player
Adjust display refresh rate ALWAYS
Sync playback to display YES
Enable HQ Scalers above 50%
Allow hardware accel. MMAL YES
System / Display
White list - only All 1920x1080 resolutions (this will force upscaling in kodi when needed)
Preferred mode Same as Movies
System / Audio
Allow passthrough NO
(The bold settings seems to be the more influent)
Nothing after the one above.
As I've rebooted the system, I will wait for the next fail to re-look into logs.
I need to revive the thread:
I've been noticing that my simple web server running over docker's container "linuxserver/letsencrypt" is stopping.
After several days looking into the logs, I've found that it only happens after a docker update as the one following:
Apr 20 04:05:00 LibreELEC crond[2632]: USER root pid 4212 cmd /storage/.kodi/userdata/addon_data/docker.linuxserver.updater/update.sh > /storage/.kodi/userdata/addon_data/docker.linuxserver.updater/update.log && /storage/.kodi/userdata/addon_data/docker.linuxserver.updater/prune.sh > /storage/.kodi/userdata/addon_data/docker.linuxserver.updater/prune.logAt this time docker container stops and do not start again unless I reboot the system.
I'm using LibreELEC 9.2.1 runnng in a RPi 4
After upgrading to 9.2.0, I've done several reboots and docker restarts
The docker crashing issue seems to be solved with this version.
Thank you !!!
I was able to replicate the problem with a fresh install:
I've Installed LibreELEC 9.1.502 in another new 8GB SD-CARD in my Pi 4 4GB.
After 1st boot configured ssh, wired ethernet, fixed ip (into which my router forwards ports 80 and 443).
Activated debug logging.
Installed docker, linux.io repo and the add-on with letsencrypt and nginx
Configured ddns in the add-on as requested per install.
All seem to be ok.
After another reboot, docker crashed as in my initial SD-CARD.
(as before, this happens roughly 1 in each 3 reboots).
This happens only in beta 2. In beta 1, All is ok.
This url is for full untouched logs of this fresh install:
(search for "segmentation fault")
Hope this help in finding the issue.
Thanks Guys.
LibreELEC has been awesome !
Thanks.
i have placed the logs above.
Had to remove/mask log entries related to personal info - Did not touch anything logged by docker.
LibreELEC 9.2 Beta 2 and Docker
I'm creating this thread to easily read and get support 
, as the previous post was placed in the news section.
Updated the system to Beta 2
I have docker installed with only the official container for letsencrypt and nginx.
a) At each 3 reboots, docker fails, at least 1 time - sometimes work, sometimes don't - always working fine in beta 1;
b) Doing a "docker restart docker.linuxserver.letsencrypt" in ssh shell, takes a lot of time (compared to Libreelec Beta 1) and fails to start again a lot of times.
c) System shutdown / reboot taking a lot of time (a stop job is running for docker container .... 3 minutes) - almost immediate with beta 1
Logs from a failed docker start after system boot:
Note docker crashes in this lines:
Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.760117072+01:00" level=info msg="libcontainerd: started new containerd process" pid=430
Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.760551072+01:00" level=info msg="parsed scheme: \"unix\"" module=grpc
Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.760600776+01:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.797000224+01:00" level=info msg="ccResolverWrapper: sending new addresses to cc: [{unix:///var/run/docker/containerd/containerd.sock 0 <nil>}]" module=grpc
Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.797126520+01:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.797396094+01:00" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0x4d6ab50, CONNECTING" module=grpc
Apr 11 17:28:41 LibreELEC dockerd[369]: time="2019-04-11T17:28:41.819133578+01:00" level=error msg="containerd did not exit successfully" error="signal: segmentation fault (core dumped)" module=libcontainerdBack to LibreELEC 9.1 Beta 1 .. All is fine with docker .. no more core dumps.
I 've also tried a Beta 2 fresh install in a clean sd-card and got the same symptoms - testing several restarts, and docker fails to start 30% to 40% of the time
I've just installed Docker and Letsencypt on a RPi4 4G without issues. Not too sure what the issue might be with your setup, but I would uninstall Docker and letsencrypt and then reinstall.
If you still have issues:
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
LibreELEC 9.2 Beta 2 and Docker
(replicated the issue)
Updated (again) the system to Beta 2
a) At each 3 reboots, docker fails, at least 1 time - sometimes work, sometimes don't - always working fine in beta 1;
b) Doing a "docker restart docker.linuxserver.letsencrypt" in ssh shell, takes a lot of time (compared to Libreelec Beta 1) and failing to start again.
c) System shutdown / reboot taking a lot ff time (a stop job is running for docker container .... 3 minutes) - almost immediate with beta 1
Logs from a failed docker start after system boot:
Back to LibreELEC 9.1 Beta 1 .. All is fine with docker .. no more core dumps.
(All I've made was upgrading from beta1 to beta 2 and then back to beta 1.
(Also tried a Beta 2 fresh install in a clean sd-card)
Should I create a new thread for this issue ?
As I've said, I've re installed everything in a new sd card, and the same issues - very slow docker loading docker container (in this case, letsencrypt with nginx) and failing with core dump 50% of the time.
I will repeat the process and provide the logs.
I've upgraded my Pi4 to LibreELEC-RPi4.arm-9.1.502.tar and found some issues with Docker.
(using docker, linuxserver.io to support docker.linuxserver.letsencrypt).
After the upgrade the letsecenrypt add-on (which includes nginx) takes a long time to boot and docker service itself fails around 50% of the boots with a core dumped error.
Docker restarts also taking a long time and exiting many times with core dumps.
Just to be sure I've re installed everything in a new sd card, and the same issues.
I've downgraded to 9.1.501 and everything is good again with docker.
I just cannot say if it is something with docker or with libreelec 9.1.502, nor what it is.
Thanks
I got to ask short of reading through three pages even though that's not the worst thing in the world if I did.
But am I the only one with this issue? Because it is starting to get really annoying and I seriously would hate to go back to a Raspberry Pi 3 on 8.2.5 just to get rid of it.
But IMO, this is why saving images are important.
Edit: Ok, I'm gonna end up with an epileptic seizure and I'm not epileptic. I'm going back to an rPi 3 on 8.2.5 until 9.2 is final on the 4. Dont know what help I cam be but should anyone have any questions. I'll respond best I can.
I can think in three possible issues:
A - in settings, input devices, hdmi - configure-it NOT to switch tv input, turn on or turn off the tv.
B - try checking if your cables are ok
C - you may have a defective pi4 (mine had a non working micro hdmi 1 (had to replace it at the shop) - validate by installing a different distribution , as the official raspbian.
i guess i have the exact same issue, but there is a solution that i found.
if you run the pi in any 60hz resolution, everything will be fine. 1080p @ 60z or 2160p @ 60hz.
the 60hz removes absolutely ALL judder for all video types and audio profiles, and with and without subtitles. just my two cents.
that is odd. You can not have judder free when watching 23.976fps or 25 / 50 fps movies at 60hz.
There is no direct conversion. These formats should be played at native refresh rates configured in the white list.
