Re: [vdr] VDR's UpdateChannels destroys channel information
On 21 March 2013 09:04, Teemu Suikki tsui...@zuik.org wrote: I have mysterious problem with some channels.. All seem to be on S13.0E, but on different transponders. According to http://en.kingofsat.net/pos-13E.php page, Disney Channel HD Italia is DVB-S2, 8PSK, SR 29900. However, I seem to have DVB-S, QPSK, SR 27500 in my channels.conf. Is the transponder sending incorrect data, or what is going on? What card(s) are you using? I have seen problems with TT-S2-3200 on other mailing lists / forums. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR's UpdateChannels destroys channel information
On 21.03.2013 10:04, Teemu Suikki wrote: Hi! I have mysterious problem with some channels.. All seem to be on S13.0E, but on different transponders. According to http://en.kingofsat.net/pos-13E.php page, Disney Channel HD Italia is DVB-S2, 8PSK, SR 29900. However, I seem to have DVB-S, QPSK, SR 27500 in my channels.conf. I have tried editing the channel directly to channels.conf, while vdr stopped. Also I have tried editing it inside vdr, from channel list - edit.. After the edit, channels shows fine for a few seconds, but then VDR updates it back to old values and channel stops showing! Mar 21 10:41:53 yavdr vdr: [16964] edited channel 179 Disney Ch. HD;SkyItalia:12207:HC34M5O0S1:S13.0E:29900:164=27:0;416=ita@106,417=eng@106:701: 919,93B,9CD:4128:318:7501:0 Mar 21 10:41:56 yavdr vdr: [16964] switching to channel 179 Here's the result of a test I ran on my VDR (TT S2-6400). I took your original channel entry and set the CA parameter to 0 (since I don't have a CAM/Smartcard for that channel), created a new channel and switched to it: newc Disney Ch.HD;SkyItalia:12207:HC34M5O0S1:S13.0E:29900:164=27:0;416=ita@106,417=eng@106:701:0:4128:318:7501:0 250 3364 Disney Ch.HD;SkyItalia:12207:HC34M5O0S1:S13.0E:29900:164=27:0;416=ita@106,417=eng@106:701:0:4128:318:7501:0 chan 3364 250 3364 Disney Ch.HD The PIDs and CA-IDs were changed automatically: Mar 21 12:11:23 vdr2 vdr: [29620] new channel 3364 Disney Ch.HD;SkyItalia:12207:HC34M5O0S1:S13.0E:29900:164=27:0;416=ita@106,417=eng@106:701:0:4128:318:7501:0 Mar 21 12:11:32 vdr2 vdr: [29620] switching to channel 3364 Mar 21 12:11:34 vdr2 vdr: [29626] changing pids of channel 3364 from 164+164=27:0;416=ita@106,417=eng@106:0:701 to 164+164=27:0;416=ita@106,417=und@106:0:701 Mar 21 12:11:34 vdr2 vdr: [29626] changing caids of channel 3364 from 0 to 919,93B,9CD Mar 21 12:11:34 vdr2 vdr: [29620] retuning due to modification of channel 3364 Mar 21 12:11:34 vdr2 vdr: [29620] switching to channel 3364 Mar 21 12:11:34 vdr2 vdr: [29620] info: Channel not available! lstc 3364 250 3364 Disney Ch.HD;SkyItalia:12207:HC34M5O0S1:S13.0E:29900:164=27:0;416=ita@106,417=und@106:701:919,93B,9CD:4128:318:7501:0 A few seconds later, the transponder data was changed: Mar 21 12:11:53 vdr2 vdr: [29626] changing transponder data of channel 3364 from 12207:HC34M5O0S1:S13.0E:29900 to 12207:HC34M2S0:S13.0E:27500 Mar 21 12:11:53 vdr2 vdr: [29620] retuning due to modification of channel 3364 Mar 21 12:11:53 vdr2 vdr: [29620] switching to channel 3364 Mar 21 12:11:53 vdr2 vdr: [29620] info: Channel not available! lstc 3364 250 3364 Disney Ch.HD;SkyItalia:12207:HC34M2S0:S13.0E:27500:164=27:0;416=ita@106,417=und@106:701:919,93B,9CD:4128:318:7501:0 You may want to use a tool like dvbsnoop and check what is broadcast in the NIT of that provider. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR's UpdateChannels destroys channel information
2013/3/21 Klaus Schmidinger klaus.schmidin...@tvdr.de: Mar 21 12:11:53 vdr2 vdr: [29626] changing transponder data of channel 3364 from 12207:HC34M5O0S1:S13.0E:29900 to 12207:HC34M2S0:S13.0E:27500 Mar 21 12:11:53 vdr2 vdr: [29620] retuning due to modification of channel Hi, ok, thanks for the confirmation! I tried dvbsnoop. It returns correct values (dvb-s2, sr 29900).. See below. Then I tried scan-s2 -c from the command line, and interestingly it reports correct SR 29900 but dvb-s, not dvb-s2.. Weird? - 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: 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] -- Teemu Suikki http://www.z-power.fi/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR's UpdateChannels destroys channel information
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?
--
Teemu Suikki
http://www.z-power.fi/
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR's UpdateChannels destroys channel information
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@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR's UpdateChannels destroys channel information
Guess what, problem solved.. My channels config had TID 7501, but the real TID is 7500.. I have no idea how this could have been changed, though? And I thought that the channel wouldn't show at all, if TID is not correct? Anyway, with TID changed to 7500, I can enable UpdateChannels and vdr won't touch the transponder data anymore. Still a bit odd that it updated the transponder data.. S13E does not have TID 7501 in any transponder, so where did the updated data come from? -- Teemu Suikki http://www.z-power.fi/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
