Posts by ApexDE

Thanks for the explanation and heads-up. I'll dig myself into that Wiki Article. I haven't found it before.

i noticed that 12.0.0 is out on git as a new branch. I guess the changes i made in my local 11.9.5.2 previous checkout will be overwritten/updated when i do "checkout 12.0.0" ?
Is there a way to keep the changes i made or will have to edit/apply the changes afterwards again?

The whole LE Development/git is completely new to me but exciting too.

I managed to set up a LibreElec 12 Development system using Ubuntu 22.04 and compiled the ffmpeg addon using 4.4.4 sources. I'm a bit proud

Best thing is: my IPTV Streams run flawless now with the selfcompiled ffmpeg 4.4.4 like on all other systems i tested which had ffmpeg 4.x on it (macOS, Synology, old LibreElec...)

i guess more reports will follow once LE12 is released and more users will upgrade. I was the first reporting IPTV problems several times with new major releases.

I'll dig myself into Raspberry LibreElec Development/Crosscompiling and try to build a ffmpeg 4.4.x package myself.

OK... all my tests here showed that i only get stable streams using ffmpeg 4.x.x versions. I guess i have to dig deeper and learn how to compile a ffmpeg4 package for/with LE 12 myself. This will get very hard i believe

EDIT: there are two different TVHeadend-Server Addons in the repo, why not a second "legacy" ffmpeg addon? One could choose which to use/install?

OK, thanks.

These "static" versions fail to establish tcp connections/resolve hostnames on LE12b2

[tcp @ 0x109fa6e0] Failed to resolve hostname chemnitz.iptv-playoutcenter.de: System error
https://chemnitz.iptv-playoutcenter.de/chemnitz/chemnitzfernsehen.stream_1/playlist.m3u8: Input/output error

i did a full restore via the LibreElec Config Tool (Kodi Menu)

you could build in a switch where you can choose to use the argon receiver or "other ones" ? When switched to argon the previous configs are backuped and when turning off the previous backuped ones are copied back?

piped ffmpeg exits on this stream also, but it takes MUCH longer, about 10-30 seconds.

I don't get any logs from ffmpeg. Maybe because of piping?

EDIT: OK, i get logging when i turn on "debug" logging instead of "fatal". Sadly, i don't see warnings or errors. ffmpeg 6.0.1 just closes the connection and exits on the IPTV streams. It says "EOF" in the log, which isn't the case. The stream was not stopped. I'll attach the ffmpeg log.

I did some further testing on other machines: Synology NAS with ffmpeg 4.4.4 : works, mac mini with ffmpeg 4.4.2: works. LibreElec 11.0.6 with ffmpeg 4.4.3: works.

Would you mind adding ffmpeg 4 as a option to LibreElec 12?

Output #0, mpegts, to 'pipe:1':
  Metadata:
    encoder         : Lavf60.3.100
  Stream #0:0, 0, 1/90000: Video: h264 (Main), 1 reference frame (avc1 / 0x31637661), yuv420p(left), 1920x1080 (0x0) [SAR 1:1 DAR 16:9], 0/1, q=2-31, 25 fps, 25 tbr, 90k tbn (default)
    Metadata:
      variant_bitrate : 7999000
      major_brand     : cmfc
      minor_version   : 0
      compatible_brands: cmfcisomiso2iso5avc1dash
  Stream #0:1(deu), 0, 1/90000: Audio: eac3 (ec-3 / 0x332D6365), 48000 Hz, 5.1(side), fltp, 256 kb/s (default)
    Metadata:
      variant_bitrate : 7999000
      major_brand     : cmfc
      minor_version   : 0
      compatible_brands: cmfcisomiso2iso5mp41dby1dash
      comment         : deutsch
    Side data:
      audio service type: main
Stream mapping:
  Stream #0:1 -> #0:0 (copy)
  Stream #0:0 -> #0:1 (copy)
