International organisation for standardisation organisation internationale de normalisation

18MPEG-4 Conformance (14496-4)

18.114496-4 Amd.23

18.1.1Topics

1. 
   Synthesized Texture Conformance
   

18.1.2Contributions

M14982: Editor's study of 14496-4:2004/PDAM.23 Synthesized Texture Conformance. Used as input to produce final text.

M14818: Summary of Voting on ISO/IEC 14496-4:2004/FPDAM 23. No comment was made.

Technical Work in Progress.

18.214496-4 Amd.24

18.2.1Topics

1. 
   File Format Conformance
   

18.2.2Contributions

M14812: Summary of Voting on ISO/IEC 14496-4:2004/FPDAM 24. No comment. Specification progressed to final stage. Good work, people!
Technical Work in Progress.

18.314496-4 Amd.25 LASeR V1 Conformance

18.3.1Topics

1. 
   LASeR Conformance
   

18.3.2Contributions

M14825: Summary of Voting on ISO/IEC 14496-4:2004/FPDAM 25. See DoC. Document progressed to final stage.

Technical Work in Progress.

18.414496-4 Amd.26 Open Font Format Conformance

18.4.1Topics

2. 
   Open Font Format Conformance
   

18.4.2Contributions

M14809: Summary of Voting on ISO/IEC 14496-4:2004/PDAM 26. No comment. Document progressed to FPDAM.
Technical Work in Progress.

18.514496-4 Amd.27 LASeR V2 Conformance

18.5.1Topics

1. 
   LASeR V2 Conformance
   

18.5.2Contributions

M14836 : Summary of Voting on ISO/IEC 14496-4:2004/PDAM 27. See DoC. Document progressed to FPDAM.
Technical Work in Progress.

19MPEG-4 Reference Software (14496-5)

19.114496-5 Amd.14

19.1.1Topics

1. 
   Open Font Format Reference Software
   

19.1.2Contributions

M14867 : Open Font Format Reference Software Implementation.

Technical Work in Progress.

19.214496-5 Amd.16

19.2.1Topics

1. 
   Symbolic Music Representation Reference Software
   

19.2.2Contributions

None.
Technical Work in Progress.

19.314496-5 Amd.17

19.3.1Topics

1. 
   LASeR Reference Software
   

19.3.2Contributions

None.

Technical Work in Progress.

20ISO File Format (14496-12)

20.1MVC

The file format group is currently considering the support needed for MVC in the ISO Base Media File Format family. We welcome contributions considering the challenges and opportunities raised at the file format level, by the MVC codec. We intend to start an amendment at the upcoming 83rd meeting.

20.2MPEG-2 Transport Streams in MP4 files

The file format group is considering the storage of MPEG-2 transport streams in the ISO Base Media File Format family. Currently there are two specifications: the DMB MAF (ISO/IEC 23000-9) and the DVB proposal supplied in liaison. We welcome contributions on the harmonization of these in a general structure that can be adopted into an amendment of ISO/IEC 14496-12. The file format group believes that a hint track approach, as shown by these specifications, is right. The proposals should:

a) provide a basis from which both the DMB MAF specifications and the DVB file format specifications could be derived, possibly by profiling the tools in the harmonized specification, and/or by extending it in non-conflicting and non-overlapping ways.

b) consider specifically the needs of a transmission format, and a recording format.

20.3RTP Recording

The file format group is considering extending the definition of RTP hint tracks to cover recording and welcomes contributions on this subject.

20.414496-12 3^rd Edition

The systems group appoints Mr. Per Fröjdh and Mr. David Singer as editors for a 3^rd edition of ISO/IEC 14496-12 (technically identical to 15444-12) and asks them to prepare a proposed text for review, and liaison to WG1, at the 83^rd meeting. This edition should incorporate ISO/IEC 14496-12:2005 with Corrigenda 1,2,3 and Amendment 1,2.

20.514496-12/Amd.2

20.5.1Topics

1. 
   Flute Hint Track
   

20.5.214966 Updated MPEG-2 TS for the DMB MAF

Thank you. There was concern expressed about the ‘offset’ fields in the sample entries, both defining offset ‘from where’ and also that that provided an unusual link between the sample entry and the stream. However, it seems that this method of storage is not needed for either PMT or OD, and therefore we could remove the modes using these offset fields.

There was a minor comment on the duration field for one-sample TS storage (permitting but not requiring the value 0 for ‘unspecified duration’).

20.5.314897 (Apple) Deriving from part 12

In MAF session Tuesday morning. Comments and improvements welcome. We might need text encouraging people not to copy the file format definitions, but instead just provide values for the parameters?

There is an existing annex in the specification on this subject; that material should be incorporated into the white paper, and perhaps the white paper should be re-introduced into the specification by way of an upcoming amendment.

20.5.414899 (Apple) Video depth and parallax

Thank you, we would like to simplify the track reference type into ‘auxv’ also, and have the question of whether it is depth, parallax (or something else) answered only by the auxiliary video descriptor. This should also go into the technology under consideration. Critique and comments are welcome (especially from experts in 23002-3).

20.5.514905 (Var) Storage of XML and associated media resources

We think we can do this roughly as follows:

inside meta-box

data references

0. 
   (self)
   
1. 
   #ffp(track_ID=2)
   
2. 
   #ffp(track_ID=3)
   

item location

10. 
    dref index 1, offset=0, length=0
    
11. 
    dref index 2, offset=0, length=0
    

item name

10. 
    name=myaudio.mp4, mime=video/mp4
    
11. 
    name=myvideo.mp4, mime=video/mp4
    

in XML, we still talk about myaudio.mp4, myvideo.mp4

20.5.614896 (Apple) Composition and decoding times

Thank you. The meeting points out that this box is still useful even with old-style unsigned CTS offsets. The editor to put this into the TuC for part 12,

20.5.7----- Re-structure the file format specification?

Yes, we probably need to do something like this. The editors to check with the secretariat on how this can be done. Perhaps if section numbers change, a cross-reference table from old to new section numbers could be provided? Input from people who have read it, and found the specification difficult to follow, would be appreciated.

We would like to incorporate 14496-12:2005 and Corrigenda 1 through 3 and Amendments 1 and 2 (these are all final or published), and make this 14496-12:2008, perhaps. There is a need for a new integrated edition, either with or without a re-structure.

One idea is to split chapter 8 (box definitions), with separate chapters for files, movies, tracks, movie fragments, and so on.

Technical Work in Progress.