SAT>IP DVB-T2 no channels found

[Harune]

Hi,

I'm running a Digital Devices OctopusNet SAT>IP receiver for DVB-T2 on a Panasonic TV via network. This works well for over 5 years now.

Currenty setting up a NextPVR instance. Looking at devices I got 4 DVB-T, 4 sat and 4 DVB-C devices. This is ok since all 4 tuner can receive terrestial, sat and cable signals.

Scanning a DVB-T tuner for channels reports 0 channels found. Running a scan on  OctopusNet revealed 60 channels.

Looking at the logs there are scann requests like

logs/nrecord.log:2025-11-28 11:36:56.657        [DEBUG][17]    About to scan: rtsp://192.168.178.10:554/?freq=490&msys=dvbt&bw=8&pids=0,16,17

I've got an m3u list for VLC that works. For the frequency above it contains 

rtsp://@192.168.178.10/?freq=490.000&bw=8&msys=dvbt2&plp=-1&pids=0,4368,4369,4372,4370,4371,4369
rtsp://@192.168.178.10/?freq=490.000&bw=8&msys=dvbt2&plp=-1&pids=0,4416,4417,4420,4418,4419,4417
rtsp://@192.168.178.10/?freq=490.000&bw=8&msys=dvbt2&plp=-1&pids=0,4400,4401,4404,4402,4403,4401
rtsp://@192.168.178.10/?freq=490.000&bw=8&msys=dvbt2&plp=-1&pids=0,4432,4433,4436,4434,4435,4433

Differ in pids (maybe not a problem since a scan was requested) and msys=dvbt vs msys=dvbt2

Is there any way to change the NextPVR request to msys=dvbt2 ?

Any other ideas how to get NextPVR working with OctopusNet?

Thanks!

[mvallevand]

It looks like the T2 ini that NextPVR needs doesn't match that m3u format and I am not sure there is working plp support.

Can you get more information on the frequencies scanned, checking the SAT>IP spec. this is what I see as an example used by NextPVR

rtsp://192.168.128.5/?freq=754&bw=8&msys=dvbt&tmode=2k&mtype=64qam&gi=132&fec=23&pids=0,16,50,201,301

and so transmission mode, modulation type, guard interval and FEC inner would all be necessary with the current support, assuming multiple plp value aren't involved. I understand you might not understand this so perhaps your OctopusNet device has more information. I can also see this page might have it https://de.wikipedia.org/wiki/Liste_der_...eutschland

