SAT>IP problems

[jcjefferies]

Using NextPVR V5 I have not been able to get SAT>IP to scan for channels correctly. I started off several months ago using Minisatip with a DVB-T tuner and TVheadend and TVMosaic and NextPVR V4 found all DVB-T channels but V5 only found channels on 1 or sometimes 2 MUX. 

I just bought a Digibit R1 SAT>IP DVB-S2 tuner and enabled just tuner 1 for testing. TVheadend, TVMosaic and NextPVR V4 scan all the specified transponders and find around the expected number of channels. However NextPVR V5 seems to find channels on around 1 in 4 transponders. A very noticeable thing is that while V5 is scanning using Tuner 1 all 4 tuner lights on the Digibit R1 come on and occasionally one goes out although Tuner 1 is the only one enabled. Each later scan seems to find fewer MUX/Transponders.

Enclosed are logs of a scan starting 11:15 of 49 Free To Air Transponders at 28.2E by the Digibit R1 and a later scan by Minisatip with DVB-T tuner starting 13:38 of 9 local MUX (3 DVB-T2) but only finds channels on one MUX. I get similar results using two other computers.

All the Minisatip channels were watchable on other devices. The Digibit R1 satellite receiver is working correctly as when using Kodi with TVheadend and TVheadend client add-ons it becomes an easy to use Free To Air satellite receiver especially if you select your local regional setting.

[attachment=569][attachment=570]

[sub]

SAT>IP in v5 is entirely new code, since it needed to be portable to different platforms and the v4 code wasn't (needed directshow etc). This new code is only relatively lightly tested, in that only a few SAT>IP users have given any reports, so bugs are definitely a possibility. I'm happy to work through any issues as quickly as I can though.

I've got a Digibit R1 SAT>IP here. As a first step, let me find it, and give that a go, to check this tuner lights thing.

[sub]

When you power up your Digibit R1, does the network light come on, or does that only happen later when you try to use the network?

I'm wondering if my device has died. I can't seem to see it or connect to it, like the networking isn't working. The power light comes on, but the network light never does, even though I've tried several different network cables.

[jcjefferies]

Thanks Sub

At power on I have the red light then after about 30 seconds the network light comes on. No tuner lights until a particular tuner is accessed except as I mentioned V5 lights up all 4 tuner lights!! As I have only had the Digibit R1 for less than a week so am no expert on the device but did get it working within a couple of hours with the help an English translation of the handbook!

I seem to be getting similar problems with Minisatip and DVB-T as I am with Digibit R1 and DVB-S so if you cannot get your Digibit R1 working perhaps testing with Minisatip would help find some of the problem. Going back several months I started off using Satpi and the writer of that software I remember identified a problem with V5 SAT>IP. However I found that Minisatip seemed to work a little better with NextPVR V5 but not good enough to be usable. I am currently running Minisatip as a Kodi add-on on one of my RPi3 NextPVR clients.

I was going to send the Minisatip logs to their forum but it took many weeks and several tries to get my account activated so forgot about it! If you think it would help I can send the Minisatip logs when used with V5 to the Minisatip forum.

Chris

[tredman]

Happy to help with any testing, I also have a digibit R1 which shows the same problem (only picks up 90 channels out of 1000 found using tvheadend).

I have previously used minisatip on the digibit in the past, will boot it up and see if it makes any diffference.

[sub]

Unfortunately I think my digibit R1 has died. I just checked with mu DD Octopus NET S2/S, and I'm still getting all the channels I'd expect to get. You guys will have to give me more info, so I can work through it why it isn't working for you.

Lets focus on one specific frequency and why it's not getting channels. jcjefferies, can you tell me a frequency that should find channels, but didn't in your scan, so I can narrow down where I'm looking in your R1 logs above?

tredman, it'd be good if you could post your logs too, and also let me know a frequency (it doesn't have to be the same frequency as jcjefferies)

[jcjefferies]

OK. I cannot remember the details of the scan in that log file so will do a new simple one. I will create an ini file with just 10 satellite frequencies so less log to look at and will note what goes on and get back in a short while!

Chris

[sub]

I will create an ini file with just 10 satellite frequencies so less log to look at and will note what goes on and get back in a short while!

Cool - thanks.

[jcjefferies]

28.2E has 109 transponders and I was using a Free To Air sub set  ini I created with only 49 transponders but for this test have made an ini using the first 10 frequencies which should give 2 or possibly 3 successful scans from previous experience.

Enclosed are 2 logs. The one timed at 1905 had channels on 3 transponders 10714, 10847 & 10906. Second scan times at 1916 only found channels on 10714. In general the first transponder is usually successful.

If the letters [PAT] [PMT] [SDT] [BAT] appear you know the scan of that transponder is successful. However sometimes you see just [PAT] [PMT] so you know there was a problem and no channels were added from that transponder.

Let me know if you would like a similar one for a DVB-T scan with Minisatip.

[attachment=579][attachment=580]

[sub]

It looks like it may be to do with these errors:

2020-01-26 19:15:45.235 [DEBUG][5] About to scan: rtsp://192.168.1.95:554/?src=1&freq=10936&sr=22000&pol=v&fec=56&msys=dvbs&mtype=qpsk&pids=0,16,17,18
2020-01-26 19:15:45.263 [ERROR][5] unexpected end of stream
2020-01-26 19:15:45.265 [ERROR][5] Unexpected error starting RTSP: System.IO.IOException: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine..
---> System.Net.Sockets.SocketException (10053): An established connection was aborted by the software in your host machine.
--- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.Read(Span`1 buffer)
at System.Net.Sockets.NetworkStream.ReadByte()
at NShared.Shim.RTSPHelper.Send(String message, String[] headers)
at NShared.Shim.RTSPHelper.Open(String url, UdpClient existingClient, String& reason)

I'm just checking the code to see if I can find a reason.