Dvbv5-scan of Astra 28.2

[mvallevand]

Yes I am willing to continue to provide test results and any combination of the hardware I have outlined above should be available to perform these tests.

Great.  Trying to understand the concept of why you are saying the NextPVR 0282.ini fill is outdated I have used my utilities to create conf files from it  (hopefully the format works!)  On Linux these would go in /usr/share/dvb/dvb-s

nextpvr-0282.conf the nextpvr ini in conf format

satforall.ini.conf  your ini converted to conf format 

satforall.extra.conf  your ini entries not in the nextpvr 0282.ini   this is probably the most interesting one for  me since I'd like to see the conf file from it to see the FTA it finds.

satforall.missing.conf nextpvr entries not in your ini file  this is on you didn't have.

0282-27565534.conf file for bouquet 275 region 65534  If you want to give me your bouquet and region I can give you the actual one as defined here https://www.satellite-calculations.com/D...Number.php . It is smaller than the nextpvr one for faster scan since (apparently) not sure how their filters work and the value of it.

The end goal is being able to generate these when needed so they are never stale.

You don't have to scan with NextPVR either just run

dvbv5-scan filename and it creates a file called dvb_channel.conf 

Martin

[satforall]

Just briefly to explain that there are a number what could be termed duplicate channels but these duplicates are in fact regional variations and do offer alternative programming at certain times of the day so I prefer to have them grouped together

Just to get things straight with NPVR in Linux. Do you need a predefined list of muxes for each satellite so NPVR knows what to scan. If not what format would the DVB5-scan command take in order to interrogate the satellite in question Astra 28.2 and yield all the known working muxes and save them to a file.

[mvallevand]

Yes I think I understand the problem you are trying to describe. For scanning right now NextPVR only understands frequencies so yes there will be duplicate channels that users need to untick and it is not automatic.

The goal of this exercise is to filter the number for frequencies scanned. Right now there are

135 on kos in their ini
72 in yours
40 in the one I scrapped.
29 in the bouquet based one.

None of this is ideal and sorry I don't understand how bouquets work well enough to grab all the FTA and do it without scanning. I figure that is what you are asking for from sub.

If this filtering works I can limit it further to the channels the users might want but can't stop the number of frequencies scanned.

Martin

[satforall]

What I can do is carry out a network scan in TVHeadend. All I need do is supply one known working mux to TVHeadend and the network scan will supply the rest. You can then use that list to create your own known active mux list in NPVR for the British Isles/European region on Astra 28.2. IIRC there are 59 muxes at the last count.

[mvallevand]

Ok I can work with that, I can compare it with the active FTA frequencies on Flysat, KOS and Lyngsat. I curious why it is so much bigger

Martin

[satforall]

Don’t forget we have 9 West African muxes which are of no interest to us as they cannot be received within the designated footprint. I’ve just manually counted the active muxes which now totals 56. The rest are muxes carrying UK/European occasional feeds. As I mentioned I will do a TVHeadend network search just to confirm exactly what I’ve outlined here.

[mvallevand]

I do understand that, my filtered list filters for UK and Europe only with FTA.

Martin

[mvallevand]

@satforall I ran my preliminary ini comparer on your original adapter conf files that you posted a few days ago and the differences where only on the ones that were not FTA. (one exception) are you saying you think I should include all the SKY provider mux even when there is no FTA on it?

The FTA exception 11597 was updated Nov 4 after I created it which shows that these lists need to be dynamic.

Code:

FREQUENCY = 11141000
    FREQUENCY = 11426000
    FREQUENCY = 11582000
    FREQUENCY = 11597000*
    FREQUENCY = 11611000
    FREQUENCY = 11626000
    FREQUENCY = 11758000
    FREQUENCY = 11778000
    FREQUENCY = 11856000
    FREQUENCY = 12012000
    FREQUENCY = 12109000
    FREQUENCY = 12187000
    FREQUENCY = 12207000
    FREQUENCY = 12246000
    FREQUENCY = 12265000
    FREQUENCY = 12285000

Martin

[satforall]

As soon as Sub has released the latest NPVR I’ll run a fresh scan of Astra 28.2 and do the same on TVHeadend. I’ll compare muxes between both and verify each mux before compiling any further lists. SES are undertaking quite a bit of satellite reconfiguration at present so I imagine you’ll be updating your list on quite a regular basis.

[mvallevand]

My original goal was to provide a utility to update the source conf file as port of the PostUpdateEPG process.

Note that NextPVR doesn't provide a conf file for Linux so you are stuck with the shit in your distro or on LE from the old TVH GitHub.

Martin