Thanks! Will the updated rpi-tools come to LibreElec Updates?
Posts by ApexDE
-
-
there is currently no other solution than compiling the ffmpeg plugin yourself. You need to set up a LibreElec Dev System for that, change a config file and have some spare hours CPU time
If you want to do that i can give you the hints on which screws you need to work to brew ffmpeg 4.4.4 which is working.
-
no, i don't have or use a argon remote.
The case has ONE green led which lights up when powered on and flashes on sd-card access. I first thought it would annoy me but it turned out that it does not it doesn't shine very light in a dark room, so it is ok for me.
-
Thanks for the infos HarryH
so, if i add a NVMe SSD to the Argon case it will be booted by default? (over the microSD being in place?)
Maybe you built in a option in your addon to check if these settings are active or even to change the boot order in the addon?
-
hello HarryH , i finally made the jump to a Raspi5 and your plugin is working fine on the Argon40 V3 case with M2-NVMe extensionboard too
speaking of NVMe: i am currently using the Raspi5 with a SD-Card. I plan to upgrade to a NVMe SSD. Do you know how what i need to add to config.txt to make it boot from the SSD? The argon scripts don't run on LibreElec i suppose?
-
i would REALLY appreciate this. This Plugin needs to be in official repo!
-
The EOF Bug of ffmpeg 6.0.1 has been reported/documented by another user now. So i am not the only one having problems.
ffmpeg 6: HLS sessions don't work (EOF) · Issue #25131 · xbmc/xbmcBug report Describe the bug ffmpeg doesn't provide a continuous stream - the playback stops after a few seconds. Expected Behavior The playback doesn't stop…github.comMaybe you can provide an official Addon with 4.4.4 static until it is fixed / update for 6.x is available?
-
Setting up a seperate RPi for some "legacy things" (e.g. ffmpeg 4.x) seems to be a good idea. I did it because ffmpeg 6.x on LE12 doesn't handle my IPTV streams correctly. No idea why. A separate RPi with LE11.0.6 serves IPTV via TVHeadend-Server for now.
-
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
-
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?
Code
Display MoreOutput #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?