On Sat, Apr 25, 2009 at 7:32 PM, Goga777 <goga777@xxxxx> wrote:
>> >> And which parameters are the wrong ones?
>> >
>> >
>> > these two parameters are wrong
>> >
>> > Frequency: 18437984 (= 11.95760 GHz) - should be another freq = 12.380
>> > Kind: 0 (0x00) [= DVB-S] - should be dvb-s2
>> >
>> > also, no any information about roll off factor, that's why vdr substituted roll off = auto , cx24116 based cards don't
>> > understand roll off = auto.
>> >
>> > Goga
>> >
>> >
>> > fixed ('00'): 0 (0x00)
>> > Modulation_type: 2 (0x02) [= 8PSK]
>> > Symbol_rate: 2506752 (= 26.4000)
>> > FEC_inner: 2 (0x02) [= 2/3 conv. code rate]
>>
>> Well, if VDR is told this is a DVB-S transponder, while in fact it is
>> DVB-S2, I'm afraid there's nothing it can do about that.
>>
>> Have you tried complaining to the provider?
>
>
> yes, sure.
>
> Answer from provider - "please use our official receivers"
>
> @klaus
>
> could you change VDR behaviour if in the NIT the rolloff is missing - is it possible to substitute roll off = 35 instead
> of roll off = auto ?
It would be buggy to use Rolloff=35%, when the actual rolloff
information is missing.
In fact this is a bug in the driver, that it can't sensibly use the
rolloff information.
With regards to DVB-S2, the rolloff information is present in the
Stream header (MATYPE)
and the driver is supposed to return back the rolloff information from
the stream header.
According to EN300 468, a DVB-S2, NBC stream will not contain any
rolloff information,
but whereas the information is available in the BBHEADER, which the
demodulator is able
to understand.
In fact this is the job of the device driver and hence the reply from
the provider to use their
receiver, There are 2 options, fix the bug in the driver, or use a
compliant device.
What will you do, if you have a narrow transponder, the same way ?
Regards,
Manu
_______________________________________________
vdr mailing list
vdr@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
