Posts by emveepee

The assumption being is the remote web configuration is done on NextPVR or TVHeadend on any browser. That configuration part wasn't made clear earlier when I said "install"

That's unnecessary, there is no more effort required loading NextPVR then TVHeadend. You may not have set the tuner up in the server. certainly, pvr.nextpvr will not load until the server is running. If you want help you can go to the NextPVR forums and we can help you further https://forums.nextpvr.com

Just getting the device installed above is just the first step. You still need to pick your scan file, tune your device and assuming the signal is good, pick your channels and set up the EPG.

Martin

You could also install NextPVR and pvr.nextpvr should also work with it.

Another option is to test with dvbv5-scan to see if your tuner scans channels independently from the backend.

You can find TVHeadend, NextPVR and VDR backends bundled with LE. Team LibreELEC promote TVHeadend, but there is also good dedicated support for NextPVR at https://forums.nextpvr.com/ if you need help.

CoreELEC did post some wiki help for TVHeadend https://wiki.coreelec.org/coreelec:tvheadend and NextPVR https://wiki.coreelec.org/coreelec:nextpvr but the instructions would be the same.

Instead of TVHeadend perhaps try NextPVR as it can also be installed on LE. It will use the same /dev/dvb tuners as TVHeadend. Schedules Direct integration is built in and fairly easy to configure. You will also get the meta art from SD in Kodi.

If you do want to this I would recommend adding you Schedules Direct account first. Then do the scan on the first tuner, update the EPG when prompted and then make sure that everything works. Afterward scan the second tuner and copy.

Note if you are testing setup with the web browser and not Kodi on an Arm device like the RP4 they are not fast enough to transcode North American OTA in real time so video transcoding is disabled LE/CE. Testing in Kodi you will get video. You could enable video transcoding in the server settings to see what I mean.

Try updating advancedsettings.xml https://kodi.wiki/view/Advancedsettings.xml#videoextensions and adding .tsv as a valid video extention. Then ffmpeg will decide if it can play it or not. If it fails upload the logs.

Quote from Noscolibre

Hello, thanks both of you for your reply.

What is backend

Thanks for your time and effort.

Many PVR clients need a backend to do tuning, scheduling, EPG and recording. Please read the Kodi wiki https://kodi.wiki/view/PVR/Backends for more information.

TVHeadend, NextPVR and VDR backends can be installed on LibreELEC as addons. Here are some CoreELEC documentation links on setting up TVHeadend https://wiki.coreelec.org/coreelec:tvheadend and NextPVR https://wiki.coreelec.org/coreelec:nextpvr. LE will be similar.

Newer model S905W2 devices which work with CoreElec are around $30 delivered. I leave the CE vs LE debate to others.

Martin

If you have the backend for NextPVR installed remotely or on the LE itself upload the LE debug log and I can have a look. The NextPVR client won't work without a backend otherwise there are no issues with 11.0.3.

Martin

Quote from jchaven

I did not. Since this was a new box and I'm lazy I decided to just try a nightly and it worked.

I was going to try your work-around on a stable if the nightly did not work.O

OK, maybe I misunderstood, I thought you said BT wasn't working.

jchaven did you try my workaround from the post just before yours?

I just got a cheap N100 Chuwi box and wifi seems to work on the nightly (I am using the 2.5G port) but the BT firmware seems to be missing.

Aug 03 18:58:45 LibreELEC kernel: Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0040-1050.sfi (-2)

In the Ubuntu link above someone noted renaming a couple of files in /usr/lib/firmware/intel/ Is there are way to do this in LE?

Edit: I figured it out, the link above has a different name for the BT firmware this worked

ls -lt .config/firmware/intel/

lrwxrwxrwx 1 root root 41 Aug 3 20:12 ibt-0040-1050.ddc -> /usr/lib/firmware/intel/ibt-1040-4150.ddc

lrwxrwxrwx 1 root root 41 Aug 3 20:12 ibt-0040-1050.sfi -> /usr/lib/firmware/intel/ibt-1040-4150.sfi

It identifies as the other BT firmware but otherwise seems ok until the proper firmware is available

Bus 003 Device 002: ID 8087:0026 Intel Corp. AX201 Bluetooth

Quote from donbrew

Soo, I use zap2xml.pl as a stand alone on my Linux entertainment server running by cron and using tv_grab_file to import into tvheadend, NextPVR can just import the xmltv file.

Several months ago I updated the Kodi zap2epg addon to work with NextPVR which works well with Kodi or from the command line. If you want to try it post on the NextPVR forum. It is a little easier then the perl script.

After deleting addons and deleting package cache I am pretty sure there is a Kodi bug that requires you to restart Kodi.

It is failing in CE and Window too on Omega. The SeekTime error makes me suspect it is the issue on seek with ffmpeg 6 https://github.com/xbmc/xbmc/issues/23199 since the faulty UpdateCurrentPTS() is being called.

Adding a rule to play ogg files with the VideoPlayer also works it doesn't try to seek on startup.

Martin

Thanks for your help so far. It will be the same file anyway so figure on 2 or 3 weeks for LE12 and much longer for LE11. You don't have to wait for the addon update, since there is an option in settings to pull the latest update once 6.1.4 is available.

ghtester let me know if you want to try a pre-release update to one file that should address the server-side issue with the EPG character set and also an issue initiating a parameter for the dvb sub-system used in changing channels. I can provde a link with more details.

If not, this update will be included 6.1.4 which will be released hopefully this coming weekend but it takes longer to trickle down to LE so you would probably need a manual update.

Thanks again for the full mux files, they were of great help.

No problem. The reason I was asking was to determine if you saw the same thing sub and I did and that is one mux only scanning was working and the problem for you was changing mux as your earlier logs indicated. The two scans I did yesterday seemed pretty complete to Saturday and beyond https://imgur.com/a/yYmwtYm so sub can continue to look at that and not a data issue.