Posts by HiassofT

    That is great! I'm curious though. What caused this issue on certain tv's?

    A tiny, not well defined, optional, bit in the HDMI protocol which we discussed about for quite a long time as it wasn't clear from the spec how it was meant to be used and how TVs should handle it.

    Basically the firmware sends a "disable display" flag (set AVMUTE) before handing over to the kernel video driver, but the kernel driver didn't implement the optional set/clear AVMUTE handling and some TVs decided to stick in the "off" state. Solution then was to always send "clear AVMUTE" bit in the control packet.

    so long,

    Hias

    Sorry, no idea, I'm not aware of any changes in that area. If you are using an RPi the changes between 10.0.3 and 10.0.4 are basically just a very minor kodi update with no video/CEC related changes.

    so long,

    Hias

    Do you still have a backup of the LE10.0.2 installation? If yes, check which widevine CDM version you used with it (inputstream helper addon will show it) and compare it with the version you are currently using.

    ISTR widevine versions from about half a year or a year ago cause a very high CPU load (heating up RPi, but streams still watchable on RPi4, but unwatchable/stuttering on RPi2/3 as the load is too high) - older versions were fine (but may not work any longer, depending on the source) - not sure about newer versions.

    Personally I gave up on trying to watch Netflix etc with kodi addons, it was just too much hassle and hit-and-miss if it worked every evening when just wanting to watch the next episode of a show or a movie, and use the Netflix app on my TV instead. A cheap chromecast (or similar) device with official Netflix/.. app support is certainly the better choice if you don't like to play the cat-and-mouse game of streaming service changes and waiting for kodi addon updates.

    so long,

    Hias

    As you swapped the firmware for a much newer version my bet would be this is causing the issue - LE 9.2.8 is using an ancient 4.19 kernel and should be running the firmware that came with it.

    Just install official 10.0.4 or LE11 nightly versions.

    so long,

    Hias

    yullaw and all others who need the hdmi_mode/hdmi_group or input-switching workarounds to get a picture after boot, can you please test with this build:

    https://www.horus.com/~hias/tmp/libreelec/LibreELEC-RPi4.arm-11.0-devel-20230116232923-b261017.img.gz

    Write it to a spare SD card, don't make any other changes, and boot it - if the changes from popcornmix work as planned you should get a picture without needing any workarounds.

    so long,

    Hias

    If you are having issues please post full debug logs - otherwise we devs are unable to know the exact circumstances and background and won't be able to resolve potential issues.

    Enable debug logging in kodi, reboot, reproduce the issue then ssh in and run "pastekodi" (or use the log upload function in libreelec settings).

    The reason for not enabling 30/29.97/25Hz and instead allowing kodi to use double rates is that otherwise you'll run into issues with interlaced videos - they report as eg 25 Hz frame rate while they contain 50 fields and kodi will output that as 50 deinterlaced frames - and you'll get hefty issues trying to play 50 frames if kodi chose to setup display with 25 frames per second.

    so long,

    Hias

    Never ever hard power-off your system.

    There is no NTFS fsck for linux, the fsck.ntfs from ntfs3g only sets the "needs to be ckecked bit" - and you have to connect the drive to a windows PC and perform the filesystem repair there.

    It's best to format the drive as ext4 if you want to use it on linux.

    so long,

    Hias

    The log shows a read error from your NAS:

    Code
    2023-01-07 16:57:40.694 T:1048    ERROR <general>: Read - Error( -1, 110, Connection timed out )
    2023-01-07 16:57:40.694 T:1048    ERROR <general>: Process - <smb://192.168.1.3/Media/News/_move/Le.Pacte.Des.Loups.2001.DC.1080p.BluRay.DDP7.1.x264-W4NK3R.mkv> source read failed with -1!

    Network on the RPi4 side looks fine (nothing suspicious in logs) so it might be worth to check your network/switch/NAS and make sure you don't have any network/cabling issues and your NAS didn't go to sleep or something like that.

    so long,

    Hias