Posts by cdvreede

    I'm not aware of any reason the update should not work, but Kodi doesn't support downgrades so systemctl stop kodi && cp -R /storage/.kodi /storage/.kodi-12.2 before doing a manual update will clone the Kodi folder and give you a simple way to revert back to 12.2 if you need to.

    Did the in-place upgrade and that went well. Unfortunately the problem that existed in version 12.2.1 AARCH also exists in version 13 - yesterdays build. it does not exist in last weeks 32-bit (pi3B) build. Will move across to a full debian platform on Hyper-V which seems to run just fine. Thnx for your help - might try again after version 13 is released...

    Check /storage/.kodi/temp/kodi.log for errors and look at the time stamps.

    If you see connection errors and time/date is not correct, set Kodi to delay startup after network for more than 10 seconds.

    Date/time all OK - log is clean. Just cannot reach the repository and even if I could it looks like there is none for LE13, just for current and older versions. Is there a different URL for LE13 add-ons??

    We aren't going to touch LE12/12.2 images again as development shifted to LE13 aeons ago. So the first thing to do is retest with a current LE13 nightly. If the issue is resolved, great. If the issue remains, you need to share proper technical details on the problem, i.e. debug logs from Kodi and/or Tvheadend that reveal what the possibly-changed magic stream format is. Until then the not-good answer to your not-good question is "Yes, shitloads changed in ffmpeg between releases" because the ffmpeg major version has been bumped and ffmpeg is a rather busy active codebase. Kodi is tightly integrated with libavcodec (not the static 'ffmpeg' binary from the tools add-on) so even if you did self-compile an LE image with an older ffmpeg version inside you're likely to cause other breakage. I'm 100% confident the unknown problem has nothing to do with an arm vs. aarch64 change.

    thnx for that - happy to test LE13 nightly but before I do would you know if a backup I make with the current 12.2.1 before going to LE13 can be restored from within LE13? in other words - since I only have one Pi4 that does all channels except for 1 OK I would like to be able to go back and forth but not sure it would work? Or even more blunt - would LE13 be stable enough to run it as a daily driver??

    thnx

    OK - long story short - channel 9 works fine AS LONG AS its not pipe'ed through ffmpeg. Sure, since the info stream is encoded with an audio codec that Kodi doesn't handle there is no sound - but no continuity errors whatsoever. That also explains why the stream runs fine in VLC - both audio and video - as VLC can decode the audio stream just fine.

    As mentioned before all other streams run just fine - no issues whatsoever - just Channel 9 that seems to cause the problem.

    My newbee conclusion is that there is something in the channel 9 stream that causes ffmpeg to crash. weirdly enough the previous version of LE didn't have that problem - so question is if there are changes to ffmpeg in 12-2.1 that can be rolled back - maybe by using an older version of the ffmpeg-tools add-on?? It could of course also be a compatibility issue between the previous version and the aarch64 version I've upgraded to??

    My setup: Pi4 siting on Ethernet - LE 12.2.1 - TVH 4.3 with mix DVB and IPTV. Recent upgrade from LE 12.2 and unfortunately autobackup overwrote my saved backup so cannot undo...

    Issue: one of the IPTV streams - Channel 9 (Sydney) shows, after the LE upgrade, continuity errors severe enough for it to break the recorded file and stream to connected Kodi/TVH Clients. The only change introduced was the LE version upgrade - no other changes introduced.

    Observations: When tuned to Channel 9 TVH shows traffic coming in and the stream is passed on to TVH Clients and is recorded just fine for about 15 seconds after which there seems to be a hickup which TVH lists as a continuity error. This hickup shows as the stream input (shown in TVH Status) to drop from 2000 to 5000 kb/s to 0 kb/s for a couple of seconds to be followed by a "catchup" of up to 100000 kb/s. While the stream gets corrupted which throws off the connected Clients - even the local loopback client on the same Pi4 that is running THV - and corrupts the recorded file TVH doesn't crash and keeps on passing on the stream and record the file. The Pi4 itself is also not under stress as it happily streams/records other streams while the Channel 9 one breaks up.

    Above behaviour is only introduced after the LE version upgrade and only seen at this stream. All other streams work fine and no continuity errors can be observed. Network does not cause this, demonstrated by running an old Minix box with LE/TVH concurrently on the same network which works fine and as expected.

    the Channel 9 stream itself is also not suspect as the stream fed into TVH (pipe://ffmpeg -loglevel fatal -probesize 10M -analyzeduration 0 -fpsprobesize 0 -headers user-agent:\ otg/1.5.1\ (AppleTv\ Apple\ TV\ 4;\ tvOS16.0;\ appletv.client)\ libcurl/7.58.0\ OpenSSL/1.0.2o\ zlib/1.2.11\ clib/1.8.56\r\nseekable:\ 0\r\nreferer:\ \ \r\n -i https://i.mjh.nz/.r/channel-9-nsw.m3u8 -vcodec copy -acodec copy -metadata service_name=mjh-channel-9-nsw -f mpegts pipe:1) doesn't seem to involve transcoding and and extracting the URL itself (https://i.mjh.nz/.r/channel-9-nsw.m3u8) and feeding that into VLC plays just fine - not a single breakup or continuity error.

    I did do the LE upgrade using the workaround method of downloading the image - LibreELEC-RPi4.aarch64-12.2.1.img - from the website and insert it in the upgrade folder. Upgrade went fine...

    reinstalled the FFMPEG tools just to make sure.

    from the add-on log:

    2026-04-05 17:52:49.660 [ INFO] subscription: 0005: "scan" unsubscribing
    2026-04-05 17:54:00.003 [ INFO] dvr: "9News Sunday" on "Channel 9" recorder starting
    2026-04-05 17:54:00.009 [ INFO] mpegts: tvh-tv.m3u8 - Channel 9 in IPTV - tuning on IPTV #1
    2026-04-05 17:54:00.022 [ INFO] subscription: 0006: "DVR: 9News Sunday" subscribing on channel "Channel 9", weight: 300, adapter: "IPTV #1", network: "IPTV", mux: "tvh-tv.m3u8 - Channel 9", provider: "FFmpeg", service: "mjh-channel-9-nsw", profile="pass", username="admin"
    2026-04-05 17:54:00.023 [ INFO] spawn: Executing "/storage/.kodi/addons/tools.ffmpeg-tools/bin/ffmpeg"
    2026-04-05 17:54:11.365 [ INFO] spawn: Executing "/storage/.kodi/addons/tools.ffmpeg-tools/bin/ffmpeg"
    2026-04-05 17:54:15.404 [WARNING] TS: IPTV/tvh-tv.m3u8 - Channel 9/mjh-channel-9-nsw: AAC @ #257 Continuity counter error (total 1)
    2026-04-05 17:54:18.574 [ INFO] spawn: Executing "/storage/.kodi/addons/tools.ffmpeg-tools/bin/ffmpeg"
    2026-04-05 17:54:26.398 [WARNING] TS: IPTV/tvh-tv.m3u8 - Channel 9/mjh-channel-9-nsw: H264 @ #256 Continuity counter error (total 1)
    2026-04-05 17:54:26.423 [WARNING] TS: IPTV/tvh-tv.m3u8 - Channel 9/mjh-channel-9-nsw: AAC @ #257 Continuity counter error (total 2)
    2026-04-05 17:54:28.431 [ INFO] spawn: Executing "/storage/.kodi/addons/tools.ffmpeg-tools/bin/ffmpeg"
    2026-04-05 17:54:30.783 [ INFO] dvr: /storage/recordings/9News Sunday/9News Sunday2026-04-0517-59-S05E14.ts from adapter: "IPTV #1", network: "IPTV", mux: "tvh-tv.m3u8 - Channel 9", provider: "FFmpeg", service: "mjh-channel-9-nsw"
    2026-04-05 17:54:30.783 [ INFO] dvr: # type lang resolution aspect ratio sample rate channels
    2026-04-05 17:54:30.783 [ INFO] dvr: 1 H264 1920x1080 ?
    2026-04-05 17:54:30.783 [ INFO] dvr: 2 AAC eng 96000 ?
    2026-04-05 17:54:35.678 [ INFO] spawn: Executing "/storage/.kodi/addons/tools.ffmpeg-tools/bin/ffmpeg"
    2026-04-05 17:54:38.113 [WARNING] TS: IPTV/tvh-tv.m3u8 - Channel 9/mjh-channel-9-nsw: H264 @ #256 Continuity counter error (total 3)
    2026-04-05 17:54:38.145 [WARNING] TS: IPTV/tvh-tv.m3u8 - Channel 9/mjh-channel-9-nsw: AAC @ #257 Continuity counter error (total 4)
    2026-04-05 17:54:43.197 [ INFO] spawn: Executing "/storage/.kodi/addons/tools.ffmpeg-tools/bin/ffmpeg"
    2026-04-05 17:54:50.652 [ INFO] spawn: Executing "/storage/.kodi/addons/tools.ffmpeg-tools/bin/ffmpeg"
    2026-04-05 17:54:53.132 [WARNING] TS: IPTV/tvh-tv.m3u8 - Channel 9/mjh-channel-9-nsw: H264 @ #256 Continuity counter error (total 5)
    2026-04-05 17:54:53.156 [WARNING] TS: IPTV/tvh-tv.m3u8 - Channel 9/mjh-channel-9-nsw: AAC @ #257 Continuity counter error (total 6)

    2026-04-06 08:02:59.465 [ INFO] spawn: Executing "/storage/.kodi/addons/tools.ffmpeg-tools/bin/ffmpeg"
    2026-04-06 08:03:02.433 [WARNING] TS: IPTV/tvh-tv.m3u8 - Channel 9/mjh-channel-9-nsw: H264 @ #256 Continuity counter error (total 23)
    2026-04-06 08:03:02.436 [WARNING] tsfix: transport stream H264, DTS discontinuity. DTS = 63000, last = 1873800
    2026-04-06 08:03:02.474 [WARNING] TS: IPTV/tvh-tv.m3u8 - Channel 9/mjh-channel-9-nsw: AAC @ #257 Continuity counter error (total 24)
    2026-04-06 08:03:02.474 [WARNING] parser: IPTV/tvh-tv.m3u8 - Channel 9/mjh-channel-9-nsw: AAC @ #257: DTS and PCR diff is very big (40836120)
    2026-04-06 08:03:04.531 [WARNING] parser: IPTV/tvh-tv.m3u8 - Channel 9/mjh-channel-9-nsw: AAC @ #257: DTS and PCR diff is very big (40835040)
    2026-04-06 08:03:06.548 [WARNING] parser: IPTV/tvh-tv.m3u8 - Channel 9/mjh-channel-9-nsw: AAC @ #257: DTS and PCR diff is very big (40834680)
    2026-04-06 08:03:06.831 [ INFO] spawn: Executing "/storage/.kodi/addons/tools.ffmpeg-tools/bin/ffmpeg"
    2026-04-06 08:03:09.460 [WARNING] tsfix: transport stream H264, DTS discontinuity. DTS = 63000, last = 1873800
    2026-04-06 08:03:09.514 [WARNING] parser: IPTV/tvh-tv.m3u8 - Channel 9/mjh-channel-9-nsw: AAC @ #257: DTS and PCR diff is very big (42650520)
    2026-04-06 08:03:11.459 [WARNING] parser: IPTV/tvh-tv.m3u8 - Channel 9/mjh-channel-9-nsw: AAC @ #257: DTS and PCR diff is very big (42651000)
    2026-04-06 08:03:13.999 [WARNING] parser: IPTV/tvh-tv.m3u8 - Channel 9/mjh-channel-9-nsw: AAC @ #257: DTS and PCR diff is very big (42651000)
    2026-04-06 08:03:14.717 [ INFO] spawn: Executing "/storage/.kodi/addons/tools.ffmpeg-tools/bin/ffmpeg"

    I just noticed that it seems to spawn ffmpeg-tools while I understand TVH is compiled with ffmpeg already included. Could it be that the external ffmpeg-tools are different/corrupted or in any way not compatible??

    any ideas - other logs or things to try to fix this??

    thnx for your help

    bit more info - turns out the PI boots fine but when it tries to mount the EXT4 partition it fails stating it cannot mount. Not always however - sometimes it fully boots up, fires up kodi and launches LE.

    is there anywhere I can look into the logfiles where it might give a reason for that failure to mount??

    thnx

    Running LE on a PI3, booting from a 1TB SSD directly. As we know there really isn't a graceful shutdown so there is always the risk of corruption...

    yes - you guessed it - my PI no longer boots as it cannot mount the disk. From the disk activity light on the USB enclosure I can see lots of activity on the disk but then it stops and boot fails. Of course I can start afresh but since I have TVheadend fully configured and lots of data on there - and SAMBA and the likes - I wonder if there is a way to get things going again without wiping everything??

    I did try a check of both the FAT16 and EXT4 partitions using Gparted on a ubuntu machine. EXT4 was clean - FAT16 OK as well. Both partitions can be mounted and read on that ubuntu machine - windows can as well.

    any ideas??

    installed latest version - USB install on a Minix 9-H running with AVR and 1080 Bravia panel - and must say I'm impressed. All of a sudden refresh rate switching works as advertised and audio passthrough has no problems whatsoever. Kudo's - this might be the best PQ from all my boxes (2017 Bravia with 17.6, Minix "androidTV" with Leia, Mibox nougat beta with 17.6, x86 windows with 17.6)

    One thing however - the box does pick up time somewhere - I did put a couple of NTP servers in the settings - but it does not want to accept that I'm NOT in the UK and therefore do not want GMT. Not seen any timezone settings. Yes, localisation allows to select Australia but that in itself cannot accurately identify the correct timezone...

    I'm sure it's a setting somewhere - in Libreelec - but where???

    thnx