2.1AHG reports
Number
|
Session
|
Title
|
Source
|
Dispositions
|
m20277
|
Plenary
|
Ad Hoc on MPEG File Formats
|
David Singer, Per Fröjdh
|
Accepted
|
m20278
|
Plenary
|
Ad Hoc on Application Format
|
Kyuheon Kim, Kugjin Yun, Gero Baese
|
Accepted
|
m20279
|
Plenary
|
Ad Hoc on Font Format Representation
|
Vladimir Levantovsky
|
Accepted
|
m20280
|
Plenary
|
Ad Hoc on MPEG-M
|
Xin Wang, Youngkwon Lim
|
Accepted
|
m20281
|
Plenary
|
Ad Hoc on MPEG-V
|
Marius Preda
|
Accepted
|
m20282
|
Plenary
|
Ad Hoc on Contract Expression Language
|
Xin Wang, Jaime Delgado
|
Accepted
|
m20283
|
Plenary
|
Ad Hoc on Dynamic Adaptive Streaming over HTTP
|
Iraj Sodagar, David Singer, Youngkwon Lim
|
Accepted
|
m20284
|
Plenary
|
Ad Hoc on MPEG Media Transport
|
Youngkwon Lim, Mohammed Raad
|
Accepted
|
m20289
|
Plenary
|
Ad Hoc on Audio Visual Description Profile
|
Masanori Sano, Jean-Pierre Evain
|
Accepted
|
All AHG reports are accepted.
2.2General technical contributions
Number
|
Session
|
Title
|
Source
|
Dispositions
|
m21150
|
Plenary
|
Table of Replies on ISO/IEC 13818-1:2007/FDAM 5
|
ITTF via SC 29 Secretariat
|
Noted
|
m21151
|
Plenary
|
Table of Replies on ISO/IEC 13818-1:2007/FDAM 6
|
ITTF via SC 29 Secretariat
|
Noted
|
m20305
|
Plenary
|
Table of Replies on ISO/IEC 14496-5:2001/FDAM 28 [SC 29 N 12017]
|
ITTF via SC 29 Secretariat
|
Noted
|
m21112
|
Plenary
|
Table of Replies on ISO/IEC 15938-12:2008/FDAM 2
|
ITTF via SC 29 Secretariat
|
Noted
|
m21108
|
Plenary
|
Table of Replies on ISO/IEC 21000-2:2005/FDAM 1
|
ITTF via SC 29 Secretariat
|
Noted
|
m21109
|
Plenary
|
Table of Replies on ISO/IEC 21000-4:2006/FDAM 2
|
ITTF via SC 29 Secretariat
|
Noted
|
m20320
|
Plenary
|
Table of Replies on ISO/IEC 23000-11:2009/FDAM 1
|
ITTF via SC 29 Secretariat
|
Noted
|
m21110
|
Plenary
|
Table of Replies on ISO/IEC 23000-12:2010/FDAM 1
|
ITTF via SC 29 Secretariat
|
Noted
|
m20409
|
Plenary
|
Table of Replies on ISO/IEC FDIS 23005-2
|
ITTF via SC 29 Secretariat
|
Noted
|
m20321
|
Plenary
|
Table of Replies on ISO/IEC FDIS 23005-3
|
ITTF via SC 29 Secretariat
|
Noted
|
m20410
|
Plenary
|
Table of Replies on ISO/IEC FDIS 23005-4
|
ITTF via SC 29 Secretariat
|
Noted
|
m20411
|
Plenary
|
Table of Replies on ISO/IEC FDIS 23005-5
|
ITTF via SC 29 Secretariat
|
Noted
|
m20306
|
Plenary
|
Table of Replies on ISO/IEC FDIS 23005-6 [SC 29 N 12018]
|
ITTF via SC 29 Secretariat
|
Noted
|
m20318
|
Plenary
|
Table of Replies on ISO/IEC FDIS 23006-1
|
ITTF via SC 29 Secretariat
|
Noted
|
m20322
|
Plenary
|
Table of Replies on ISO/IEC FDIS 23006-2
|
ITTF via SC 29 Secretariat
|
Noted
|
m20856
|
Plenary
|
Table of Replies on ISO/IEC FDIS 23007-3
|
ITTF via SC 29 Secretariat
|
Noted
|
m20399
|
Plenary
|
Panel discussion: The MPEG “standards factory†meets Italian ICT industry Torino, Museo dell’Automobile, 2011/07/20T18:30-20:00
|
Leonardo Chiariglione
|
Noted
|
m21222
|
Plenary
|
Usage of RVC in MPEG Systems
|
Jean Le Feuvre, Mickael Raulet, Jérome Gorin, Françoise Préteux
|
Noted
|
m21379
|
Plenary
|
Information about the possible revision of 21000-2 AMD1 and 21000-4 AMD2
|
Tiejun Huang
|
Noted
|
m21178
|
Plenary
|
AVDP AHG report
|
EBU, NHK
|
Noted
|
m21196
|
Plenary
|
MPEG-H Vision
|
Jaeyeon Song
|
Accepted
N12247, N12248
|
m21303
|
Plenary
|
Proposal to extend MPEG-21 DII with means to support a semantically explicit declaration of relationships between Digital Items
|
Teresa Andrade (INESC Porto), Helder Castro (INESC Porto)), Leonardo Chiariglione (CEDEO), Aziz Moussas (NTUA), Giuseppe Tropea (CNIT),
|
Accepted
N12147
|
m21300
|
Plenary
|
The CONVERGENCE project – A bird’s eye view
|
Leonardo Chiariglione (CEDEO), Stefano Salsano (CNIT), Giuseppe Tropea (CNIT)
|
Noted
|
m21299
|
Plenary
|
Schedule of events during the ISO meetings in Torino (2011/07/14-23)
|
Leonardo Chiariglione
|
Noted
|
m21286
|
Plenary
|
MIME type for MPEG-2 Transport Streams David Singer, Thomas
|
MIME type for MPEG-2 Transport Streams David Singer, Thomas
|
Accepted
N12172
|
m21271
|
DASH
|
Coding-independent Code-Points
|
David Singer, Thomas Stockhammer
|
Accepted
N12172
|
m21381
|
DASH
|
Information about the possible revision of 21000-2 AMD1 and 21000-4 AMD2
|
Tiejun Huang
|
Noted
|
m21300
Introduction of CONVERGENCE project targeting content centric network with semantic contents discovery by using MPEG standard. It is advised to consider MMT, too.
m21303
Proposal to introduce ontology based inter-DI relationship in DID by extending DII, dii:Relationships. This contribution also proposed to standardize core ontology for relationship
3MPEG-2 Systems (13818-1) 3.1Topics 3.1.1ISO/IEC 13818-1:2007 AMD 7 Signalling of frame compatible and service compatible stereoscopic video 3.1.2ISO/IEC 13818-1:2007 AMD 8 Simplified carriage of MPEG-4 over MPEG-2
3.2Contributions
Number
|
Session
|
Title
|
Source
|
Dispositions
|
m20315
|
MPEG-2
|
Summary of Voting on ISO/IEC 13818-1:2007/PDAM 7
|
SC 29 Secretariat
|
Accepted
N12114, N12115
|
m21139
|
MPEG-2
|
Summary of Voting on ISO/IEC 13818-1:2007/PDAM 8
|
SC 29 Secretariat
|
Accepted
N12140, N12116
|
m21223
|
MPEG-2
|
Editors input for text of PDAM8 of 13818-1
|
Jean Le Feuvre, Cyril Concolato,
|
Accepted
N12116
|
m21225
|
MPEG-2
|
Carriage of BIFS over MPEG-2 TS
|
Jean Le Feuvre
|
Accepted
N12116
|
m20315
The GNB requests additional information in the document about the two methods for signalling stereoscopic content in PDAM 7, i.e. (1) using different stream types or (2) using descriptor(s) with an existing stream type.
The GNB thinks, that more clarifying text is required in subclause 2.4.4.9 in addition to Note3. Especially, text is required discussing potential problems for existing receivers. Furthermore the GNB would appreciate an improvement of the definition of or the inclusion of appropriate notes for the two descriptors in the subclauses 2.6.82 to 2.6.87 in order to notify the reader about the aforementioned potential implications for existing receivers.
Regarding to frame compatible mode, it is requested to enhance its consistency with ISO/IEC 13818-2/DAM 4. Specifically, the following two modifications as described in the output document (WG 11 N 11913) are requested:
- Signal MPEG-2 video with frame compatible mode based on ISO/IEC 13818-2/DAM 4 by using the existing stream_type value of 0x02, that is, MPEG-2 systems defines only stream_type value of 0x02 for MPEG-2 video with the frame compatible mode;
- Change the syntax name "stereo_scopic_video_format" in MPEG2_stereoscopic_video_format_descriptor() to"arrangement_type".
Regarding to service compatible mode, it is requested to improve the usability of the new descriptors. Specifically, the following three modifications as described in the output document (WG 11 N 11913) are requested:
- Change the syntax name "2D_view_flag" in Stereoscopic_program_info_descriptor() to "usable_as_2D" and move its signaling location to Stereoscopic_ video_info_descriptor();
- Mandate that Stereoscopic_video_info_descriptor() shall be included for both the base view video stream component and additional view video component in the PMT;
- Define a value of upsampling factor syntaxes that decoders are expected to use the information in the video elementary stream to determine appropriate upsampling factors.
Regarding to service compatible mode, it is requested to specify each of stereoscopic service types (2D (monoscopic) service, Frame compatible stereoscopic 3D service, and Service-compatible stereoscopic 3D service).
Regarding to service compatible mode, if the second JNB comment is adopted and the third JNB comment is not adopted, it is requested to remove Stereoscopic_program_info_descriptor() from this amendment.
PDAM 7 listed 2 extensions – (1) Additional stream_type to signal frame compatible use and (2) Descriptor.
The expectation is that all MPEG-2 receivers and systems that will support 3D would be upgradable to process a new descriptor or a new stream_type or both.
MPEG-2 receivers and systems that do not support 3D need to ignore services that contain 3D. This requires them to process the new descriptor if option 1 is chosen which in turn requires these devices to be capable of being upgraded.
There are a part of such receivers and devices that may not be capable of being upgraded to process the new descriptor. However, these systems do not acquire a service for which it does not recognize a new stream_type.
Members agreed to a proposal where MPEG would specify a new stream_type and descriptor to signal frame compatible MPEG-2 video content where both these syntax elements will not be normative. Application standards could mandate these syntax elements (like AVC SEI).
Study text removed the use of new stream_type (0x22) as members felt that all MPEG-2 receivers can be upgraded to process descriptor.
-
USNB requests using study text.
Proposal for MPEG-2 system level signaling for frame compatible 3D component
-
Stream_type = 0x02 continues to signal MPEG-2 video coded service component (both 2D only or 3D frame compatible).
-
New descriptor type (0x34 or 52) is used to include additional information about the ‘frame compatible’ component (such as frame packing arrangement type). The descriptor must be used with stream_type = 0x02 to signal 3D frame compatible component.
-
Example PMT’s:
-
2d only will just have one video component with stream_type =0x02 and no descriptor.
-
3d frame compatible component is signaled using stream_type = 0x02 with the new descriptor (normative).
Proposal for MPEG-2 system level signaling of service compatible component streams
-
Stream_type = 0x02 continues to signal MPEG-2 2d-only base layer service component.
-
Stream_type = 0x1B continues to signal AVC 2d-only base layer service component.
-
New stream_types (= 0x22 and 0x23) is used to signal service compatible enhancement component for MPEG-2 and AVC respectively. The enhancement can compressed independent of base layer using either MPEG-2 or AVC video. A new stream_type is suggested instead of stream_type values of 0x02 (MPEG-2 video) or stream_type = 0x1B (AVC video) so that receivers do not decode the enhancement only and render the decoded video.
-
Two new descriptors (0x35 or 53 and 0x36 or 54) are proposed to include information on the ‘service compatible’ enhancement. This will include the type of codec, composition information etc.
Dostları ilə paylaş: |
