[Mp4-tech] H264

[Gary Sullivan]

Regarding Natrajan's comment about the cost of ISO/IEC 13818-1/AMD 3:
Note that ISO/IEC 13818-1 is a common-text standard with ITU-T H.222.0.
See http://tinyurl.com/cg2ae.
And anyone can get a copy of three ITU-T standards for free.  A link to
how to do that can always be found on the MPEG-IF web site resources
page.  (Just click on "I wish to REGISTER in order to download up to
three (3) Recommendations free of charge" on the web page
http://ecs.itu.ch/cgi-bin/ebookshop).
If you need to pay instead of get a copy for free (e.g., if you have
already gotten three free from the ITU), then I think ISO's price is
cheaper in this case.  In some other cases of common-text standards, you
will find the ITU price to be cheaper.
Best Regards,
Gary Sullivan
+> -----Original Message-----
+> From: mp4-tech-bounces lists.mpegif.org 
+> [mailto:mp4-tech-bounces lists.mpegif.org] On Behalf Of Rob 
+> Koenen (MPEGIF)
+> Sent: Sunday, September 25, 2023 1:47 PM
+> To: mp4-tech lists.mpegif.org
+> Cc: natarajanv nds.com
+> Subject: FW: [Mp4-tech] H264
+> 
+> Forwarding message that was discarded because sending 
+> address was not on the
+> list.
+> 
+> Rob
+> 
+> -----Original Message-----
+> From: Vittal, Natarajan [mailto:natarajanv nds.com] 
+> Sent: Sunday, 25 September 2023 16:48
+> To: hong Liu; mp4-tech lists.mpegif.org
+> Subject: RE: [Mp4-tech] H264
+> 
+> Hong Liu,
+> 
+> Please refer to ISO IEC 13818-1 Amendment 3, for carrying 
+> AVC (also known as
+> H.264 or MPEG-4 part 10) in MPEG-2 TS. You can get this doc 
+> from the ISO
+> store. It is not expensive. This document lists all the 
+> changes needed to
+> carry AVC over MPEG-2. As an illustration stream type is 
+> 0x1B indicating a
+> H.264 stream. Similarly stream type for carrying
+> MPEG-4 SL or FlexMux streams, IPMP streams, etc. in MPEG-2 
+> TS are defined.
+> There are a good number of changes, which you can better 
+> understand by
+> looking at the spec indicated above. 
+> 
+> As regarding transporting H.264 over other transport 
+> protocols they are
+> defined under respective protocol definitions. As examples 
+> if you have to
+> stream H.264 over RTP you can use RFC 3984, the RTP Payload 
+> Format for
+> MPEG-4 Audio/Visual Streams is RFC 3016, the RTP Payload Format for
+> MPEG-4 system stream is RFC 3460. A look at the DMIF spec 
+> will give you a
+> general idea.
+> 
+> Hope above info gives you some lead.
+> 
+> Regards,
+> Natrajan
+> 
+> 
+> -----Original Message-----
+> From: mp4-tech-bounces lists.mpegif.org
+> [mailto:mp4-tech-bounces lists.mpegif.org] On Behalf Of hong Liu
+> Sent: Friday, September 23, 2023 7:39 PM
+> To: mp4-tech lists.mpegif.org
+> Subject: [Mp4-tech] H264
+> 
+> Hello, 
+> 
+> I am wondering if there is a way to wrap the H264 video file 
+> and other audio
+> files to any transport layer format (like mpeg-2 transport stream). 
+> 
+> BTW: like mpeg-4, is there standard to wrap mpeg-4 system stream to
+> mpeg-2 transport stream?
+> 
+> Thanks experts to give me any hints.
+> 
+>  
+> 
+> 
+> 
+> 		
+> __________________________________
+> Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
+> _______________________________________________
+> NOTE: Please use clear subject lines for your posts. Include [audio,
+> [video], [systems], [general] or another apppropriate 
+> identifier to indicate
+> the type of question you have.
+> 
+> Note: Conduct on the mailing list is subject to the 
+> Antitrust guidelines
+> found at
+> http://www.mpegif.org/public/documents/vault/mp-out-30042-Ant
+> itrust.php
+> 
+> 
+> *************************************************************
+> ***************
+> *******
+> Information contained in this email message is intended only 
+> for use of the
+> individual or entity named above. If the reader of this 
+> message is not the
+> intended recipient, or the employee or agent responsible to 
+> deliver it to
+> the intended recipient, you are hereby notified that any 
+> dissemination,
+> distribution or copying of this communication is strictly 
+> prohibited. If you
+> have received this communication in error, please 
+> immediately notify the
+> postmaster in.nds.com and destroy the original message.
+> *************************************************************
+> ***************
+> **********
+> 
+> 
+> _______________________________________________
+> NOTE: Please use clear subject lines for your posts. Include 
+> [audio, [video], [systems], [general] or another 
+> apppropriate identifier to indicate the type of question you have.
+> 
+> Note: Conduct on the mailing list is subject to the 
+> Antitrust guidelines found at 
+> http://www.mpegif.org/public/documents/vault/mp-out-30042-Ant
+> itrust.php
+>