Es pes ts Stream difference

The digital signal actually transmits data streams. Generally, the data streams include the following three types: ES is the original code stream, and contains the continuous code streams of video, audio, or data. Ts is a transmission stream consisting of 188 bytes in a fixed length. It contains one or more programs with independent time bases and is suitable for environments with many error codes.
We all know that the TS package starts with 0x47 and is a Synchronization Byte. Each packet is 188 bytes long. So we can easily synchronize ts streams, such as packet loss. You only need to find n consecutive (for example, 5) 188-length ts packages. If they all start with 0x47, these packages can basically be considered as valid ts packages. PES is the basic code stream generated by packaging. It divides the basic code stream es into packets of varying length as needed, and adds a header to form the packaged basic code stream PES. PS is a program stream. The difference between PS stream and TS stream is that the packet structure of PS stream is variable length, while the packet structure of TS stream is fixed length. In a MPEG-2 system, the standard information flow generated by the es stream of video, audio and secondary data is called the MPEG-2 Transfer Stream for actual transmission. The process of information combination/separation is called system re-connection/sub-connection. According to the different quality of the transmission media, two composite information flows are defined in the MPEG-2: transmission stream (TS) and program flow (PS: programstream)

The difference between TS stream and PS stream is that the packet structure of TS stream is fixed length, while the packet structure of PS stream is variable length. The difference in the structure of the PS package and the TS package leads to different resistance to the transmission error code, so the application environment is also different. The ts code stream adopts a fixed-length packet structure. When the transmission error code breaks the synchronization information of a TS packet, the receiver can detect the synchronization information in the bread at a fixed position, in this way, synchronization is resumed to avoid information loss. The length of the PS package varies. Once the synchronization information of a PS package is lost, the receiver cannot determine the synchronization location of the next package, which may lead to a loss of data and serious loss of information. Therefore, TS code streams are generally used when the channel environment is poor and the transmission error code is high. When the channel environment is good and the transmission error code is low, generally, the PS code stream is used because the TS code stream has strong ability to resist the transmission error code, so the MPEG-2 code streams transmitted in the transmission media are basically using the TS code stream package.
The encoder generates ts streams and the transmission interface is the ASI port. The whole function of the encoder is to convert the analog signal into es, package it into PES, and then package it into TS stream output. Multiplex combines multiple single programs or multi-program TS streams into one multi-program TS streams, and then sends them to the synthesizer. The digital satellite receiver is a TS stream and also an ASI interface, which may contain one or more programs, and some may also have one analog signal for audio and video output. A satellite receiver is used to simulate audio and video signals.
Real-Time Transport Protocol (RTP) is a network transmission protocol. The RTP protocol details the standard packet formats for transmitting audio and video on the Internet. It was initially designed as a multicast protocol, but was later used in many unicast applications. RTP is often used in streaming media systems (with RTCP protocol), video conferencing and one-click push to talk systems (with H.323 or sip), making it the technical basis of the IP telephone industry. The RTP protocol is used together with the RTP control protocol RTCP, And it is built on the User Datagram Protocol. The RTP packet is a fixed byte of 12 bytes, followed by N optional CSRC (the number is determined by a field of the first 12 bytes ). Then, the extension package may exist, and the number of bytes is also determined in the extension field.