SAT>IP

[jcjefferies]

I am thinking of getting a DVB-S2 SAT>IP tuner so to learn about it I am having a play with SAT>IP software to see how it plays with Windows NPVR v5. I have been trying TVheadend, Minisatip & SATPI with DVB-T USB devices and each has advantages and disadvantages!

SATPI is simple to setup but actively refused the connection on port 554 from NPVR so not able to tune!

Minisatip started when I eventually after a long search found a working startup switch combination! A DVB-T2 tuner scanned and found channels but only DVB-T ones! A switch to cure that?

TVheadend seemed easier to setup on LibreElec than Linux but still complicated! It scanned and found channels but NPVR could not detect the channels and was not able to scan. So many menu options!

1) Does NPVR search for SAT>IP servers on both ports 554 & 9983?
2) With TVheadend should NPVR detect the channels found by a TVH scan or should it be empty and let NPVR scan?


Chris

[sub]

1) Does NPVR search for SAT>IP servers on both ports 554 & 9983?

No - it currently only tries to use 554. I'd not come across a SAT>IP device using anything other than 554, until someone mentioned one a few days ago.

2) With TVheadend should NPVR detect the channels found by a TVH scan or should it be empty and let NPVR scan?

I'm not sure what you mean here. NextPVR doesn't know anything about TVHeadend. It does it's own scan of the device. ie, works it's way through each frequencies, looking for signals, finding channels etc.

[jcjefferies]

Under Linux by default TVheadend runs the SATIP server on port 8893 even if you set it to 554 in the web setup and tells you its done that in the logs. There is a setting in /etc/default/tvheadend to set it to run as root.

When NPVR detects a TVheadend SATIP server which I had earlier setup and scanned for channels I was assuming that NPVR wanted to copy the channels over so now know that is not what it wanted to do.

I have not been able to get the Linux version of TVH SATIP server to use port 554 even following instructions posted to change the settings!! However the LibreElec TVH add-on says it is running on port 554 in the log when you activate the server by default!

Chris

[sub]

I didn't even know that TVHeadend could be a SATIP server. I've mainly used physical SAT>IP devices, but have also used minisatip.

If you can supply your logs showing NextPVR starting up, i'll try to add support for port 8893.

When NPVR detects a TVheadend SATIP server which I had earlier setup and scanned for channels I was assuming that NPVR wanted to copy the channels over so now know that is not what it wanted to do

No, it doesn't used a channel list that TVHeadend scanned earlier. It always scans for it's own channels.

[spudjg1]

I'm having this issue, I'm not able to scan sat ip. I get no search results when useing v5, I use dvb viewer to supply the source for dvb s and dvb t useing port 544.

[jcjefferies]

What I have learnt about SAT>IP in the last week or so:-

NextPVR only searches for SAT>IP on port 554!

Under Linux if you want to use the default SAT>IP server port 554 you MUST start the it as root. Otherwise the server will refuse to start or default to a high port number.

Dont use the SAT>IP server built into TVheadend! It dosnt have a good reputation! Even though the logs may say the server started the tuner is probably not visible on the network!

TVheadend does have a SAT>IP client useful for faultfinding. In the web menu select :- "Configuration > DVB Inputs > TV Adaptors" for info on available tuners, local and SAT>IP. You may have to select :- "Configuration > General > SAT>IP Server > Discover SAT>IP servers" to update the list! I may be wrong but I seem to remember that it displays the port number if 554 is not used.

LibreElec has add-ons available from Minisatip and TVheadend.

Chris

[sub]

I'm having this issue, I'm not able to scan sat ip. I get  no search results when useing v5, I use dvb viewer to supply the source for dvb s and dvb t useing port 544.

Wait, 544 or 554? (could just be a typo - just trying to determine if there is another port number in the mix)

[spudjg1]

I'm having this issue, I'm not able to scan sat ip. I get  no search results when useing v5, I use dvb viewer to supply the source for dvb s and dvb t useing port 544.

I'm having this issue, I'm not able to scan sat ip. I get  no search results when useing v5, I use dvb viewer to supply the source for dvb s and dvb t useing port 544.

Wait, 544 or 554? (could just be a typo - just trying to determine if there is another port number in the mix)

Sorry it was just a typo, it uses port 554

[jcjefferies]

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

[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 ?