SAT>IP

[spudjg1]

With dvb viewer it allows you create an m3u file, and it works as an iptv source. Would this use the same port 554 In the same way as sat ip ?

Ignore that it uses another port when I checked the logs !

[sub]

Sub

While trying to learn about SAT>IP I have yet to get NextPVR fully working with any SAT>IP software. I have given up on TVheadend at least for now and Minisatip almost works but runs my DVB-T2 tuner as a DVB-T tuner and the possible switch to cure that does not seem to work so need to look into that.

Can you send a log showing that DVB-T2 scan? We don't use DVB-T2 here, so there was a bit of guess work, and I may need to tweak things.

So I tried SatPI but scans from NextPVR finds no channels. The writer of the software is usually very quick to reply and asked for a copy of the SATPI logs and also the NextPVR logs covering the scanning period. Before I emailed the logs I saw evidence in the SATPI log that channels were found on the first mux scanned but then things went wrong. He has identified the problem  which he says is caused by NextPVR not using a SessionID as in SATIP spec! He also commented that he was not sure how Minisatip got round this!

Below is his reply :-
I see the problem during the TEARDOWN on 12:02:10 there is no SessionID in the request which according to the SAT>IP specification should be there. This way SatPI is not closing the stream because it cant find it, and gives an "RTSP/1.0 503 Service Unavailable". Later at 12:03:22 the watch-dog kicked in because the connection was closed at "Oct 15 12:02:10 chris-Linux-PC SatPI[981]: RTSP Client 192.168.1.89:51692 Connection closed with fd: 9" and there were no keep-alive message received.

I'll try installing SATPI here and give it a go.

It's worked fine for me with minisatip, and with my physical devices (Digibit R1, and Octopus.NET 8 tuner S2).

[sub]

When you tried SATPI, do you see "[PAT]" or "[PMT]" next to the frequency it's scanning? (indicating it's getting data)

[Reddwarf]

Sub

While trying to learn about SAT>IP I have yet to get NextPVR fully working with any SAT>IP software. I have given up on TVheadend at least for now and Minisatip almost works but runs my DVB-T2 tuner as a DVB-T tuner and the possible switch to cure that does not seem to work so need to look into that.

So I tried SatPI but scans from NextPVR finds no channels. The writer of the software is usually very quick to reply and asked for a copy of the SATPI logs and also the NextPVR logs covering the scanning period. Before I emailed the logs I saw evidence in the SATPI log that channels were found on the first mux scanned but then things went wrong. He has identified the problem  which he says is caused by NextPVR not using a SessionID as in SATIP spec! He also commented that he was not sure how Minisatip got round this!

Below is his reply :-
I see the problem during the TEARDOWN on 12:02:10 there is no SessionID in the request which according to the SAT>IP specification should be there. This way SatPI is not closing the stream because it cant find it, and gives an "RTSP/1.0 503 Service Unavailable". Later at 12:03:22 the watch-dog kicked in because the connection was closed at "Oct 15 12:02:10 chris-Linux-PC SatPI[981]: RTSP Client 192.168.1.89:51692 Connection closed with fd: 9" and there were no keep-alive message received.

Chris

A while back I did some struggeling (is that a word) with minisatip on Linux but gave up in the end. It found channels on my DVB-S tuners but only on DVB-S, NOT DVB-S2, sounds similar to your DVB-T/T2 problem. Also I need decrypting to work and OSCAM seems very complicated to get working on Linux.

[sub]

While trying to learn about SAT>IP I have yet to get NextPVR fully working with any SAT>IP software. I have given up on TVheadend at least for now and Minisatip almost works but runs my DVB-T2 tuner as a DVB-T tuner and the possible switch to cure that does not seem to work so need to look into that.

I think I know what is happening with your DVB-T2 channels. What country/region are you picking for the scan?

