Le mercredi 12 novembre 2008 13:08:44 Alex Betis, vous avez écrit : > > 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. It's specified in Satellite Descriptor: modulation_system==1, =>S2 modulation_system==0, =>S -- Christophe Thommeret
Attachment:
satDesc.jpeg
Description: JPEG image
_______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
