Talk:MPEG transport stream/Archive 1

Cuts

Hope nobody gets too worried by the amount I just cut out, but there was just too much wrong and confused stuff. This article still needs major help. The bottom stuff is just sort of random unstructured meandering around things that are vaguely related. Preferably, most of that would be cut out, or at least organized, and the article would be fleshed out with stuff like specification details and applications.Snacky 05:36, 27 May 2006 (UTC)

State was is wrong or confused or clean it up. I'll restore some of it. Appreciate your additions, they look very nice. Daniel.Cardenas 14:12, 27 May 2006 (UTC)

Hardware interface

Is there a standard hardware interface that people use to get the transport stream from one device to another? DVB vaguely mentions "a synchronous parallel interface (SPI), synchronous serial interface (SSI), or asynchronous serial interface (ASI)".

But asynchronous serial interface focuses on ASCII over RS-232. So do people really send video over RS-232? If not, what (specifically) *do* people use to carry video from one device to another? —Preceding unsigned comment added by 65.70.89.241 (talk • contribs) 15:30, 10 August 2006

You can use whatever you want. For digital video equipment, ASI over BNC-terminated coax is probably the most common mechanism, making it something of a de facto requirement within the industry. But there's nothing that says you HAVE to use it (why should there be)? Snacky 18:33, 10 August 2006 (UTC)

Sample of tools: Verticle lists versus Horizontal

What is the point of making the lists vertical and creating all that white space? I prefer the more compact horizontal list. Daniel.Cardenas 16:29, 27 December 2006 (UTC)

Hey, what about VLC player?

VLC player can play TS files too, so I think it should be included in the tools... 216.49.71.146 19:42, 25 September 2007 (UTC)

I think the purpose of the tools section, are tools that help analyze the transport stream, more then superficially viewing the contents. Daniel.Cardenas 01:28, 26 September 2007 (UTC)

PID? Program Number ?

In "Program" section, it reads:

  Transport stream has a concept of programs. A single program has a unique PID and 
  the elementary streams associated with that program have the same PID.

A single program has a unique program_number, not PID, doesn't it? —Preceding unsigned comment added by Motonari (talk • contribs) 16:19, 29 September 2007 (UTC)

I'm not aware of program numbers, where are they? I am aware of PIDs in the TS packet header. Daniel.Cardenas 17:18, 29 September 2007 (UTC)

program_number is a unique numeric value to identify a program, which is coded in PAT. You can find a formal definition in ISO/IEC 13818-1 2.4.4.3. Motonari 18:02, 29 September 2007 (UTC)

Purpose of slice

In Layers of communication, the explanation of slice says

 lowest layer that encoder can change DCT coding values to manage bit rate

I'm not sure where this explanation come from. The only bit rate related parameter in splice is quantiser_scale_code (ISO/IEC 13818-2 6.3.16) but even this parameter can be changed in macroblock layer.

The purpose of slice is not explicitly explained in the standard, but it's obvious based on the syntax; it's an error propagation preventer. Since all intra predictions and motion vectors are reset at the start of each slice, errors in a splice are not propagated to another slice. —Preceding unsigned comment added by Motonari (talk • contribs) 01:05, 30 September 2007 (UTC)

M2TS

What about M2TS which has 192 bytes per packet? Mikus (talk) 01:45, 23 January 2008 (UTC)

Nice job on the edit. :-) Thanks! Daniel.Cardenas (talk) 04:32, 23 January 2008 (UTC)

wrong template?

While the text at the beginning of the article lines nicely with the box on the right, if you look at the subsequent sections you see that the text column (on the left) is too near to the boxes on the right, to the point that it touches them. I suspect it is a bug in the template used, could anyone with the right knowledge correct the problem? --Pot (talk) 13:26, 8 May 2009 (UTC)

SPTS, TP, M2T ?

I don't think "SPTS", "TP" or "M2T" are widely used abbreviations for describing an MPEG transport stream.

• What is "TP"? Does that mean "Transport Protocol"? If so, I think it is wrong, because there are various transport protocols.
• "SPTS" is used for a Single-Program Transport Stream, but AFAIK that is only one particular type of MPEG Transport Stream. There is also MPTS - Multi Program Transport Stream. I think these abbreviations are not typically used for "any" MPEG Transport stream.
• M2T - I think it is used as a filename extension ".m2t" and not as an abbreviation for MPEG transport stream (or am I wrong?). Filename extensions should be placed in the file type infobox and not as an "other name" for the article. (Look at MPEG program stream article.)

--89.173.66.229 (talk) 17:24, 8 June 2010 (UTC)

Perhaps you are right. Anyways, they lack citations. I'm deleting them. Fleet Command (talk) 19:25, 8 June 2010 (UTC)