LibreElec file locations

[jcjefferies]

I had already found that DVB-S "Scan Channels" is looking in /storage/.kodi/service.nextpvr/nextpvr.bin/data/tuning/DVB-S for tuning files and not in dtv-scan-tables. The DVB-T tuner seemed to be working correctly and looking in dtv-scan-tables/dvb-t for scans.

I didnt know that SAT>IP tuner would be different to an ordinary tuner as they behave the same under Windows!

I have been experimenting with file formats in the directory but at the moment I get an error or nothing happens!!

[sub]

I had already found that DVB-S "Scan Channels" is looking in /storage/.kodi/service.nextpvr/nextpvr.bin/data/tuning/DVB-S for tuning files and not in dtv-scan-tables. The DVB-T tuner seemed to be working correctly and looking in dtv-scan-tables/dvb-t for scans.

I didnt know that SAT>IP tuner would be different to an ordinary tuner as they behave the same under Windows!

On Windows, everything uses the .ini files included with NextPVR.

On Linux, physical USB/PCI/PCIe tuners use dtv-scan-tables (since they're based on libdvbv5, and it requires this format of file). SAT>IP uses the ini files that are included with NextPVR.

I have been experimenting with file formats in the directory but at the moment I get an error or nothing happens!!

If you want to post the logs, I can take a look.

[mvallevand]

No need to experiment with formats your Windows ini file should work in Linux.

I always get burned when I don't ask for logs, it would have bee so clear much earlier.

Martin

[jcjefferies]

It was only yesterday that I understood that SAT>IP tuners use different tuning files under Linux to other tuners!

So a clean install of NextPVR server on LibreElec 10 Nightly as I edited and moved some of the tuning files.

Enclosed are the logs. 

At 12:30:45 the 28.2 file is selected and lists 109 transponders then error as it tries to scan first transponder.

Chris

[mvallevand]

That could be me. What do you have in the port settings in the Kodi GUI settings page? I had to make a change because in testing I had to override the port for the guy testing it and I only tested non standard ports.

Martin

[jcjefferies]

I am just off out for a while but had a quick look!

Do you mean the SAT>IP RTSP port set to 554?

If not I need more details where to look!

Chris

[mvallevand]

Yes if it says that then there could be an issue, or maybe you need to restart the service (disable/enable) The NextPVR logs don't show it reading the variable but maybe that is because it is empty.

If it fails after the restart edit the startup file

nano /storage/.kodi/addons/service.nextpvr/bin/nextpvr.start

and change

export SATIP_RTSP_PORT=$satiprtsp

to

export SATIP_RTSP_PORT=554

I will do some testing here too.

Martin

[mvallevand]

The LE script bug is a little bit tricky. I would

- delete the SAT>IP device from NextPVR web (hold control) since NextPVR saves the original port with the device.
- disable the NextPVR service in Kodi.
- continue into Configure and hit OK
- enable the service

There's a bug in NextPVR too since it doesn't delete the deleted devices from the SATIP_RECORDER table but I don't think that will impact this.

Martin

[jcjefferies]

Thanks Martin that seems to have cured the problem! I just did a scan at 28.2 and it found 648 channels but around 200 of those are encrypted plus there are another 200 encrypted it did not find.
Tomorrow I will try my stripped down scan file used on the Windows NextPVR server with only 24 transponders instead of about 110!

Chris

[mvallevand]

I've got an updated zip file that fixes the default port problem in the addon and I submitted it to LE. If you want to test it before it is released let me know.

Martin