EnoSat Posted July 4, 2014 Author Posted July 4, 2014 yes , offline analyse work ok PS: 3 min TS file Quote
Griga Posted July 5, 2014 Posted July 5, 2014 Thanks. It's interesting - ATSC SI on a DVB-S transponder. I have never seen something like this before. It's some kind of feed, I guess? At least highly non-standard. In a true ATSC mux I would expect AC3 audio, not MPEG audio. Do you think it is necessary to add live ATSC analysis for cases like this? A registration descriptor containing a GA94 format identifier, as you can see it in the PMT, may act as ATSC indicator. Or is the offline analysis (as you call it) sufficient? If it is only broadcasted temporarily or in rare cases I would rather save the work. Quote
EnoSat Posted July 5, 2014 Author Posted July 5, 2014 yes, this not standart as T2-MI or MIS for some DVB-T transmitters from DVB-S2 transponders (90E,55E,49E,31E,21E,5W,12W) , but next ATSC i am view only on occasional italian feeds on 10 East Quote
Derrick Posted July 7, 2014 Posted July 7, 2014 Live ATSC parsing is performed by TSReader and 4T2 Content Analyser. But in this case it doesn't provide much useful information PAT Table SectionCount: 1 Sections PAT Section 0 TransportStreamID: 1 (0x0001) TableID: 0 (0x00) SectionLength: 13 (0x00D) SectionData 00: 00 B0 0D 00 01 C3 00 00 00 02 E0 20 3E 04 0C EA .°...Ã....à >..ê Received on PID: 0 (0x00) SectionSyntaxIndicator: True TableIDExtension: 1 (0x0001) VersionNumber: 1 (0x01) CurrentNextIndicator: Current SectionNumber: 0 (0x00) LastSectionNumber: 0 (0x00) PAT Items Item 0 for program 2 (0x0002) "<unknown>" ProgramNumber: 2 (0x0002) ProgramMapPID: 32 (0x0020)PMT Table SectionCount: 1 Sections Map for program 2 (0x0002) "<unknown>" ProgramNumber: 2 (0x0002) "<unknown>" PCRPID: 33 (0x0021) Descriptors Descriptor 0 DescriptorTag: 5 (0x05) "registration_descriptor" DescriptorSpace: ATSC DefaultISOLanguageCode: "" DescriptorLength: 4 DescriptorData: 00: 05 04 47 41 39 34 ..GA94 FormatDescriptor: 1195456820 (0x47413934) "GA94 ATSC" Descriptor 1 DescriptorTag: 5 (0x05) "registration_descriptor" DescriptorSpace: ATSC DefaultISOLanguageCode: "" DescriptorLength: 4 DescriptorData: 00: 05 04 B6 AC F1 79 ..¶¬ñy FormatDescriptor: -1230179975 (0xB6ACF179) "" Descriptor 2 DescriptorTag: 12 (0x0C) "Multiplex_buffer_utilization_descriptor" DescriptorSpace: ATSC DefaultISOLanguageCode: "" DescriptorLength: 4 DescriptorData: 00: 0C 04 00 00 FF FF ....ÿÿ BoundValidFlag: False LTWOffsetLowerBound: 0 (0.00ms) LTWOffsetUpperBound: 32767 (364.08ms) Descriptor 3 DescriptorTag: 194 (0xC2) "ATSC user defined" DescriptorSpace: ATSC DefaultISOLanguageCode: "" DescriptorLength: 1 DescriptorData: 00: C2 01 00 Â.. TableID: 2 (0x02) SectionLength: 75 (0x04B) SectionData 00: 02 B0 4B 00 02 C3 00 00 E0 21 F0 15 05 04 47 41 .°K..Ã..à!ð...GA 10: 39 34 05 04 B6 AC F1 79 0C 04 00 00 FF FF C2 01 94..¶¬ñy....ÿÿÂ. 20: 00 02 E0 21 F0 08 02 03 1A 48 5F 06 01 02 03 E0 ..à!ð....H_....à 30: 24 F0 09 0A 04 75 6E 64 00 03 01 67 03 E0 25 F0 $ð...und...g.à%ð 40: 09 0A 04 75 6E 64 00 03 01 67 F9 F5 04 8A ...und...gùõ.Š Received on PID: 32 (0x20) SectionSyntaxIndicator: True TableIDExtension: 2 (0x0002) VersionNumber: 1 (0x01) CurrentNextIndicator: Current SectionNumber: 0 (0x00) LastSectionNumber: 0 (0x00) Streams Stream 0 StreamType 2 (0x02) (ITU-T Rec. H.262 | ISO/IEC 13818-2 Video or ISO/IEC 11172-2 constrained parameter videostream) ElementaryPID 33 (0x0021) Descriptors Descriptor 0 DescriptorTag: 2 (0x02) "video_stream_descriptor" DescriptorSpace: ATSC DefaultISOLanguageCode: "" DescriptorLength: 3 DescriptorData: 00: 02 03 1A 48 5F ...H_ MultipleFrameRateFlag: False FrameRateCode: 3 (25.000 fps) MPEG1OnlyFlag: False ConstrainedParameterFlag: True StillPictureFlag: False ProfileAndLevelIndication: 72 (0x48), Profile "Main", Level: "Main" ChromaFormat: "420" FrameRateExtensionFlag: False Descriptor 1 DescriptorTag: 6 (0x06) "data_stream_alignment_descriptor" DescriptorSpace: ATSC DefaultISOLanguageCode: "" DescriptorLength: 1 DescriptorData: 00: 06 01 02 ... AlignmentType: 2 (Video: "Video access unit", Audio "Reserved") Stream 1 StreamType 3 (0x03) (ISO/IEC 11172 Audio) ElementaryPID 36 (0x0024) Descriptors Descriptor 0 DescriptorTag: 10 (0x0A) "ISO_639_language_descriptor" DescriptorSpace: ATSC DefaultISOLanguageCode: "" DescriptorLength: 4 DescriptorData: 00: 0A 04 75 6E 64 00 ..und. Items Item 0 ISO639LanguageCode: und (Undetermined) AudioType: (0x00) Audio Undefined Descriptor 1 DescriptorTag: 3 (0x03) "audio_stream_descriptor" DescriptorSpace: ATSC DefaultISOLanguageCode: "" DescriptorLength: 1 DescriptorData: 00: 03 01 67 ..g FreeFormatFlag: False ID: True Layer: 2 (0x2) VariableRateAudioIndicator: False Stream 2 StreamType 3 (0x03) (ISO/IEC 11172 Audio) ElementaryPID 37 (0x0025) Descriptors Descriptor 0 DescriptorTag: 10 (0x0A) "ISO_639_language_descriptor" DescriptorSpace: ATSC DefaultISOLanguageCode: "" DescriptorLength: 4 DescriptorData: 00: 0A 04 75 6E 64 00 ..und. Items Item 0 ISO639LanguageCode: und (Undetermined) AudioType: (0x00) Audio Undefined Descriptor 1 DescriptorTag: 3 (0x03) "audio_stream_descriptor" DescriptorSpace: ATSC DefaultISOLanguageCode: "" DescriptorLength: 1 DescriptorData: 00: 03 01 67 ..g FreeFormatFlag: False ID: True Layer: 2 (0x2) VariableRateAudioIndicator: FalseMGT Table SectionCount: 1 Sections MGT Section 0 TablesDefined: 6 (0x0006) Descriptors TableID: 199 (0xC7) SectionLength: 80 (0x050) SectionData 00: C7 C0 50 00 00 C3 00 00 00 00 06 00 00 FF FB E1 ÇÀP..Ã.......ÿûá 10: 00 00 00 59 F0 00 01 00 FF 00 E1 00 00 00 0E F0 ...Yð...ÿ.á....ð 20: 00 01 01 FF 01 E1 00 00 00 0E F0 00 01 02 FF 02 ...ÿ.á....ð...ÿ. 30: E1 00 00 00 0E F0 00 01 03 FF 03 E1 00 00 00 0E á....ð...ÿ.á.... 40: F0 00 03 01 FF FB E0 00 00 01 D8 F0 00 F0 00 62 ð...ÿûà...Øð.ð.b 50: 1F 03 81 .. Received on PID: 8187 (0x1FFB) SectionSyntaxIndicator: True TableIDExtension: 0 (0x0000) VersionNumber: 1 (0x01) CurrentNextIndicator: Current SectionNumber: 0 (0x00) LastSectionNumber: 0 (0x00) PSIP Table definitions 0 (0x0000) "Terrestrial VCT with current_next_indicator="1"" TableType: 0 (0x0000) "Terrestrial VCT with current_next_indicator="1"" TableTypePID: 8187 (0x1FFB) TableTypeVersionNumber: 1 (0x01) NumberBytes: 89 (0x00000059) TableTypeDescriptorLength: 0 (0x00000000) Descriptors 256 (0x0100) "EIT-0" TableType: 256 (0x0100) "EIT-0" TableTypePID: 7936 (0x1F00) TableTypeVersionNumber: 1 (0x01) NumberBytes: 14 (0x0000000E) TableTypeDescriptorLength: 0 (0x00000000) Descriptors 257 (0x0101) "EIT-1" TableType: 257 (0x0101) "EIT-1" TableTypePID: 7937 (0x1F01) TableTypeVersionNumber: 1 (0x01) NumberBytes: 14 (0x0000000E) TableTypeDescriptorLength: 0 (0x00000000) Descriptors 258 (0x0102) "EIT-2" TableType: 258 (0x0102) "EIT-2" TableTypePID: 7938 (0x1F02) TableTypeVersionNumber: 1 (0x01) NumberBytes: 14 (0x0000000E) TableTypeDescriptorLength: 0 (0x00000000) Descriptors 259 (0x0103) "EIT-3" TableType: 259 (0x0103) "EIT-3" TableTypePID: 7939 (0x1F03) TableTypeVersionNumber: 1 (0x01) NumberBytes: 14 (0x0000000E) TableTypeDescriptorLength: 0 (0x00000000) Descriptors 769 (0x0301) "RRT with rating_region 1" TableType: 769 (0x0301) "RRT with rating_region 1" TableTypePID: 8187 (0x1FFB) TableTypeVersionNumber: 0 (0x00) NumberBytes: 472 (0x000001D8) TableTypeDescriptorLength: 0 (0x00000000) DescriptorsSTT Table SectionCount: 1 Sections STT Section 0 SystemTime: 0 (0x00000000) "06.01.1980" GPSUTCOffset: 0 (0x00000000) DayLightSaving: 0 (0x0000) Status: "Off" Status: "Off" DayOfMonth: 0 (0x00) Hour: 0 (0x00) Descriptors TableID: 205 (0xCD) SectionLength: 17 (0x011) SectionData 00: CD C0 11 00 00 C1 00 00 00 00 00 00 00 00 00 00 ÍÀ...Á.......... 10: 3E 06 BC 1B >.¼. Received on PID: 8187 (0x1FFB) SectionSyntaxIndicator: True TableIDExtension: 0 (0x0000) VersionNumber: 0 (0x00) CurrentNextIndicator: Current SectionNumber: 0 (0x00) LastSectionNumber: 0 (0x00)EIT Table Received on PID: 7936 (0x1F00) EIT Section 2 NumEventsInSection: 0 (0x0000) Descriptors TableID: 203 (0xCB) SectionLength: 11 (0x00B) SectionData 00: CB F0 0B 00 02 03 00 00 00 00 9D 1F 5D E9 Ëð.........]é Received on PID: 7936 (0x1F00) SectionSyntaxIndicator: True TableIDExtension: 2 (0x0002) VersionNumber: 1 (0x01) CurrentNextIndicator: Current SectionNumber: 0 (0x00) LastSectionNumber: 0 (0x00) Received on PID: 7937 (0x1F01) EIT Section 2 NumEventsInSection: 0 (0x0000) Descriptors TableID: 203 (0xCB) SectionLength: 11 (0x00B) SectionData 00: CB F0 0B 00 02 03 00 00 00 00 9D 1F 5D E9 Ëð.........]é Received on PID: 7937 (0x1F01) SectionSyntaxIndicator: True TableIDExtension: 2 (0x0002) VersionNumber: 1 (0x01) CurrentNextIndicator: Current SectionNumber: 0 (0x00) LastSectionNumber: 0 (0x00) Received on PID: 7938 (0x1F02) EIT Section 2 NumEventsInSection: 0 (0x0000) Descriptors TableID: 203 (0xCB) SectionLength: 11 (0x00B) SectionData 00: CB F0 0B 00 02 03 00 00 00 00 9D 1F 5D E9 Ëð.........]é Received on PID: 7938 (0x1F02) SectionSyntaxIndicator: True TableIDExtension: 2 (0x0002) VersionNumber: 1 (0x01) CurrentNextIndicator: Current SectionNumber: 0 (0x00) LastSectionNumber: 0 (0x00) Received on PID: 7939 (0x1F03) EIT Section 2 NumEventsInSection: 0 (0x0000) Descriptors TableID: 203 (0xCB) SectionLength: 11 (0x00B) SectionData 00: CB F0 0B 00 02 03 00 00 00 00 9D 1F 5D E9 Ëð.........]é Received on PID: 7939 (0x1F03) SectionSyntaxIndicator: True TableIDExtension: 2 (0x0002) VersionNumber: 1 (0x01) CurrentNextIndicator: Current SectionNumber: 0 (0x00) LastSectionNumber: 0 (0x00) Quote
EnoSat Posted August 30, 2014 Author Posted August 30, 2014 (edited) Any chance preview radio IP stream from sat ? next IP radio on 7 East Radio Polska 12633 V DVB-S/QPSK SR-1085 FEC-3/4 Edited August 30, 2014 by EnoSat Quote
Derrick Posted February 5, 2015 Posted February 5, 2015 There is a new test transponder on 33,5W (Hylias 1), 12483V, 15000, DVB-S2, QPSK, 3/4 with a couple of particularities Only a single service with multiple video and audio tracks is transmitted. PAT/PMT changes from time to time to new version with different es_pids and a different pcr. The analyzer can keep track with the live stream but gets totally confused when playing back a recording of the mux. Quote
Griga Posted February 5, 2015 Posted February 5, 2015 6030 Mbps, or with other words, a 6 Gbps transponder. Quite a lot That's because TransEdit uses the PCR (resp. the first PCR PID that it encounters) for controlling the data rate when reading a TS file with the same speed "as received live". Things like that happen If the PCR is discontinuous. Quote
Derrick Posted February 5, 2015 Posted February 5, 2015 Things like that happen If the PCR is discontinuous. Not necessarily ..same file, different tool (also pcr based): Quote
Griga Posted February 5, 2015 Posted February 5, 2015 Tells me nothing, and to be true, not a matter of particular interest for me... Quote
Derrick Posted February 5, 2015 Posted February 5, 2015 Sounds rather ignorant. I thought it would be appreciated when possible bugs are revealed. Here it seems to be a real bug. That's because TransEdit uses the PCR (resp. the first PCR PID that it encounters) for controlling the data rate This transport stream only has a single service and hence a single PCR. The PMT changes after a while to another version with different PIDs. The old service is discontinued and with it the PCR. But there will be a new service with a fresh PCR. This can be demonstrated with yet another tool Quote
EnoSat Posted April 17, 2015 Author Posted April 17, 2015 (edited) Hi, what situation with support MIS and PLS (etc. Mediaset on 13 East/11919 V ? Edited April 17, 2015 by EnoSat Quote
Derrick Posted June 29, 2015 Posted June 29, 2015 Some SI tables and table_id values are not correctly resolved. The analyser of my example shows on the left a TDT with PID 20. On the right hand window the analyser only shows a TOD. When examining the ts_packets with the hex viewer only table_id value 0x70 shows up but not 0x73 which is the id of the TOT. /edit in normal cases when both table_ids are present, the analyser shows both TDT and TOT on the left but only TOT on the right. Quote
Griga Posted June 30, 2015 Posted June 30, 2015 in normal cases when both table_ids are present, the analyser shows both TDT and TOT on the left but only TOT on the right. This is ok, because the list on the right is a PID list, not a table list. However, TOT/TDT would be clearer, as well as SDT/BAT that share PID 17. Only a TDT is broadcasted in your case, so that's what you get in the Hex Viewer. There is nothing wrong about it. Quote
Derrick Posted June 30, 2015 Posted June 30, 2015 There is nothing wrong about it. ..it's at least misleading and inconsistent. The hex view contains only 0x70 but is called TOT which should read 0x73 and left and right have different names for the same stream. Quote
Antonio Posted July 1, 2015 Posted July 1, 2015 small bug of a form Transedit without transponders. Quote
Griga Posted July 1, 2015 Posted July 1, 2015 Nice effect TransEdit doesn't know what to do, so it tries to do everything at the same time at this point. Sometimes software acts like humans. Quote
EnoSat Posted March 6, 2016 Author Posted March 6, 2016 (edited) Hi, why analyse only stream from http source ? [sATTYPE] 1=6500 2=TS Stream Net:0 [DVB] 0=11 1=http://stream.zivekamery.sk/live/KUBINSKA1.stream/playlist.m3u8|tuning error 2=http://stream.zivekamery.sk:1935/live/KUBINSKA1.stream/playlist.m3u8|Kubinska hola 2k port 1935 3=rtmp://stream.zivekamery.sk/live/KUBINSKA1.stream|tuning error 4=rtmp://stream.zivekamery.sk/live/KUBINSKA1.stream.flv|tuning.error 5=rtmp://stream.zivekamery.sk:1935/live/KUBINSKA1.stream|waaaiiitttiiinnng 6=rtmp://stream.zivekamery.sk:1935/live/KUBINSKA1.stream.flv|waaaiiitttiiinnng 7=rtsp://stream.zivekamery.sk/live/KUBINSKA1.stream|tuning error 8=rtsp://stream.zivekamery.sk/live/KUBINSKA1.stream.flv|tuning.error 9=rtsp://stream.zivekamery.sk:1935/live/KUBINSKA1.stream|the server cannot provide the request transponder 10=rtsp://stream.zivekamery.sk:1935/live/KUBINSKA1.stream.flv|the server cannot provide the request transponder 11=stream.zivekamery.sk:1935/live/KUBINSKA1.stream/playlist.m3u8|tuning error 2=http://stream.zivekamery.sk:1935/live/KUBINSKA1.stream/playlist.m3u8|Kubinska hola 2k port 1935 Edited March 6, 2016 by EnoSat Quote
Griga Posted March 7, 2016 Posted March 7, 2016 Sorry, rtmp (flash): no go rtsp: only if it conforms with the Sat>IP specifications, as delivered by the Recording Service. http: must deliver a transport stream (pure TS or conforming with the HLS protocol that additionally uses m3u8 playlists). udp/rtp: must contain a transport stream 1 Quote
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.