International organisation for standardisation

3.4Action Points

4MPEG-4 Conformance (14496-4)

4.1Topics

4.1.1ISO/IEC 14496-4:2004 AMD 40 ExtendedCore2D profile conformance

4.2Contributions

Number	Session	Title	Source		Dispositions
m20328	Scene	Summary of Voting on ISO/IEC 14496-4:2004/DAM 40	SC 29 Secretariat	None

4.3Summary of discussions

4.4Action Points

5MPEG-4 Reference Software (14496-5)

5.1Topics

5.1.1ISO/IEC 14496-5:2001 AMD 29 Reference software for PMSI for LASeR

5.1.2ISO/IEC 14496-5:2001 AMD 30 ExtendedCore2D profile reference software

5.2Contributions

Number	Session	Title	Source	Dispositions
m20329	Scene	Summary of Voting on ISO/IEC 14496-5:2001/DAM 29	SC 29 Secretariat	Accepted N12118
m20333	Scene	Summary of Voting on ISO/IEC 14496-5:2001/DAM 30	SC 29 Secretariat	Accpted N12119 N12120

5.3Summary of discussions

5.4Action Points

• 
  .
  

6MPEG-4 BIFS (14496-11)

6.1Topics

6.1.1Exploration

• 
  Remote and Collaborative work
  

6.2Contributions

Number	Session	Title	Source		Dispositions
m21161	Scene	Use Cases for Collaborative Applications	Jamie MARSHALL, Mihai MITREA, Bojan JOVESKI, Francoise PRETEUX	Accepted N12208
m21162	Scene	Draft Context and Objectives for MPEG Scene Technology with Collaborative Applications	Jamie MARSHALL, Mihai MITREA, Bojan JOVESKI, Ludovico GARDENGHI, Francoise PRETEUX	Accepted N12207
m21163	Scene	Draft Requirements on MPEG Scene Technology for Collaborative Applications	Jamie MARSHALL, Mihai MITREA, Bojan JOVESKI, Ludovico GARDENGHI, Francoise PRETEUX	Accepted N12206
m21164	Scene	Draft Call for Proposals for Scene Technologies for Collaborative Applications	Jamie MARSHALL, Mihai MITREA, Bojan JOVESKI, Ludovico GARDENGHI, Francoise PRETEUX	Accepted N12209
m21165	Scene	Collaboration Technology Mandate Report: Cross-media collaboration	Bojan JOVESKI, Ludovico GARDENGHI, Mihai MITREA, Rama Rao Ganji, Iain James MARSHALL, Françoise PRETEUX	Noted

6.3Summary of discussions

m21165

demonstration of a new framework enabling cross-media collaboration, i.e. allowing users to collaborate within the same scene but using different types of media (BIFS vs. LASeR)

This application needs a standardized “hook” to convey information for collaborative client (similar to video decoder) and format for generalized description to be conveyed.
This could be a good item for application format standard.

6.4Action Points

7MPEG-4 ISO Base File Format (14496-12)

7.1Topics

7.1.1ISO/IEC 14496-12:2008/AMD 2 Support for sub-track selection & switching, post-decoder requirements, and color information

7.1.2ISO/IEC 14496-12:2008/AMD 3 DASH support and RTP reception hint track processing

7.1.3ISO/IEC 14496-12:2008/AMD 4 MP4 files as a playlist using file tracks

7.2Contributions

Number	Session	Title	Source	Dispositions
m21319	File Format	ISOBMFF: Comments on FPDAM2.2	Miska M. Hannuksela	Deferred
m21321	File Format	On Movie Fragments and Edit Lists, for 14496-12 (ISO Base Media File Format)	David Singer	accepted N12124 N12125
m21327	File Format	Clarifying Random Access Points and Sync Samples in the file format	David Singer	Deferred
m21136	File Format	ISOBMFF: Controlling Sample Timing in Fragmented Files	Miska M. Hannuksela	Accepted N12124 N12125
m20400	File Format	DASH: Representation timeline alignment for ISO BMFF	Mark Watson	Accepted N12124 N12125
m21272	File Format	Two minor issues with movie fragments in the Part 12 format	David Singer	Accepted N12124 N12125
m20334	File Format	Summary of Voting on ISO/IEC 14496-12:2008/DAM 3 & ISO/IEC 15444-12:2008/DAM 3	SC 29 Secretariat	Finland, France, Germany, Japan, Sweden, UK, USA
m21144	File Format	ISOBMFF: Support for incomplete tracks	Miska M. Hannuksela	Accepted N12126
m21145	File Format	ISOBMFF: Editorial update of Annex H of DAM3	Miska M. Hannuksela	Accepted N12124 N12125
m21121	File Format	ISO base media file format: 'stdp' box	Ye-Kui Wang	Accepted N12124 N12125
m21201	File Format	Proposed update to ISO/IEC 14496-12 ISO base media file format applying 32bit indexing for itemID and item_count	Noboru Harada, Takehiro Moriya, Yutaka Kamamoto,	Accepted N12126
m21296	File Format	File Format – on stereoscopic video indication	Jaeyeon Song, Sungryeul Rhyu, Kyungmo Stanley Park, Kwang-Cheol Choi, Gun-Ill Lee, Kyuheon Kim, Jangwon Lee	Deferred
m21359	File Format	On M2TS compression as file format hint track	Waqar Zia, Alex Kyungho Kim	Accepted N12126
m20430	File Format	Extend ISO/IEC File Format with Error Correction for Multimedia Preservation	Walter Allasia, Wo Chang	Deferred
m21096	DASH	DASH: Indication of Subsegments Starting with SAP	Miska M. Hannuksela, Ye-Kui Wang	Accepted N12124 N12125
m21435		ISOBMFF: SAP definitions and 'sidx' box Miska M. Hannuksela	ISOBMFF: SAP definitions and 'sidx' box Miska M. Hannuksela	Accepted N12124 N12125

