Re: VDR's UpdateChannels destroys channel information

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 21.03.2013 14:07, Teemu Suikki wrote:
A bit more into this..

I tried dvbsnooping different satellites, I noticed some difference.

This is from Thor, 1.0W:


-----------------------
     Transport_stream_ID: 4 (0x0004)
     Original_network_ID: 70 (0x0046)  [= 1 degree W | Telenor]
     reserved_1: 15 (0x0f)
     Transport_descriptor_length: 191 (0x00bf)

             DVB-DescriptorTag: 67 (0x43)  [=
satellite_delivery_system_descriptor]
             descriptor_length: 11 (0x0b)
             Frequency: 17967360 (=  11.22900 GHz)
             Orbital_position: 16 (=   1.0)
             West_East_flag: 0 (0x00)  [= WEST]
             Polarisation: 0 (0x00)  [= linear - horizontal]
             Kind: 0 (0x00)  [= DVB-S]
             fixed ('00'): 0 (0x00)
             Modulation_type: 1 (0x01)  [= QPSK]
             Symbol_rate: 2379776 (=  24.5000)
             FEC_inner: 5 (0x05)  [= 7/8 conv. code rate]

             DVB-DescriptorTag: 65 (0x41)  [= service_list_descriptor]
             descriptor_length: 30 (0x1e)
                service_ID: 418 (0x01a2)[ --> refers to PMT program_number]
                service_type: 1 (0x01)  [= digital television service]

                (other sid's follow, cut away for clarity)
----------------------------

But this "faulty" transponder in S13E:

----------------------------
    Transport_stream_ID: 7500 (0x1d4c)
     Original_network_ID: 64511 (0xfbff)  [= Sky Italia | Sky Italia Spa.]
     reserved_1: 15 (0x0f)
     Transport_descriptor_length: 54 (0x0036)

             DVB-DescriptorTag: 65 (0x41)  [= service_list_descriptor]
             descriptor_length: 39 (0x27)
                service_ID: 4117 (0x1015)[ --> refers to PMT program_number]
                service_type: 25 (0x19)  [= advanced codec HD digital
television service]

                (other sid's follow, cut away for clarity)

             DVB-DescriptorTag: 67 (0x43)  [=
satellite_delivery_system_descriptor]
             descriptor_length: 11 (0x0b)
             Frequency: 19007128 (=  12.20698 GHz)
             Orbital_position: 304 (=  13.0)
             West_East_flag: 1 (0x01)  [= EAST]
             Polarisation: 0 (0x00)  [= linear - horizontal]
             Kind: 1 (0x01)  [= DVB-S2]
             Roll Off Faktor: 0 (0x00)  [= Alpha 0.35]
             Modulation_type: 2 (0x02)  [= 8PSK]
             Symbol_rate: 2723840 (=  29.9000)
             FEC_inner: 3 (0x03)  [= 3/4 conv. code rate]

----------------------------

So.. DVB-DescriptorTag's 65 and 67 appear in opposite order! Could it
be that VDR has transponder data still uninitialized when it is
scanning the service id, because 67 is not arrived yet?

I just checked, but VDR doesn't parse the service_list_descriptor. So it shouldn't
matter whether it comes before or after the satellite_delivery_system_descriptor.

Klaus

_______________________________________________
vdr mailing list
vdr@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


[Index of Archives]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Big List of Linux Books]     [Fedora Users]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux