Allan Stirling wrote: > dvbsnoop gives me the following: > ------------------------------------------------------------ > SECT-Packet: 00000001 PID: 0 (0x0000), Length: 44 (0x002c) > Time received: Thu 2005-06-23 22:20:09.035 > ------------------------------------------------------------ > 0000: 00 b0 29 07 ee e3 00 00 00 00 e0 10 11 39 e1 01 ..)..........9.. > 0010: 11 fa e1 07 11 fb e1 09 12 5f e1 04 12 c2 e1 0c ........._...... > 0020: 12 c9 e1 0b 13 2a e1 0a 24 a9 24 84 .....*..$.$. > > PID: 0 (0x0000) [= assigned for: ISO 13818-1 Program Association Table > (PAT)] > Guess table from table id... > PAT-decoding.... > Table_ID: 0 (0x00) [= Program Association Table (PAT)] > section_syntax_indicator: 1 (0x01) > (fixed): 0 (0x00) > reserved_1: 3 (0x03) > Section_length: 41 (0x0029) > Transport_Stream_ID: 2030 (0x07ee) > reserved_2: 3 (0x03) > Version_number: 17 (0x11) > current_next_indicator: 1 (0x01) [= valid now] > Section_number: 0 (0x00) > Last_Section_number: 0 (0x00) > > Program_number: 0 (0x0000) > reserved: 7 (0x07) > Network_PID: 16 (0x0010) > > Program_number: 4409 (0x1139) > reserved: 7 (0x07) > Program_map_PID: 257 (0x0101) > > Program_number: 4602 (0x11fa) > reserved: 7 (0x07) > Program_map_PID: 263 (0x0107) > > Program_number: 4603 (0x11fb) > reserved: 7 (0x07) > Program_map_PID: 265 (0x0109) > > Program_number: 4703 (0x125f) > reserved: 7 (0x07) > Program_map_PID: 260 (0x0104) > > Program_number: 4802 (0x12c2) > reserved: 7 (0x07) > Program_map_PID: 268 (0x010c) > > Program_number: 4809 (0x12c9) > reserved: 7 (0x07) > Program_map_PID: 267 (0x010b) > > Program_number: 4906 (0x132a) > reserved: 7 (0x07) > Program_map_PID: 266 (0x010a) > > Where you can clearly see that 4703 is listed, with a PID of 260. I > think there must be something wrong in the PAT parsing, since I get the > following with a slightly modified ca_zap: > > parse_pat: PAT => Section Length=[41], TS ID=[12270] > service_id: 4703 The service_id seems to be retrieved .... regarding TSID let me take a look. Manu