Perhaps as a test try this scan file if you are not in Berlin (in Berlin change the 1/4 to 1/8

Code:

[[TERTYPE]
1=Germany
2=DVB-T2 Test

[DVB]
0=1
1=490000,8,T2,8k,16qam,1/4,2/3

Ideally if sub or I could access you SAT>IP tuner from the internet we might be able to help more.

Martin

[Harune]

It looks like the T2 ini that NextPVR needs doesn't match that m3u format and I am not sure there is working plp support. 

Can you get more information on the frequencies scanned, checking the SAT>IP spec. this is what I see as an example used by NextPVR

rtsp://192.168.128.5/?freq=754&bw=8&msys=dvbt&tmode=2k&mtype=64qam&gi=132&fec=23&pids=0,16,50,201,301

and so transmission mode, modulation type, guard interval and FEC inner would all be necessary with the current support, assuming multiple plp value aren't involved.  I understand you might not understand this so perhaps your OctopusNet device has more information.  I can also see this page might have it https://de.wikipedia.org/wiki/Liste_der_...eutschland

Perhaps as a test try this scan file if you are not in Berlin (in Berlin change the 1/4 to 1/8

Code:

[[TERTYPE]
1=Germany
2=DVB-T2 Test

[DVB]
0=1
1=490000,8,T2,8k,16qam,1/4,2/3

Ideally if sub or I could access you SAT>IP tuner from the internet we might be able to help more.

Martin

Well, not sure what you want me to do...

I got a listing out of the devices, two different formats attached.

Not sure how to perform the scan tests, can you please explain?

[mvallevand]

Attachments need to be zipped.

For that test unzip the attached ini file and put it in /opt/nextpvr/system/data/tuning/DVB-T/ and select it for the scan.  Then send the zipped logs.

Martin

[Harune]

It looks like the T2 ini that NextPVR needs doesn't match that m3u format and I am not sure there is working plp support. 

Can you get more information on the frequencies scanned, checking the SAT>IP spec. this is what I see as an example used by NextPVR

rtsp://192.168.128.5/?freq=754&bw=8&msys=dvbt&tmode=2k&mtype=64qam&gi=132&fec=23&pids=0,16,50,201,301

and so transmission mode, modulation type, guard interval and FEC inner would all be necessary with the current support, assuming multiple plp value aren't involved.  I understand you might not understand this so perhaps your OctopusNet device has more information.  I can also see this page might have it https://de.wikipedia.org/wiki/Liste_der_...eutschland

Perhaps as a test try this scan file if you are not in Berlin (in Berlin change the 1/4 to 1/8

Code:

[[TERTYPE]
1=Germany
2=DVB-T2 Test

[DVB]
0=1
1=490000,8,T2,8k,16qam,1/4,2/3

Ideally if sub or I could access you SAT>IP tuner from the internet we might be able to help more.

Martin

Well, not sure what you want me to do...

I got a listing out of the devices, two different formats attached.

Not sure how to perform the scan tests, can you please explain?

Found tuning/DVB-T and created a test ini following https://tvhelfer.de/dvbt2/de/hh :

Code:

[TERTYPE]
1=Germany
2=Test

[DVB]
0=3
1=490,8,T2,16k,64qam,19/128,1/2
2=570,8,T2,16k,64qam,19/128,3/5
3=634,8,T2,16k,64qam,19/128,1/2

in log I now see 

Code:

2025-11-28 19:45:56.254 [DEBUG][18]     About to scan: rtsp://192.168.178.10:554/?freq=490&bw=8&msys=dvbt2&tmode=16k&mtype=64qam&gi=19/128&fec=1/2&pids=0,16,17
2025-11-28 19:46:08.276 [DEBUG][18]     About to scan: rtsp://192.168.178.10:554/?freq=570&bw=8&msys=dvbt2&tmode=16k&mtype=64qam&gi=19/128&fec=3/5&pids=0,16,17
2025-11-28 19:46:21.250 [DEBUG][18]     About to scan: rtsp://192.168.178.10:554/?freq=634&bw=8&msys=dvbt2&tmode=16k&mtype=64qam&gi=19/128&fec=1/2&pids=0,16,17

 
very similar to rtsp lines in m3u but still no channel found

Is there any way to omit tmode, mtype, gi and fec and to add more pids?

[Harune]

Attachments need to be zipped.

The scan lists from device- now zipped

[mvallevand]

Your link is more recent so the change makes sense. T2 is is in Khz not Mhz like the other DVB-T files so that was a good choices too.

No currently there is no way to change what is sent that is why I asked if your SAT>IP server could be opened for sub and I. For the gi and fec I would be tempted to use gi=auto and fec=23 based on this https://github.com/DigitalDevices/octone...scan.c#L86

For the initial scan those pids are fine, they should find all the channels on the frequency eg in theory 490 should find all the ARD-NDR channels each with the correct pids.

Martin

[Harune]

This seems to work

Code:

[DVB]
0=3
1=490,8,T2,auto,64qam,auto,12
2=570,8,T2,auto,64qam,auto,35
3=634,8,T2,auto,64qam,auto,12

but next problems:

- Only 490MHz is scanned for EPG data
- no live tv on uiclient (tuner required for recording error message)

[mvallevand]

That's closer but also this is virgin territory so we'd need to see the logs.

Actually scratch that, although the logs would confirm I think that issue was discussed here https://forums.nextpvr.com/showthread.ph...#pid604038 and this update to NShared.dll https://forums.nextpvr.com/showthread.ph...#pid604286 should continue without the error.

Martin

[mvallevand]

You added another issue, so yes we still need the logs. Basically don't post problems without the zipped logs.

Martin