Posts by HiassofT

  • HDMI Black level - Raspberry 4 - Librelelc 10.0.2 - Limited out of the box ?

    For 10bit content the driver will check in the order RGB 4:4:4 12 bit -> YCbCr 4:2:2 12bit -> RGB 4:4:4 10bit -> RGB 4:4:4 8bit if both the sink and the RPi support that format.

    It takes max TMDS bandwidth, YCbCr 4:2:2 and 10/12 (30/36) bit flags from EDID and also max TMDS rate from RPi into account (4kp60 / 600MHz TMDS is opt-in in config.txt) and picks the first supported format.

    so long,

    Hias

  • HDMI Black level - Raspberry 4 - Librelelc 10.0.2 - Limited out of the box ?

    mathmath51 can you test with hdmi_enable_4kp60=1 in config.txt (you also need to enable HDMI Ultra HD Deep Color support in your TV's setting - this is usually HDMI-port specific) on LE 10.0.2?

    LE10.0.2 supports outputting at 10 and 12bit, LE10.0.1 only sent 8bit HDMI.

    So on LE10.0.1 your 4kp23.97 file is transmitted as RGB 4:4:4 8bit, 10.0.2 without 4kp60 enabled transmits at YCbCr 4:2:2 12bit, with 4kp60 enabled it transmits RGB 4:4:4 12bit - all that could make a difference.

    so long,

    Hias

  • Freezing, losing Connection, sporadic stops

    I'd recommend also monitoring signal strength / quality at both ends.

    On the RPi you should have a bar indicator roughly showing it, and your AP/router may have that, too (my OpenWrt router shows link quality of each connected wifi device).

    5GHz wifi has benefits if your device is near the router, but if there's a wall in between things can change drastically and 2.4GHz may be the better choice (so that's not actually a workaround but a wise decision based on physical facts - higher frequencies are affected more by obstacles like walls than lower frequencies).

    so long,

    Hias

  • RPI4 Nightlies Crash System from 20220723-0008ab5

    Cris_ the hint is/was in the crash dump:

    At the very beginning it says it crashed in thread 1:

    Code
    Program terminated with signal SIGSEGV, Segmentation fault.
#0  0xf7853198 in strlen () from /usr/lib/libarmmem-v7l.so
[Current thread is 1 (Thread 0xc8cfc240 (LWP 1657))]

    Then a bit down look at the backtrace of thread 1 and you see it crashed in pvr.iptvsimple - that's the offender

    so long,

    Hias

  • Freezing, losing Connection, sporadic stops

    The log shows several wifi disconnects and reconnects. Got a new neighbor or one of them switching APs maybe? Unfortunately these things are kind of normal with WIFI, best solution is you switch to ethernet LAN or powerline (the latter can be a bit unreliable, too though, but is in general far more reliable than wifi).

    so long,

    Hias

  • Micro Stutters / Frame Drops with 10.0.2 (Matrix)

    If you get the issue with latest LE10 nightly as well then please post a debug log - mediainfo of a problematic file and a sample could be useful too.

    Another thing to try would be overclocking the RPi (RPi2/3 h264 decoders are clocked a bit low and struggle with higher bitrate/fps videos), eg try adding these settings to config.txt

    Code
    core_freq=500
h264_freq=500
over_voltage=6

    so long,

    Hias

  • finding the optimal Monitor setting

    It's highly unlikely you'll damage your monitor if you select a resolution listed in it's EDID.

    Damaging monitors was an issue with CRTs some 30+ years ago if you exceeded the specs - later CRTs were clever enough to check the signal and show a warning in that case.

    It's quite common that computer monitors with HDMI inputs also support SD resolutions so you can hook up eg a DVD player.

    BUT: computer monitors often have rather poor scalers, so in that case you might get better picture quality by letting LE do the SD->HD upscaling - I see NUC mentioned in your sig, that should be able to do high quality scaling.

    In that case only enable the native resolution of your monitor in the whitelist at all refresh rates (except 25 and 29.97/30Hz as mentioned in the wiki) or the commonly used higher consumer resolutions (eg 1920x1080 and maybe 1280x720). If you use eg a 1920x1200 monitor it may only support 60Hz at the native resolution but offer 1920x1080 at 50 and 59.9x Hz as well.

    So, you'll have to check yourself which combination gives the best picture results.

    so long,

    Hias

  • finding the optimal Monitor setting

    In general: your TV will often be able to do better upscaling than eg an RPi, so if your TV has native support for some resolution you need then enable it in the whitelist.

    eg 1280x720 - add it (at 50 and 60Hz), that's what your HD (satellite?) streams use.

    720x576 (or 720x480 in "NTSC land") may be a candidate, too, but test it. My LG OLED supports it but annoyingly forces overscan at these resolutions (despite having set "Just scan" - i.e. no overscan in the TV settings). This is OK if you play from a DVD player but not so much with kodi as it'll cut off parts of the overlays (eg player control when paused or going to player settings).

    Allow double refresh rates: yes, you need that. Interlaced content will report in frame rate, eg 25 frames for 50i fields, and you don't want kodi to switch to 25 Hz - it'll deinterlace and output 50 frames.

    3:2 pulldown - you only need that if your TV doesn't support 23.97/24 Hz, then kodi will switch to 59.9x/60Hz.

    so long,

    Hias

  • 4k 60hz Whitelist

    Did you enable "Ultra HDMI deep color" (or some similar setting) on your TV (it's usually a per-HDMI-port setting and some TVs don't support 4kp60 4:4:4 on all ports)? RPi4 won't output 4kp60 without that.

    so long,

    Hias