Posts by HiassofT

    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

    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

    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

    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

    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

    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

    And we have a link to the wiki right on the top of every page here - most users seem to find that and search there, and the few who need a bump into the right direction (no offense at all to you, BTW, I've missed obvious stuff too myself) is something we can easily handle :)

    so long,

    Hias

    As a general hint: be careful with the tips you find on the net, especially if they are older than a few months. Lots of stuff is changing which means old info is completely outdated now.

    Eg forget about most stuff you found in the milhouse thread from 2019 - we have 2022 now :)

    Keep drmprime rendering with direct-to-plane enabled, otherwise performance will suck and you won't get HDR output.

    Also keep gpu_mem at default, it's only used for H264 decoding nowadays.

    The default config you get from current LE plain installation is pretty optimal and there are only very few cases where tweaking advanced settings etc actually helps.

    so long,

    Hias

    It's pretty much the same as on RPiOS (ex Raspbian), just config.txt is located at /flash instead of /boot and you have to remount it read-write in order to change files there - see https://wiki.libreelec.tv/configuration/config_txt

    Just add dtoverlay=allo-digione to the end of config.txt and reboot, then you should be able to select it as an audio device (and as a passthrough device for AC3/DTS if you want/need) in Kodi's System->Audio settings.

    so long,

    Hias

    No, that's a limitation of the display driver (it may even be a limitation of the hardware).

    When you switch from full to limited range the driver needs to completely reinit the hardware to change the output colorspace conversion - previously it combined the RGB full range Kodi GUI with YUV limited range video and output it as RGB full range, now both need to be combined and outputted as limited - as you can imagine that requires different combination and functions (internally colorspace conversion matrices) to be applied - this can't be changed "on the fly".

    so long,

    Hias

    These modechanges (modesets) are unavoidable as they are needed to push the changes through the video driver. And by changing max_bpc you are actually changing HDMI clocks - 12bit need 1.5x higher clocks than 8bit so the whole video output block needs to be reinitialized to set the correct HDMI output (which now runs 1.5 times faster than before).

    BTW: not sure why you set Colorspace to 12, that would be DCI-P3_RGB_Theater?

    My guess is you could leave Colorspace and max_bpc as they are and only change Broadcast RGB property.

    so long,

    Hias

    Verifying if it was indeed OK with 9.2 is a good idea - not that we're chasing a ghost :)

    If it works with 9.2 it might also be worth trying with latest LE10 nightly from here https://test.libreelec.tv/10.0/RPi/RPi2/ - it contains a few video fixes, one of that was rather hefty stuttering on certain files though.

    You can enable/disable subtitles during playback with the subtitles settings - press OK on your remote (or enter on keyboard) to bring up the player / progress overlay, you'll see various setting-icons in the bottom bar.

    so long,

    Hias