EnoSat Posted January 3, 2012 Share Posted January 3, 2012 (edited) TransEdit 3.8.2.0 (no tested on all transponders) -in PAT_pid other PMT_pid as in application (SID 0x3712 PMT 0x0022) -analysed PMT-pid added to bad SID (PMT 0x0043 SID 0x3712) Edited January 3, 2012 by EnoSat Quote Link to comment
Griga Posted January 3, 2012 Share Posted January 3, 2012 Only few people are able to read SI tables in the hex viewer. Obviously you are one of them Ok, then go a step further and also read the hex viewer output for PMT PID 0x0043. The PMT contains the service ID (resp. program_number) as backward reference. From the ISO specifications, section 2.4.4.8, Program Map Table: program_number – program_number is a 16-bit field. It specifies the program to which the program_map_PID is applicable. Guess which program_number you will find in the PMT... The Analyzer has to handle a contradiction in this case. It can't know which information is right and which is wrong... Quote Link to comment
Derrick Posted January 3, 2012 Share Posted January 3, 2012 ..the analyzer got lost. I don't think that backward reading is the proper way There are even more contradictions. According to the analyzer both SIDs 14099 and 14098 refer to the same PMT_PID 0x0043. Nothing wrong with that but for 14098 the pmt shows a mpeg video whereas there's nothing for 14099. Both are characterized by service type 1 in the SDT. Last not least, the PAT defines 0x0022 as PMT_PID for program number 14098. PID 0022 is missing. Maybe it's just a fault and 0x0021 was meant as PMT. According to the ISO syntax 0x0021 is a PMT 02B0183713CB0000E045F00609040B00E04702E045F0006A39B14C - CRC OK 02 -> table_id: program_map_section 0018 -> section_length PMT 24 bytes 3713 -> program number 05 -> version number 01 -> current_next_indicator 00 -> section number 00 -> last section number 0045 -> PCR Pid F006 -> and 0FFF = 0006 program info length 6 bytes 0904 -> CA_descriptor length 4 bytes 0B00 -> Norwegian Telekom ("Conax") E047 -> and 1FFF = 0047 ECM-Pid 02 -> ITU-T Rec. H.262 | ISO/IEC 13818-2 Video or ISO/IEC 11172-2 constrained parameter video stream E045 -> and 1FFF = 0045 F000 -> ES_info length 0 Bytes Quote Link to comment
HaraldL Posted January 4, 2012 Share Posted January 4, 2012 Btw. I don't know if it's related but I had to go back to TransEdit 3.8.1 because 3.8.2 skipped several transponders here while scanning Astra 19.2, some of the PAT/PMT/SDT/NIT symbols gone red on these transponders where they didn't with previous versions of TransEdit. After scan there were many channels listed as dead but they are working. TransEdit 3.8.1 still works fine here, every transponder and channel is found correctly. If this is a new problem please move this post to a new thread. And if a new support.zip is needed (last one posted here) please tell me. Quote Link to comment
Derrick Posted January 4, 2012 Share Posted January 4, 2012 Your problem is probably hardware related and has nothing to do with this bug. Transedit has problems to read the SI tables. The default timeouts are more than sufficient to receive the corresponding tables (PAT, PMT, SDT, NIT) in time. Try again -> "Detect Devices". In the support.zip I see different vendors (defining the control method) for the same card: transedit.ini (3.8.1.0) -> vendor=3 hardware.xml -> vendor=0 svchardware.xml -> vendor=3 Quote Link to comment
EnoSat Posted January 6, 2012 Author Share Posted January 6, 2012 (edited) ..the analyzer got lost. I don't think that backward reading is the proper way There are even more contradictions. According to the analyzer both SIDs 14099 and 14098 refer to the same PMT_PID 0x0043. Nothing wrong with that but for 14098 the pmt shows a mpeg video whereas there's nothing for 14099. Both are characterized by service type 1 in the SDT. Last not least, the PAT defines 0x0022 as PMT_PID for program number 14098. PID 0022 is missing. Maybe it's just a fault and 0x0021 was meant as PMT. According to the ISO syntax 0x0021 is a PMT 02B0183713CB0000E045F00609040B00E04702E045F0006A39B14C - CRC OK 02 -> table_id: program_map_section 0018 -> section_length PMT 24 bytes 3713 -> program number 05 -> version number 01 -> current_next_indicator 00 -> section number 00 -> last section number 0045 -> PCR Pid F006 -> and 0FFF = 0006 program info length 6 bytes 0904 -> CA_descriptor length 4 bytes 0B00 -> Norwegian Telekom ("Conax") E047 -> and 1FFF = 0047 ECM-Pid 02 -> ITU-T Rec. H.262 | ISO/IEC 13818-2 Video or ISO/IEC 11172-2 constrained parameter video stream E045 -> and 1FFF = 0045 F000 -> ES_info length 0 Bytes hi, yes i know about this bug in PAT table (fix must only broadcast operator) + ECM 0047 too missing in TS stream Edited January 6, 2012 by EnoSat Quote Link to comment
Derrick Posted January 6, 2012 Share Posted January 6, 2012 ..please use only relevant parts for citations. ECM 0047 too missing in TS stream not true. The pid is in the list but with a ? cos it can't be found in any table (exept in the orphaned PMT 0x0021 ). Maybe ist's just a fault by the provider or 'security by obscurity' As can be easily seen, it has the syntax of an ECM: 807064706264201261C665CBB1901AC93788E186A7D495E96CE6090D8580F0E4F241C21DEE43025A7BDA59569311DE50FF46483053DA03CB5A35ACE65C13AEEF9BCC737AB59D55C44A6710DC9D54216BF91BCB341870391E8768E48380873509236D74EF6616B2 80 -> table_id 7064 -> ECM length 100 bytes There are more faults on this transponder. Both german parliament channels transmit video with a wrong aspect ratio. It says 4:3 but obviously it's 16:9 (looks narrow minded ). Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.