File Optimization for Satellites & Services xml

[Onga-Onga]

Greetings Coders ...
Please may I explain a method of making the Tuner Control much simpler and easier to edit / understand.

See both scripts here to understand the difference in the two , and then read my comments about the reasons for both .

1 Change code to accept editing of frequencies with the followining structure :
ie ... 12456 , and not have to have 12456000 .

Zapit Conf file to allow just 11300 , and not 11300000 .
The code should automatically add the 000 by default .( if conversion to khz is absolutely necessary in Tuner.so of Fe Control .

Allow zapit conf . to use C-Band LO also , so it can be loaded as
5150 , not 5150000

Then when loading any parameters like 3500 -> 4200 the zapit file will know what LO to use . 3.5 ghz -> 4.2 Ghz

ie ....
diseqcRepeats=0
diseqcType=3
feTimeout=10
lastChannel=1
lastChannelMode=0
lastChannelRadio=1
lastChannelTV=74
lastSatellitePosition=192
lnb0_OffsetHigh=11300 <- KuBAND - Pacific DBS ( my lnb )
lnb0_OffsetLow=05150 <- CBAND - ( my lnb )
lnb1_OffsetHigh=10600 <-KuBand high
lnb1_OffsetLow=09750 <- KuBand low
lnb2_OffsetHigh=10600
lnb2_OffsetLow=09750
lnb3_OffsetHigh=106000
lnb3_OffsetLow=09750
makeRemainingChannelsBouquet=true


=========================
NORMAL / CURRENT ( standard method )
============
-->
- <satellites>
- <sat name="I701-Ku 180E" flags="1" position="180">
<transponder frequency="11060000" symbol_rate="30000000" polarization="1" fec_inner="3" />
<transponder frequency="11514000" symbol_rate="30000000" polarization="1" fec_inner="3" />
<transponder frequency="11610000" symbol_rate="30000000" polarization="0" fec_inner="3" />
</sat>
- <sat name="I701-C 180E" flags="1" position="180">
<transponder frequency="3769000" symbol_rate="20000000" polarization="1" fec_inner="7" />
<transponder frequency="3772000" symbol_rate="4556000" polarization="1" fec_inner="3" />
<transponder frequency="3846000" symbol_rate="5362000"

==============================


This is the structure I would like to see ALL Neutrino follow , and it will allow a much better understanding for all .

an example is here ....... BETTER METHOD - LESS DATA !!
NEW IDEA / ALTERED METHOD ( OPTIMIZED )
-->
- <satellites>
- <sat name="I701-Ku 180E" flags="1" position="180">
<transponder frequency="11060" symbol_rate="30000" polarization="1" fec_inner="3" />
<transponder frequency="11514" symbol_rate="30000" polarization="1" fec_inner="3" />
<transponder frequency="11610" symbol_rate="30000" polarization="0" fec_inner="3" />
</sat>
- <sat name="I701-C 180E" flags="1" position="180">
<transponder frequency="3769" symbol_rate="20000" polarization="1" fec_inner="7" />
<transponder frequency="3772" symbol_rate="4556" polarization="1" fec_inner="3" />
<transponder frequency="3846" symbol_rate="5362"


===========================
The above altered method ...is much prefered / better , because of the following :

1 - Less data to edit .
2 - File size is less ...MUCH LESS !!
3- File read time is faster .
4 - GUI display is simpler for all FREQ , and SYMB data ( 6 less chrs )
5 - More functional understanding .

Neutrino has brilliant features ...lets give it some more !!
Please try to code my ideas , there are much benefits to be gained .

The reading of Satellites file , needs to be able to accept OLD and NEW style satellites file methods . ( as shown above )

Basically , the ONLY major thing that Neutrino is missing is the flexibilty of the Tuner Controls ( LNB Selection , LNB Polarity , LNB Switch , Ttansponder Band detection ...etc )
The coders of Enigma have picked up on this , we just need Neutrino to do it too ....
Over time , we will see a migration to samller Satellites.xml file , Services , Bouquets etc etc , because when you have hundreds of channels loaded / stored , there is a lot of extra 000's not needed .

Any thoughts on this coders ??
Hope ive been helpful .
Cheers Onga-Onga

Best regards
Onga-Onga