So I tried SatPI but scans from NextPVR finds no channels. The writer of the software is usually very quick to reply and asked for a copy of the SATPI logs and also the NextPVR logs covering the scanning period. Before I emailed the logs I saw evidence in the SATPI log that channels were found on the first mux scanned but then things went wrong. He has identified the problem  which he says is caused by NextPVR not using a SessionID as in SATIP spec! He also commented that he was not sure how Minisatip got round this!

Below is his reply :-
I see the problem during the TEARDOWN on 12:02:10 there is no SessionID in the request which according to the SAT>IP specification should be there. This way SatPI is not closing the stream because it cant find it, and gives an "RTSP/1.0 503 Service Unavailable". Later at 12:03:22 the watch-dog kicked in because the connection was closed at "Oct 15 12:02:10 chris-Linux-PC SatPI[981]: RTSP Client 192.168.1.89:51692 Connection closed with fd: 9" and there were no keep-alive message received.

Chris

I've been experimenting with SATPI and seeing weird things, and no channels here. I've emailed the SATPI guy with some questions.

From what I can see in the SATPI logs, it is passing the SessionID on TEARDOWN, so I don't think it's that. One thing I did notice is it's very slow to "addpids". It seems to stop and restart the device, which kind of stuffs things up if it's going to wait a maximum of 10 seconds per frequency, but it's going need to add more than 10 pids, and they're taking over a second per pid. The other SAT>IP servers I've tested add these pretty much instantly.

[sub]

After exchanging a couple of emails with the SATPI guys, I've got NextPVR working with the SATPI server. It did related to the 'addpids' call functioning very slowly with this server.

To get your DVB-T2 working, with SATPI or minisatip, we'll need to copy your tuning file and make a slight tweak to the tuning strings.

[jcjefferies]

Thank Sub.I started playing with SAT>IP as I am thinking of getting a Digibit R1 but the whole experience has been painful!! Its good to hear that that NextPVR works the Digibit R1.

Minisatip is the software nearest to working so will try their forum to find a fix to specify DVB-T2 tuner. Today have been trying TVheadend on LibreElec as it runs as root by default so can use port 554 but NPVR does not see it. However it sometimes takes several reboots to work!! TVH does have options to specify the tuner type,

Chris

[sub]

Here is an example from another user that successfully used DVB-T2 with NextPVR.

Germany-Koeln-T2.ini:

Code:

[TERTYPE]
1=Germany
2=Koeln, Bonn T2

[DVB]
0=6
1=514,8,T2,16K,64QAM,19128,35
2=586,8,T2,16K,64QAM,19128,12
3=594,8,T2,32K,64QAM,116,23
4=626,8,T2,32K,64QAM,116,23
5=650,8,T2,32K,64QAM,116,23
6=538,8,T2,16K,64QAM,19128,35

So basically you need to copy your existing .ini file, from C:\Users\Public\NPVR-Data\Tuning\DVB-T, and edit any DVB-T2 frequencies to be formatted the way it is above. You can leave DVB-T frequencies as-is.

After changing your ini file, I'm pretty sure you'll find the channels in minisatip.

[sub]

The same ini files are used for tuning regular DVB tuners on Windows, where you conveniently never need to worry about the difference between DVB-T and DVB-T2 and the drivers take care of that automatically for you. Unfortunately with SAT>IP you need to modify the file to explicitly tell it which frequencies are DVB-T2.

[jcjefferies]

Thanks Sub

I had not seen your email when I sent my email very late last night!

That is great news that SatPi now works with NextPVR. I did think SATPI was a bit of obscure software as "make" failed with an error when I downloaded it but the writer cured the problem within a few hours. A couple of days ago tried to run SAT>IP software on Raspbian and found SATPI comes pre installed!

I think you quoted the wrong location of the ini files!! Yesterday I deleted all the DVB-T files except my local one and they are in C:\Program Files\NPVR\data\tuning\DVB-T.

The DVB-T2 tuning data format looks quite a bit different to the standard one NextPVR uses ignoring the frequency. I will try the new tuning data later as its a bit early in the day here!

Chris