Hello,
I have a few months old system with vdr 2.0.6. VDR is used only as a backend for xbmc (via xvdr plugin).
Everything works fine except for a few lags which I tracked to VDR creating new channels every now and then. When I checked the channels I noticed there are duplicates (there are 36374 channels and many of them are there about 500 times). I wouldn't be surprised if vdr would suffer performance problem with such number of channels.
See the setup.conf (not changed in months), syslog and part of channels (got by LSTC command) and stats: https://gist.github.com/juriad/2b635ef475a6ddf829ab
Why VDR creates duplicate channels? Is there problem with my configuration or is it a bug in vdr? What other information shall I provide?
Thanks for your help.
On 22.01.2015 15:51, Adam Juraszek wrote:
Hello,
I have a few months old system with vdr 2.0.6. VDR is used only as a backend for xbmc (via xvdr plugin).
Everything works fine except for a few lags which I tracked to VDR creating new channels every now and then. When I checked the channels I noticed there are duplicates (there are 36374 channels and many of them are there about 500 times). I wouldn't be surprised if vdr would suffer performance problem with such number of channels.
See the setup.conf (not changed in months), syslog and part of channels (got by LSTC command) and stats: https://gist.github.com/juriad/2b635ef475a6ddf829ab
Why VDR creates duplicate channels? Is there problem with my configuration or is it a bug in vdr? What other information shall I provide?
Looks like VDR doesn't find an existing channel in its Channels list when it encounters a new version of the SDT. At the moment I have no idea how that could happen.
Is this a plain vanilla, unpatched version 2.0.6 of VDR?
Klaus
On Fri, Jan 23, 2015 at 11:23 AM, Klaus Schmidinger Klaus.Schmidinger@tvdr.de wrote:
On 22.01.2015 15:51, Adam Juraszek wrote:
Hello,
I have a few months old system with vdr 2.0.6. VDR is used only as a backend for xbmc (via xvdr plugin).
Everything works fine except for a few lags which I tracked to VDR creating new channels every now and then. When I checked the channels I noticed there are duplicates (there are 36374 channels and many of them are there about 500 times). I wouldn't be surprised if vdr would suffer performance problem with such number of channels.
See the setup.conf (not changed in months), syslog and part of channels (got by LSTC command) and stats: https://gist.github.com/juriad/2b635ef475a6ddf829ab
Why VDR creates duplicate channels? Is there problem with my configuration or is it a bug in vdr? What other information shall I provide?
Looks like VDR doesn't find an existing channel in its Channels list when it encounters a new version of the SDT. At the moment I have no idea how that could happen.
Is this a plain vanilla, unpatched version 2.0.6 of VDR?
Klaus
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Yes, it is unpatched version (just checked diff againts vdr-2.0.6.tar.bz2). I tried to use gdb to see what is happening.
Anyway, the backtrace of call of method cChannels::NewChannel is: #0 cChannels::NewChannel (this=0x76b800 <Channels>, Transponder=0xf992a0, Name=Name@entry=0x7f74ce78fdf0 "CT 1 HD", ShortName=ShortName@entry=0x7f74ce790df0 "", Provider=Provider@entry=0x7f74ce791df0 "Towercom", Nid=Nid@entry=3, Tid=3234, Sid=4901, Rid=0) at channels.c:1013 #1 0x00000000004d64ee in cSdtFilter::Process (this=0xf9aa40, Pid=<optimized out>, Tid=<optimized out>, Data=<optimized out>, Length=<optimized out>) at sdt.c:105 #2 0x00000000004d727c in cSectionHandler::Action (this=0xfa41e0) at sections.c:211 #3 0x00000000004f8b23 in cThread::StartThread (Thread=0xfa41e0) at thread.c:262 #4 0x00007f74d79920a4 in start_thread (arg=0x7f74ce794700) at pthread_create.c:309 #5 0x00007f74d63acccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
I tried to create a core-dump but gdb failed to do so.
On 23.01.2015 16:43, Adam Juraszek wrote:
On Fri, Jan 23, 2015 at 11:23 AM, Klaus Schmidinger Klaus.Schmidinger@tvdr.de wrote:
On 22.01.2015 15:51, Adam Juraszek wrote:
Hello,
I have a few months old system with vdr 2.0.6. VDR is used only as a backend for xbmc (via xvdr plugin).
Everything works fine except for a few lags which I tracked to VDR creating new channels every now and then. When I checked the channels I noticed there are duplicates (there are 36374 channels and many of them are there about 500 times). I wouldn't be surprised if vdr would suffer performance problem with such number of channels.
See the setup.conf (not changed in months), syslog and part of channels (got by LSTC command) and stats: https://gist.github.com/juriad/2b635ef475a6ddf829ab
Why VDR creates duplicate channels? Is there problem with my configuration or is it a bug in vdr? What other information shall I provide?
Looks like VDR doesn't find an existing channel in its Channels list when it encounters a new version of the SDT. At the moment I have no idea how that could happen.
Is this a plain vanilla, unpatched version 2.0.6 of VDR?
Klaus
Yes, it is unpatched version (just checked diff againts vdr-2.0.6.tar.bz2). I tried to use gdb to see what is happening.
Anyway, the backtrace of call of method cChannels::NewChannel is: #0 cChannels::NewChannel (this=0x76b800 <Channels>, Transponder=0xf992a0, Name=Name@entry=0x7f74ce78fdf0 "CT 1 HD", ShortName=ShortName@entry=0x7f74ce790df0 "", Provider=Provider@entry=0x7f74ce791df0 "Towercom", Nid=Nid@entry=3, Tid=3234, Sid=4901, Rid=0) at channels.c:1013 #1 0x00000000004d64ee in cSdtFilter::Process (this=0xf9aa40, Pid=<optimized out>, Tid=<optimized out>, Data=<optimized out>, Length=<optimized out>) at sdt.c:105 #2 0x00000000004d727c in cSectionHandler::Action (this=0xfa41e0) at sections.c:211 #3 0x00000000004f8b23 in cThread::StartThread (Thread=0xfa41e0) at thread.c:262 #4 0x00007f74d79920a4 in start_thread (arg=0x7f74ce794700) at pthread_create.c:309 #5 0x00007f74d63acccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
I tried to create a core-dump but gdb failed to do so.
Maybe you can add some debug output when a channel named "CT 1 HD" is encountered in the SDT and then searched for in the Channels list. Since the channel apparently *is* in the list, the search for it seems to fail at some point. We need to find out the reason for that.
Klaus
25.01.2015 13:21, Klaus Schmidinger kirjutas:
On 23.01.2015 16:43, Adam Juraszek wrote:
On Fri, Jan 23, 2015 at 11:23 AM, Klaus Schmidinger Klaus.Schmidinger@tvdr.de wrote:
On 22.01.2015 15:51, Adam Juraszek wrote:
Hello,
I have a few months old system with vdr 2.0.6. VDR is used only as a backend for xbmc (via xvdr plugin).
Everything works fine except for a few lags which I tracked to VDR creating new channels every now and then. When I checked the channels I noticed there are duplicates (there are 36374 channels and many of them are there about 500 times). I wouldn't be surprised if vdr would suffer performance problem with such number of channels.
See the setup.conf (not changed in months), syslog and part of channels (got by LSTC command) and stats: https://gist.github.com/juriad/2b635ef475a6ddf829ab
Why VDR creates duplicate channels? Is there problem with my configuration or is it a bug in vdr? What other information shall I provide?
Looks like VDR doesn't find an existing channel in its Channels list when it encounters a new version of the SDT. At the moment I have no idea how that could happen.
Is this a plain vanilla, unpatched version 2.0.6 of VDR?
Klaus
Yes, it is unpatched version (just checked diff againts vdr-2.0.6.tar.bz2). I tried to use gdb to see what is happening.
Anyway, the backtrace of call of method cChannels::NewChannel is: #0 cChannels::NewChannel (this=0x76b800 <Channels>, Transponder=0xf992a0, Name=Name@entry=0x7f74ce78fdf0 "CT 1 HD", ShortName=ShortName@entry=0x7f74ce790df0 "", Provider=Provider@entry=0x7f74ce791df0 "Towercom", Nid=Nid@entry=3, Tid=3234, Sid=4901, Rid=0) at channels.c:1013 #1 0x00000000004d64ee in cSdtFilter::Process (this=0xf9aa40, Pid=<optimized out>, Tid=<optimized out>, Data=<optimized out>, Length=<optimized out>) at sdt.c:105 #2 0x00000000004d727c in cSectionHandler::Action (this=0xfa41e0) at sections.c:211 #3 0x00000000004f8b23 in cThread::StartThread (Thread=0xfa41e0) at thread.c:262 #4 0x00007f74d79920a4 in start_thread (arg=0x7f74ce794700) at pthread_create.c:309 #5 0x00007f74d63acccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
I tried to create a core-dump but gdb failed to do so.
Maybe you can add some debug output when a channel named "CT 1 HD" is encountered in the SDT and then searched for in the Channels list. Since the channel apparently *is* in the list, the search for it seems to fail at some point. We need to find out the reason for that.
Klaus
Is there any progress? Maybe my problem related to this too. I just jumped from vdr-2.1.6 to the 2.1.8 and now I have many false OBSOLETE channels. For example, i have channel (svdrpsend printout): 875 TV11:11804:hM2O0S0:S4.8E:27500:6001=2:6002=@3:6006:90F,93E:6000:86:8:0
but this and any other channels on that transponder marked as OBSOLETE:
Feb 2 22:14:50 akovdr vdr: [5269] creating new channel 'TV11,;' on S4.8E transponder 111804 with id 86-8-6000-0 Feb 2 22:14:50 akovdr vdr: [5269] creating new channel 'TV 2 Filmkanalen,;Viasat' on S4.8E transponder 111804 with id 86-8-6010-0 Feb 2 22:14:50 akovdr vdr: [5269] creating new channel 'Ticket,;' on S4.8E transponder 111804 with id 86-8-6020-0 Feb 2 22:14:50 akovdr vdr: [5269] creating new channel 'MTV NO,;' on S4.8E transponder 111804 with id 86-8-6040-0 Feb 2 22:14:50 akovdr vdr: [5269] creating new channel 'Viasat History,;' on S4.8E transponder 111804 with id 86-8-6050-0 Feb 2 22:14:50 akovdr vdr: [5269] creating new channel 'Viasat Sport Baltic,;' on S4.8E transponder 111804 with id 86-8-6060-0 Feb 2 22:14:50 akovdr vdr: [5269] creating new channel 'Sjuan,;' on S4.8E transponder 111804 with id 86-8-6080-0 Feb 2 22:14:50 akovdr vdr: [5269] creating new channel 'TV4 Film,;' on S4.8E transponder 111804 with id 86-8-6090-0 Feb 2 22:14:50 akovdr vdr: [5269] creating new channel 'Viasat Nature East,;' on S4.8E transponder 111804 with id 86-8-6030-0 Feb 2 22:14:50 akovdr vdr: [5269] changing name of channel 822 from 'Viasat Sport Baltic,;' to 'Viasat Sport Baltic OBSOLETE,;OBSOLETE ' Feb 2 22:14:50 akovdr vdr: [5269] changing name of channel 875 from 'TV11,;' to 'TV11 OBSOLETE,;OBSOLETE ' Feb 2 22:14:50 akovdr vdr: [5269] changing name of channel 876 from 'TV 2 Filmkanalen,;' to 'TV 2 Filmkanalen OBSOLETE,;OBSOLETE ' Feb 2 22:14:50 akovdr vdr: [5269] changing name of channel 877 from 'Viasat History,;' to 'Viasat History OBSOLETE,;OBSOLETE ' Feb 2 22:14:50 akovdr vdr: [5269] changing name of channel 878 from 'Sjuan,;' to 'Sjuan OBSOLETE,;OBSOLETE ' Feb 2 22:14:50 akovdr vdr: [5269] changing name of channel 879 from 'TV4 Film,;' to 'TV4 Film OBSOLETE,;OBSOLETE ' Feb 2 22:14:50 akovdr vdr: [5269] changing name of channel 880 from 'Viasat Nature East,;' to 'Viasat Nature East OBSOLETE,;OBSOLETE ' Feb 2 22:14:50 akovdr vdr: [5269] changing name of channel 888 from 'MTV NO,;' to 'MTV NO OBSOLETE,;OBSOLETE ' Feb 2 22:14:50 akovdr vdr: [5269] changing name of channel 945 from 'Ticket,;' to 'Ticket OBSOLETE,;OBSOLETE '
At the same time this problem not occurred with DVB-C channels. 250 2 ETV2:266000:C0M256:C:6875:300=2:310=est@3,311=est@3:0:B00:1004:16:1:0
In the DVB settings UpdateChannels = 4 selected.
br, Arthur
Lugupidamisega, Arthur 2.02.2015 23:22, Arthur kirjutas:
25.01.2015 13:21, Klaus Schmidinger kirjutas:
On 23.01.2015 16:43, Adam Juraszek wrote:
On Fri, Jan 23, 2015 at 11:23 AM, Klaus Schmidinger Klaus.Schmidinger@tvdr.de wrote:
On 22.01.2015 15:51, Adam Juraszek wrote:
Hello,
I have a few months old system with vdr 2.0.6. VDR is used only as a backend for xbmc (via xvdr plugin).
Everything works fine except for a few lags which I tracked to VDR creating new channels every now and then. When I checked the channels I noticed there are duplicates (there are 36374 channels and many of them are there about 500 times). I wouldn't be surprised if vdr would suffer performance problem with such number of channels.
See the setup.conf (not changed in months), syslog and part of channels (got by LSTC command) and stats: https://gist.github.com/juriad/2b635ef475a6ddf829ab
Why VDR creates duplicate channels? Is there problem with my configuration or is it a bug in vdr? What other information shall I provide?
Looks like VDR doesn't find an existing channel in its Channels list when it encounters a new version of the SDT. At the moment I have no idea how that could happen.
Is this a plain vanilla, unpatched version 2.0.6 of VDR?
Klaus
Yes, it is unpatched version (just checked diff againts vdr-2.0.6.tar.bz2). I tried to use gdb to see what is happening.
Anyway, the backtrace of call of method cChannels::NewChannel is: #0 cChannels::NewChannel (this=0x76b800 <Channels>, Transponder=0xf992a0, Name=Name@entry=0x7f74ce78fdf0 "CT 1 HD", ShortName=ShortName@entry=0x7f74ce790df0 "", Provider=Provider@entry=0x7f74ce791df0 "Towercom", Nid=Nid@entry=3, Tid=3234, Sid=4901, Rid=0) at channels.c:1013 #1 0x00000000004d64ee in cSdtFilter::Process (this=0xf9aa40, Pid=<optimized out>, Tid=<optimized out>, Data=<optimized out>, Length=<optimized out>) at sdt.c:105 #2 0x00000000004d727c in cSectionHandler::Action (this=0xfa41e0) at sections.c:211 #3 0x00000000004f8b23 in cThread::StartThread (Thread=0xfa41e0) at thread.c:262 #4 0x00007f74d79920a4 in start_thread (arg=0x7f74ce794700) at pthread_create.c:309 #5 0x00007f74d63acccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
I tried to create a core-dump but gdb failed to do so.
Maybe you can add some debug output when a channel named "CT 1 HD" is encountered in the SDT and then searched for in the Channels list. Since the channel apparently *is* in the list, the search for it seems to fail at some point. We need to find out the reason for that.
Klaus
Is there any progress? Maybe my problem related to this too. I just jumped from vdr-2.1.6 to the 2.1.8 and now I have many false OBSOLETE channels. For example, i have channel (svdrpsend printout): 875 TV11:11804:hM2O0S0:S4.8E:27500:6001=2:6002=@3:6006:90F,93E:6000:86:8:0
but this and any other channels on that transponder marked as OBSOLETE:
Feb 2 22:14:50 akovdr vdr: [5269] creating new channel 'TV11,;' on S4.8E transponder 111804 with id 86-8-6000-0 Feb 2 22:14:50 akovdr vdr: [5269] creating new channel 'TV 2 Filmkanalen,;Viasat' on S4.8E transponder 111804 with id 86-8-6010-0 Feb 2 22:14:50 akovdr vdr: [5269] creating new channel 'Ticket,;' on S4.8E transponder 111804 with id 86-8-6020-0 Feb 2 22:14:50 akovdr vdr: [5269] creating new channel 'MTV NO,;' on S4.8E transponder 111804 with id 86-8-6040-0 Feb 2 22:14:50 akovdr vdr: [5269] creating new channel 'Viasat History,;' on S4.8E transponder 111804 with id 86-8-6050-0 Feb 2 22:14:50 akovdr vdr: [5269] creating new channel 'Viasat Sport Baltic,;' on S4.8E transponder 111804 with id 86-8-6060-0 Feb 2 22:14:50 akovdr vdr: [5269] creating new channel 'Sjuan,;' on S4.8E transponder 111804 with id 86-8-6080-0 Feb 2 22:14:50 akovdr vdr: [5269] creating new channel 'TV4 Film,;' on S4.8E transponder 111804 with id 86-8-6090-0 Feb 2 22:14:50 akovdr vdr: [5269] creating new channel 'Viasat Nature East,;' on S4.8E transponder 111804 with id 86-8-6030-0 Feb 2 22:14:50 akovdr vdr: [5269] changing name of channel 822 from 'Viasat Sport Baltic,;' to 'Viasat Sport Baltic OBSOLETE,;OBSOLETE ' Feb 2 22:14:50 akovdr vdr: [5269] changing name of channel 875 from 'TV11,;' to 'TV11 OBSOLETE,;OBSOLETE ' Feb 2 22:14:50 akovdr vdr: [5269] changing name of channel 876 from 'TV 2 Filmkanalen,;' to 'TV 2 Filmkanalen OBSOLETE,;OBSOLETE ' Feb 2 22:14:50 akovdr vdr: [5269] changing name of channel 877 from 'Viasat History,;' to 'Viasat History OBSOLETE,;OBSOLETE ' Feb 2 22:14:50 akovdr vdr: [5269] changing name of channel 878 from 'Sjuan,;' to 'Sjuan OBSOLETE,;OBSOLETE ' Feb 2 22:14:50 akovdr vdr: [5269] changing name of channel 879 from 'TV4 Film,;' to 'TV4 Film OBSOLETE,;OBSOLETE ' Feb 2 22:14:50 akovdr vdr: [5269] changing name of channel 880 from 'Viasat Nature East,;' to 'Viasat Nature East OBSOLETE,;OBSOLETE ' Feb 2 22:14:50 akovdr vdr: [5269] changing name of channel 888 from 'MTV NO,;' to 'MTV NO OBSOLETE,;OBSOLETE ' Feb 2 22:14:50 akovdr vdr: [5269] changing name of channel 945 from 'Ticket,;' to 'Ticket OBSOLETE,;OBSOLETE '
At the same time this problem not occurred with DVB-C channels. 250 2 ETV2:266000:C0M256:C:6875:300=2:310=est@3,311=est@3:0:B00:1004:16:1:0
In the DVB settings UpdateChannels = 4 selected.
I'm not sure how helpful this information is, but there SDT table part from dvbsnoop printout:
dvbsnoop -n 1 -adapter 3 -nph 0x11
dvbsnoop V1.4.50 -- http://dvbsnoop.sourceforge.net/ ------------------------------------------------------------ SECT-Packet: 00000001 PID: 17 (0x0011), Length: 718 (0x02ce) Time received: Tue 2015-02-03 10:42:27.989 ------------------------------------------------------------ PID: 17 (0x0011) [= assigned for: DVB Service Description Table (SDT), Bouquet Association Table (BAT)]
Guess table from table id... SDT-decoding.... Table_ID: 66 (0x42) [= Service Description Table (SDT) - actual transport stream] section_syntax_indicator: 1 (0x01) reserved_1: 1 (0x01) reserved_2: 3 (0x03) Section_length: 715 (0x02cb) Transport_Stream_ID: 8 (0x0008) reserved_3: 3 (0x03) Version_number: 27 (0x1b) current_next_indicator: 1 (0x01) [= valid now] Section_number: 0 (0x00) Last_Section_number: 0 (0x00) Original_network_ID: 86 (0x0056) [= >>ERROR: not (yet) defined... Report!<<] reserved_4: 255 (0xff)
Service_id: 6000 (0x1770) [= --> refers to PMT program_number] reserved_1: 63 (0x3f) EIT_schedule_flag: 0 (0x00) EIT_present_following_flag: 1 (0x01) Running_status: 0 (0x00) [= undefined] Free_CA_mode: 1 (0x01) [= streams [partially] CA controlled] Descriptors_loop_length: 62 (0x003e)
DVB-DescriptorTag: 72 (0x48) [= service_descriptor] descriptor_length: 8 (0x08) service_type: 1 (0x01) [= digital television service] service_provider_name_length: 0 (0x00) service_provider_name: "" service_name_length: 5 (0x05) Service_name: "TV11" -- Charset: Latin alphabet no. 5
DVB-DescriptorTag: 95 (0x5f) [= private_data_specifier_descriptor] descriptor_length: 4 (0x04) PrivateDataSpecifier: 86 (0x00000056) [= >>ERROR: not (yet) defined... Report!<<]
DVB-DescriptorTag: 130 (0x82) [= User defined/ATSC reserved] descriptor_length: 40 (0x28) Descriptor-data: 0000: 73 77 65 00 4d 66 69 6e 00 00 6e 6f 72 00 00 64 swe.Mfin..nor..d 0010: 61 6e 00 00 65 73 74 00 00 6c 69 74 00 00 6c 61 an..est..lit..la 0020: 76 00 00 72 75 73 00 00 v..rus..
DVB-DescriptorTag: 83 (0x53) [= CA_identifier_descriptor] descriptor_length: 2 (0x02) CA_system_ID: 2319 (0x090f) [= News Datacom (Videoguard)]
Service_id: 6010 (0x177a) [= --> refers to PMT program_number] reserved_1: 63 (0x3f) EIT_schedule_flag: 0 (0x00) EIT_present_following_flag: 1 (0x01) Running_status: 0 (0x00) [= undefined] Free_CA_mode: 1 (0x01) [= streams [partially] CA controlled] Descriptors_loop_length: 81 (0x0051)
DVB-DescriptorTag: 72 (0x48) [= service_descriptor] descriptor_length: 27 (0x1b) service_type: 1 (0x01) [= digital television service] service_provider_name_length: 7 (0x07) service_provider_name: "Viasat" -- Charset: Latin alphabet no. 5 service_name_length: 17 (0x11) Service_name: "TV 2 Filmkanalen" -- Charset: Latin alphabet no. 5
DVB-DescriptorTag: 95 (0x5f) [= private_data_specifier_descriptor] descriptor_length: 4 (0x04) PrivateDataSpecifier: 86 (0x00000056) [= >>ERROR: not (yet) defined... Report!<<]
DVB-DescriptorTag: 130 (0x82) [= User defined/ATSC reserved] descriptor_length: 40 (0x28) Descriptor-data: 0000: 73 77 65 00 00 66 69 6e 00 00 6e 6f 72 00 16 64 swe..fin..nor..d 0010: 61 6e 00 00 65 73 74 00 00 6c 69 74 00 00 6c 61 an..est..lit..la 0020: 76 00 00 72 75 73 00 00 v..rus..
DVB-DescriptorTag: 83 (0x53) [= CA_identifier_descriptor] descriptor_length: 2 (0x02) CA_system_ID: 2319 (0x090f) [= News Datacom (Videoguard)]
Service_id: 6020 (0x1784) [= --> refers to PMT program_number] reserved_1: 63 (0x3f) EIT_schedule_flag: 0 (0x00) EIT_present_following_flag: 1 (0x01) Running_status: 0 (0x00) [= undefined] Free_CA_mode: 1 (0x01) [= streams [partially] CA controlled] Descriptors_loop_length: 64 (0x0040)
DVB-DescriptorTag: 72 (0x48) [= service_descriptor] descriptor_length: 10 (0x0a) service_type: 1 (0x01) [= digital television service] service_provider_name_length: 0 (0x00) service_provider_name: "" service_name_length: 7 (0x07) Service_name: "Ticket" -- Charset: Latin alphabet no. 5
DVB-DescriptorTag: 95 (0x5f) [= private_data_specifier_descriptor] descriptor_length: 4 (0x04) PrivateDataSpecifier: 86 (0x00000056) [= >>ERROR: not (yet) defined... Report!<<]
DVB-DescriptorTag: 130 (0x82) [= User defined/ATSC reserved] descriptor_length: 40 (0x28) Descriptor-data: 0000: 73 77 65 00 1a 66 69 6e 00 45 6e 6f 72 00 00 64 swe..fin.Enor..d 0010: 61 6e 00 4d 65 73 74 00 0f 6c 69 74 00 57 6c 61 an.Mest..lit.Wla 0020: 76 00 59 72 75 73 00 00 v.Yrus..
DVB-DescriptorTag: 83 (0x53) [= CA_identifier_descriptor] descriptor_length: 2 (0x02) CA_system_ID: 2319 (0x090f) [= News Datacom (Videoguard)]
-
Adam Juraszek -
Arthur -
Klaus Schmidinger