On Wed, Nov 12, 2008 at 1:24 PM, BOUWSMA Barry <freebeer.bouwsma@xxxxxxxxx> wrote:
Howdy, this is probably a stupid question, as I neither
have DVB-S2 hardware nor have attempted to use anything
but a rather hacked scan from dvb-apps, but...
(implicitly -> explicitly?)
On Wed, 12 Nov 2008, Alex Betis wrote:
> DVB-S2 by specifying S1 or S2 in freq file, also if you implicitly specify
> QPSK in frequency file the utility will not scan DVB-S2, same logic also for
> 8PSK that will scan only DVB-S2 and will not try to scan DVB-S.
Oh man, I'll probably never remember the difference :)
I meant explicitly in that case.
I can see the logic for 8PSK=>DVB-S2, but as far as I
can see, QPSK does not imply purely DVB-S...
NIT result: 12324000 V 29500000 pos 28.2E FEC 3/4 DVB-S2 QPSK
one of eight such transponders, based on parsing the NIT
tables. Also, a note from my inital 19E2 scan file to
remind me why it failed:
S 11914500 h 27500 ## DVB-S2 QPSK (0x05)
May be no longer up-to-date.
Google search shows that you're right about it, thanks for pointing on that.
I'll leave only 8PSK => DVB-S2 binding. People who want to insist on DVB-S only scanning will have to specify S1 in their frequency file.
I'll probably add also a switch to block S2 scanning at all for those who don't have S2 compatable card.
BTW, you give here example of NIT parsing, do you know the format of the message and what field specifies that the delivery system is DVB-S2? scan utility code doesn't parse it, so I just add both DVB-S and DVB-S2 scans for newly added transponder from NITmessage.
Of course, if I'm misunderstanding, or failing to grasp
something obvious if I actually laid my hands on the
code, please feel free to slap me hard and tell me to
shove off.
thanks
barry bouwsma
_______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
