International organisation for standardisation organisation internationale de normalisation

9.3Action Points

10MPEG-4 File Format (14496-14)

10.1Topics

10.1.1ISO/IEC 14496-14:2003 AMD 1 Handling of MPEG-4 Audio enhancement layers

10.2Contributions

10.3Action Points

11MPEG-4 AVC File Format (14496-15)

11.1Topics

11.1.1ISO/IEC 14496-15:2004/FPDAM 3 MVC File Format

11.2Contributions

Session	Number	Title	Source
File Format	m16361	Extractors in the MVC file format	Anthony Vetro David Singer
File Format	m16426	On MVC File Format	Miska M. Hannuksela
File Format	m16444	Comments to the MVC file format draft	Ye-Kui Wang Miska Hannuksela
File Format	m16445	A proposal to MVC file format	Ye-Kui Wang

11.2.1m16361 Extractors in the MVC file format

We will try this in the study. We need to document the relationship between operating point and mvc2 tracks, and also if the mvc2 tracks are dense (in the sense that all views are decoded). We need to have three sample entry types to satisfy different usage models:

• 
  mvc1 - pure mvc data, maybe using aggregators
  
• 
  mvc2 - mvc and extractors and aggregators
  
• 
  mvc3 –only: extractors and aggregators, i.e. no VCL NAL units
  

The editors should try making a single common definition for avc2.

We do indeed need an informative section on these ‘usage models’ that will attempt to relay our hard-won understanding to future readers. That text should cover something like:

“The support for MVC includes a number of tools, and there are various ‘models’ of how they might be used. In particular, an MVC stream can be placed in tracks in a number of ways, among which are the following:

1. 
   all the views in one track, labeled with sample groups;
   
2. 
   each view in its own track, labeled in the sample entries;
   
3. 
   a hybrid, one track with the whole set, and other one-view tracks for some or all of the independent views;
   
4. 
   the expected operating points each in a track (e.g. the AVC base, a stereo pair, a multiview scene).”