Posts by smp

Use the Whitelist (System-->Display-->Whitelist)

Add or uncomment 0.0.0.0/0 in /storage/.kodi/userdata/addon_data/service.multimedia.vdr-addon/config/svdrphosts.conf

How is the quality of deinterlacing of live TV 50Hz video (e.g. compared to Raspberry Pi 2/3)? Are those Rockchip devices capable of advanced deinterlacing like on RPi or is it just a basic BOB deinterlacing?

Quote from NDTradd

videos with 29.97 fps frame rate are still jerky, even though the TV is verifiably set to 29.97Hz.

The 29.97 and 30Hz modes should not normally be used. Just leave 60, 59.94, 24 and 23.98Hz modes in the whitelist and remove 29.97/30Hz modes.

Quote from NDTradd

if I force 23.98Hz resolution, then the 29.97 fps videos play absolutely smoothly, with Sync Playback to Display still set to Off (and I have a VERY critical eye - there is no judder at all). I don't get what's going on

Is it a footage that was originally shot on film at 24 fps? My guess is that Inverse Telecine is going on. If it is a DVD with a so-called "soft-telecine" encode (a 24p encode with pulldown flags) - Kodi probably just ignores the pulldown flags when the HDMI output is forced to 23.98Hz. That's why you get a smooth playback.

Once the license keys are saved to an OTP memory they can be removed from config.txt.

You can check your license keys with this command:

vcgencmd otp_dump | grep -E 45:\|46:

The license info is saved to a built-in eeprom (OTP memory) in broadcom SoC.

Did you try to change config_hdmi_b o o s t? (the word b o o s t is apparently censored on this forum)

Quote from Cubytus

vcgencmd measure_temp command returns anywhere from 80 to 84.9'C during playback.

The RPi 3 currently sits in the aluminum Flirc Kodi case.

This shouldn't happen with Flirc case. Looks like there is no contact at all with a SoC and a built-in heat sink.

I just tested with kernel 4.18.0 - the issue seem to be fixed - I blocked the signal from LNB and when the signal came back - tuner was able to lock it.

Nevermind, I did more testing and this issue randomly pops up with any kernel including 4.9.

However, with kernel 4.18 I encountered another issue - VDR (or VNSI) does not seem to function - I don't get any picture.

CvH or anyone - can you test if VDR/VNSI works on your hardware with kernel 4.18?

I want to test with those mutex commits reverted - I tried to revert on kernel 4.14 but I have no idea how to do this.

After upgrading from kernel 4.9.80 to 4.14.61 on my RPi3 I noticed this:

After the signal is lost (e.g. due to bad weather) and when it comes back - the tuner (DVBSky S960) does not lock the signal anymore. A reboot is required. I was able to reproduce this issue multiple times by blocking the signal from the LNB. Never had this issue with kernel 4.9.

Quote from Ipaddle

Nice, is this going to get fixed in future builds? I miss my Godfather Collection...

Use Milhouse builds for now. There is no such issue in his builds.

This build does not play DVDs (VIDEO_TS folders).

21:22:27.076 T:1567503216   ERROR: Error on dvdnav_open

I came across this issue when building my own RPi2 images from current LE master. I used Ubuntu 16.04 as a build host.

There are 2 ways to fix this:

- do not enable LTO for building Kodi

or

- build in Ubuntu 17.10 or 18.04.

I am not aware of any other hardware that will give you similar HDMI config options.

Those tweaks are for raspberry pi only.

-

-

Manually edit diseqc.conf.