[M4IF Technotes] FW: [M4IFmembers] Stream ID Assignment in MPEG-4 Start-codes and MPEG-2 System Draf t Amendments

[Rob Koenen]

Let's move to the Technotes list.
Rob
-----Original Message-----
From: Munsi Haque [mailto:
Sent: Wednesday, September 26, 2023 9:34 AM
To: M4IF member list (E-mail)
Subject: [M4IFmembers] Stream ID Assignment in MPEG-4 Start-codes and MPEG-2
System Draf t Amendments
Dear Members :
We have noticed the following issues in the ISO Working Group-11 documents:
1) In document w3908.doc, Table-21 specifies the start-codes with stream ID,
as shown below . These start-codes are for MPEG-4 specific visual  streams.
The start-codes with streamID C0 to C5 are assigned for MPEG-4 specific
streams.  Also so far I could not locate the start code C6 through FF as
System Start Code, in the corresponding System Spec, w3561.doc.
BM__Ref461688497                                                 Table 21:
Start Code Values
name
start code value
(hexadecimal)
video_object_start_code
00 through 1F
video_object_layer_start_code
20 through 2F
reserved
30 through 3F
fgs_bp_start_code
40 through 5F
reserved
60 through AF
visual_object_sequence_start_code
B0
visual_object_sequence_end_code
B1
user_data_start_code
B2
group_of_vop_start_code
B3
video_session_error_code
B4
visual_object_start_code
B5
vop_start_code
B6
slice_start_code
B7
extension_start_code
B8
fgs_vop_start_code
B9
fba_object_start_code
BA
fba_object_plane_start_code
BB
mesh_object_start_code
BC
mesh_object_plane_start_code
BD
still_texture_object_start_code
BE
texture_spatial_layer_start_code
BF
texture_snr_layer_start_code
C0
texture_tile_start_code
C1
texture_shape_layer_start_code
C2
stuffing_start_code
             C3
reserved
C4-C5
System start codes (see note)
C6 through FF
NOTE  System start codes are defined in ISO/IEC 14496-1
 2) In document w3845.doc (ISO/IEC 13818-1: 2000: Proposed Draft Amednment
1: Transport of Metadata), Table 2-18 shows the following:
                                 Table 2-18 -- Stream_id assignments 
Stream_id
Note
stream coding
1011 1100
1
program_stream_map
1011 1101
2
private_stream_1
1011 1110
padding_stream
1011 1111
3
private_stream_2
110x xxxx
ISO/IEC 13818-3 or ISO/IEC 11172-3 or ISO/IEC 13818-7 or ISO/IEC 14496-3
audio stream number x xxxx   
1110 xxxx
ITU-T Rec. H.262 | ISO/IEC 13818-2 or ISO/IEC 11172-2 or ISO/IEC 14496-2
video stream number xxxx
1111 0000
3
ECM_stream
1111 0001
3
EMM_stream
1111 0010
5
ITU-T Rec. H.222.0 | ISO/IEC 13818-1 Annex A or ISO/IEC 13818-6_DSMCC_stream
1111 0011
2
ISO/IEC_13522_stream
1111 0100
6
ITU-T Rec. H.222.1 type A
1111 0101
6
ITU-T Rec. H.222.1 type B
1111 0110
6
ITU-T Rec. H.222.1 type C
1111 0111
6
ITU-T Rec. H.222.1 type D
1111 1000
6
ITU-T Rec. H.222.1 type E
1111 1001
7
ancillary_stream
1111 1010
ISO/IEC14496-1_SL-packetized_stream
1111 1011
ISO/IEC14496-1_FlexMux_stream
1111 1100
descriptive data stream
1111 1101
reserved data stream
1111 1110
reserved data stream
1111 1111
4
program_stream_directory
As you see in the above table, if the MPEG-4 audio streams are carried in
MPEG-2 System packets (PES), then the streamID 0xC0 to 0xDF are used for
audio stream.
3) So there could be some mismatches, if those MPEG-4 streams of  
                 "texture_snr_layer_start_code  C0" 
                  " texture_tile_start_code  C1 " 
                  " texture_shape_layer _start_code  C2 " 
                  " stuffing _start_code  C3 " 
or "reserved  C4 -C5" are carried by MPEG-2 system streams. [Munsi Haque] Is
it a serious mismatch ?
Also it may be noted that w3845.doc is a PROPOSED DRAFT AMENDEMNT, and so it
is not final yet perhaps .
Best regards ,
Munsi Haque
TVIA, Inc.
4001 Burton Drive, Santa Clara, CA 95054, USA
e-mail: mhaque   tvia.com <mailto:mhaque   tvia.com>  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/mp4-tech/attachments/20010926/c984f899/attachment.html