7.3Summary of discussions

m21321

Accepted in general; allow in the file format the edit that establishes the mapping, ensure that the segment index talks about times after this correction, and say here it is mapping a composition time to the initial presentation time, and it is ‘typically’ the composition time of the first frame that is mapped to 0. This also works for audio; make sure the write-up applies to the AAC pre-roll case. Editors to check that the movie fragment case of audio is no longer commented as unsupported.
m21096

We agree to add an annex “SAP type definitions” to the file format and remove it from DASH.

We will try to provide at least a short definition of each field, and then simplify the table as much as possible (e.g. maybe some lines can be merged, ideally losing the reference_type column). We make sure that the ‘presentation times’ are after the adjustment of any edit list in the movie box.

We also need the DASH edits (which are in 20339). We need a revision of this into systems plenary, that integrates these changes and the DASH-revised base text. (See m21435, below).

m20400

Thank you, the sentence inserted and the edit list is covered by another contribution.

m21121

Thank you, accepted in general. Editors to integrate multiple contributions on the same topic.

m21272

Thank you, accepted in general. Editors to integrate multiple contributions on the same topic. We do not make the stipulation that tracks are consistent.

m21136

1. 
   It proposes enabling of signed composition time offsets in the Track Run box. [[done]]
   
2. 
   It is clarified that the Composition to Decode box applies only to the initial movie and not the movie fragments following. [[ok, accepted into this amendment]]
   
3. 
   A Track Extension Properties (‘trep’) is proposed to be optionally included in the Movie Extends box. The ‘trep’ box can be used to document or summarize characteristics of the track in the subsequent movie fragments. It may contain any number of child boxes.[[accepted into amendment 4]]
   
4. 
   It is proposed that the Composition to Decode box may also appear in the Track Extension Properties box and then documents all the following movie fragments of the track.[[ok, but make 0 for composition end time be unknown? into amendment 4]]
   
5. 
   Amendment 3 allows Sample Group Description boxes in Track Fragment boxes. Consequently, a client can no longer rely on the sample group description entries in the Movie box to describe the sample grouping of entire presentation including movie fragments. Alternative Startup Sequence Properties (‘assp’) box is therefore proposed to be included in Track Extension Properties box to summarize the characteristics of sample group description entries that may be expected to appear within track fragments for alternative startups sequence sample groups.[[also into amendment 4]]
   
6. 
   Now that the 'rap ' sample grouping is introduced for indicating open GOP random access points in Amendment 3, it is proposed that the alternative startup sequence sample grouping may also be used in conjunction with random access points indicated by the 'rap ' sample grouping.[[accepted into this amendment]]
   

m21144

Accepted into amendment 4.
m21145

Accepted without presentation. Thank you.

m21435

Thank you. We need careful choice of terms in the introduction to the SAP types; editors to work on that, visibly on the mailing list. Where SAP Types are used, clarify that all other values are reserved. A number of editorial/phrasing issues were raised, which will be handled by the editor(s).

m21201

Thank you. We agree to start an amendment 4 at this meeting. We will update all the item_ID, including the flute hint track ones, for consistency. We can handle item references with something like the following:

aligned(8) class SingleItemTypeReferenceBox(referenceType) extends Box(referenceType) {
unsigned int(16) from_item_ID;
unsigned int(16) reference_count;
for (j=0; junsigned int(16) to_item_ID;
}
}
aligned(8) class SingleItemTypeReferenceBoxLarge(referenceType) extends Box(referenceType) {
unsigned int(32) from_item_ID;
unsigned int(16) reference_count;
for (j=0; junsigned int(32) to_item_ID;
}
}

aligned(8) class ItemReferenceBox extends FullBox(‘iref’, version, 0) {

if (version==0)
{ SingleItemTypeReferenceBox references[]; }
else if (version==1)
{ SingleItemTypeReferenceBoxLarge references[]; }
}

m21359

We like the idea; we take it into amendment 4. Experts to work together to resolve/improve the design and provide text for amendment 4 initial version.