SAT>IP

[sub]

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.

Sorry, yes you're right - I forget that some of the files on my machine live in different places.

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!

From memory I think most of the UK frequencies are DVB-T, and only one or two DVB-T2 frequencies in each transmitter, so probably only having to edit a couple of lines.

[jcjefferies]

Sub

Using Minisatip and my DVB-T2 tuner I created a singe frequency tuning file for a DVB-T2 mux which worked using default syntax but did not find DVB-T2 mux. Is the modified DVB-T2 file supposed to go back in C:\Program Files\NPVR\data\tuning\DVB-T ? I have no idea what the two items are at the end of each line so left them blank. The moment I changed it to the other format there is an error:-

25] Scan Tuning Plan:
[25] - 1
[25] - 1,482166,8,T2,32K,64QAM,,
[25] Unexpected error building tuning string: System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(ReadOnlySpan`1 str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(ReadOnlySpan`1 s, NumberStyles style, NumberFormatInfo info)
at NShared.Recorders.SATIPScanner.GetTuningFromString(String transponderInfo, Int32 frequency, Int32 bandwidth, Int32 sid, Int32 onid, Int32 tsid, Int32 serviceType, Int32 major, Int32 minor, Boolean encrypted)
[25] About to scan:
[25] Unexpected error starting RTSP: System.UriFormatException: Invalid URI: The URI is empty.
at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
at System.Uri..ctor(String uriString)
at NShared.Shim.RTSPHelper.Open(String url, UdpClient existingClient, String& reason)
[25] Failed to start device connection. Scan stopping.

Even removing just the "=1" at the start of the line on a working setup causes an error. Also removing the DVB-T2 data at the end of the line gave an error

At one point I got an Array Error inferring the data was outside the range expected but now cannot remember the syntax of the line I was using.

Will it need an updated version of NextPVR to work with SATPI? It does have a setup web page which may get over the DVB-T2 problem.

Chris

[sub]

Sub

Using Minisatip  and my DVB-T2 tuner I created a singe frequency tuning file for a DVB-T2 mux which worked using default syntax but did not find DVB-T2 mux. Is the modified DVB-T2 file supposed to go back in C:\Program Files\NPVR\data\tuning\DVB-T ? I have no idea what the two items are at the end of each line so left them blank. The moment I changed it to the other format there is an error:-

25] Scan Tuning Plan:
[25]  - 1
[25]  - 1,482166,8,T2,32K,64QAM,,
[25] Unexpected error building tuning string: System.FormatException: Input string was not in a correct format.
  at System.Number.StringToNumber(ReadOnlySpan`1 str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
  at System.Number.ParseInt32(ReadOnlySpan`1 s, NumberStyles style, NumberFormatInfo info)
  at NShared.Recorders.SATIPScanner.GetTuningFromString(String transponderInfo, Int32 frequency, Int32 bandwidth, Int32 sid, Int32 onid, Int32 tsid, Int32 serviceType, Int32 major, Int32 minor, Boolean encrypted)
[25] About to scan:
[25] Unexpected error starting RTSP: System.UriFormatException: Invalid URI: The URI is empty.
  at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
  at System.Uri..ctor(String uriString)
  at NShared.Shim.RTSPHelper.Open(String url, UdpClient existingClient, String& reason)
[25] Failed to start device connection. Scan stopping.

Even removing just the "=1" at the start of the line on a working setup causes an error. Also removing the DVB-T2 data at the end of the line gave an error

At one point I got an Array Error inferring the data was outside the range expected but now cannot remember the syntax of the line I was using.

Can you post the contents of the ini file you've created?

Will it need an updated version of NextPVR to work with SATPI? It does have a setup web page which may get over the DVB-T2 problem.

Yes, as mentioned, SATPI support is fixed for the next release.

I'm pretty sure you'll need to do these same DVB-T2 updates to the ini file before it'll work with SATPI too.

[jcjefferies]

First is the data for the original DVB-T2 mux with the other 8 mux deleted which found just DVB-T channels. Just removing "1," (Not what I originally said) from the start of the line to make it look like the start of German one posted caused an error message like to one posted.

TERTYPE]
1=United Kingdom
2=Central - Ridge Hill 3
[DVB]
0=1
1=1,482166,0,0,8

I think this below was the data used for the scan that failed with the error I sent. Dont think it made any difference if I removed the "0s" at the end. I also added a "." to the frequency so it was in MHZ like the German one.

TERTYPE]
1=United Kingdom
2=Central - Ridge Hill 2
[DVB]
0=1

1=1,482166,8,T2,32K,64QAM,0,0,

Chris

[sub]

Yeah, for T2, that is the wrong format. It needs to be like this:

1=482,8,T2,32K,64QAM,19128,35

These parts are:
1) frequency in MHZ
2) bandwidth (8MHz in UK)
3) T2
4) tmode
5) modulation
6) guard interval
7) fec

[sub]

It looks like this is RidgeHill parameters, so we need to translate these into the ini format

Code:

[C22+ BBC B HD]
        DELIVERY_SYSTEM = DVBT2
        FREQUENCY = 482167000
        BANDWIDTH_HZ = 8000000
        CODE_RATE_HP = 2/3
        CODE_RATE_LP = NONE
        MODULATION = QAM/256
        TRANSMISSION_MODE = 32K
        GUARD_INTERVAL = 1/128
        HIERARCHY = NONE
        STREAM_ID = 0
        INVERSION = AUTO

[sub]

I think it's:

1=482,8,T2,32K,256QAM,1128,23

[jcjefferies]

WOW! Thanks it found the HD channels!!

I will set it up tomorrow for for a full scan of all 9 mux.

I would have tried it earlier but was busy on other things and relying on the email notification the new web site sends so didnt look at NextPVR until this evening. So was surprised to see your three messages. The notifications do seem a bit unreliable!

Thanks again

Chris

[sub]

WOW! Thanks it found the HD channels!!

Great!

[jcjefferies]

The next day I reconfigured the local transmitter ini file on my NPVR V5 Windows server to include the extra DVB-T2 config data required for SAT>IP. I setup SATPI as my SAT>IP server with my DVB-T/T2 tuner and NextPVR now detected it correctly found the DVB-T and DVB-T2 mux and all the channels. So NextPVR now works with SATPI!

Unfortunately shortly afterwards the DVB-T2 tuner stopped working on on Linux via a SAT>IP using Minisatip or SATPI server on three different computers or directly connected to TVheadend! All computers have the required firmware files installed! However the tuner still works correctly when directly connected to my Windows V5 server!!! The spare DVB-T still works on all but its the DVB-T2 that is the problem!!!

I will give up on this for now and revisit again in a week or so!!