Using NextPVR instead of TVHheadend this is a piece of cake, no XMLTV the JSON data is totally integrated using the username and password you were likely using with EPG123 and you get the meta art too.
Posts by emveepee
-
-
If LibreElec is a good thing, then it should have a working pvr manager. Or an option on how to install it.
Ok you have the log info. so here are the notes on configuring it https://github.com/kodi-pvr/pvr.iptvsimple Again the addon is platform agnostic so support for configuring it after download would be on the Kodi forum
-
Thank goodness. Mainly just poking the thread for awareness before users start trying to update old BIOSes.
-
This isn't the support forum for pvr.iptvsimple that would be on the Kodi forum. On top of that the OP didn't provide logs just a useless snippet.
Martin
-
Kodi is still only alpha and alpha 1 was released less than six months. The date really is a team Kodi decision anyway.
That being said I find Piers quite stable and it does what I need. The labels alpha and beta can be misleading.
-
I'm familiar with German TV. The problem might be the data during the switch to regional program. Post a log from that time...
This log (on Windows)
is from NextPVR backend playing the sample that DeltaMikeCharlie linked but I can do LE if you think it is different I can repost. Thinking about the network tuner I use doesn't do PID filtering so I'd have to manually add the pids base on different scan times.External Content pastebin.comContent embedded from external sources will not be displayed without your consent.Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
The sample changes mpeg ts programs about 12 minutes in, but Kodi did pick up the change and continue.
```2026-01-09 21:27:29.387 T:10292 info <general>: Opening stream: 0 source: 256
2026-01-09 21:27:29.387 T:10292 info <general>: Opening stream: 1 source: 256
2026-01-09 21:27:29.387 T:10292 info <general>: Opening stream: 3 source: 256
...
2026-01-09 21:39:39.480 T:10292 info <general>: Opening stream: 6 source: 256
2026-01-09 21:39:39.480 T:10292 info <general>: Opening stream: 7 source: 256
2026-01-09 21:39:39.480 T:10292 info <general>: Opening stream: 8 source: 256 -
If netboot is working won't you have logs on your nfs drive to share even if ssh doesn't work?
-
I then hacked the package.mk file to point to file:///path/to/file for the files that I had manually downloaded, but the LE build system did not recognise the 'file:' protocol.
To enable file: protocol I had this help RE: Kodi Crashes after Next-PVR installation
-
Recently HiassofT added libx264 to the external ffmpeg I wonder if the same thing has to be done within Kodi or if that is even possible with DRM Prime
It's not transcoding though since the source is already h264 so I wonder if it something else. nosen if you enabled subtitles in the plugin does turning them off help?
-
-
Cleaning up I found an old Vontar KK RK3566 box that I forgot about and searched and found a random-ish link that has a working Armbian 22.4 (but I didn't put it on the LAN) While it boots I see a firefly bootloader and it says station-m2 but the "official" m2 Armbian doesn't load
Is there anything in this Armbian that might help identify what is needed to boot or build this on LE? Here is dmesgif it helpsExternal Content pastebin.comContent embedded from external sources will not be displayed without your consent.Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy. -
I actually submitted a PR for a addon which doesn't need a script using this syntax
python -m zipfile --extract source.zip directory
However I feel a utf-8 unzip would probably help others extracting downloads etc.
-
Unless I am missing something the busybox unzip does not support utf-8 filenames. Could it be updated or configured for utf-8 or would a replacement be available?
Code
Display Moreunzip -l /storage/recordings/NPVR.zip | grep Austria 1194 12-29-2019 06:33 data/tuning/DVB-T/Austria - All Regions.ini 1016 12-29-2019 06:33 data/tuning/DVB-T/Austria - Alle Regionen.ini 140 12-29-2019 06:33 data/tuning/DVB-T/Austria - Burgenland.ini 138 12-29-2019 06:33 data/tuning/DVB-T/Austria - K▒rnten.ini 219 12-29-2019 06:33 data/tuning/DVB-T/Austria - Nieder▒sterreich.ini 163 12-29-2019 06:33 data/tuning/DVB-T/Austria - Ober▒sterreich.ini 120 12-29-2019 06:33 data/tuning/DVB-T/Austria - Salzburg.ini 158 12-29-2019 06:33 data/tuning/DVB-T/Austria - Steiermark.ini 171 12-29-2019 06:33 data/tuning/DVB-T/Austria - Tirol.ini 122 12-29-2019 06:33 data/tuning/DVB-T/Austria - Vorarlberg.ini 80 12-29-2019 06:33 data/tuning/DVB-T/Austria - Wien.inivs
Code
Display More7z l /storage/recordings/NPVR.zip | grep Austria 2019-12-28 13:33:20 ....A 1194 384 data/tuning/DVB-T/Austria - All Regions.ini 2019-12-28 13:33:20 ....A 1016 337 data/tuning/DVB-T/Austria - Alle Regionen.ini 2019-12-28 13:33:20 ....A 140 97 data/tuning/DVB-T/Austria - Burgenland.ini 2019-12-28 13:33:20 ....A 138 95 data/tuning/DVB-T/Austria - Kärnten.ini 2019-12-28 13:33:20 ....A 219 129 data/tuning/DVB-T/Austria - Niederösterreich.ini 2019-12-28 13:33:20 ....A 163 111 data/tuning/DVB-T/Austria - Oberösterreich.ini 2019-12-28 13:33:20 ....A 120 87 data/tuning/DVB-T/Austria - Salzburg.ini 2019-12-28 13:33:20 ....A 158 105 data/tuning/DVB-T/Austria - Steiermark.ini 2019-12-28 13:33:20 ....A 171 104 data/tuning/DVB-T/Austria - Tirol.ini 2019-12-28 13:33:20 ....A 122 87 data/tuning/DVB-T/Austria - Vorarlberg.ini 2019-12-28 13:33:20 ....A 80 64 data/tuning/DVB-T/Austria - Wien.ini -
For a router PC with no reference to a GPU I'd wait for more information.
-
Doesn't this https://github.com/LibreELEC/Libr…/package.mk#L41 mean that the libx264 and libx265 are only enabled for x86_64?
I'd like to see it enabled for the RK35* and the RPi5 if possible. Here in North America OTA is largely mpeg2video and we can't play that back in NextPVR's browser. Even if it can't do 1x transcoding some users still transcode to h264 mp4 in parallel with the recordings.
-
That is what I tried
orange:~ # /storage/.kodi/addons/tools.ffmpeg-tools/bin/ffmpeg -hide_banner -decoders | grep 264
VFS..D h264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
V..... h264_v4l2m2m V4L2 mem2mem H.264 decoder wrapper (codec h264)
orange:~ # /storage/.kodi/addons/tools.ffmpeg-tools/bin/ffmpeg -hide_banner -encoders | grep 264
V..... h264_v4l2m2m V4L2 mem2mem H.264 encoder wrapper (codec h264) -
The ffmpegx add-on provides an ffmpeg binary wth h264 support (not sure about h265). Hardware encoding is still some way off as the kernel is still missing a defined uAPI for V4L2 encoding so there's a choreographed dance between kernel, specs, and userspace apps like gstreamer and ffmpeg to pull off.
Service.nextpvr installs ffmpeg-tools and I tried to find ffmpegx and couldn't. I installed TVH too but couldn't find it in .Kodi. How do I find it?
I did try to use -f v4l and thought it was my lack of understanding causing the missing ioctl messages. -