Posts by nvdias

Quote from spontex

Hi,

I have been running TVH 4.2 for years, but I just reinstalled my computer from scratch and told myself that it would be nice to try TVH 4.3, since there is a feature I would like (better image cache management to avoid thousands of temporary files and slow startup).

So I took the latest LibreElec (9.2.3) and the latest TVH nightly (4.3-1885-08.06.2020) and installed it.

It worked a few hours, but now it does not anymore, due to a crash (log attached).

I have read on the forum that I might be due to a mismatch between the config file version and the TVH version.

It happened just after I set up my EPG by using the Kodi addon and pointing it to my XMLTV file location.

Many thanks

Display More

I'm also using tvheadend 4.3 betas for quite a while.

Version 1867 works great.

Yesterday I've tested version 1885 and had the same issues as you

It also happened some version ago.

I suggest you use 1867 until the next releases comes out.

Tvheadend nightly builds for LibreELEC

(As I always backup tvheadend add on settings before an upgrade, it was easy to restore the settings and resinstall previous version.

Settings are here:

/storage/.kodi/userdata/addon_data/service.tvheadend42/)

A small update:

Just
<smartredraw>true</smartredraw>

needs to be removed.

Found it !

So, let me explain:

Following HiassofT sugestion of renaming .kodi and running a clean kodi install: Everything works just fine ! No stuck notification

So: What's wrong ?

Back to "my" .kodi.

Went into peripheral definitions, looking into userdata, but nothing.

Started to remove everything that it was not default, disabled and enable add-ons, etc ...

And remembered to looin into config files, as .... advancedsettings.xml

namely this section:

<gui>
  <algorithmdirtyregions>0</algorithmdirtyregions>
  <smartredraw>true</smartredraw>
</gui>

Removing this part from advancedsetings.xml solves the problem of the hanging cec notificaiton at startup.

Thank you HiassofT for pointing out the way

Quote from HiassofT

CEC is working fine here, too (RPi4, LG TV), and I haven't spotted any CEC related changes between 9.2.1 and 9.2.3 yet.

nvdias could you try replacing start.elf and fixup.dat in /flash with the files from 9.2.1 and test if this makes a difference?

so long,

Hias

Hi,

I've made as you suggested replacing start.elf and fixup.dat with the ones from 921 over 923.

The same issue: Stuck pluse-eight CEC adater notification

Back to 9.2.1: All ok

Quote from HiassofT

ah, and it would also be interesting to see the full kodi debug log and journal after the stuck notification appeared.

ssh in, then run pastekodi and post the URL.

so long,

Hias

HiassofT I have the logs from a run with 9.2.3 and the notification stuck.

But they have a lot of personal info (tvhaedend, inadyn, letsencrypt, they all place to much personal info in the journal).

May I send-them to you as an attachment by private message ?

EDIT: There is no info about the notification in the logs, but I may share them anyway,

I’ve been using libreelec with rpi4 since it was released.
never had an issue with cec

the pi is connected to the tv with a hdmi cable.

this issue happens only with version 9.2.3

I’m just using my Sony Android tv with its remote control - had connected multiple different devices , including also a pi3 and different os distributions without issues.

I've updated from Libreelec 9.2.1 to 9.2.3.

Running on a Raspberry Pi 4, 4GB

At boot I now get

"pulse-eight cec adapter" notification stuck on screen.

It does not go awaing and prevents any other notification to be displayed.

Going back to 921, it works ok.

Back again o 923: notification stuck.

Is there any idea on what may be the issue ?

I've compared kodi.log from both 921 and 923 versions using winmerge and there is no differences (besides the obvious version changes in libreelec, kodi and kernel):

There is also no warning or error reported in journal regarding hdmi or cec

diff lines in 921:

NOTICE: Starting Kodi (18.6 Git:leia_pi4_18.6-Leia). Platform: Linux ARM 32-bit
NOTICE: Using Release Kodi x32 build
NOTICE: Kodi compiled 2020-03-03 by GCC 8.3.0 for Linux ARM 32-bit version 4.19.106 (267114)
NOTICE: Running on LibreELEC (official): 9.2.1, kernel: Linux ARM 32-bit version 4.19.106

NOTICE: ADDON: xbmc.addon v18.6.0 installed

over_voltage_avs=-23750

NOTICE: Checking resolution 23

dff lines in 923:

NOTICE: Starting Kodi (18.7 Git:leia_pi4_18.7.1-Leia). Platform: Linux ARM 32-bit
NOTICE: Using Release Kodi x32 build
NOTICE: Kodi compiled 2020-06-01 by GCC 8.3.0 for Linux ARM 32-bit version 4.19.122 (267130)
NOTICE: Running on LibreELEC (official): 9.2.3, kernel: Linux ARM 32-bit version 4.19.122

DEBUG: Thread Announce start, auto delete: false

NOTICE: ADDON: xbmc.addon v18.7 installed

over_voltage_avs=-17500

NOTICE: Checking resolution 16

NOTICE: VideoInfoScanner: Starting scan ..
NOTICE: Register - new cec device registered on cec->RPI: CEC Adapter (2708:1001)

Anyone else with this issue ?

Quote from chewitt

... Do not "sync playback to display" ....

Exactly.

Quote from kreeture

Thanks guys,

Interestingly there is no 25hz option for 1080 and I tried just whitelisting 1080 at 50 but I still get the judder as the TV is switching to 1080p.

Is there anyway to force Kodi to use 1080i instead, maybe this would solve my issue?

Just whitelist 1920x1080@ 50, disable sync playback to display, and enable "Adjust display refresh rate" "on start/stop".

That would be all you need.

I use a usb dvb-c receiver and there are no issues .

---

You should also look into your tvheadend configuration:

Aren't you using any stream processing that may be changing the framerate ?

Try to force "pass" profile as default.

The attached images are my "Pass" and "htsp" profiles current configurations:

(tweaked a little bit to get best results with handling some video artefacts in reception)

[configuration / stream / streamprofiles]

I also use:

"General / base / packet backlog" : active

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:

Docker Hub

### 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.

Quote from harun-cuk17

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?

Quote from Mattx

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.log

At 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:

http://ix.io/20xr

(search for "segmentation fault")

Hope this help in finding the issue.

Thanks Guys.

LibreELEC has been awesome !