updated DVB-C tuning file for SAT>IP The Netherlands and question

[retrofan]

Hi, here's the updated tuning SAT>IP file for cable operator Ziggo, The Netherlands.
All the other ones can be deleted as they are outdated.
Please update NextPVR with this file with the next release. Thanks!

I also noticed the first frequency (266 MHz) doesn't list the scanned channels. I think it's because an illegal character which NextPVR doesn't ignore.
Can you please add support for adding those channels and ignoring the illegal character?
It looks like a space or something. Then the channels can be added without problems.
Thank you!

See attachment for logfile and tuning file.
Best regards!
 
</service_information>
 
2024-08-01 12:02:50.715               [ERROR][24]      Unexpected error parsing SAT>IP service information: '.', hexadecimal value 0x00, is an invalid character. Line 88, position 19.

[sub]

Thanks for the updated file. I'll include it with the next release.

If you can manage to capture a 1 minute full transport stream from 266Mhz, and put it somewhere like onedrive/googledrive, I'll check what is happening with that character and fix the issue.

[mvallevand]

For tuning support like that you will need to record a full mux for sub to look at. One minute should be fine

To do that you will need ffmpeg 6 or 7 on a remote PC (on Linux use single quotes)

Code:

ffmpeg -rtsp_flags satip_raw -i "rtsp://192.168.178.1:554/?freq=266 sr=6900 msys=dvbc mtype=256qam bw=8 pids=all" -map 0 -c copy -f data -y fullmux.ts

If you SAT>IP box doesn't support pids=all I can't remember what pids you need to add so sub will need to pipe in.

The file would need to be on external file (it will be around 200MB) like GoogleDrive, OneDrive, mega.nz, filetranser.io

Martin

[retrofan]

Thanks for the updated file. I'll include it with the next release.

If you can manage to capture a 1 minute full transport stream from 266Mhz, and put it somewhere like onedrive/googledrive, I'll check what is happening with that character and fix the issue.

Great, thanks!

Sure, no problem :-)

Here it is:
https://www.dropbox.com/scl/fi/neuvmuobz...2q7ue&dl=1

[retrofan]

For tuning support like that you will need to record a full mux for sub to look at.  One minute should be fine

To do that you will need ffmpeg 6 or 7 on a remote PC (on Linux use single quotes)

Code:

ffmpeg -rtsp_flags satip_raw -i "rtsp://192.168.178.1:554/?freq=266 sr=6900 msys=dvbc mtype=256qam bw=8 pids=all" -map 0 -c copy -f data -y fullmux.ts

If you SAT>IP box doesn't support pids=all I can't remember what pids you need to add so sub will need to pipe in.

The file would need to be on external file (it will be around 200MB) like GoogleDrive, OneDrive, mega.nz, filetranser.io

Martin

Yes, you're right, it's about 200MB. I put it on Dropbox and used this program to record all pids (my SAT>IP server does support this):

https://www.dvbviewer.com/griga/TransEdi...indow.html

It's a very nice tool which I always use and it's part of DVBViewer.

[mvallevand]

Thanks for the file using it sub was able to find the issue.  Could I have another frequency to scan to complete the test with an EPG, this one seems to be mainly radio stations with very little OTA guide information.  How much guide data is available from your service?

Martin

[retrofan]

Thanks for the file using it sub was able to find the issue.  Could I have another frequency to scan to complete the test with an EPG, this one seems to be mainly radio stations with very little OTA guide information.  How much guide data is available from your service?

Martin

Hi Martin, yes, ofcourse. Here it is:

https://www.dropbox.com/scl/fi/7qom44bu0...ls7vu&dl=1

Great that sub was able to find the issue!

[retrofan]

Another question about SAT>IP device scanning. As you can see in the files, also the LCN (Logical Channel Number) is included.
Is there a way you guys can add support for LCN so the channelnumbers are the same in NextPVR as with my cable operator?

And it would also be cool if the channelscan can be exported to SAT>IP M3U with those LCN numbers included using the tvg-chno parameter.

Just like this:

#EXTM3U
#EXTINF:-1 tvg-chno="1" tvg-name="NPO 1",NPO 1
rtsp://192.168.178.1:554/?freq=386&msys=dvbc&sr=6900&mtype=256qam&pids=0,16,17,20,2000,2001,2101,2011

By the way, I saw the bw parameter in the SAT>IP urls of NextPVR, but isn't this a parameter for DVB-T and DVB-C2? I'm using DVB-C right now.
https://github.com/catalinii/minisatip/b..._1_2_2.pdf

(page 66 and 68 of the SAT>IP specifictation document)

[mvallevand]

That works not a lot of metadata but certainly there are some, rytek XMLTV is probably better and I expect Schedules Direct would be best.

Note sure why your stations don't have LCN support, sub would need to comment, I am used to seeing that in other DVB based channels. Not sure the bw parameter matters.

For the export I don't see why NextPVR would need to export raw URL's since you can already export the m3u of the NextPVR channels as streaming ts files. Many SAT>IP devices already let you create do that sort of m3u now, but there are few player for it anyway. It also seems counterproductive since a PVR should be in control of the channels it presents, this takes tuners away from PVR and stops things like multrec (multiple recordings on the same mux)

Martin

[retrofan]

Okay, I see, thanks, I see your point!

I will try Rytec XMLTV!

Regarding LCN, could it be because my cable operator uses NIT other instead of Actual NIT? I don't know, I'm guessing :-)