Press [q] to stop, [?] for help
[vost#0:0/copy @ 0x3ee66320] cur_dts is invalid [init:1 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream)
[aost#0:1/copy @ 0x3ee736a0] cur_dts is invalid [init:1 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream)
[vost#0:0/copy @ 0x3ee66320] cur_dts is invalid [init:1 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream)
Automatically inserted bitstream filter 'h264_mp4toannexb'; args=''
EOF in input file 0
Terminating demuxer thread 0
No more output streams to write to, finishing.
[out#0/mpegts @ 0x3ee3b1f0] All streams finished
[out#0/mpegts @ 0x3ee3b1f0] Terminating muxer thread
[AVIOContext @ 0x3ee86530] Statistics: 1517348 bytes written, 0 seeks, 91 writeouts
frame=   40 fps=0.0 q=-1.0 Lsize=    1482kB time=00:00:01.56 bitrate=7741.6kbits/s speed= 218x    
video:1386kB audio:50kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 3.172454%
Input file #0 (http://192.168.178.21:6060/api/zde/live/zdf):
  Input stream #0:0 (audio): 50 packets read (51200 bytes); 
  Input stream #0:1 (video): 40 packets read (1419491 bytes); 
  Total: 90 packets (1470691 bytes) demuxed
Output file #0 (pipe:1):
  Output stream #0:0 (video): 40 packets muxed (1419491 bytes); 
  Output stream #0:1 (audio): 50 packets muxed (51200 bytes); 
  Total: 90 packets (1470691 bytes) muxed
0 frames successfully decoded, 0 decoding errors
[AVIOContext @ 0x3ee93820] Statistics: 0 bytes read, 0 seeks
[AVIOContext @ 0x3ee5ad70] Statistics: 0 bytes read, 0 seeks
[AVIOContext @ 0x3eec1a70] Statistics: 0 bytes read, 0 seeks
[AVIOContext @ 0x3eeb2b10] Statistics: 0 bytes read, 0 seeks
[AVIOContext @ 0x3ee38020] Statistics: 55110 bytes read, 0 seeks
[AVIOContext @ 0x3edba890] Statistics: 934 bytes read, 0 seeks

Yes, that was my first test: Fan always on. And it didn't work so i thought the addon in general doesn't work.

Can you built in a switch for the Argon remote and the others so it doesn't break the other remotes when installing the addon without the lock file? I believe one should actively choose to use the Argon remote instead of the formerly used one. You could backupcopy the previously used remote config files also?

OK, that idea was good, i got a step closer: under LE12b2 the pipe closes after about one second, under LE11 it stays open (as supposed to be) with the following command:

ffmpeg -loglevel fatal -i http://192.168.178.21:6060/api/zde/live/zdf -vcodec copy -acodec copy -f mpegts pipe:1 >test.ts

i guess TVHeadend-Server executes the above command everytime again once ffmpeg exits/closes the pipe, so that explains the extreme problems and stutter. So the problem lies within ffmpeg as i believed. Question now is why ffmpeg 6.0.2 closes the IPTV stream/pipe after 1 second and ffmpeg 4.4.3 works as expected.

Oh gosh, haven't seen this. Sorry and thanks

i got the Argon Fan working again using your plugin, well done!

Why isn't the plugin in the LibreElec repository?

Hello HarryH ,

i installed your plugin but it killed my MCE-USB Remote. It worked again after i restored my backup. Is there a way to use your plugin but keep my MCE USB Receiver/Remote working?

Sorry for the missing input. All running on Raspi4B.

I set up a separate Raspi4B running LE 11.0.6, same TVHeadend-Server version and same IPTV Streams just as a server for TVHeademd. I set up another Raspi4B with LE12b2 just as TV Headend Client. The HTSP streams served from the LE 11.0.6 run fine.

If i run the same configuration all on LE12b2 with the newer ffmpeg (through TV Headend) the streams are unwatchable: stutter and skipping (even seconds back again and starting over from that point)

So my guess is that the newer ffmpeg Version on LE12b2 has problems in piping. Could your counter-check that?

I'll try to provide debug logs and dig deeper.

Greetings

Hello,

I have a problem concerning my IPTV streams, like with all new major LE releases in the past

I ffmpeg pipe my TV Provider streams through TV Headend and watch them with the TV Headend Plugin in LE. TVHeadend Server is running on the same machine and is using the provided ffmpeg binary from the plugin.

It seems that ffmpeg in LE12 (6.0.1) has problems with the TV provider streams. The streams stutter and are extremely choppy. Under LE11 with the older ffmpeg everything is fine.

Playback via a TVHeadend Client on my smartphone results in choppy/stutter playback too, so it must be the ffmpeg pipe within TVHeadend Server on LE12. DVB-T2 Streams from the same TV Headend Server play fine, both in Kodi and on the Smartphone with the TVH-Client (DVB Streams aren't touched by ffmpeg in any way)

thanks for letting us test the new LE.

I wanted to jump in the beta train and it looked promising at first. But there is a problem concerning my IPTV streams, like with all new major LE releases in the past

I ffmpeg pipe my TV Provider streams through TV Headend and watch them with the TV Headend Plugin in LE. TVHeadend Server is running on the same machine and is using the provided ffmpeg binary from the plugin.

It seems that ffmpeg in LE12 (6.0.1) has problems with the TV provider streams. The streams stutter and are extremely choppy. Under LE11 with the older ffmpeg everything is fine.

Playback via a TVHeadend Client on my smartphone results in choppy/stutter playback too, so it must be the ffmpeg pipe within TVHeadend Server on LE12. DVB-T2 Streams from the same TV Headend Server play fine, both in Kodi and on the Smartphone with the TVH-Client (DVB Streams aren't touched by ffmpeg in any way)

Would you mind adding a ffmpeg plugin with the 4.4.x ffmpeg version as a alternative?

Thanks for the headsup! This will hopefully be fixed before the first official LE12 build will be out.

Thanks, already running nicely on my RPi4