Hi....
I am glad to be a member in your forum
My suggestions :
1- Real names of the channels
When I'm searching some channels on Hotbird 13E and other Sats doesn't have a real name such as(#1-#2-#3) so I hope to fix this problem.
2- Network search takes so long
I hope to make this search by an option (check box)
so if i don't want to search by NIT ; I can disable that check box
to take into consideration
Thanks.
#3
Hi
how can make network search ??
is it included through Channel Search ,
is it for search all channels or to know any missed freq in Transponders file .
how can make network search ??
is it included through Channel Search ,
is it for search all channels or to know any missed freq in Transponders file .
#4
In fact the Network Information Tables do contain entries for other transponders, that could even get updated on-the-fly.
This way new transponders can be linked in without having to update transponder lists.
First of all this is meant for receivers, that don't get firmware updates automatically.
Of course software solutions can also benefit from this.
NIT reading would then happen as a background task after channel switching, normally lasting just a few seconds and not causing noticeable extra traffic. Not even on a very slow machine, like a stone age Pentium II 500 MHz, used here with DVBsVCR2 years ago, which also used automatic NIT parsing based transponder updates. Did not require full transponder lists this way, just a base package of seed channels, to get started.
NIT parsing can either be used, to just update transponder information, or also be added to a standard procedure for a full scan. In the second case, NIT aided scanning should happen AFTER the list based scan, to automatically include new transponders, even if only being daisy chained to another new one.
Some notes on limitations of this procedure:
There are satellite positions, that contain more than one network.
Means, not even all regular transponders would be found this way, from reading just one transponder's table. That's why this option should at least parse the table after each channel switching to another transponder.
Feeds would not be found this way.
And it's possible, you would be getting doublets of complete transponders, if the software / firmware used a different frequency resolution / rounding procedure than the table transmitted, like by ignoring or rounding up / down the kHz values' last digits.
BTW, this is a very good reason, to never ever compensate LOF offsets by editing the transponder tables. Instead edit the LOF value directly.
NIT scanning should be blocked by the software, if recordings are made or scheduled, to avoid channel database changes within such a period.
This way new transponders can be linked in without having to update transponder lists.
First of all this is meant for receivers, that don't get firmware updates automatically.
Of course software solutions can also benefit from this.
NIT reading would then happen as a background task after channel switching, normally lasting just a few seconds and not causing noticeable extra traffic. Not even on a very slow machine, like a stone age Pentium II 500 MHz, used here with DVBsVCR2 years ago, which also used automatic NIT parsing based transponder updates. Did not require full transponder lists this way, just a base package of seed channels, to get started.
NIT parsing can either be used, to just update transponder information, or also be added to a standard procedure for a full scan. In the second case, NIT aided scanning should happen AFTER the list based scan, to automatically include new transponders, even if only being daisy chained to another new one.
Some notes on limitations of this procedure:
There are satellite positions, that contain more than one network.
Means, not even all regular transponders would be found this way, from reading just one transponder's table. That's why this option should at least parse the table after each channel switching to another transponder.
Feeds would not be found this way.
And it's possible, you would be getting doublets of complete transponders, if the software / firmware used a different frequency resolution / rounding procedure than the table transmitted, like by ignoring or rounding up / down the kHz values' last digits.
BTW, this is a very good reason, to never ever compensate LOF offsets by editing the transponder tables. Instead edit the LOF value directly.
NIT scanning should be blocked by the software, if recordings are made or scheduled, to avoid channel database changes within such a period.
My signature:
Please read here:
On Bug Reports And Other Complaints
and there:
BOARD RULES - READ THIS!
I don't give support by e-mail or PM.
And I will never assist on PayTV hacking.
PM ME FOR THIS AND YOUR ACCOUNT WILL BE DELETED IMMEDIATELY, WITHOUT ANY WARNING!!!
NEVER EVER DARE TO CONTACT ME FOR PRO VERSION ISSUES!
I am not responsible for that.
Check the 'Activation' section.
Please keep it in English here, or Russian in the Russian section, or German in the German section.
I don't read nor write Klingonian or any other language than English and German.
Addressing me personally in any exotic language will be treated as severe insulting! Be warned!!!
1.)AMD Phenom II x4 940, GA-MA770-UD3, 8 GB DDR2-6400. 7 Pro SP1 x64 + XP Pro SP3 x86
DVB-S2: Cynergy S2 USB HD
2.)P4 3200 i865G (F-S Scenic W600pwr) XP Pro SP3
DVB-S: hauppauge WinTV Nexus-S rev. 2.2, driver TT 2.19h, hardware mode
19.2°,13°,28.x°E,30°W, DiSEqC 1.0
Auf Deutsch:
DVB-Cube <<< Das deutsche DVB-Forum >>>
Please read here:
On Bug Reports And Other Complaints
and there:
BOARD RULES - READ THIS!
I don't give support by e-mail or PM.
And I will never assist on PayTV hacking.
PM ME FOR THIS AND YOUR ACCOUNT WILL BE DELETED IMMEDIATELY, WITHOUT ANY WARNING!!!
NEVER EVER DARE TO CONTACT ME FOR PRO VERSION ISSUES!
I am not responsible for that.
Check the 'Activation' section.
Please keep it in English here, or Russian in the Russian section, or German in the German section.
I don't read nor write Klingonian or any other language than English and German.
Addressing me personally in any exotic language will be treated as severe insulting! Be warned!!!
1.)AMD Phenom II x4 940, GA-MA770-UD3, 8 GB DDR2-6400. 7 Pro SP1 x64 + XP Pro SP3 x86
DVB-S2: Cynergy S2 USB HD
2.)P4 3200 i865G (F-S Scenic W600pwr) XP Pro SP3
DVB-S: hauppauge WinTV Nexus-S rev. 2.2, driver TT 2.19h, hardware mode
19.2°,13°,28.x°E,30°W, DiSEqC 1.0
Auf Deutsch:
DVB-Cube <<< Das deutsche DVB-Forum >>>
#5
example, this network freq in 42E :
11962\3333
with receiver box set Network search and make search all .
and with DD search only new freq and it's nice function.
my question is how can use it in ProgDVB ?
simply

11962\3333
with receiver box set Network search and make search all .
and with DD search only new freq and it's nice function.
my question is how can use it in ProgDVB ?
simply
