INTERNATIONAL ORGANISATION FOR STANDARDISATIONORGANISATION INTERNATIONALE DE NORMALISATION

ISO/IEC JTC 1/SC 29/WG 11CODING OF MOVING PICTURES AND AUDIO

ISO/IEC JTC 1/SC 29/WG 11 N9963Hannover, DE – July 2008

Source: Leonardo Chiariglione Title: Report of 85th meetingStatus

Report of 85th meeting.................................................................................................................1Annex A – Attendance list........................................................................................................17Annex B – Agenda....................................................................................................................22Annex C – Input contributions..................................................................................................26Annex D – Output documents...................................................................................................37Annex E – Requirements report................................................................................................43Annex F – Systems report.........................................................................................................48Annex G – Video report............................................................................................................82Annex H – JVT report...............................................................................................................94Annex I – Audio report...........................................................................................................133Annex J – 3DG report.............................................................................................................158

Report of 85th meeting

1 Opening The 85th MPEG meeting was held at Hannover on 2008/07/21T09:00-27T19:30.

2 Roll call of participants Annex 1 gives the attendance list

3 Approval of agenda The agenda adopted is provided in Annex 2

4 Allocation of contributions The list of input documents is provided in Annex 3

5 Communications from Convenor There was no specific communication

1

6 Report of previous meeting This was approved

7 Processing of NB Position PapersNational Body position papers were presented and responses drafted where appropriate

8 Work plan management

8.1 Media coding

8.1.1 AAC-ELDThe following document was approved

10032 Report on the Verification Test of MPEG-4 AAC-ELD

8.1.2 New Profiles for ALS and SLSThe following document was approved

10033 WD on New Profiles for ALS and SLS

8.1.3 Multiview Video Coding (MVC)The following documents were approved

9977 Disposition of Comments on ISO/IEC 14496-10:200X/FPDAM 1 9978 Text of ISO/IEC 14496-10:200X/FDAM 1 Multiview Video Coding

8.1.4 AFX 3rd editionThe following document was approved

10021 WD4.0 of AFX 3rd Edition

8.1.5 Frame-based Animated Mesh CompressionThe following document was approved

10017 Text of ISO/IEC 14496-16:2006/FDAM 2 (Frame based Animation Mesh Compression)

8.1.6 Multiresolution profile

8.1.7 Scalable-complexity 3D mesh compressionThe following documents were approved

10018 Text of WD2.0 of ISO/IEC 14496-16:2006/AMD 4 (Scalable Complexity 3D Mesh Compression)

10022 CE on Scalable Complexity 3D Mesh Coding

2

8.1.8 Open Font Format extensionsThe following documents were approved

10067 DoC on ISO/IEC CD 14496-22 2nd Edition10068 Text of ISO/IEC FCD 14496-22 2nd Edition

8.1.9 Codec Configuration RepresentationThe following document was approved

9984 Study Text of ISO/IEC FCD 23001-4 Codec Configuration Representation9988 Description of Core Experiments in RVC9989 RVC Work Plan and FU Development Status9990 RVC Vision

8.1.10 Video Tool LibraryThe following document was approved

9985 Study Text of ISO/IEC FCD 23002-4 Video Tool Library9987 WD 2 of ISO/IEC 23002-4/Amd.2 (Tools for MPEG-4 ASP, AVC HP and SVC)9989 RVC Work Plan and FU Development Status

8.1.11 Spatial Audio Object CodingThe following documents were approved

10045 Study on ISO/IEC CD 23003-2:200x, Spatial Audio Object Coding10046 Status and Workplan on SAOC Core Experiments

8.1.12 3D Video CodingThe following documents were approved

9991 Description of Exploration Experiments in 3D Video Coding9992 Results of 3D Experts Viewing

8.1.13 Unified Speech and Audio CodingThe following document was approved

10047 Report on Unified Speech and Audio Coding Call for Proposals

8.1.14 Media Value Chain OntologyThe following document was approved

10070 WD1.0 of ISO/IEC 21000-19 Media Value Chain Ontology

3

8.1.15 Representation of Sensory ExperienceThe following documents were approved

10081 WD1.0 of ROSE10082 Core Experiments on ROSE

8.1.16 New Video CodingThe following documents were approved

9993 New Challenges in Video Coding Standardization 9994 Workshop on New Challenges in Video Coding Standardization – Call for

Contributions9995 Workshop on New Challenges in Video Coding Standardization –Program

8.1.17 New Audio Coding

8.2 Composition coding

8.2.1 LASeR Amd.2The following documents were approved

10064 Request for ISO/IEC 14496-20 LASeR Amd.210065 Text of ISO/EC 14496-20 LASeR/PDAM2

8.2.2 Presentation of Structured InformationThe following document was approved

10066 WD1.0 of ISO/EC 14496-20 LASeR/Amd.3 Presentation of Structured Information

8.2.3 Rich Media UI Framework The following document was approved

10085 Context and Objectives of Rich Media UI Framework

8.2.4 Interactive Digital RadioThe following document was approved

10086 Requirements on technologies to support Interactive Digital Radio

4

8.3 Description coding

8.3.1 Image Signature ToolsThe following document was approved

9979 Study Text of ISO/IEC 15938-3:2001/FPDAM 3 Image Signature Tools

8.3.2 Video Signature ToolsThe following documents were approved

9980 Use Cases of MPEG-7 Visual Signature Tools9981 Call for Proposals on Video Signature Tools9982 MPEG-7 Visual XM Document version 34.0

8.4 Transport and File formats

8.4.1 Carriage of SVC in MPEG-2 Systems

The following documents were approved

10058 DoC on ISO/IEC 13818-1:2007/FPDAM3 Carriage of SVC in MPEG-2 Systems10059 Text of ISO/IEC 13818-1:2007/FDAM3 Carriage of SVC in MPEG-2 Systems

8.4.2 Miscellaneous additions to File FormatThe following document was approved

10061 Study of ISO/IEC 14496-12/PDAM.1 Misc. Addition to FF

8.4.3 AVC File Format extensions for MVCThe following document was approved

10062 ISO/IEC 14496-15 WD2.0 MVC File Format

8.5 Multimedia architecture

8.5.1 Interfaces between virtual and real worldsThe following documents were approved

10104 Draft Requirements for MPEG-V Version 210105 MPEG-V Extended Call for Requirements

8.5.2 MPEG eXtensible Middleware The following documents were approved

5

10083 WD1.0 of MXM Architecture and Technologies10084 WD1.0 of MXM APIs10106 Requirements for additional MXM technologies10107 CfP for additional MXM technologies

8.6 Application formats

8.6.1 GeneralThe following documents were approved

10108 MAF Overview10111 MAF Overview presentation document

8.6.2 Photo Player Application FormatThe following document was approved

9983 Working Draft of ISO/IEC 23000-3/Amd.2 Conformance Testing for Photo Player MAF

8.6.3 Video Surveillance Application FormatThe following documents were approved

10075 Draft DoC on ISO/IEC FCD 23000-10 (Video Surveillance Application Format)10076 Study Text of ISO/IEC FCD 23000-10 (Video Surveillance Application Format)

8.6.4 Stereoscopic Video Application FormatThe following document was approved

10079 Study Text of ISO/IEC FCD 23000-11 (Stereoscopic Video Application Format)

8.6.5 Interactive Music Application FormatThe following document was approved

10109 Draft Call for Proposals on Interactive Music Application Format

8.7 Reference implementation

8.7.1 MPEG-1 and -2 on MPEG-4 Reference SoftwareThe following documents were approved

10043 DoC on ISO/IEC 14496-5:2001/FPDAM 20, MPEG-1 and -2 on MPEG-410044 ISO/IEC 14496-5:2001/FDAM 20, MPEG-1 and -2 on MPEG-4

6

8.7.2 SVC Reference SoftwareThe following document was approved

9975 Study Text of ISO/IEC 14496-5:2001/FPDAM 19 Reference Software for Scalable Video Coding

8.7.3 MVC Reference SoftwareThe following documents were approved

9973 Request for ISO/IEC 14496-5:2001/Amd.159974 Text of ISO/IEC 14496-5:2001/PDAM 15 Reference Software for Multiview Video

Coding

8.7.4 3D Graphics Compression Model Reference SoftwareThe following document was approved

10015 Text of ISO/IEC 14496-5:2001/FPDAM 22 (3DG Compression Model Reference Software)

8.7.5 Scene Partitioning Reference SoftwareThe following document was approved

10016 Request for ISO/IEC 14496-5:2001/AMD25 (Scene Partitioning Reference Software)

8.7.6 Professional Archival Application Format Reference SoftwareThe following document was approved

10072 WD1.0 of ISO/IEC 23000-6/Amd1 PA-AF Conformance and Reference Software

8.7.7 Digital Multimedia Broadcasting Application Format Reference SoftwareThe following documents were approved

10073 Request for ISO/IEC 23000-9/Amd.1 DMB AF Conf. And Ref. Soft.10074 Text of ISO/IEC 23000-9/PDAM1 DMB AF Conf. And Ref. Soft.

8.7.8 Video Surveillance Application Format Reference SoftwareThe following documents were approved

10077 Request for ISO/IEC 23000-10/Amd.1 VS AF Conf. And Ref. Soft.10078 Text of ISO/IEC 23000-10/PDAM1 VS AF Conf. And Ref. Soft.

7

8.7.9 Stereoscopic Video Application Format Reference SoftwareThe following document was approved

10080 Workplan for Stereoscopic Video Application Format Ref. Soft and Conf.

8.7.10 Video Tool Library Reference SoftwareThe following document was approved

9986 WD 2 of ISO/IEC 23002-4/Amd.1 (Conformance and Reference Software)

8.8 Conformance

8.8.1 New Profiles for Professional Applications ConformanceThe following documents were approved

9968 Disposition of Comments on ISO/IEC 14496-4:2004/FPDAM 309969 Text of ISO/IEC 14496-4:2004/FDAM 30 Conformance Testing for New Profiles for

Professional Applications

8.8.2 Scalable Video Coding ConformanceThe following documents were approved

9970 Disposition of Comments on ISO/IEC 14496-4:2004/FPDAM 319971 Text of ISO/IEC 14496-4:2004/FDAM 31 Conformance Testing for Scalable Video

Coding

8.8.3 Multiview Video Coding ConformanceThe following document was approved

9972 Working Draft 1 of ISO/IEC 14496-4:2004/Amd.38 Conformance Testing for Multiview Video Coding

8.8.4 MPEG-4 Audio ConformanceThe following document was approved

10041 Proposed ISO/IEC 14496-26, Audio Conformance

8.8.5 AAC-ELD, OAFI and additional AAC ConformanceThe following document was approved

10040 Study on ISO/IEC 14496-4:2004/PDAM 36, AAC-ELD, OAFI and additional AAC Conformance

8

8.8.6 MultiResolution Profile ConformanceThe following document was approved

10029 Text of ISO/IEC 14496-4:2004/FPDAM 33 (MultiResolution Profile Conformance)

8.8.7 3D Graphics Compression Model ConformanceThe following document was approved

10019 DOCR on ISO/IEC 14496-4:2004/PDAM 3410013 Text of ISO/IEC 14496-4:2004/FPDAM 34 (3DG Compression Model

Conformance)

8.8.8 Scene Partitioning ConformanceThe following document was approved

10014 Request for ISO/IEC 14496-4:2004/AMD39 (Scene Partitioning Conformance)

8.8.9 Professional Archival Application Format Conformance

10072 WD1.0 of ISO/IEC 23000-6/Amd1 PA-AF Conformance and Reference Software

8.8.10 Digital Multimedia Broadcasting Application Format Conformance

10073 Request for ISO/IEC 23000-9/Amd.1 DMB AF Conf. And Ref. Soft.10074 Text of ISO/IEC 23000-9/PDAM1 DMB AF Conf. And Ref. Soft.

8.8.11 Video Surveillance Application Format Conformance The following documents were approved

10077 Request for ISO/IEC 23000-10/Amd.1 VS AF Conf. And Ref. Soft.10078 Text of ISO/IEC 23000-10/PDAM1 VS AF Conf. And Ref. Soft.

8.8.12 Stereoscopic Video Application Format Conformance The following document was approved

10080 Workplan for Stereoscopic Video Application Format Ref. Soft and Conf.

8.8.13 Video Tool Library ConformanceThe following document was approved

9986 WD 2 of ISO/IEC 23002-4/Amd.1 (Conformance and Reference Software)

9

8.9 Maintenance

8.9.1 Systems coding standards

10063 ISO/IEC 14496-15/DCOR3

8.9.2 Video coding standards

9976 Study Text of ISO/IEC 14496-10:200X/DCOR 1

8.9.3 Audio coding standardsThe following documents were approved

10030 ISO/IEC 13818-4:2004/Amd 2:2005/DCOR 2, AAC Conformance10031 ISO/IEC 13818-7:2006/DCOR 1, AAC10034 ISO/IEC 14496-3:2005/DCOR 6, AAC10035 ISO/IEC 14496-3:2005/AMD 2:2006/DCOR 4, HE-AAC V2 Profile10036 ISO/IEC 14496-3:2005/AMD 3:2006/DCOR 2, SLS10037 ISO/IEC 14496-3:2005/AMD 9:2008/DCOR 1, AAC-ELD10039 ISO/IEC 14496-4:2004/DCOR 6, AAC-LD10042 ISO/IEC 14496-4:2004/AMD13:200x/DCOR 2, AAC-LD bitstreams

8.9.4 3DG coding standards

10023 DOCR on ISO/IEC 14496-5:2001/PDAM 2210020 Study Text of ISO/IEC 14496-16:2006/AMD1:2007/COR2

8.10 Time lineThe following documents were approved

10001 MPEG Standards10002 Table of unpublished FDISs10003 Work plan and time line

9 Organisation of this meeting

9.1 Tasks for subgroupsThe following tasks were assigned

Requirements Std Pt Amd20 Use of Laser and BIFS for UI

4 X Support of interactive digital radioA 12 Interactive music AFV CfR for Interfaces with virtual worlds

10

Transfer Media Value Chain Ontology results to SystemsTransfer Representation of Sensory Experience Information results to SystemsUser Interface frameworkTransfer MPEG eXtensible Middleware results to SystemsDescription of work items for 10003Contribution to press release Carriage of SVC on MP2 TS MVC CfP for video signature AAC ELD VT USAC kick off New Audio lossless profiles FAMCNew standard areas Video

Open Call: 1st August Paper submission: 5 September Final program: 10 September

Audio Gaming

Systems Std Pt Amd2 1 3 Carriage of SVC

Cor Carriage of AVC4 1 RA

4 26 Open Font Format Conformance37 FF conformance

5 14 Open Font Format Reference Software23 Synthetised texture RS

AVC FF RSSVC FF RS

11 6 Scene partitioning12 1 Miscellanea

Cor.1 Flute15 3 MVC File Format20 3 Laser-BIFS integration20 Presentation of Structured Information22 2nd Ed Open Font Format

7 5 MPEG query format RS6 MPEG query format Conformance

21 7 Cor1 Amendment on query fomat capability

8 1 Minor enhancement19 MVCO

A 4 1 Musical Slide Show MAF conformance & RS2 Protected Musical Slide Show MAF conformance & RS

5 2nd Ed Media Streaming MAF6 Professional Archival AF7 1 Open Access AF Refence Software and Conformance

11

8 Portable Video Player AF RS & C9 Cor 1 DMB MAF9 1 DMB MAF Reference Software and Conformance

10 Video Surveillance MAF1 Video Surveillance MAF Reference Software and

Conformance11 Stereoscopic video AF 12 Interactive music AF

B 2 1 Fragment Request Unit RS and ConformanceE 8 M3W Reference Software and Conformance

MPEG eXtensible MiddlewareInformation exchange with virtual worldsRepresentation of sensory effects informationUpdate MPEG technology web page MAFsContribution to press releaseDescription of work itemsOpen Font Format, MediaValue Chain Ontology, Representation of Sensory Experience, Joint use of Laser and BIFS, Presentation of Structured Information, AVC File Format extensions for MVC, MPEG eXtensible Middleware

Video2 2 3 1080P/60 level

4 3 1080P/60 level conformance4 2 5 Simple Studio Profile level 5 and 6

Cor 3 Simple Studio Profile level 44 35 Simple Studio Profile level 5 and 6 conformance

7 3 3 Image Signature Tools3 4 Video Signature Tools

4 9 3 Reference Hardware DescriptionA 3 1 Photo Player Reference Software

2 Photo Player ConformanceB 4 Codec Configuration DescriptionC 4 Video Tool Library

4 1 Video Tool Library Conformance & RS3DV/FTVUpdate MPEG technology web pageContribution to press releaseDescription of work items

JVT 4 4 30 New AVC Profiles for Professional Applications Conformance

31 Scalable Video Coding Conformance38 MVC C

5 19 Scalable Video Coding Reference SW15 MVC RS

12

10 1 Multi-View Video CodingCor 1 Miscellanea2 AVC Constrained Baseline Profile

Update MPEG technology web pageContribution to press releaseDescription of work items

Audio 4 3 ALS profileSLS profile

3 AAC-ELD VT4 36 AAC-ELD conformance5 24 AAC-ELD Reference Software

D 2 Spatial Audio Object Coding3 USAC

Update MPEG technology web pageContribution to press releaseDescription of work itemsNew audio issues

3DG4 4 32 FAMC (Frame based Animated Mesh Compress.)

Conformance33 Multiresolution profile conformance34 3D Graphics Compression model Conformance

5 21 FAMC (Frame based Animated Mesh Compress.) Reference software

22 3D Graphics Compression model Reference Software11 6 Space partitioning16 3rd Ed

2 Frame-based animated mesh compression3 Multiresolution profile4 Scalable complexity 3DMC

25 3D Graphics Compression modelInformation exchange with virtual worldsUpdate MPEG technology web pageContribution to press releaseDescription of work items

9.2 Joint meetings The following joint meetings were held

Groups What Day Where TimeS, R RoSE, MVCO, Tue Sys 09:00-10:00S, R, 3 MXM, MPEG-V Tue Sys 10:00-11:00S, R UI framework reqs Tue Sys 11:00-12:00R, V Future video stds Tue Video 14:00-16:00R, S, V, A, 3 Gaming Wed Plenary 11:00-12:00A, S, R Interactive music AF Wed Audio 16:00-17:00

13

S, R New BIFS profile for DMB Wed Sys 17:00-17:30A, R New directions in audio Wed Aud 17:00-18:00S, R LASeR reqs for per2per comm. Wed Sys 17:30-18:00R, V Future video stds Thu Video 09:00-10:00A, R New audio profiles Thu Req 11:00-11:30

10 WG management

10.1 Terms of reference The terms of reference were approved

10000 Terms of reference

10.2 Editors The following documents were approved

10404 Editors of MPEG standards10012 Project Editors for ISO/IEC Certificates of Appreciation

10.3 Liaisons The following liaison statements were issued

10088 Liaison statement to SC34/WG2 on Open Font Format10089 Liaison statement to WG 1 on PA-AF10090 Liaison statement to ITU-T SG16 on IPTV10092 Liaison statement to Open IPTV Forum on IPTV10093 Liaison statement to ATSC M/H on Rich Media10094 Liaison statement to DVB MIS10095 Liaison statement to TC 100 on Audio Book10096 Liaison statement to TC 100 on CDV 60728-1-210097 Liaison statement to TC 100 on NP: Multimedia Systems and Equipment10055 Liaison statement to ATSC on Carriage of SVC10056 Liaison statement to DVB on Carriage of SVC10057 Liaison statement to SCTE on Carriage of SVC9996 Liaison Statement to SMPTE re RVC 9997 Liaison Statement to ITU-T SG 9 re FTV 9998 Liaison Statement to ATSC9999 Liaison Statement from JVT to various Organizations re MVC10049 Liaison response to ITU-T SG 16 (m15261, m15516)10050 Liaison response to IEC TC 100 (m15555)

10.4 Ad hoc groups

10100 Ad Hoc Group on Application Format10099 Ad Hoc Group on MPEG File Formats

14

10098 Ad Hoc Group on Scene Representation10027 AHG on 3D Video Coding10060 AHG on 3DGC documents, software maintenance and core experiments10053 AHG on Audio Standards Maintenance10103 AHG on Font Format10110 AHG on Information Exchange with Virtual Worlds10024 AHG on Maintenance of MPEG-4 Visual related Documents, Reference Software

and Conformance10026 AHG on MPEG-7 Visual10101 AHG on MVCO WD Editing10028 AHG on New Challenges in Video Coding Standardization10025 AHG on Reconfigurable Video Coding10054 AHG on SAOC, USAC, and Support for new Loudspeaker Configurations10102 AHG on the RoSE Framework

10.5 Asset management The following documents were approved

10005 Schema assets updates10006 Software assets10007 Conformance assets10008 Content assets10009 URI assets

10.6 IPR management The following document was approved

10010 Standards under development for which a call for patent statements is issued

10.7 Work plan

11 Administrative matters

11.1 Responses to National Bodies The following documents were approved

10051 Response to FNB (m15551)10052 Response to KNB (m15720)

11.2 Schedule of future MPEG meetings The following meeting schedule was approved

# City Country yy mm dd-dd85 Hannover DE 08 07 21-2586 Busan KR 08 10 13-17

15

87 Lausanne CH 09 02 02-0688 Maui, HI US 09 04 20-2489 London UK 09 06-07 29-0390 Xian CN 09 10 26-3091 Kyoto JP 10 01 18-2292 ? AU? 10 04 12-1693 ? IT 10 07 19-2394 ? ? 10 10

11.3 Promotional activities

The following documents were approved

10069 MPEG-4 White Paper – Font Format10071 MPEG-A White Paper – Professional Archival Application Format9965 Hannover press release

12 Resolutions of this meeting These were approved

13 A.O.B There was no other business

14 ClosingThe meeting closed at 2008/07/25T19:30

16

Annex A – Attendance list

First Name Last Name Affiliation CountryDr. Christian Timmerer Klagenfurt University AustriaMr. Kenneth Vermeirsch UGent - MMLab BelgiumMr. T. Wiegand Fraunhofer HHI BerlinDr. Philippe Gournay VoiceAge Corporation CanadaMr. Roch Lefebvre Université de Sherbrooke CanadaMr. Redwan Salami VoiceAge Corporation CanadaMrs. Dandan Ding Zhejiang University ChinaDr. Wen Gao Peking University ChinaPr. Yun He Tsinghua University ChinaDr. Junyan Huo Xidian University ChinaMr. Sixin Lin Huawei Tech. Ltd Co. ChinaMr. Siwei MA Peking University ChinaMr. Honggang Qi Chinese Academy of Sciences ChinaMr. Lianhuan Xiong Huawei Technologies Co. Ltd. ChinaPr. Lu Yu Zhejiang University China

Dr.Gwo Giun (Chris) Lee National Cheng Kung University China

Mr. Ying Chen Tampere University of Technology FinlandMr. Miska Hannuksela Nokia Research Center FinlandDr. Juha Vartiainen SFS FinlandDr. Ye-Kui Wang Nokia FinlandMr. Berthelot Bertrand France Telecom - Orange Labs FranceMr. Vincent Bottreau Thomson FranceMr. Marc Brelot RTL FranceMr. Cyril Concolato Telecom Paristech FranceDr. Patrick Gioia Orange Labs FranceMr. Marc Guez Vucher SCPP FranceMr. Owen Lagadec iKlax Media FranceMr. Jean Le Feuvre Telecom Paristech FranceMr. Patrick Lopez Thomson FranceMr. AVARO OLIVIER STREAMEZZO FranceMr. Stephane Pateux France Telecom FranceMr. Pierrick Philippe Orange Labs FranceMr. Marius Preda Telecom FranceMr. Laurent Primaux iKlax Media FranceMr. Micka‘l Raulet INSA de Rennes FranceMr. David Virette France Telecom FranceMr. Schreiner Stephan Fraunhofer Institut GermanyMr. Bacigalupo Virgilio Fraunhofer Institut GermanyMr. Gero Baese Siemens GermanyMr. Johannes Boehm Thomson GermanyPr. Karlheinz Brandenburg Fraunhofer IDMT GermanyMr. Heribert Brust Fraunhofer HHI GermanyMr. Gero BŠse Siemens GermanyMr. Stefan Doehlae Fraunhofer IIS GermanyDr. Ralf Geiger Fraunhofer IIS GermanyMr. Sebastian Gerke Fraunhofer HHI GermanyDr. Bernhard Grill Fraunhofer IIS GermanyMr. Karsten Grueneberg Fraunhofer HHI GermanyMr. Oliver Hellmuth Fraunhofer IIS GermanyDr. Florian Keiler Thomson Germany

17

Dr. Peter Kuhn European Patent Office GermanyDr. Terentiev Leonid Fraunhofer Institut GermanyMr. Tilman Liebchen LG Electronics GermanyMr. Marcus Mueller Heinrich-Hertz-Institut GermanyDr. Karsten Mueller Fraunhofer HHI GermanyMr. Markus Multrus Fraunhofer IIS GermanyMr. Frederik Nagel fraunhofer Institut GermanyMr. Max Neuendorf fraunhofer Institut GermanyPr. Jens-Rainer Ohm RWTH Aachen University GermanyMr. Heiko Purnhagen Dolby Germany GmbH GermanyMr. Fengyan Qi Huawei Technologies GermanyMr. Thomas Schierl Fraunhofer HHI GermanyMr. Andreas Schneider Dolby Germany GmbH GermanyMr. Markus Schnell Fraunhofer IIS GermanyDr. Gerald Schuller TU Ilmenau GermanyDr. Heiko Schwarz Fraunhofer HHI GermanyDr. Aljoscha Smolic Fraunhofer HHI GermanyMr. Ralph Sperschneider Fraunhofer IIS GermanyMr. HervŽ Taddei Huaewei Technologies GermanyMr. Herbert Thoma Fraunhofer IIS GermanyMr. Steffen Wittmann Panasonic GermanyDr. Oliver Wuebbolt Thomson Germany

Mr.Frederik Leonhard Zilly Fraunhofer HHI Germany

Dr. Yui-Lam Chan Hong Kong Polytechnic University Hong KongMs. Carmen Cheng Hong Kong ASTRI Hong KongMr. Roni Even Polycom IsraelMrs. sabina brufani sisvel ItalyMr. Leonardo Chiariglione Cedeo.net ItalyMr. Filippo Chiariglione Cedeo.net ItalyMr. Giovanni Cordara Telecom Italia ItalyMr. Diego Gibellino Telecom Italia ItalyMr. Kohtaro Asai Mitsubishi Electric Corporation JapanMr. Takeshi Chujoh Toshiba Corporation JapanMr. Shigeru Fukushima JVC JapanMr. Noboru Harada NTT JapanMr. Shinya Hasegawa Sharp Corporation JapanMr. Takashi Ito Fujitsu Laboratories Ltd. JapanMr. Satoshi Ito Toshiba Corporation JapanMr. Kota Iwamoto NEC Corporation JapanMr. Itaru Kaneko Tokyo Polytechnic JapanMr. Kimihiko Kazui Fujitsu Laboratories Ltd. JapanMr. Kei Kikuiri NTT DoCoMo JapanMr. Hideaki Kimata NTT JapanMr. Masatsugu Kitamura For more convenient AV life JapanMr. Takuyo Kogure Matsushita Electric Ind. Co , Ltd. JapanMr. Jun Matsumoto Sony JapanMr. Takehiro Moriya NTT JapanDr. Tokumichi Murakami Mitsubishi Electric Corporation JapanDr. Katsuyuki Nakamura Hitachi Ltd. JapanMr. Yasushige Nakayama NHK JapanMr. Takahiro Nishi Panasonic JapanMr. Toshiyuki Nomura NEC JapanMr. Takeshi Norimatsu Panasonic JapanMr. Ryoma Oami NEC Corporation JapanMs. Yukiko Ogura IPSJ Japan

18

Ms Yukiko Ogura IPSJ JapanMr. Shohei Saito Hitachi Ltd. JapanMr. Satoru Sakazume Victor Company of Japan, Ltd. JapanMr. Shun-ichi Sekiguchi Mitsubishi Electric Corporation JapanDr. Takanori Senoh NICT JapanMr. Osamu Shimada NEC Corporation JapanMr. Shinya Shimizu NTT JapanMr. Kazuo Sugimoto Mitsubishi Electric Corporation JapanDr. Ken Sugiyama NEC Corporation JapanMr. Teruhiko Suzuki Sony Corp. JapanDr. Kazuyoshi Suzuki Nagoya University JapanMr. Thiow Keng Tan NTT DoCoMo, Inc. JapanPr. Masayuki Tanimoto Nagoya University JapanMr. Akiyuki Tanizawa Toshiba JapanMr. Yasuaki Tokumo Sharp Corporation JapanDr. Akio Yamada NEC JapanMr. Tomoo Yamakage Toshiba Corporation JapanMr. Tomoyuki Yamamoto Sharp JapanMr. Takahiro Yamasaki Oki Electric Industry Co., Ltd. JapanDr. Yoshiyuki Yashima NTT Japan

Il Hong Shin ETRI KoreaMr. Dong Gyu Sim Kwangwoon University KoreaMr. Jeong-Hwan Ahn Samsung Electronics KoreaDr. Elena Alshina Samsung Electronics KoreaMr. Gun Bang ETRI KoreaDr. Jihun Cha ETRI KoreaDr. Maeng-Sub Cho ETRI KoreaMrs. Ayoung Cho Inha University KoreaPr. Yoonsik Choe Yonsei University KoreaDr. Haechul Choi ETRI KoreaDr. Miran Choi ETRI KoreaMr. Byeongho Choi KETI KoreaMr. Bumsuk Choi ETRI KoreaMr. Kevin S.C Ham Audizen KoreaMr. Yo-Sung Ho GIST KoreaMr. Jin Woo Hong ETRI KoreaMr. Seo§Young Hwang Samsung Electronics KoreaMrs. Inseon Jang ETRI KoreaPr. Euee Seon Jang Hanyang University KoreaMr. Yong-Joon Jeon KoreaMr. Byeong Moon Jeon LG Electronics KoreaMr. Byeungwoo Jeon Sungkyunkwan University KoreaMr. Dong-Seok Jeong Inha University Korea Mr. Ju Kyong Jin Inha University KoreaMr. Sanghyun Joo ETRI KoreaDr. Yang-Won Jung LG Electronics KoreaMr. Kyeong Ok Kang ETRI KoreaMr. Dong Soo Kim LG Electronics KoreaDr. Hui Yong Kim ETRI KoreaMr. Kyuheon Kim KoreaMr. Byungchul Kim KoreaMr. Hyungyu Kim Hanyang University KoreaMr. Daiyong Kim Hanyang University KoreaDr. Yongtae Kim Samsung KoreaMr. Yongje Kim KoreaPr. Sang-Kyun Kim Myongji Univeristy Korea

19

Mr. Seon Tae Kim ETRI KoreaJung Hoe Kim Samsung Electronics KoreaJongyoun Kim Netntv Korea

Mr. Jung Wan Ko Samsung Electronics Co.,Ltd KoreaMr. Seo Kyong-Sok Samsung KoreaMr. Sinwook Lee Hanyang Univ KoreaDr. Sangyoun Lee Yonsei University KoreaMr. Cheon Lee GIST KoreaMr. Seung Wook Lee ETRI KoreaMr. Taejin Lee ETRI KoreaMr. Kyohyuk Lee KoreaMrs. Tammy Lee Samsung Electronics Co. Ltd KoreaMr. Yung Lyul Lee Jejong University KoreaMr. Taebeom Lim KETI KoreaDr. Jung Eun Lim LG Electronics KoreaMr. Young«-Kwon Lim Net&Tv Inc. KoreaMr. Kim Myoung-Jin Soongsil University KoreaDr. Weon geun O ETRI KoreaProf. Seoung-Jun Oh Kwangwoon University KoreaDr. Weon geun Oh ETRI KoreaMr. Hee-Suk Pang Sejong University KoreaMr. Changseob Park Korean Broadcasting System KoreaMr. HeungSik Park KoreaProf. Hochong Park Kwangwoon University KoreaMr. JeongHoon Park Samsung Electronics KoreaPr. Young-cheol Park Yonsei University Korea

Kyungmo Park Samsung Electronics KoreaMr. Jeongil Seo ETRI KoreaMr. Hwaseon Shin KETI KoreaMr. KyoungSoo Son Hanyang University Korea

Jaeyeon Song Samsung Electronics KoreaMr. Jung Suk Suh Samsung Electronics Co., Ltd KoreaMr. Jaewon Sung LG Electronics KoreaMr. Hendry Tan Korea ICU KoreaDr. Gi-Mun Um ETRI KoreaMr. Kwanghyun Won Sungkyunkwan University KoreaMr. Won-Keun Yang ETRI KoreaMr. Alex Chungku Yie Humax Co., Ltd. KoreaDr. Jeong-Ju Yoo ETRI KoreaMr. Sungyong Yoon LG Electornics KoreaMr. Kugjin Yun ETRI KoreaMr. Kyoung-ill Kim ETRI KoreaDr. Henney Oh LG Electronics KoreaDr. Eunmi Oh Samsung Electronics KoreaDr. Hyungsik suh LG electronics koreaMr. Wiebe de Haan Philips NederlandsMr. Fons Bruls Philips Research Netherlands

Sampaio Lobo Lincoln Motorola NetherlandsMr. Werner Oomen Philips NetherlandsMr. Yann Bodo Joost Technologies NetherlandsMr. Sebastian Brangoulo Joost Technologies NetherlandsMr. Jean H.A. Gelissen Philips Research Netherlands

Marek Domanski Poznan Uni Tech PolandMr. Krzysztof Klimaszewski Poznan University of Technology, KTMiM PolandMr. Olgierd Stankiewicz Poznan University of Technology, KTMiM PolandMr. Ti Eu Chan Institute For Infocomm Research (A*STAR) Singapore

20

Dr. Tuan Kiang Chiew Institute for Infocomm Research A*STAR SingaporeDr. Haibin Huang Institute for Infocomm Research SingaporeDr. Haiyan Shu Institute for Infocomm Research SingaporeMr. Tai Hou Tng Institute for Infocomm Research SingaporeMrs. Wei Yao Institute for Infocomm Research SingaporeMrs. Huan Zhou Panasonic Singapore Laboratories Ltd. SingaporeDr. Yongwei Zhu Institute for Infocomm Research SingaporeMr. Pablo Carballeira López Universidad Politécnica de Madrid SpainPr. Jaime Delgado UPC SpainDr. Oscar Divorra Escoda Telefonica SpainMr. Marc Gauvin sDae SpainPr. Francisco Mor‡n Burgos Universidad PolitŽcnica de Madrid SpainMr. Victor Rodriguez-Doncel Universitat Polit?nica de Catalunya SpainDr. Per Froejdh Ericsson SwedenMr. Kristofer Kjšrling Dolby SwedenMrs. Ivana Radulovic Ericsson SwedenDr. Anisse Taleb Ericsson SwedenPr. Touradj Ebrahimi EPFL SwitzerlandMr. Christophe Lucarz EPFL SwitzerlandMr. James Annesley Kingston University UKDr. Miroslaw Bober Mitsubishi Electric ITE-VIL UKDr. Paul Brasnett Mitsubishi Electric ITE UKDr. Yue Feng Universtiy of Glasgow UKDr. Panos Kudumakis Queen Mary University of London UKDr. Stavros Paschalakis Mitsubishi Electric ITE B.V. VIL UKDr. Leszek Cieplinski Mitsubishi Electric ITE-VIL UKMr. Motta Giovanni QUALWMM USADr. Lazar Bivolarski Logitech, Inc. USAMr. Peisong Chen Qualcomm USADr. Yi-Jen Chiu Intel Corporation USAMr. Alberto Duenas W&W Communications, Inc. USAMr. Alex Eleftheriadis Vidyo Inc. USAMr. Louis Fielder Dolby Laboratories Inc. USAMr. Munsi Alaul Haque Intel Corporation USADr. Barry G. Haskell Apple USADr. Shih-Ta Hsiang Motorola, Inc. USADr. Walter Husak USA

Marta Karczewicz Quakomm USAMr. Vladimir Levantovsky Monotype USAMr. Jian Lu Vobile, Inc. USAMr. Ajay Luthra Motorola USADr. Sam Narasimhan Motorola USAMr. Purvin Pandit Thomson USAMr. Schuyler Quackenbush Audio Research Labs USADr. Yuriy A. Reznik Qualcomm Inc. USAMr. Suman Sharma Intel Corporation USAMrs. Xiaojin Shi Apple USAMr. David W Singer Apple USADr. Gary J Sullivan Microsoft USADr. Huifang Sun Mitsubishi Elec Res Labs USADr. Dong Tian Thomson Inc. USADr. Alexandros Tourapis Dolby Laboratories USADr. Anthony Vetro Mitsubishi Elec Res Labs USAMr. Xin Wang ContentGuard, Inc. USADr. Sehoon Yea Mitsubishi Elec Res Labs USADr. Haoping Yu Huawei Technologies USA

21

Annex B– Agenda

1    Opening 2    Roll call of participants 3    Approval of agenda 4    Allocation of contributions 5    Communications from Convenor 6    Report of previous meeting 7    Processing of NB Position Papers 8    Work plan management   1  Media coding    1MPEG-2 Main Profile Level for 1080@50/60p    2MPEG-4 Visual Simple Studio Profile Levels 5 and 6    3AAC-ELD    4Multiview Video Coding (MVC)    5Frame-based Animated Mesh Compression    6Multiresolution profile    7Low-complexity 3D mesh compression    8Open Font Format extensions    9Codec Configuration Representation   10Video Tool Library   11Spatial Audio Object Coding   123D Video Coding   13Unified Speech and Audio Coding   14Media Value Chain Ontology   15Representation of Sensory Experience   16New Video Coding   17New Audio Coding  2  Composition coding    1Joint use of Laser and BIFS    2Scene partitioning    3Presentation of Structured Information    4User Interface framework  3  Description coding    1Image Signature Tools    2Video Signature Tools    3MPEG-7 Query Format

22

  4  Systems support  5  IPMP  6  Digital Item    1Schema files for MPEG-21 standards    2Security in Event Reporting  7  Transport and File formats    1Carriage of SVC in MPEG-2 Systems    2AVC File Format extensions for MVC    3Digital Item File Format  8  Multimedia architecture    13D Graphics Compression Model    2Interfaces between virtual and real worlds    3Extensible Multimedia Platform  9  Application formats    1Protected Musical Slide Show Application Format    2Professional Archival Application Format    3Open Access Application Format    4Portable Video Player Application Format    5Video Surveillance Application Format    6Video Stereoscopic Application Format    7Interactive music Application Format 10  Reference implementation    1MPEG-1 and -2 on MPEG-4 Reference Software    2BSAC Extensions Reference Software    3AAC-ELD Reference Software    4New Profiles for Professional Applications Reference Software    5SVC Reference Software    6File Format Reference Software    7Geometry and Shadow Reference Software    8Frame-based Animated Mesh Compression Reference Software    93D Graphics Compression Model Reference Software   10Open Font Format Reference Software   11MPEG-7 Systems Reference Software   12MPEG-21 REL Reference Software   13Photo Player MAF Reference Software   14Musical Slide Show MAF Reference Software   15Binary MPEG format for XML Reference Software   16MPEG Surround Reference Software

23

   17M3W Reference Software 11  Conformance    1MPEG-2 Main Profile Level for 1080@50/60p Conformance    2MPEG-4 Visual Simple Profile Level 6 Conformance    3New Profiles for Professional Applications Conformance    4Scalable Video Coding Conformance    5AAC-ELD, OAFI and additional AAC Conformance    6MPEG-1 and -2 Audio in MPEG-4 Conformance    7BSAC Conformance    8File Format Conformance    9Geometry & Shadow Conformance   10Frame-based Animated Mesh Compression Conformance   11MultiResolution Profile Conformance   123D Graphics Compression Model Conformance   13Synthesized Texture Conformance   14Laser Conformance   15Open Font Format Conformance   16Improvements to Geographic Descriptor Conformance   17MPEG Surround Conformance   18M3W Conformance   19Video Tool Library Conformance 12  Maintenance    1Systems coding standards    2Video coding standards    3Audio coding standards    43DG coding standards    5Visual description coding standards    6Audio description coding standards    7MPEG-21 standards    8MPEG-A standards 13  Time line

9    Organisation of this meeting     1 Tasks for subgroups    2 Joint meetings

10    WG management   1 1 Terms of reference   2 2 Officers   3 3 Editors

24

  4 4 Liaisons   5 5 Work item assignment   6 6 Ad hoc groups   7 7 Asset management      1Reference software      2Conformance      3Test material      4URI     8 IPR management     9 Work plan

11    Administrative matters   1  Responses to National Bodies   2  Schedule of future MPEG meetings   3  Promotional activities

12    Resolutions of this meeting 13    A.O.B 14    Closing

25

Annex C – Input contributions

No. Source Title

m15492 Webmaster Hannover document register

m15493Yi-Shin Tung, Teruhiko Suzuki Ad Hoc Group on Maintenance of MPEG-4

Visual related Documents, Reference Software and Conformance

m15494 Euee S. Jang, Marco Mattavelli, Yoshihisa Yamada

Ad Hoc Group on Reconfigurable Video Coding

m15495 Miroslaw Bober, Ryoma Oami Ad Hoc Group on MPEG-7 Visual

m15496 Hideaki Kimata, Karsten Müller Ad Hoc Group on 3D Video and Free Viewpoint Television Coding

m15497 Lazar Bivolarski, Jens-Rainer Ohm, Jörn Ostermann

Ad Hoc Group on New Challenges in Video Coding Standardization

m15498 Patrick Gioia, Francisco Morán Burgos

Ad Hoc Group on 3DGC documents and software maintenance

m15499 R. Sperschneider Ad Hoc Group on Audio Standards Maintenance

m15500 S. Quackenbush, Eunmi Oh Ad Hoc Group on Unified Speech and Audio Coding, SAOC and AAC-ELD

m15501 Sanghyun Joo, Jean Gelissen, Christian Timmerer Ad Hoc Group on the RoSE Framework

m15502 Xin Wang Ad Hoc Group on Call for Proposals for a Media Value Chain Ontology

m15503 Jean Gelissen, Marius Preda Ad Hoc Group on Information Exchange with Virtual Worlds

m15504Young-Kwon Lim , Jean-Claude Dufourd, Jaeyeon Song, Cyril Concolato

Ad Hoc Group on Scene Representation

m15505 David Singer Ad Hoc Group on MPEG File Formats

m15506 Kyuheon Kim, Hui Yong Kim, Jean Cha, Noboru Harada, Hendry Ad Hoc Group on Application Format

m15507 Kyoungro Yoon, Mario Doeller Ad Hoc Group on MPEG Query Format

m15508 Olivier Avaro Ad Hoc Group on MxM

m15509 ITTF via SC29 Secretariat Table of Replies on ISO/IEC 21000-18:2007/FDAM 1 [SC 29 N 9414]

26

m15510 ITTF via SC29 Secretariat Table of Replies on ISO/IEC FDIS 23002-2 [SC 29 N 9415]

m15511 ITTF via SC29 Secretariat Table of Replies on ISO/IEC FDIS 29116-1 [SC 29 N 9416]

m15512 ITTF via SC29 Secretariat Table of Replies on ISO/IEC 23002-1:2006/FDAM 1 [SC 29 N 9457]

m15513 SC29 Secretariat Summary of Voting on ISO/IEC 14496-4:2004/FPDAM 30 [SC 29 N 9481]

m15514 ITU-T SG 9 via SC29 Secretariat Liaison Statement from ITU-T SG 9 [SC 29 N 9482]

m15515 ITU-T SG 9 via SC29 Secretariat Liaison Statement from ITU-T SG 9 [SC 29 N 9483]

m15516 ITU-T SG 16 via SC29 Secretariat Liaison Statement from ITU-T SG 16 [SC 29 N 9498]

m15517 ITTF via SC29 Secretariat Table of Replies on ISO/IEC 14496-3:2005/FDAM 9 [SC 29 N 9505]

m15518 SC29 Secretariat Summary of Voting on ISO/IEC 14496-16:2006/FPDAM 2 [SC 29 N 9506]

m15519 ITU-T SG 16 via SC29 Secretariat Liaison Statement from ITU-T SG 16 on IPTV [SC 29 N 9516]

m15520 Mark Callow Guide to the MPEG Subversion Repository

m15521 Itaru Kaneko Architecture for the MPEG User Interface Framework

m15522 Richard Clark Summary of Voting on ISO/IEC 13818-1:2007/FPDAM 3.2 [SC 29 N 9517]

m15523 Marius Preda Summary of Voting on ISO/IEC FCD 23000-10 [SC 29 N 9518]

m15524 Francisco Morán Table of Replies on ISO/IEC 14496-4:2004/FDAM 29 [SC 29 N 9527]

m15525 Cyril Concolato Table of Replies on ISO/IEC 14496-15:2004/FDAM 2 [SC 29 N 9528]

m15526 Jean Le Feuvre Table of Replies on ISO/IEC 21000-5:2004/FDAM 3 [SC 29 N 9529]

m15527 KyungMo Park Table of Replies on ISO/IEC 14496-5:2001/FDAM 16 [SC 29 N 9530]

m15528 SC29 Secretariat Table of Replies on ISO/IEC 14496-5:2001/FDAM 17 [SC 29 N 9531]

m15529 SC29 Secretariat Table of Replies on ISO/IEC FDIS 23000-5

27

[SC 29 N 9532]

m15530 ITTF via SC29 Secretariat Table of Replies on ISO/IEC FDIS 23000-7 [SC 29 N 9533]

m15531 ITTF via SC 29 Secretariat Table of Replies on ISO/IEC FDIS 23000-9 [SC 29 N 9534]

m15532 ITTF via SC 29 Secretariat Summary of Voting on ISO/IEC 14496-10:200X/FPDAM 1

m15533 ITTF via SC 29 Secretariat Summary of Voting on ISO/IEC CD 14496-22 [2nd Edition]

m15534 ITTF via SC 29 Secretariat Summary of Voting on ISO/IEC 14496-4:2004/FPDAM 31

m15535 ITTF via SC 29 Secretariat Table of Replies on ISO/IEC 23003-1:2007/FDAM 1

m15536 ITTF via SC 29 Secretariat Table of Replies on ISO/IEC 23003-1:2007/FDAM 2

m15537 ITTF via SC 29 Secretariat Table of Replies on ISO/IEC 14496-4:2004/FDAM 20

m15538 SC29 Secretariat Liaison Statement from DVB TM-AVC [SC 29 N 9536]

m15539SC29 Secretariat IEC NP: Multimedia systems and equipment

-- Multimedia home network configuration -- Basic reference model

m15540 SC29 Secretariat Depth Map Estimation Software version 3

m15541 ITTF via SC 29 Secretariat Reference software of OctreeImage and PointTexture

m15542 ITTF via SC 29 Secretariat Liaison Statement from TTA [SC 29 N 9559]

m15543 ITTF via SC29 Secretariat IEC CDV 60728-1-2

m15544 DVB via SC 29 Secretariat Liaison Statement from ITU-T SG 16 on MXW [SC 29 N 9564]

m15545 IEC TC 100 via SC29 Secretariat Speech and Audio listening test lab report from Dolby

m15546 Olgierd Stankiewicz Analysis of speech and audio listening test data

m15547 Krzysztof Wegner Technical description of the Dolby Philips proposal for the speech and audio work- item

m15548 Jeong-Hwan Ahn Speech and Audio listening test lab report from Philips

28

m15549 Shinjun Lee Proposed network of functional units for AVC High Profile

m15550 GyeongJa Jang New BIFS Profile for Interactive Digital Radio

m15551 TTA via SC 29 Secretariat FRNB comment on the Unified Speech and Audio Coding Exploration Activity

m15552IEC TC 100 via SC29 Secretariat Information on an interim technical standard

for next-generation satellite digital broadcasting in Japan

m15553 ITU-T SG 16 via SC 29 Secretariat Results of Exploration Experiment in 3D Video Coding for Dog Data Set

m15554 Kristofer Kjörling Liaison Statement from 3GPP

m15555 Werner Oomen IEC CD 61937-10

m15556 Kristofer Kjörling IEC CD 62571

m15557 Heiko Purnhagen Liaison Statement from DVB

m15558 Kristofer Kjörling JNB Comment on Text of ISO/IEC 14496-10:200X/DCOR1 (N9574)

m15559 Werner Oomen Proposed update of FCD ISO/IEC 23002-4: Video Tool Library (VTL)

m15560 Jonas Samuelsson Sensory Effects Metadata for RoSE Framework

m15561 Lars Villemoes User Sensory Preferences Metadata for RoSE Framework

m15562 Barbara Resch Sensory Device Capabilities Metadata for RoSE Framework

m15563 Erik Schuijers Sensory Device Commands Metadata for RoSE Framework

m15564 Pontus Carlsson Response to CfP on unified speech and audio coding

m15565 Werner Oomen Speech & Audio - Listening Test, Report & Results - Thomson

m15566 Jeroen Koppens Speech & Audio - Description of Technology of the Thomson proposal

m15567 Gwo Giun Lee Listening test results for Unified Speech and Audio Coding from Samsung

m15568 He-Yuan Lin Technical description of the ETRI proposal

29

for the unified speech and audio coding

m15569Yuan-Long Cheng Proposal on standardization of a filter set for

converting between 4:2:2/4:2:0 chrominance sampling

m15570 Ming-Jiun Wang Unified speech and audio coding listening test report from ETRI

m15571 Benoît Pellan Liaison Statement from WG 1

m15572Young-Kwon Lim Listening Test Report for CE on separating

real-environment signals into multiple objects from ETRI

m15573 Cyril Concolato 3D Video Exploration Experiment on Baseline Length Dependency

m15574Pierrick Philippe on behalf of the FRNB

Listening test results of Test 1 for SAOC CE on separating real-environment signals into multiple objects

m15575Yasushige Nakayama Listening test results of Test 2 for SAOC CE

on separating real-environment signals into multiple objects

m15576 Aljoscha Smolic A Proposal on preset functionality for teleconferencing application

m15577 Yongzhe Wang Requirements for next-generation video coding standard

m15578 Karsten Mueller On motion block size and partitions for 4:4:4 coding

m15579 3GPP via SC 29 Secretariat Analysis for Ad Hoc Group on New Challenges in Video Coding Standardization

m15580IEC TC 100 via SC 29 Secretariat Technical considerations for Ad Hoc Group

on New Challenges in Video Coding Standardization

m15581 IEC TC 100 via SC 29 Secretariat Report on the USAC listening test at LGE

m15582 DVB via SC 29 Secretariat LGE submission to Unified Speech & Audio Coding

m15583teruhikos_at_jp.sony.com Results of Depth Estimation and View

Synthesis on Doorflowers Test Data Set for EEs in 3D Video Coding

m15584 Kazuo Sugimoto Experimental Results on Depth Estimation and View Synthesis with subpixel-precision

m15585 Kenji Otoi RoSE description schemes for realistic TV commercials

30

m15586 Yoshihisa Yamada Listening test reports for CE on separating real-environment signals

m15587 Kohtaro Asai Proposed syntax revision for redundancy reduction in SAOC

m15588 B.S Choi Comments on SAOC operation modes and module

m15589 Sanghyun Joo Exploration Experiments on seq 'Arrive book' & 'Alt-moabit'

m15590 B.S Choi Creation of LDV streams out of MV sequences

m15591 Sanghyun Joo Proposals for MVC File Format

m15592 Sanghyun Joo Proposal for support of the additional downmix by MPEG SAOC

m15593B.S Choi Proposed Text for White Paper of ISO/IEC

23000-6 Professional Archival Application Format

m15594 Sanghyun Joo Enhancement of Temporal Consistency for Multi-view Depth Map Estimation

m15595 B.S Choi Results of Exploration Experiment on View Synthesis

m15596 Eunmi Oh Proposed Text for Working Draft of ISO/IEC 23000-6 PA-AF Reference Software

m15597 JungHoe Kim Boundary Filtering on Synthesized Images for 3D Video

m15598 Miyoung Kim Proposal of work plan for a 3D multichannel audio configuration

m15599 KiHyun Choo Experimental Results of EE on LeavingLaptop sequence for MPEG-FTV

m15600 Hosang Sung On MVC File Format

m15601 Johannes Boehm Additional Use Cases for UI Framework

m15602 Oliver Wuebbolt Analysis of MPEG-21 UED for Personalization

m15603 Florian Keiler First feedback/comments on the DCCI programmatic API for personalization

m15604 Florian Keiler Addition information on the MPEG UI Framework

m15605 Oliver Wuebbolt List of Adjacent Clip Pairs in the VCE-7 Dataset

31

m15606 Johannes Boehm Removal of Partially Identical Clips from the VCE-7 Dataset

m15607 Eunmi Oh Camera Capturing of Video Clips for VCE-7 Robustness Test

m15608 Miyoung Kim Report on USAC subjective tests at VoiceAge test site

m15609 JungHoe Kim Technical Description of the VoiceAge Candidate for USAC

m15610 Taejin Lee Analysis of Combined Listening Test Results for USAC

m15611 Seungkwon Beack File format support for reception of SRTP and MIKEY messages

m15612 Minje Kim Response to the call for technologies for RoSE

m15613 Kyeongok Kang Analysis of unified speech and audio coding listening test results

m15614 Hochong Park CD proposal of LASeR in IPTV

m15615 Youngcheol Park Response to the extended call for requirements for MPEG-V

m15616 Akira Nakagawa A Proposal on Conformance Testing for Photo Player Application Format

m15617 Kimihiko Kazui Response to the extended call for requirements for MPEG-V

m15618 Shunsuke Kobayashi Speech and Audio listening test lab report (Ericsson)

m15619 Taejin Lee Report on USAC Subjective Tests at Fraunhofer IIS Test Site

m15620Seungkwon Beack Exploration Experiment results on

'Champagne_tower' and 'Pantomime' sequences

m15621 Minje Kim Technical Decsription of the Fraunhofer IIS Submission for the CfP on USAC

m15622 Kyeongok Kang Proposal for the Presentation of Structured Information

m15623WG 1 via SC 29 Secretariat Proposal on implementation Capturing on

camera and Interlaced/Progressive conversion for VCE-7 modification

m15624 Jeongil Seo Suggestion to solve the problem of unstable trimming point in modification for VCE-7

32

m15625 Seungkwon Beack Analysis of USAC Listening Test Data

m15626 Kyeongok Kang A proposal for technical specification of Interactive Music AF

m15627 Taka Senoh Cross verification results of Image Signature

m15628 Kenji Yamamoto Proposed new profile for MPEG-4 SLS

m15629 Ryutaro Oi Proposed Corrigendum on MPEG-4 SLS

m15630 Tomoyuki Mishina New version of the BSDL2CALML parser in RVC

m15631 Makoto Okui Ontology for IP Media Networks (IPM-Net): A response to the MVCO CfP

m15632Osamu Shimada Listening test report for CE on separating

real-environment signals into multiple objects for the MPEG SAOC system

m15633Toshiyuki Nomura Additional information on the mono

downmix mode for the enhanced Karaoke / Solo processing for the MPEG SAOC system

m15634Akihiko Sugiyama Proposal for adoption of additional

downmix / upmix scenarios for the MPEG SAOC system

m15635 Osamu Hoshuyama Report on corrections for the MPEG SAOC CD text

m15636Osamu Shimada Proposal for the file-based storage of

rendering information for the MPEG SAOC system

m15637 Toshiyuki Nomura Proposed ELD Verification Test Report

m15638 Akihiko Sugiyama proposed correction to MPEG-2 SBR conformance

m15639 Osamu Hoshuyama proposed clarification for MPEG-2 and MPEG-4 AAC

m15640 Osamu Shimada proposed correction of the MPEG-4 HE AAC v2 profile

m15641Keisuke Masatoki further considerations regarding the 960

transform length in the AAC profile, the HE AAC profile and the HE AAC v2 profile

m15642 Toshiyuki Nomura Update on Conformance for AAC-ELD

m15643 Akihiko Sugiyama 84th MPEG Audio Report

m15644 Osamu Hoshuyama Draft Report on Unified Speech and Audio Coding Call for Proposals Submissions

33

m15645Hiroshi Saruwatari AAC decoder complexity consideration

relative to the support of different frame lengths

m15646 Shun-ichi Sekiguchi Improved Matching for Global Image Signature

m15647 Yoshihisa Yamada Proposed Improvements for Local Image Signature

m15648 Yoshiaki Kato EE results on Leaving laptop

m15649 Kohtaro Asai Timed Representation of Metadata for the Presentation of Structured Information (PSI)

m15650 Tokumichi Murakami Possible Instantiations of the RoSE Framework

m15651 Shun-ichi Sekiguchi Response to Call for Proposals on RoSE: Sensory Effect Metadata

m15652 Shuichi Yamagishi Response to Call for Proposals on RoSE: Sensory Device Capabilities

m15653 Yusuke Itani TFAN software description

m15654 Kohtaro Asai Update of the API for 3D compression benchmark with MyMultimediaWorld.com

m15655 Tokumichi Murakami France Telecom listening test results for the CfP on Unified Speech and Audio Coding

m15656Kyohyuk Lee France Telecom contribution to the analysis

of the listening test results following the CfP on Unified Speech and Audio Coding

m15657 Elena Alshina Meeting Report of the 27th JVT Meeting (24-29 April 2008, Geneva, Switzerland)

m15658 Jeonghoon Park Image Signature for Complex Conditions

m15659 Woojin Han Error in the ?FRext? extension to the AVC file format

m15660 Junghye Min Proposal for MPEG-4 ALS profile/levels

m15661 Kyohyuk Lee EE results on lovebird2

m15662 Elena Alshina Liaison response on N9787

m15663 Jeonghoon Park CAVLC Validation Procedure and Implementation for AVS in RVC Framework

m15664 Woojin Han Updated text and reference SW for ISO/IEC 23000-9 (DMB-AF)

m15665 Junghye Min Conformance file contribution for ISO/IEC

34

23000-9 (DMB-AF)

m15666 Dong Soo Kim Validation Report for VCE-5

m15667 Sungyong Yoon CE Report on the SC3DMC

m15668 Jaehyun Lim Editorial and Technical Comments on Working Draft of SC3DMC

m15669 Hyun-Kook Lee A Proposal on Quantization of 3D Mesh Coding

m15670 Henney Oh Video content contribution for VCE-7 from KBS

m15671 Yang-Won Jung Video content contribution for VCE-7 from Inha University

m15672 Dong Soo Kim View Synthesis Software and assessment of its performance

m15673 Sungyong Yoon Comments on the preliminary call for proposal for video signature

m15674 Jaehyun Lim EE results on lovebird1 sequence

m15675 Hyun-Kook Lee MPEG User Interface Framework and W3C WebApps Widgets

m15676 Shinya Shimizu Requirements for the MPEG UI Framework

m15677 Hideaki Kimata LASeR Requirements for Person to Person Communication Services Signaling

m15678Shinya Shimizu Report on the subjective testing of Unified

Speech and Audio Coding proposals at Huawei

m15679 Hideaki Kimata DDL of Intra MPEG AVC decoder

m15680 Maeng-Sub Cho DDL Graph Editor

m15681 Jin-Seo Kim Proposal for RoSE Metadata

m15682 Bon-Ki Koo Industry Trends around Video Coding

m15683 Yong Soo Joo Encoder implementation for FAMC

m15684 Sang-Kyun Kim Study text of ISO/IEC 23000-11 FCD Stereoscopic Video Application Format

m15685 Yang-Won Jung Workplan for ISO/IEC 23000-11 Conformance and Reference Software

m15686 Henney Oh Response to MXM Call for Proposals

m15687 Dong Soo Kim Collection of MXM Use Cases

35

m15688 Sungyong Yoon Proposal of MXM Technologies

m15689 Yang-Won Jung Proposal of MXM API

m15690 Henney Oh Response to the extended call for requirements for MPEG-V

m15691 Yang-Won Jung Source code for WaveletSubdivisionSurfaces and Footprint-Based Coding

m15692 Henney Oh Migration of the Reference Software on the SVN

m15693fons.bruls_at_philips.com Proposal for adding support of platform-

independent language tag strings in the 'name' table.

m15694 lincoln.lobo_at_philips.com Proposal for adding support for left-to-right and right-to-left glyph alternatives.

m15695 fons.bruls_at_philips.com Preliminary comments on the 14496-12 PDAM

m15696 lincoln.lobo_at_philips.com Simple View Synthesis

m15697 rene.klein.gunnewiek_at_philips.com Experimental Results for Exploration Experiment in 3D Video

m15698 Miska M. Hannuksela Proposing an Architecture for MPEG Media Value Chain Ontology

m15699 Ye-Kui Wang Modified FUID definition for multiple tool libraries

m15700 Ying Chen Delete

m15701 Jeongil Seo The Single Non-hierarchical Image Signature for All Modifications

m15702 Seungkwon Beack Cross verification result for ETRI VCE-6 proposal

m15703 Kyeongok Kang Introduction of Token description in VTL

m15704 Kwangki Kim Consideration on an approach for developing a new video codec

m15705 hendry_at_icu.ac.kr Update of ISO/IEC 23000-10/Amd1 WD2.0 Conformance and Reference Software

m15706 mkim_at_icu.ac.kr Deleted

m15707 harada.noboru_at_lab.ntt.co.jp Comments on ISO/IEC 23002-4 FCD

m15708 moriya.takehiro_at_lab.ntt.co.jp Comments on ISO/IEC 23001-4 FCD

36

m15709 sblee_at_gist.ac.kr (Sang-Beom Lee) Liaison Statement from SC 27/WG 2

m15710 hoyo_at_gist.ac.kr (Yo-Sung Ho) iKlax Requirements for MPEG Interactive Music

m15711 leecheon_at_gist.ac.kr (Cheon Lee) ATSC Liaison

m15712hoyo_at_gist.ac.kr (Yo-Sung Ho) Java software based on Mpeg7 schema

including amendment ISO/IEC 15938-5:2003/Amd.3:2008

m15713 hendry_at_icu.ac.kr USAC listenig test analysis from LGE

m15714 houari_at_icu.ac.kr Report of AHG on MXM

m15715 mkim_at_icu.ac.kr Comment on proposal for MPEG-4 ALS profiles/levels

m15716 harada.noboru_at_lab.ntt.co.jp Encoder implementation for WaveletSubdivisionSurface

m15717 moriya.takehiro_at_lab.ntt.co.jp MPEG RoSE Framework: A New Work Item?

m15718 leecheon_at_gist.ac.kr (Cheon Lee) Requirements for additional MXM technologies

m15719 hoyo_at_gist.ac.kr (Yo-Sung Ho) Encoder implementation for Footprint-based Coding

m15720 Yasushige Nakayama KNB comment on the Unified Speech and Audio Coding Exploration Activity

m15721 Gi-Mun Um Delete

37

Annex D– Output documents

No. Source Title

09960 Convener List of Documents from the 85th Meeting in Hannover, Germany

09961 Convener Resolutions of the 85th Meeting in Hannover, Germany

09962 Convener List of AHGs Established at 85th Meeting in Hannover, Germany

09963 Convener Report of the 85th Meeting in Hannover, Germany

09964 Convener Guidelines for Electronic Distribution of MPEG M and N Documents

09965 Convener Press Release of the 85th Meeting in Hannover, Germany

09966 Convener Meeting Notice of the 86th Meeting in Busan, Rep. of Korea

09967 Convener Guide for WG 11 Meeting Hosts

09968 Video Disposition of Comments on ISO/IEC 14496-4:2004/FPDAM 30

09969 Video Text of ISO/IEC 14496-4:2004/FDAM 30 Conformance Testing for New Profiles for Professional Applications

09970 Video Disposition of Comments on ISO/IEC 14496-4:2004/FPDAM 31

09971 Video Text of ISO/IEC 14496-4:2004/FDAM 31 Conformance Testing for Scalable Video Coding

09972 Video Working Draft 1 of ISO/IEC 14496-4:2004/Amd.38 Conformance Testing for Multiview Video Coding

09973 Video Request for ISO/IEC 14496-5:2001/Amd.15

09974 Video Text of ISO/IEC 14496-5:2001/PDAM 15 Reference Software for Multiview Video Coding

09975 Video Study Text of ISO/IEC 14496-5:2001/FPDAM 19 Reference Software for Scalable Video Coding

09976 Video Study Text of ISO/IEC 14496-10:200X/DCOR 1

09977 Video Disposition of Comments on ISO/IEC 14496-10:200X/FPDAM 1

09978 Video Text of ISO/IEC 14496-10:200X/FDAM 1 Multiview Video Coding

09979 Video Study Text of ISO/IEC 15938-3:2001/FPDAM 3 Image Signature Tools

09980 Video Use Cases of MPEG-7 Visual Signature Tools

09981 Video Call for Proposals on Video Signature Tools

09982 Video MPEG-7 Visual XM Document version 34.0

09983 Video Working Draft of ISO/IEC 23000-3/Amd.2 Conformance Testing for

38

Photo Player MAF

09984 Video Study Text of ISO/IEC FCD 23001-4 Codec Configuration Representation

09985 Video Study Text of ISO/IEC FCD 23002-4 Video Tool Library

09986 Video WD 2 of ISO/IEC 23002-4/Amd.1 (Conformance and Reference Software)

09987 Video WD 2 of ISO/IEC 23002-4/Amd.2 (Tools for MPEG-4 ASP, AVC HP and SVC)

09988 Video Description of Core Experiments in RVC

09989 Video RVC Work Plan and FU Development Status

09990 Video RVC Vision

09991 Video Description of Exploration Experiments in 3D Video Coding

09992 Video Results of 3D Experts Viewing

09993 Video New Challenges in Video Coding Standardization

09994 Video Workshop on New Challenges in Video Coding Standardization - Call for Contributions

09995 Video Workshop on New Challenges in Video Coding Standardization - Programme

09996 Convener Liaison Statement to SMPTE re RVC

09997 Convener Liaison Statement to ITU-T SG 9 re FTV

09998 Convener Liaison Statement from JVT to ATSC

09999 Convener Liaison Statement from JVT to various Organizations re MVC

10000 Convener Terms of reference

10001 Convener MPEG Standards

10002 Convener Table of unpublished FDISs

10003 Convener Work plan and time line

10004 Convener Editors of MPEG standards

10005 Convener Schema assets updates

10006 Convener Software assets

10007 Convener Conformance assets

10008 Convener Content assets

10009 Convener URI assets

10010 Convener Standards under development for which a call for patent statements is

39

issued

10011 Convener List of organisation with which MPEG is in liaison

10012 Convener Project Editors for ISO/IEC Certificate of Appreciation

10013 3DGC Text of ISO/IEC 14496-4:2004 FPDAM 34 (3DG Compression Model Conformance)

10014 3DGC Request for ISO/IEC 14496-4:2004/AMD39 (Scene Partitioning Conformance)

10015 3DGC Text of ISO/IEC 14496-4:2004 FPDAM 22 (3DG Compression Model Reference Software)

10016 3DGC Request for ISO/IEC 14496-4:2004/AMD25 (Scene Partitioning Reference Software)

10017 3DGC Text of ISO/IEC 14496-16:2006 FDAM 2 (Frame based Animation Mesh Compression)

10018 3DGC Text of WD2.0 of ISO/IEC 14496-16:2006 AMD 4 (Scalable Complexity 3D Mesh Compression)

10019 3DGC DOC on ISO/IEC 14496-16:2006 AMD1:2007 DCOR2 (for 3DMC compression)

10020 3DGC Study Text of ISO/IEC 14496-16:2006 AMD1:2007 COR2

10021 3DGC WD4.0 of AFX 3rd Edition

10022 3DGC CE on Scalable Complexity 3D Mesh Coding

10023 3DGC DOCR on ISO/IEC 14496-5:2001/PDAM 22

10024 Convener AHG on Maintenance of MPEG-4 Visual related Documents, Reference Software and Conformance

10025 Convener AHG on Reconfigurable Video Coding

10026 Convener AHG on MPEG-7 Visual

10027 Convener AHG on 3D Video Coding

10028 Convener AHG on New Challenges in Video Coding Standardization

10029 3DGC Text of ISO/IEC 14496-4:2004 FPDAM 33 (MultiResolution Profile Conformance)

10030 Audio ISO/IEC 13818-4:2004/Amd 2:2005/DCOR 2, AAC Conformance

10031 Audio ISO/IEC 13818-7:2006/DCOR 1, AAC

10032 Audio Report on the Verification Test of MPEG-4 AAC-ELD

10033 Audio WD on New Profiles for ALS and SLS

10034 Audio ISO/IEC 14496-3:2005/DCOR 6, AAC

40

10035 Audio ISO/IEC 14496-3:2005/AMD 2:2006/DCOR 4, HE-AAC V2 Profile

10036 Audio ISO/IEC 14496-3:2005/AMD 3:2006/DCOR 2, SLS

10037 Audio ISO/IEC 14496-3:2005/AMD 9:2008/DCOR 1, AAC-ELD

10038 Audio Considerations regarding the 960 frame length in the MPEG-4 AAC family of profiles

10039 Audio ISO/IEC 14496-4:2004/DCOR 6, AAC-LD

10040 Audio Study on ISO/IEC 14496-4:2004/PDAM 36, AAC-ELD, OAFI and additional AAC Conformance

10041 Audio Proposed ISO/IEC 14496-26, Audio Conformance

10042 Audio ISO/IEC 14496-4:2004/AMD13:200x/DCOR 2, AAC-LD bitstreams

10043 Audio DoC on ISO/IEC 14496-5:2001/FPDAM 20, MPEG-1 and -2 on MPEG-4

10044 Audio ISO/IEC 14496-5:2001/FDAM 20, MPEG-1 and -2 on MPEG-4

10045 Audio Study on ISO/IEC CD 23003-2:200x, Spatial Audio Object Coding

10046 Audio Status and Workplan on SAOC Core Experiments

10047 Audio Report on Unified Speech and Audio Coding Call for Proposals

10049 Convener Liaison response to ITU-T SG 16 (m15261, m15516)

10050 Convener Liaison response to IEC TC 100 (m15555)

10051 Convener Response to FNB (m15720)

10052 Convener Response to KNB (m15551)

10053 Convener AHG on Audio Standards Maintenance

10054 Convener AHG on SAOC, USAC, and Support for new Loudspeaker Configurations

10055 Convener Liaison statement to ATSC on Carriage of SVC

10056 Convener Liaison statement to DVB on Carriage of SVC

10057 Convener Liaison statement to SCTE on Carriage of SVC

10058 Systems DoC on ISO/IEC 13818-1:2007/FPDAM3.2 Carriage of SVC in MPEG-2 Systems

10059 Systems Text of ISO/IEC 13818-1:2007/FDAM3.2 Carriage of SVC in MPEG-2 Systems

10060 Convener AHG on 3DGC documents, software maintenance and core experiments

10061 Systems Study of ISO/IEC 14496-12/PDAM.1 Misc. Addition to FF

41

10062 Systems ISO/IEC 14496-15 WD2.0 MVC File Format

10063 Systems ISO/IEC 14496-15/DCOR3

10064 Systems Request for ISO/IEC 14496-20 LASeR Amd.2

10065 Systems Text of ISO/EC 14496-20 LASeR/PDAM2

10066 Systems WD1.0 of ISO/EC 14496-20 LASeR/Amd.3 Presentation of Structured Information

10067 Systems DoC on ISO/IEC CD 14496-22/ 2nd Edition

10068 Systems Text of ISO/IEC FCD 14496-22 2nd Edition

10069 Systems MPEG-4 White Paper - Font Format

10070 Systems WD1.0 of ISO/IEC 21000-19 Media Value Chain Ontology

10071 Systems MPEG-A White Paper - Professional Archival Application Format

10072 Systems WD1.0 of ISO/IEC 23000-6/Amd1 PA-AF Conformance and Reference Software

10073 Systems Request for ISO/IEC 23000-9/Amd.1 DMB AF Conf. And Ref. Soft.

10074 Systems Text of ISO/IEC 23000-9/PDAM1 DMB AF Conf. And Ref. Soft.

10075 Systems Draft DoC on ISO/IEC FCD 23000-10 (Video Surveillance Application Format)

10076 Systems Study Text of ISO/IEC FCD 23000-10 (Video Surveillance Application Format)

10077 Systems Request for ISO/IEC 23000-10/Amd.1 VS AF Conf. And Ref. Soft.

10078 Systems Text of ISO/IEC 23000-10/PDAM1 VS AF Conf. And Ref. Soft.

10079 Systems Study Text of ISO/IEC FCD 23000-11 (Stereoscopic Video Application Format)

10080 Systems Workplan for Stereoscopic Video Application Format Ref. Soft and Conf.

10081 Systems WD1.0 of ROSE

10082 Systems Core Experiments on ROSE

10083 Systems WD1.0 of MXM Architecture and Technologies

10084 Systems WD1.0 of MXM APIs

10085 Systems Context and Objectives of Rich Media UI Framework

10086 Requirements Requirements on technologies to support Interactive Digital Radio

10087 Webmaster VOID - Document number not used

10088 Convener Liaison statement to SC34/WG2 on Open Font Format

42

10089 Convener Liaison statement to WG 1 on PA-AF

10090 Convener Liaison statement to ITU-T SG16 on IPTV

10091 Convener Guide to MPEG Subversion Repository

10092 Convener Liaison statement to Open IPTV Forum on IPTV

10093 Convener Liaison statement to ATSC M/H on Rich Media

10094 Convener Liaison statement to DVB MIS

10095 Convener Liaison statement to TC 100 on Audio Book

10096 Convener Liaison statement to TC 100 on CDV 60728-1-2

10097 Convener Liaison statement to TC 100 on NP: Multimedia Systems and Equipment

10098 Convener Ad Hoc Group on Scene Representation

10099 Convener Ad Hoc Group on MPEG File Formats

10100 Convener Ad Hoc Group on Application Format

10101 Convener AHG on MVCO WD Editing

10102 Convener AHG on the RoSE Framework

10103 Convener AHG on Font Format

10104 Requirements Draft Requirements for MPEG-V Version 2

10105 Requirements MPEG-V Extended Call for Requirements

10106 Requirements Requirements for additional MxM Technologies

10107 Requirements CfP for additional MXM technologies

10108 Requirements MAF Overview

10109 Requirements Draft Call for Proposals on Interactive Music Application Format

10110 Convener AHG on Information Exchange with Virtual Worlds

10111 Requirements MAF Overview presentation document

43

Annex E – Requirements report

Source: Jörn Ostermann (Leibniz Universität Hannover)

1. Requirements documents approved at this meeting

No. TitleN10086

Requirements on technologies to support Interactive Digital Radio

N10104

Draft Requirements for MPEG-V Version 2

N10105

MPEG-V Extended Call for Requirements

N10106

Requirements for additional MXM technologies

N10107

CfP for additional MXM technologies

N10108

MAF Overview

N10109

Draft Call for Proposals on Interactive Music Application Format

N10111

MAF Overview presentation document

2. MPEG-V: Information exchange with virtual worlds

The following responses to the Extended Call for requirements have been received as contributions to the 85th Hannover MPEG meeting:

M15615: Response to the extended call for requirements for MPEG-VM15617: Response to the extended call for requirements for MPEG-V M15690: Response to the extended call for requirements for MPEG-V

These contributions focus mainly on MPEG-V Part 3 ‘Interfaces between virtual worlds and physical world’. They were integrated into the existing MPEG-V draft requirements document (N9902). The architecture for MPEG-V has been further developed (Figure 1). It appears that MPEG-V as well as Rose can fit into one architecture (Figure 2).

Several companies indicated that there are additional requirements that will be contributed at the next meeting. In order to accommodate these requirements, a new requirements document N10104 (Draft Requirements for MPEG-V Version 2) and another call for requirements N10105 (MPEG-V Extended Call for Requirements) were issued. The work plan agreed upon in the 83rd meeting has been delayed by one meeting again since the requirements for this work item are not yet in a sufficiently mature state. However, another delay in issuing the call for proposals beyond the 86th meeting might endanger the MPEG-V project.

44

Figure 1 Architecture for MPEG-V

Figure 2 Mapping of Rose onto the MPEG-V Architecture

ConsumerDevice(s)

SDC

SE

SDCUSP

RoSE Engine

RoSE

RoSE Engine

Sensory Effect

Metadata

Provider Consumer Device(s)

User Sensory Preferences

Sensory Device

Capabilities

Sensory Device

CommandsSensory Effect Delivery Format

User Preferences Delivery Format

Sensory Device Capability Delivery Format

1

1

2

2

3

4

3

4 Sensory Device Command Delivery Format

Scope of standarization(Normative)

Not in the scope of standarization(Informative)

Digital Content Provider (Virtual World,(serious) game,simulator, DVD, …)

45

3. RoseThe following documents have been submitted as a response to the call for proposals (N9899) on three work items (Sensory Effects Metadata, User Sensory Preferences Metadata, and Sensory Device Capabilities/Commands Metadata):M15560: Sensory Effects Metadata for RoSE FrameworkM15561: User Sensory Preferences Metadata for RoSE FrameworkM15562: Sensory Device Capabilities Metadata for RoSE FrameworkM15563: Sensory Device Commands Metadata for RoSE FrameworkM15585: RoSE description schemes for realistic TV commercialsM15612: Response to the call for technologies for RoSEM15650: Possible Instantiations of the RoSE FrameworkM15651: Response to Call for Proposals on RoSE: Sensory Effect MetadataM15652: Response to Call for Proposals on RoSE: Sensory Device CapabilitiesM15681: Proposal for RoSE Metadata

The evaluation of the response to the call extracted sufficient technology to start the technical work for the standard. Therefore, Rose was transferred to the Systems Group. There was no agreement yet on which part of MPEG should be the home for Rose. At this point, the options are a separate standard for Rose, Rose as part of MPEG-4 and Rose as part of MPEG-V. The latter option appears to be the most appealing.

4. Media Value Chain OntologyAs a response to its Call for Proposals (N9907), MPEG received two contributions by three organisations:M15631 Ontology for IP Media Networks (IPM-Net)M15698 Proposing an Architecture of MPEG Media Value Chain OntologyThe evaluation of the response to the call extracted sufficient technology to start the technical work for the standard. Therefore, MVCO was transferred to the Systems Group. It will become part of MPEG 21.

5. Interactive Music Application Format MAFA MAF supporting playback of multiple audio streams was requested at the 84th meeting. Compared to the music player MAF, additional streams have to play synchronously. An additional requirement was presented at this meeting:M15710: iKlax Requirements for MPEG Interactive Music In order to provide some control over the playback to the music author, constraints on how different streams are played back have to be definable. It appears that no new coding technology has to be developed in order to enable the available requirements.

A Draft Call for Proposals on Interactive Music Application Format (N10109) was issued. We expect to finalize the call at the next meeting. Since the companies presenting requirements are already selling products in the market, a timely development of a MAF appears to be important.

6. MPEG eXtensible Middleware (MXM)In response to the CfP (N9894) for MXM and associated Requirements (N9893), one proposal supported by several companies has been received.M15686: Letter accompanying the response

46

M15687: Collection of use casesM15688: Specification of the technologies that are required to match the use casesM15689: Proposed specificationSince the proposed solution provides sufficient technical substance for technical work, this work item was transferred to the Systems Group. In their proposal, the contributors identify additional requirements for MXM mainly in the area of protocols for content identification, authorisation and storage. Since these requirements were found to be valid, new requirements and a new call were issued: N10106 Requirements for additional MXM technologiesN10107 CfP for additional MXM technologies

7. LASeR for Person to Person CommunicationsLASeR is currently used on many mobile platforms. However, it lacks efficient capabilities to communicate with other terminals:M15677 LASeR Requirements for Person to Person Communication Services Signallingdefines these.

8. Lossless Audio CodingSeveral requests for standardizing a profile for lossless audio coding were made by different industries. M15628 Proposed new profile for MPEG-4 SLSM15660 Proposal for MPEG-4 ALS profile/levelsM15715 Comment on proposal for MPEG-4 ALS profiles/levelsThe first two profiles for coding lossless audio are now defined in WD on New Profiles for ALS and SLS (N10033):

SLS, which is supported by several companies, provides an enhancement to AAC and it will be called HD-AAC. The selected tools provide a good balance between coding efficiency and complexity.

ALS, which is requested by ARIB (Association of Radio Industries and Business) in Japan, is seen as a low complexity alternative to PCM coding of multi-channel audio signals. In order to stabilize this profile, firm support from the ARIB consortium will have to be provided.

9. Explorations

9.1. Requirements for Interactive RadioRequirements for Interactive Radio over DMB for French radio stations were brought to MPEG:M15550 New BIFS Profile for Interactive Digital Radio

While the proposers identify BIFS as a technology to satisfy the requirements, it is not clear whether that solution is preferable to a LASeR-based solution. A requirements documentN10086 Requirements on technologies to support Interactive Digital Radiohas been issued. This document is technology agnostic.

9.2. Exploration on MPEG User Interface FrameworkAs user interfaces (UI) become more divers and more plentiful, MPEG would like to explore currently available UI technology and investigate what is still missing in order to make MPEG technology more usable in modern user interfaces considering requirements like description language for UI specification, personalization, UI exchange between devices and

47

UI aggregation. This exploration was described in N9895 at the last meeting. Additional requirements were received at this meeting:M15601 Additional Use Cases for UI FrameworkM15676 Requirements for the MPEG UI FrameworkThe exploration document was not updated. Work on the architecture for MPEG UI progressed.

9.3. Presentation of Structured Information (PSI)MPEG wants to develop a standard that enables declarative representation of structured information such as MPEG-21 Digital Item to maintain interoperable presentation of it across different implementations by conforming such standard, so-called PSI (Presentation of Structured Information). MPEG received two responses to the call for proposals (N9905) and associated requirements (N9904):M15622 Proposal for the Presentation of Structured InformationM15649 Timed Representation of Metadata for the Presentation of Structured Information

(PSI)Since most of the requirements are at least partially fulfilled, the technical work started in the Systems Group.

9.4. Future Work ItemsAudio, 3DGC, and Video subgroups continued to brainstorm on directions subject to further MPEG standards. Gaming was identified as an application area that could make use of MPEG technology beyond the currently used image, video and texture coding technology. Especially the use of geometry coding appears to be beneficial to the industry.

A meeting on the future of video coding with several company contributions outlining the roadmap for display, storage device and the requirements on network bandwidth was attended by more than 200 participants. M15577 Requirements for next-generation video coding standardM15704 Consideration on an approach for developing a new video codecM15579 Analysis for Ad Hoc Group on New Challenges in Video Coding Standardization M15580 Technical considerations for Ad Hoc Group on New Challenges in Video Coding

StandardizationThere appears to be a trend towards consumer displays with a resolution of 4k or 8k pixels/line at 60 Hz progressive scan. Storage capacity will be available. The request for transmitting video to the consumer at a rate below 50Mb/s was made. 2012 is envisioned for the start of using 4k displays in consumer applications. One demonstration showed HD video coding rate reductions of 25%. However, it is unclear whether current MPEG test sequences were shot with cameras of appropriate optical and electrical resolution.Internal documents capturing the state of discussion were improved and appropriate adhoc groups established. At the 85th meeting, a one-day workshop on New Challenges in Video Coding Standardization will be held.

48

Annex F – Systems report

Source: Systems Chair and Break-out group ChairsTitle: Systems Meeting ReportStatus: DraftEditor: Olivier Avaro (Streamezzo)

Contributors: David Singer (Apple), Young-Kwon Lim (Net&TV), Gero Baese (Siemens), Jaieme Delgado (UPC), Christian Timmerer (University of Klagenfurt)

1 OverviewThe main outputs of the meeting from the Systems Sub-group perspective are:No. Title TBP AvailableX 13818-1 MPEG-2 Systems10058 DoC on ISO/IEC 13818-1:2007/FPDAM3.2 Carriage of SVC in MPEG-2

SystemsNo 08/07/25

10059 Text of ISO/IEC 13818-1:2007/FDAM3.2 Carriage of SVC in MPEG-2 Systems No 08/08/15X 14496-12 ISO File Format10061 Study of ISO/IEC 14496-12/PDAM.1 Misc. Addition to FF No 08/07/25X 14496-15 AVC File Format10062 ISO/IEC 14496-15 WD2.0 MVC File Format No 08/07/2510063 ISO/IEC 14496-15/DCOR3 No 08/07/25X 14496-20 LASeR10064 Request for ISO/IEC 14496-20 LASeR Amd.2 No 08/07/2510065 Text of ISO/EC 14496-20 LASeR/PDAM2 No 08/07/2510066 WD1.0 of ISO/EC 14496-20 LASeR/Amd.3 No 08/07/25X 14496-22 Open Font Format10067 DoC on ISO/IEC CD 14496-22 2nd Edition No 08/07/2510068 Text of ISO/IEC FCD 14496-22 2nd Edition Yes 08/09/1210069 MPEG-4 White Paper – Font Format Yes 08/07/25X 21000-19 Media Value Chain Ontology10070 WD1.0 of ISO/IEC 21000-19 Media Value Chain Ontology No 08/07/25X 23000-6 Professional Archival Application Format10071 MPEG-A White Paper – Professional Archival Application

FormatYes 08/08/15

10072 WD1.0 of ISO/IEC 23000-6 PA-AF/Amd.1 Conformance and Reference Software

No 08/07/25

X 23000-9 Digital Multimedia Broadcasting Application Format10073 Request for ISO/IEC 23000-9/Amd.1 DMB AF Conf. And Ref. Soft. No 08/07/2510074 Text of ISO/IEC 23000-9/PDAM1 DMB AF Conf. And Ref. Soft. No 08/07/25X 23000-10 Video Surveillance Application Format10075 Draft DoC on ISO/IEC FCD 23000-10 (Video Surveillance Application Format) No 08/07/2510076 Study Text of ISO/IEC FCD 23000-10 (Video Surveillance Application Format) No 08/08/1510077 Request for ISO/IEC 23000-10/Amd.1 VS AF Conf. And Ref. Soft. No 08/07/2510078 Text of ISO/IEC 23000-10/PDAM1 VS AF Conf. And Ref. Soft. No 08/08/15X 23000-11 Stereoscopic Video Application Format10079 Study Text of ISO/IEC FCD 23000-11 (Stereoscopic Video Application Format) No 08/07/2510080 Workplan for Stereoscopic Video Application Format Ref. Soft and Conf. No 08/07/25X Project Started – Representation of Sensory Experience10081 WD1.0 of ROSE No 08/07/2510082 Core Experiments on ROSE No 08/07/25X Project Started – MPEG eXtensible Middleware10083 WD1.0 of MXM Architecture and Technologies No 08/07/25

49

10084 WD1.0 of MXM APIs No 08/07/25X Exploration10085 Context and Objectives of Rich Media UI Framework No 08/07/25X Assets and Standing Documents10005 MPEG Schema Assets Updates No 08/07/2510009 MPEG URIs No 08/07/25X Liaison10088 Liaison statement to SC34/WG2 on Open Font Format No 08/07/2510089 Liaison statement to WG 1 on PA-AF No 08/07/2510090 Liaison statement to ITU-T SG16 on IPTV No 08/07/2510091 Liaison statement to ATIS IPTV FG on IPTV No 08/07/2510092 Liaison statement to Open IPTV Forum on IPTV No 08/07/2510093 Liaison statement to ATSC M/H on Rich Media No 08/07/2510094 Liaison statement to DVB MIS No 08/07/2510095 Liaison statement to TC 100 on Audio Book No 08/07/2510096 Liaison statement to TC 100 on CDV 60728-1-2 No 08/07/2510097 Liaison statement to TC 100 on NP: Multimedia Systems and

EquipmentNo 08/07/25

10055 Liaison statement to ATSC on Carriage of SVC No 08/07/2510056 Liaison statement to DVB on Carriage of SVC No 08/07/2510057 Liaison statement to SCTE on Carriage of SVC No 08/07/25

50

2 General issues

2.1 GeneralThe meeting report from Antalya has been approved.The following demonstrations have been made:

None.

2.2 List of standards under developmentPr Pt Edit. Project Description CfP WD CD FCD FDIS

2 1 2006 Cor.2 Transport of AVC 08/04 08/104 1 200x Amd.4 Registration

Authority07/10 08/10 09/01

4 4 2008 Amd.37 File Format Conf. 08/04 08/10 09/02 09/074 5 2007 Amd.14 Open Font Format

Ref. Soft07/10 07/10 08/04 09/01

4 5 2007 Amd.xx AVC File Format Ref. Soft

TBS

4 5 2007 Amd.xx SVC File Format Ref. Soft

TBS

4 5 2007 Amd.23 Synth. Texture Ref. Soft

08/04 08/10 09/04

4 11 2005 Amd.6 Scene Partitioning 08/01 08/04 08/104 12 200x Amd.1 Misc. Addition to FF 08/04 08/10 09/044 12 200x Cor.1 Cor. On Flute 08/04 08/104 15 200x Amd.3 MVC File Format 08/04 08/10 09/02 09/074 20 2008 Amd.2 Scene Adaptation 08/07 08/10 09/074 20 2008 Amd.3 PSI 08/07 08/10 09/02 09/074 22 2008 2nd Ed. Open Font Format 08/01 08/07 09/0121 7 200x Cor.1 DIA Cor. 08/04 08/1021 8 200x Amd.1 Minor Enhance. Ref.

Soft07/10 08/04 08/10

21 19 200x 1st Ed. Media Value Chain Onto.

08/07 08/10 09/02 09/07

A 4 200x Amd.1 MSS AF Conf. and Soft

07/07 07/10 08/04 08/10

A 4 200x Amd.2 Prot. MSSAF Conf. & Soft

08/04 08/10 09/04

A 5 200x 2nd Ed. MS AF 08/01 08/10 09/02 09/07A 6 200x 1st Ed. Professional

Archival AF07/10 08/01 08/04 08/10

A 7 200x Amd.1 OA AF Ref. Soft and Conf.

08/01 08/04 08/10

A 8 200x Amd.1 PVP AF Soft. And Conf.

A 9 200x Amd.1 DMB AF Soft. And Conf.

08/07 08/10 09/04

A 10 200x 1st Ed. Video Surveillance 07/04 07/07 08/01 08/10

51

AFA 10 200x Amd.1 Video Surveillance

AFA 11 200x 1st Ed. Stereoscopic Video

AF07/04 08/01 08/04 08/10

A 11 200x 1st Ed. SVAF Ref. Soft. And Conf.

08/07 08/10 09/04 09/07

B 2 200x Amd.1 FRU Ref. Soft. And Conf.

E 8 200x 1st Ed. Ref. Soft. and Conformance

07/01 07/07 08/04 08/10

X - - - Rep. of Sens. Exp. 08/07 08/10 08/02 09/07X - - - MxM 08/07 08/10 08/02 09/07

52

2.3 Standing Documents

Pr Pt Documents No. Meeting1 1 MPEG-1 White Paper – Multiplex Format N7675 05/07 Nice1 1 MPEG-1 White Paper – Terminal Architecture N7676 05/07 Nice1 1 MPEG-1 White Paper – Multiplexing and

SynchronizationN7677 05/07 Nice

2 1 MPEG-2 White Paper – Multiplex Format N7678 05/07 Nice2 1 MPEG-2 White Paper – Terminal Architecture N7679 05/07 Nice2 1 MPEG-2 White Paper – Multiplexing and

SynchronizationN7680 05/07 Nice

2 11 MPEG-2 White Paper – MPEG-2 IPMP N7503 05/07 Poznan4 1 MPEG-4 White Paper – MPEG-4 Systems N7504 05/07 Poznan4 1 MPEG-4 White Paper – Terminal Architecture N7610 05/10 Nice4 1 MPEG-4 White Paper – M4MuX N7921 06/01 Bangkok4 1 MPEG-4 White Paper – OCI N8148 06/04 Montreux4 6 MPEG-4 White Paper – DMIF N8149 06/04 Montreux4 11 MPEG-4 White Paper – BIFS N7608 05/10 Nice4 12 MPEG-4 White Paper – ISO File Format N8150 06/04 Montreux4 14 MPEG-4 White Paper – MP4 File Format N7923 06/01 Bangkok4 15 MPEG-4 White Paper – AVC FF N7924 06/01 Bangkok4 13 White Paper on MPEG-4 IPMP N7505 05/07 Poznan4 13 MPEG IPMP Extensions Overview N6338 04/03 München4 17 White Paper on Streaming Text N7515 05/07 Poznan4 18 White Paper on Font Compression and Streaming N7508 05/07 Poznan4 20 Presentation Material on LASER N6969 05/01 Hong-

Kong4 20 White Paper on LASeR N7507 05/07 Poznan4 22 White Paper on Open Font Format N7519 05/07 Poznan7 1 MPEG-7 White Paper - MPEG-7 Systems N7509 05/07 Poznan7 1 MPEG-7 White Paper – Terminal Architecture N8151 06/04 Montreux21 9 MPEG-21 White Paper – MPEG-21 File Format N7925 06/01 BangkokA X MPEG Application Format Overview N9421 07/10 ShenzhenA X MAF Overview Document N9840 08/04

ArchampsA X MAF Overview Presentation N9841 08/04

ArchampsB X MPEG-B White Paper – BinXML N7922 06/01 BangkokE X MPEG Multimedia Middleware Context and

ObjectivesN6335 04/03 München

E X 1rst M3W White paper N7510 05/07 PoznanE X 2nd M3W White Paper : Architecture N8152 06/04 MontreuxE X Tutorial on M3W N8153 06/04 MonreuxE X M3W White Paper : Multimedia Middleware

ArchitectureN8687 06/10 Hanzhou

E X M3W White Paper : Multimedia API N8688 06/10 HanzhouE X M3W White Paper : Component Model N8689 06/10 HanzhouE X M3W White Paper : Resource and Quality

ManagementN8690 06/10 Hanzhou

53

E X M3W White Paper : Component Download N8691 06/10 HanzhouE X M3W White Paper : Fault Management N8692 06/10 HanzhouE X M3W White Paper : System Integrity

ManagementN8693 06/10 Hanzhou

54

2.4 Mailing Lists Reminder

Topic Information Kindly Managed by

General Systems

List

Liste Reflector : gen-sys@lists.uni-klu.ac.atList-Subscribe:

http://lists.uni-klu.ac.at/mailman/listinfo/gen-sysmailto:gen-sys-request@lists.uni-klu.ac.at?subject=subscribe

List-Archive: http://lists.uni-klu.ac.at/pipermail/gen-sysList-Help: mailto:gen-sys-request@lists.uni-klu.ac.at?subject=help

University of Klagenfurt

BiM

Liste Reflector : mpeg7-sys@lists.uni-klu.ac.atList-Subscribe:

http://lists.uni-klu.ac.at/mailman/listinfo/mpeg7-sysmailto:mpeg7-sys-request@lists.uni-klu.ac.at?subject=subscribe

List-Archive: http://lists.uni-klu.ac.at/pipermail/mpeg7-sysList-Help: mailto:mpeg7-sys-request@lists.uni-klu.ac.at?subject=help

University of Klagenfurt

File Format

Liste Reflector : mp4-sys@lists.uni-klu.ac.atList-Subscribe:

http://lists.uni-klu.ac.at/mailman/listinfo/mp4-sysmailto:mp4-sys-request@lists.uni-klu.ac.at?subject=subscribe

List-Archive: http://lists.uni-klu.ac.at/pipermail/mp4-sysList-Help: mailto:mp4-sys-request@lists.uni-klu.ac.at?subject=help

University of Klagenfurt

LASeR

Liste Reflector : mpeg-laser@lists.uni-klu.ac.atList-Subscribe:

http://lists.uni-klu.ac.at/mailman/listinfo/mpeg-lasermailto:mpeg-laser-request@lists.uni-klu.ac.at?subject=subscribe

List-Archive: http://lists.uni-klu.ac.at/pipermail/mpeg-laserList-Help: mailto:mpeg-laser-request@lists.uni-klu.ac.at?subject=help

University of Klagenfurt

MAF

Liste Reflector : maf-sys@lists.uni-klu.ac.atList-Subscribe:http://lists.uni-klu.ac.at/mailman/listinfo/maf-sysmailto:maf-sys-request@lists.uni-klu.ac.at?subject=subscribeList-Archive: http://lists.uni-klu.ac.at/pipermail/maf-sysList-Help: mailto:maf-sys-request@lists.uni-klu.ac.at?subject=help

University of Klagenfurt

MPEG-2 on File Format

#1: Please subscribe via http://lists.uni-klu.ac.at/mailman/listinfo/isoff-transport. Please use only that email address for posting messages with which you're subscribed. Otherwise the email won't be delivered. #2: The email address for posting messages is: isoff-transport@lists.uni-klu.ac.at

University of Klagenfurt

55

 #3: The archive is accessible via http://lists.uni-klu.ac.at/mailman/private/isoff-transport/ for list members only.

2.5 FAQThe FAQ were updated as needed.

2.6 AOBNone.

3 MPEG-2 Systems (13818-1)

3.1 General

3.2 13818-1:2005 Amd.3 Carriage of SVC

3.2.1 Topics1. Transport of Scalable Video Coding

3.2.2 ContributionsM15522: Summary of Voting on ISO/IEC 13818-1:2007/FPDAM 3.2 [SC 29 N 9517].See DoC. Taken into account to produce FDAM text.

Work Completed

3.3 13818-1:2005 DCOR.2

3.3.1 Topics1. Corrigendum on the carriage of AVC

3.3.2 ContributionsNone.

Technical Work in Progress.

4 MPEG-4 Conformance (14496-4)

4.1 14496-4 Amd.37 File Format Conformance

4.1.1 Topics1. File Format Conformance

56

Since we said we were waiting for critical mass, and nothing arrived here, probably no action now. Editors to review whether (a) we have all the information for these files and (b) what features still need conformance action.

[After meeting: the spreadsheet looks pretty good. Only a few features are not covered. If no comments and no new files in Busan, maybe we should issue PDAM there.]

Technical Work in Progress.

5 MPEG-4 Reference Software (14496-5)

5.1 14496-5 Amd.14

5.1.1 Topics1. Open Font Format Reference Software

5.1.2 ContributionsNone.

Technical Work In Progress.

5.2 14496-5 Amd.23

5.2.1 Topics1. Synthesized Texture Reference Software

5.2.2 ContributionsNone.

Technical Work In Progress.

6 MPEG-4 Scene Presentation (14496-11)

6.1 14496-11/Amd.6

6.1.1 Topics1. Scene Partitionning

6.1.2 ContributionsNone.

Technical Work In Progress.

57

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

7.1 14496-12/Cor1

7.1.1 Topics1. Corrigendum Items

7.1.2 ContributionsNone.

Technical Work In Progress.

7.2 14496-12:2008/Amd1

7.2.1 Topics1. New Edition & Amd.1

7.2.2 15611 File format support for reception of SRTP and MIKEY messagesExcellent, thank you. Editors to make a study text and a resolution asking NBs to consider the study. The ROC storage remains somewhat an open question (sample groups? sample entry? sample?). Comments, please. Also, we suggest boxing the key indicator length as this is syntactically compatible with OMA. However, the DVB liaison has a different design (5.4.2.3.2) and it’s hard to see how we can be compatible with both. Comments, please.

7.2.3 15695 Preliminary comments on the 14496-12 PDAMNoted, thank you. Some of these questions were explained at this meeting and this may help you revise the questions.

We are slightly concerned that we need to do a lot, once we have received comments, and that we might not have all the experts we need in Busan. Would an ad-hoc meeting help? If so, neither date nor location are obvious.

Technical Work in Progress.

8 MPEG-4 AVC Base File Format (14496-15)

8.1 14496-15:2004/Amd.3? MVC FF

8.1.1 Topics1. MVC File Format Extensions

8.1.2 15600 On MVC File FormatThank you. We agree a file format sample is one or more view components (of one access unit). The track references seem right; maybe we can allow applications to decide whether the AVC base must be in its own track or not?Some of this addresses the same questions as the next contribution and the minutes there reflect consideration of both.

58

8.1.3 15591 Proposals for MVC File FormatThank you. Lots of detailed work here. One overall question for the two contributions is to what extent we can use the same code points (e.g. track reference types) as SVC even if the 4 characters aren’t quite ‘right’ for MVC. Another is whether some use of extractors would enable building complete ‘cookbook’ tracks for a given (set of) view(s). (Tracks which were then essentially ‘complete’ could then be so marked).Maybe in the case that there are both (a) multiple views per track and (b) multiple tracks, then the groups are mandatory (or else merging two tracks would require decoding NAL unit headers and perhaps slice headers, and SPSs). (Indeed, this is in the revised WD).

The use of alternate groups seems complex. Are the members of the groupdifferent views from the same set of multiple views?different multiple view groups?alternative ‘simple video’ versions of particular views of a multiple view set?

Looks like the proposal covers this, with the major difference from SVC that (a) are not a group. We can use sample groups, track references, and track selection info however. We probably need a track selection entry that says “I differ by multi-view or view coding” (e.g. the same set of views with a different base).

Some concern about movie-level structures as they are fragile with respect to track addition or deletion. There is also some overlap here with track selection, but of course this is handling sets of tracks etc. But it’s not at all clear that this can be re-written as a ‘distributed program’ across the multiple tracks. One possible idea is to have tracks with the groups, meta-data and track references but no samples? Is there a place for all the data? What boxes in the sample table would be empty or missing? This needs thought. Indeed, such a track could have extractors to say how to make it (optionally) and indeed we could have a bit next to complete_rep that says whether the track knows how to build all the data for this view set. But that adds a ‘mode’ to the reader. More thought needed. This might mesh well with using track selection information, on first look.

We’re currently not using extractors, but it may be that there are some uses; perhaps for indicating ‘cookbook’ all the data for a set of views (including dependency). Indeed, in that case, where more than one view is wanted, the order of extractors and NAL units would be define at least partially the needed output order (but not fully)?

The maximum disparity might vary over time. Should this be in a temporal structure (e.g. sample groups)? The trouble is that it is a piece of information about the relationship between two views, which in turn might be in multiple tracks. Clearly at file level this can be the overall max_disparity, of course.

Do we need to say more about where parameter sets are stored (in the track closest to the base, following dependencies, of the views that need this parameter set?).

Do we go to PDAM? If it doesn’t make a difference to the completion date, no. The FF group also leans towards no, but the editor to check the calendar and systems plenary to decide.

[After the meeting: There isn’t time for a ballot now before Busan, so any FPDAM would be in Lausanne either way, so we hold off and do PDAM at Busan.]

59

8.1.4 15659 Error in the ‘FRext’ extension to the AVC file format Three choices:change the if to simply if (more_data), and use the sps_ext array always; question: what

about sps_ext in SVC enhancement layers?move the sps_ext to the sps array always; but what about existing implementations using the

indicated profiles?hybrid; leave it where it is for these profiles, and put them in the sps array otherwise.

We go with (c).On the reserved NAL units, it should be that both the AVC spec and the file format spec reserve the value. Then ignore the NA.

Technical Work in Progress.

9 MPEG-7

9.1 15938-5 Reference Software

M15712: Java software based on Mpeg7 schema including amendment ISO/IEC 15938-5:2003/Amd.3:2008. Document not uploaded.

10 LASeR (14496-20)

10.1 14496-20/Amd.xxx

10.1.1 Topics1. LASeR Extensions2. Presentation of Structured Information

10.1.2 ContributionsM15614: CD proposal of LASeR in IPTV. This contribution analysis the open issues listed in the current WD. Dispositions to proposed items are as follows:

attribute vs. element : Accepted to define new attributes. There was understanding that adding new attribute might violate the extension rule defined by W3C. However, this rule doesn’t seem to be generally obeyed. Therefore, it would be better to take technically preferable solution.

attributes to describe adaptation criteria : accepted to define only minimum values for screen size and available memory. It was concerned that it’s not easy to measure and apply CPU power and remaining battery in a meaningful way.  

display size event for dynamic adaptation : accepted to include. EnhancedSceneIndicator in the LASeR header : accepted priority: Accepted in principal. Detailed syntax and semantics should clearly mention

the selection criteria for the case of combination of this priority and other attributes. alternative : rejected because this is duplication of features already supported by

switch

60

resource (change) events : accepted to include DisplaySizeChange and MemoryStatus events

M15622: Proposal for the Presentation of Structured Information. Was reviewed in detail in the AHG (see AHG report). Taken as a basis to produce related specification.

M15649: Timed Representation of Metadata for the Presentation of Structured Information (PSI). Was reviewed in detail in the AHG (see AHG report). Already a standard of MPEG. Can be used in a more general framework where server side standardization is usefull.

Technical Work in Progress.

11 LASeR (14496-22) Open Font Format

11.1 14496-22/Amd.1

11.1.1 Topics

1. Open Font Format Extension

11.1.2 ContributionsM15533: Summary of Voting on ISO/IEC CD 14496-22 [2nd Edition]. See Doc. Taken into account to produce FCD text.

M15693: Proposal for adding support of platform-independent language tag strings in the 'name' table. M15694: Proposal for adding support for left-to-right and right-to-left glyph alternatives. Support for the comments in the DoC. Accepted.

Technical Work in Progress.

12 21000 MPEG-21

12.1 21000-7 DIA

12.1.1 Topics1. Corrigendum

12.1.2 ContributionsNone.

Technical Work In Progress.

12.2 21000-8 Reference Software

12.2.1 Topics1. MPEG-21 Reference Software

61

12.2.2 ContributionsNone.

Technical Work In Progress.

12.3 21000-19 Media Value Chain Ontology

12.3.1 Topics1. Media Value Chain Ontology

12.3.2 ContributionsM15631, M15698 : Ontology for IP Media Networks (IPM-Net): A response to the MVCO CfP and Proposing an Architecture for MPEG Media Value Chain Ontology. Taken as a basis to produce working draft of MVCO.

Technical Work In Progress.

13 MPEG-A MAF (23000)

13.1 23000-5 Media Streaming MA

13.1.1 Topics1. Media Streaming MAF

13.1.2 ContributionsNone.

Technical Work in Progress.

13.2 23000-6 Professional Archival AF

13.2.1 Topics1. Professional AF

13.2.2 ContributionsM15593: Proposed Text for White Paper of ISO/IEC 23000-6 Professional Archival Application Format. Taken as the basis to output the white paper on PA-AF.

M15596: Proposed Text for Working Draft of ISO/IEC 23000-6 PA-AF Reference Software. Taken as basis to out the WD1.0 of ref. soft.

Technical Work in Progress.

13.3 23000-7 Open Access Application Format

13.3.1 Topics1. Open Access Application Format

13.3.2 ContributionsNone.

Technical Work in Progress.

62

13.4 23000-9 DMB Application Format

13.4.1 Topics1. DMB Application Format

13.4.2 ContributionsM15665: Conformance file contribution for ISO/IEC 23000-9 (DMB-AF). Used as the basis to produce PDAM text.M15664: Updated text and reference SW for ISO/IEC 23000-9 (DMB-AF). Used as the basis to produce PDAM text.

Technical Work in Progress.

13.5 23000-10 Video Surveillance MAF

13.5.1 Topics1. Video Surveillance MAF 1st Edition

13.5.2 ContributionsM15523: Summary of Voting on ISO/IEC FCD 23000-10 [SC 29 N 9518]. See DoC.M15705: Update of ISO/IEC 23000-10/Amd1 WD2.0 Conformance and Reference Software.

Technical Work in Progress.

13.6 23000-11 Stereoscopic Video AF

13.6.1 Topics1. Stereoscopic Video AF

13.6.2 ContributionsM15684: Study text of ISO/IEC 23000-11 FCD Stereoscopic Video Application Format. Taken as basis to produce study text.M15685: Workplan for ISO/IEC 23000-11 Conformance and Reference Software. Taken as basis to produce workplan for Conf. and Ref. Soft.

Technical Work in Progress.

13.7 23000-12 Interactive Music AF

13.7.1 Topics1. Interactive Music AF

13.7.2 ContributionsM15710: iKlax Requirements for MPEG Interactive Music. Requirements accepted and integrated in the MAF Overview document.M15626: A proposal for technical specification of Interactive Music AF. Contribution reviewed and noted.

Cf. requirements report for next steps on this activity.

63

14 MPEG-E Multimedia Middleware (23004)

14.1 Multimedia Middleware

14.1.1 Topics1. MPEG Multimedia Middleware

14.1.2 ContributionsNone.

Technical Work in Progress.

15 Project Started

15.1 Representation of Sensory Effects

15.1.1 Topics1. Representation of Sensory Effects

15.1.2 Contributions

Input Contribution Document No.Sensory Effects Metadata for RoSE Framework m 15560 Summary:

— Technologies used: XML Schema, MPEG-7 DS, SNVT from LonWorks— General Structure: Organization of SEM description into SEM, Desc, Seg, frag— Effect List for the mapping process in the RoSE engine, i.e., the mapping of sensory

effects metadata to sensory device commands according to the user preferences and sensory device capabilities Metadata

— Effect Variables for synchronized control of SEM— General information: MPEG-7 description metadata— Attributes: Priority, isMandatory, isAdaptable, DependentEffectID,

AlternativeEffectID— Various sensory effects (see m 15560 for details)— Simple Types (LuxType, FreqType, etc.) adopted from LonWorks— Converted several SNVT binary types to their XML equivalents— Which kind of technology is needed to implement this mapping process? (complexity,

efficiency, etc.)

Action: Go to WD and conduct CE monitored by AhG

Input Contribution Document No.User Sensory Preferences Metadata for RoSE Framework m 15561 Summary:

— Technologies used: XML Schema, MPEG-7 DS— General Structure: Person – Descriptions – Preferences— PreferenceDescription: priority, disableAll + allows for describing detailed effect

preferences

64

— Various preferences (see m 15561 for details) aligned with m 15560 — Harmonize/integrate with MPEG-21 DIA UED User Characteristics and the various

preference types defined there?

Action: Go to WD and conduct CE monitored by AhG

Input Contribution Document No.Sensory Device Capabilities Metadata for RoSE Framework m 15562 Summary:

— Technologies used: XML Schema, LonWorks— Capabilities divided into common capabilities and device-specific capabilities— Various capabilities (see m 15562 for details)— Harmonize/integrate with MPEG-21 DIA UED Terminal Capabilities?

Action: Go to WD and conduct CE monitored by AhG

Input Contribution Document No.Sensory Device Commands Metadata for RoSE Framework m 15563 Summary:

— Technologies used: XML Schema, LonWorks— Also divided into common commands and device-specific commands— Various commands (see m 15563 for details) and aligned with m 15562

Action: Go to WD and conduct CE monitored by AhG

Input Contribution Document No.RoSE description schemes for realistic TV commercials m15 585 Summary:

— Technologies used: XML Schema, MPEG-7 DS/D, MPEG-21 DIA tools, LonWorks— CommercialSensoryEffect: various sensory effects (see m15 585 for details);

overlaps exits with other proposals— CommercialSensoryPreference: various user preferences (see m15 585 for details);

overlaps exits with other proposals— CommercialSensoryDeviceCapability: various device capabilities (see m15 585 for

details); overlaps exist with other proposals— CommercialSensoryDeviceCommand: the commands (see m15 585 for details);

overlaps exist with other proposals— Complete proposal (similar to m15560-63) and it may need to be harmonized with

other proposals, i.e., identify overlaps, etc.

Action: Go to WD and conduct CE monitored by AhG

Input Contribution Document No.Response to the call for technologies for RoSE m15 612 Summary:

— Technologies used: no detailed information available (see below)— Overview of amBX which stands for “ambient experience”— amBX script = sensory effect metadata— Experience description: high-level abstraction (sunny, cool, explosion) and low-level

abstraction (turn on fan at speed x)

65

— Timing: start, end, duration— Conditional and priority mechanisms— If the set of devices changes, the engines takes into account, e.g., if device is removed

the engine will try to transfer experience parts to remaining devices— Some minor remarks w.r.t. the RoSE requirements— No xml schema’s provided at this meeting, will be provided after discussions of the

terms and conditions of the scope of the activity — Need to revise the requirements based on the remarks of this input contribution— Need to discuss the details of the technologies when provided

Action: Go to WD and conduct CE monitored by AhG

Input Contribution Document No.Possible Instantiations of the RoSE Framework m15 650 Summary:

— Informative contribution presenting possible instantiations of the RoSE framework: unicast, multicast/broadcast, download & play

Action: as it is informative not action required.

Input Contribution Document No.Response to Call for Proposals on RoSE: Sensory Effect Metadata m15 651 Summary:

— Technologies used: XML Schema, MPEG-21 DIA— General structure of sensory effect metadata which is referred to as SEM schema

tools— Usage of patterns for describing sensory effects— Fragmentation of sensory effect metadata (i.e., for piece-wise, streamed processing

thereof) and associating time information to these fragments— It may need to be harmonized with other proposals, i.e., identify overlaps, etc.

Action: Go to WD and conduct CE monitored by AhG

Input Contribution Document No.Response to Call for Proposals on RoSE: Sensory Device Capabilities

m15 652

Summary:— Technologies used: XML Schema, MPEG-21 DIA— General structure of sensory device capabilities: extension of the terminal

capabilities as defined in MPEG-21 Digital Item Adaptation (note: this approach might by also applicable for the user sensory preferences).

— Actual sensory device capabilities based on patterns— It may need to be harmonized with other proposals, i.e., identify overlaps, etc.

Action: Go to WD and conduct CE monitored by AhG

Input Contribution Document No.Proposal for RoSE Metadata m1 5681 Summary:

— Technologies used: XML Schema, MPEG-7 DS

66

— Provider Preference (Sensory Effect Metadata): expresses preferences of the provider in terms of the permissible range for the control parameter of user sensory device

— Device Group Control (Sensory Effect Metadata): ChannelTypeID for the configuration of devices and ControlData for the parameters of sensory effects

— User Effect Adaptation (User Sensory Preferences): very detailed user preferences w.r.t. who, when, where, what, and how.

— Looks very complex but also innovative; it may need to be harmonized with other proposals, i.e., identify overlaps, etc.

Action: Go to WD and conduct CE monitored by AhG

Technical Work in Progress.

67

15.2 MPEG eXtensible Middleware

15.2.1 Topics1. MPEG eXtensible Middleware Architecture and Technology2. MXM APIs

15.2.2 ContributionsOne very detailed and complete response was received in answer to the call for proposal. The response was organized in four different documents summarized below:

M15686: Letter accompanying the responseM15687: Collection of use casesM15688: Specification of the technologies that are required to match the use casesM15689: Proposed specification

The tables below summarizes how the responses match the requirements of the CfP:

Table 1 : Identification of requirements satisfied1. Offer access to selected individual MPEG and related technologies through standard APIs Y2. Offer APIs to

a. Access i. Media encoders/decoders

1. Audio Y2. Video Y3. 3DG Y4. Binary XML N

ii. Audio/Video/3DG players Yiii. Presentation Engine

1. BIFS N2. LASeR Y3. HTML N

iv. IPMP functionality1. IPMP components Y

b. Create/edit/parsei. Digital Items Y

ii. Metadata1. MPEG-7 Y2. MPEG-21 Y3. TVA N

iii. Licences Yiv. File Formats Y

c. Stream/consume contenti. Audio Y

ii. Video Yiii. Scene Yiv. Metadata Yv. Digital Items Y

d. Store/consume content in distributed environmentsi. Peer-to-peer (P2P) infrastructure based on e.g. Distributed Hash Tables (DHT) Y

ii. Search for content Ye. Communicate between devices

68

i. Player with Licence server etc. Y3. Support interfacing with security elements in devices such as those provided by ISO/IEC

11889 Trusted Platform ModuleY

4. Be documented in at least one Programming Language (APIs) Ya. A Programming Language independent version of the APIs may be supported as well

by MXMY

5. Be modular to enable easy customisation for specific needs and to form various media value-chain easily

Y

6. Be designed to be re-usable in complete environments such as the M3W Framework Y

Table 2: Identification of requirements not satisfied and suggested ways by which MPEG could obtain the corresponding technology/ies

Requirements not satisfied

Reasons/How requirements could be satisfied

Binary XML The proponents could not devote resources to satisfy this requirement. As MPEG has identified several application for Binary XML, it could easily extend the current proposal to support this requirement using it internal expertise

BIFS and HTML Presentation

The proponents could not devote resources to satisfy these requirements. However, the BIFS and HTML specificities can be easily accommodated with the material contained in the submission

Visual description The proponents have provided support to Visual descriptors used in the Photo Player Application Format. More Visual descriptors can be supported using the same procedure highlighted in the proposal

Audio description The proponents could not devote resources to satisfy this requirement. As MPEG has identified several application for audio description, it could easily extend the current proposal to support this requirement using it internal expertise

TVA metadata The proponents could not devote resources to satisfy this requirement. However, there exists enough openly accessible significant material that can be used to develop the TVA Metadata part of the MXM API

In addition, new requirements were satisfied by the proposal (even they were not called for): - Content identification (APIs and protocol)- Content upload (APIs and protocol)- License upload (APIs and protocol)- Access to Video output /Audio output / Event APIs (APIs)

They are detailed in the table below and new CfP was issued (Cf. Req. report):

Table 3: Identification of additional requirements satisfiedNew requirement How it is handled

API to remote store a content item (Digital Item + resources)

Proposal of API and of specific technology provided. If accepted this could be added to ISO/IEC 29116

API to remote store a licence

Supported by the proposed solution.

API to identify a Digital Item or elements thereof

Supported by the proposed solution.

API to authenticate a Digital Item or

Supported by the proposed solution.

69

elements thereofAPI to verify a role Document m15689 proposes a specific API to verify a role, but there is no

Media Value Chain Ontology (MVCO) technology proposal in m15688. We believe that the proposed API is MVCO-technology agnostic. If MPEG will develop its own MVCO technology there may be a need to make fine adjustments as the MVCO standardisation progresses

Resource rendering Proposal of API providedDigital Item Presentation

Document m15689 proposes a specific API to present digital items, but there is no Presentation of Structured Information (PSI) technology proposal in m15688. We believe that the proposed API is PSI-technology agnostic. If MPEG will develop its own PSI technology there may be a need to make fine adjustments as the PSI standardisation progresses

A process for developing the standard was discussed and approved by MPEG:- MXM use cases definition- MXM API requirements definition- MXM API specification- MXM technologies specification

The inputs contribution was taken as the basis to produce the 2 output WD:- Architecture and Technologies- APIs

Technical Work in Progress.

16 Requirements and Exploration

16.1 Requirements & ProfilesM15550: New BIFS Profile for Interactive Digital Radio. See Req.M15677: LASeR Requirements for Person to Person Communication Services Signaling.

16.2 Standing DocumentsNone.

16.3 New Proposals

16.3.1 Rich Media UI FrameworkM15521: Discussed in Paris. See AHG report.

M15601: Additional Use Cases for UI Framework. Use cases to be added as annex in the Rich Media UI Framework Context and Objectives.

M15604: Addition information on the MPEG UI Framework. Used as input for the Rich Media UI Framework Context and Objectives.

M15676: Requirements for the MPEG UI Framework. Used as input for the Rich Media UI Framework Context and Objectives.

70

M15602: Analysis of MPEG-21 UED for Personalization. Proposal to use MPEG-21 UED for describing Users Preferences and Terminal capability. Noted.

M15603: First feedback/comments on the DCCI programmatic API for personalization. For information. Noted.

Decision on next steps on dynamic Rich Media Scene adaptation:- Definition of an ontology for Rich Media Scene Adaptation- Specification of APIs to access this ontology from the scene in IDL

languagei. With Ecmascript bindings.

ii. Other mappings ? - Walthrough for using this framework (TO BE INVESTIGATED):

i. With PSIii. With Script

iii. Others

M15675: MPEG User Interface Framework and W3C WebApps Widgets. For information. Analysis part integrated in the Contexte and Objective document.

16.3.2 Proposal for Standardization of Interfaces with Virtual Worlds M15615, M15617, M15690: See Req. report.

17 LiaisonCf. Liaison output.

71

18 Latest References and Publication StatusReference on the ISO Web Site : http://www.itscj.ipsj.or.jp/sc29/open/29view/29n9270c.htm

Pr Pt Standard No. Issue Status Doc. With Purpose ISO Award

2 1 ISO/IEC 13818-1/Amd.7 Published 2000/12 Done2 1 ISO/IEC 13818-1:2000 (MPEG-2 Systems 2nd Edition) 00/12 Published 2000/12 Proposed2 1 ISO/IEC 13818-1:2000/COR1 (FlexMux Descr.) N3844 01/01 Pisa Published 2002/03 N/A2 1 ISO/IEC 13818-1:2000/COR2 (FlexMuxTiming_ descriptor) N4404 01/12 Pattaya Published 2002/12 N/A2 1 ISO/IEC 13818-1:2000/Amd.1 (Metadata on 2) & COR1 on Amd.1 N5867 03/07

TrondheimPublished 2003/12 Proposed

2 1 ISO/IEC 13818-1:2000/Amd.2 (Support for IPMP on 2) N5604 03/03 Pattaya Published 2004/03 N/A2 1 ISO/IEC 13818-1:2000/Amd.3 (AVC Carriage on MPEG-2) N5771 03/07

TrondheimPublished XXXX Proposed

2 1 ISO/IEC 13818-1:2000/Amd.4 (Metadata Application CP) N6847 04/10 Palma FDAM ITTF to be published N/A2 1 ISO/IEC 13818-1:2000/Amd.5 (New Audio P&L Sig.) N6585 04/07

RedmondFDAM ITTF to be published N/A

2 1 ISO/IEC 13818-1:2000/COR3 (Correction for Field Picture) N6845 04/10 Palma COR ITTF to be published N/A2 1 ISO/IEC 13818-1:2000/COR4 (M4MUX Code Point) N7469 05/07 Poznan COR ITTF to be published N/A2 1 ISO/IEC 13818-1:2000/COR5 (Corrections related to 3rd Ed.) N7895 06/01

BangkokCOR ITTF to be published N/A

2 1 ISO/IEC 13818-1:2006 (MPEG-2 Systems 3rd Edition) 06/xx Published ITTF TBP2 1 ISO/IEC 13818-1:2006/Amd.1 (Transport of Streaming text) N8369 06/07

KlagenfurtFDAM ITTF to be published TBP

2 1 ISO/IEC 13818-1:2006/Amd.2 (Carriage of Auxialiry Video Data) N8798 07/01 Marrakech

FDAM ITTF to be published TBP

2 1 ISO/IEC 13818-1:2006/Cor.1.2 (Reference to AVC Specification) N9365 07/10 Shenzhen

FDAM ITTF to be published TBP

2 1 ISO/IEC 13818-1:2006/Amd.3 (SVC in MPEG-2 Systems) N1005 08/07 FDAM ITTF to be published TBP

72

8 Hannover2 11 ISO/IEC 13818-1:2003 (IPMP on 2) N5607 03/03 Pattaya Published 2003/12 Proposed4 1 ISO/IEC 14496-1 (MPEG-4 Systems 1st Ed.) N2501 98/10 Atl. City Published 1999/12 Done4 1 ISO/IEC 14496-1/Amd.1 (MP4, MPEG-J) N3054 99/12 Hawaii Published 2001/11 Done4 1 ISO/IEC 14496-1/Cor.1 N3278 00/03

Noordwijk.Published 2001/11 N/A

4 1 ISO/IEC 14496-1:2001 (MPEG-4 Systems 2nd Ed.) N3850 01/01 Pisa Published 2001/11 N/A4 1 ISO/IEC 14496-1:2001/Amd.1 (Flextime) Published 2002/10 Done4 1 ISO/IEC 14496-1:2001/Cor.1 N4264 01/07 Sydney COR ITTF N/A4 1 ISO/IEC 14496-1:2001/Cor.2 N5275 02/10 Shangai COR ITTF N/A4 1 ISO/IEC 14496-1:2001/Cor.3 N6587 04/07

RedmondCOR ITTF N/A

4 1 ISO/IEC 14496-1:2001/Amd.2 (Textual Format) N4698 02/03 Jeju Island

AMD ITTF N/A

4 1 ISO/IEC 14496-1:2001/Amd.3 (IPMP Extensions) N5282 02/10 Shanghai

Published 2004-05 N/A

4 1 ISO/IEC 14496-1:2001/Amd.4 (SL Extension) N5471 02/12 Awaji Published 2003/12 N/A4 1 ISO/IEC 14496-1:2001/Amd.7 (AVC on 4) N5976 03/10

BrisbannePublished 2004-08 N/A

4 1 ISO/IEC 14496-1:2001/Amd.8 (ObjectType Code Points) N6202 03/12 Hawaii AMD ITTF to be published N/A4 1 ISO/IEC 14496-1:200x/Amd.1 (Text Profile Descriptors) N7229 05/04 Busan PDAM ITTF Final Text

EditingN/A

4 1 ISO/IEC 14496-1:200x/Cor4 (Node Coding Table) N7473 05/07 Poznan PDAM ITTF to be published N/A4 1 ISO/IEC 14496-1 (MPEG-4 Systems 3rd Ed.) N5277 02/10

ShanghaiIS ITTF to be published Proposed

4 1 ISO/IEC 14496-1:200x/Amd.1 (Text Profile Descriptors) N7229 05/04 Busan PDAM ITTF Final Text Editing

N/A

4 1 ISO/IEC 14496-1:200x/Cor.1 (Clarif. On audio codec behavior) N8117 06/04 Montreux

COR ITTF Final Text Editing

N/A

4 1 ISO/IEC 14496-1:200x/Amd.2 (3D Profile Descriptor Extensions) N8372 06/07 Klagenfurt

PDAM ITTF to be published N/A

4 1 ISO/IEC 14496-1:200x/Cor.2 (OD Dependencies) N8646 06/10 COR ITTF to be published N/A

73

Hangzhou4 1 ISO/IEC 14496-1:200x/Amd.3 (JPEG 2000 support in Systems) N8860 07/01

MarrakechPDAM ITTF to be published N/A

4 4 ISO/IEC 14496-1:200x/Amd.17 (ATG Conformance) N8861 07/01 Marrakech

PDAM ITTF to be published N/A

4 4 ISO/IEC 14496-1:200x/Amd.22 (AudioBIFS v3 conformance) N9295 07/07 Lausanne

PDAM ITTF to be published N/A

4 4 ISO/IEC 14496-1:200x/Amd.23 (Synthesized Texture conformance) N9369 07/10 Shenzhen

PDAM ITTF to be published N/A

4 4 ISO/IEC 14496-1:200x/Amd.24 (File Format Conformance) N9370 07/10 Shenzhen

PDAM ITTF to be published N/A

4 4 ISO/IEC 14496-1:200x/Amd.25 (LASeR V1 Conformance) N9372 07/10 Shenzhen

PDAM ITTF to be published N/A

4 4 ISO/IEC 14496-1:200x/Amd.26 (Open Font Format Conf.) N9815 08/04 Archamps

PDAM ITTF to be published N/A

4 4 ISO/IEC 14496-1:200x/Amd.27 (LASeR Amd.1 Conformance) N9816 08/04 Archamps

PDAM ITTF to be published N/A

4 5 ISO/IEC 14496-1:200x/Amd.12 (File Format) N9020 07/04 San Jose PDAM ITTF to be published N/A4 5 ISO/IEC 14496-1:200x/Amd.16 (SMR Ref. Soft) N9672 08/01 Antalya PDAM ITTF to be published N/A4 5 ISO/IEC 14496-1:200x/Amd.17 (LASeR Ref. Soft) N9674 08/01 Antalya PDAM ITTF to be published N/A4 6 ISO/IEC 14496-6:2000 Published 2000/12 N/A4 8 ISO/IEC 14496-8 (MPEG-4 on IP Framework) N4712 02/03 Jeju Published 2004-05 Proposed4 11 ISO/IEC 14496-11 (MPEG-4 Scene Description 3rd

Edition) N6960 05/01

HongKongFDIS SC29 Final Text

EditingProposed

4 11 ISO/IEC 14496-11/Amd.1 (AFX) N5480 02/12 Awaji FDAM ITTF Integration in 1st

Ed.N/A

4 11 ISO/IEC 14496-11/Amd.2 (Advanced Text and Graphics) N6205 03/12 Hawaii FDAM ITTF Integration in 1st

Ed.N/A

4 11 ISO/IEC 14496-11/Cor.1 N6203 03/12 Hawaii COR SC29 N/A4 11 ISO/IEC 14496-11/Cor.3 Valuator/AFX related correction N6594 04/07

RedmondCOR ITTF Integration in 1st

Ed.N/A

4 11 ISO/IEC 14496-11/Amd.3 Audio BIFS Extensions N6591 04/07 FDAM ITTF Integration in 1st Proposed

74

Redmond Ed.4 11 ISO/IEC 14496-11/Amd.4 XMT and MPEG-J Extensions N6959 05/01

HongKongFDAM ITTF Integration in 1st

Ed.N/A

4 11 ISO/IEC 14496-11/Cor.3 (Audio BIFS Integrated in 3rd Edition) N7230 05/04 Busan COR ITTF Final Text Editing

N/A

4 11 ISO/IEC 14496-11/Cor.5 (Misc Corrigendum) N8383 06/07 Klagenfurt

COR SC29 N/A

4 11 ISO/IEC 14496-11/Amd.5 Symbolic Music Representation

N8657 06/10 Hangzhou

FDAM ITTF TBP

4 11 ISO/IEC 14496-11/Cor.6 (AudioFx Correction) N9021 07/04 San Jose COR SC29 N/A4 12 ISO/IEC 14496-12 (ISO Base Media File Format) N5295 02/10

ShanghaiPublished 2004-02 Proposed

4 12 ISO/IEC 14496-12/Amd.1 ISO FF Extension N6596 04/07 Redmond

FDAM ITTF FDAM 04/11/30 N/A

4 12 ISO/IEC 14496-12/Cor.1 (Correction on File Type Box)

N7232 05/04 Busan COR ITTF Final Text Editing

N/A

4 12 ISO/IEC 14496-12/Cor.2 (Miscellanea) N7901 06/01 Bangkok

COR ITTF Final Text Editing

N/A

4 12 ISO/IEC 14496-12/Amd.1 (Description of timed metadata)

N8659 06/10 Hangzhou

FDAM ITTF N/A

4 12 ISO/IEC 14496-12/Cor.3 (Miscellanea) N9024 07/04 San Jose COR ITTF Final Text Editing

N/A

4 12 ISO/IEC 14496-12/Amd.2 (Flute Hint Track) N9023 07/04 San Jose FDAM ITTF N/A4 13 ISO/IEC 14496-13 (IPMP-X) N5284 02/10

ShanghaiIS ITTF to be published Proposed

4 14 ISO/IEC 14496-14 (MP4 File Format) N5298 02/10 Shanghai

Published 2003-11 Proposed

4 14 ISO/IEC 14496-14/Cor.1 (Audio P&L Indication) N7903 06/01 Bangkok

COR ITTF Final Text Editing

N/A

4 15 ISO/IEC 14496-15 (AVC File Format) N5780 03/07 Trondheim

Published 2004-04 Proposed

4 15 ISO/IEC 14496-15/Amd.1 (Support for FREXT) N7585 05/10 Nice FDAM ITTF Final Text N/A

75

Editing4 15 ISO/IEC 14496-15/Cor.1 N7575 05/10 Nice COR ITTF N/A4 15 ISO/IEC 14496-15/Cor.2 (NAL Unit Restriction) N8387 06/07

KlagenfurtCOR ITTF N/A

4 15 ISO/IEC 14496-15/Amd.2 (SVC File Format Extension)

N9682 08/01 Antalya FDAM ITTF N/A

4 17 ISO/IEC 14496-17 (Streaming Text) N7479 05/07 Poznan FDAM ITTF TBP4 18 ISO/IEC 14496-18 (Font Compression and Streaming) N6215 03/12 Hawaii Published 2004-07 Proposed4 18 ISO/IEC 14496-18/Cor.1 (Misc. corrigenda and

clarification)N8664 06/10

HangzhouCOR ITTF N/A

4 19 ISO/IEC 14496-19 (Synthesized Texture Stream) N6217 03/12 Hawaii Published 2004-07 Proposed4 20 ISO/IEC 14496-20 (LASeR) N7588 05/10 Nice FDAM Editor TBP4 20 ISO/IEC 14496-20/Cor.1 (Misc. corrigenda and

clarification)N8666 06/10

HangzhouCOR ITTF N/A

4 20 ISO/IEC 14496-20/Amd.1 (LASeR Extension) N9029 07/04 San Jose FDAM ITTF N/A4 20 ISO/IEC 14496-20/Cor.2 (Profile Removal) N9381 07/10

ShenzhenFDAM ITTF N/A

4 20 ISO/IEC 14496-20/Amd.2 (SVGT1.2 Support) N9384 07/10 Shenzhen

FDAM ITTF N/A

4 22 ISO/IEC 14496-22 (Open Font Format) N8395 06/07 Klagenfurt

FDAM Editor Final Text Editing

TBP

7 1 ISO/IEC 15938-1 (MPEG-7 Systems) N4285 01/07 Sydney Published 2002/07 Done7 1 ISO/IEC 15938-1/Amd.1 (MPEG-7 Systems Extensions) N6326 04/03 Munich FDAM ITTF FDAM 04/11/28 N/A7 1 ISO/IEC 15938-1/Cor.1 (MPEG-7 Systems Corrigendum) N6328 04/03 Munich COR Editor N/A7 1 ISO/IEC 15938-1/Cor.2 (MPEG-7 Systems Corrigendum) N7490 05/07 Poznan COR ITTF N/A7 1 ISO/IEC 15938-1/Amd.2 (BiM extension) N7532 05/10 Nice FDAM ITTF N/A7 2 ISO/IEC 15938-2 (MPEG-7 DDL) N4288 01/07 Sydney Published 2002/02 Done7 7 ISO/IEC 15938-7/Amd.2 (Fast Access Ext. Conformance) N8672 06/10

HangzhouFDAM ITTF N/A

7 12 ISO/IEC 15938-12 MPEG Query Format N9830 08/04 Archamps

FDAM ITTF N/A

76

21 9 ISO/IEC 21000-9 (MPEG-21 File Format) N6975 05/01 HongKong

FDIS ITTF FDIS 05/01/21 Done

21 9 ISO/IEC 21000-9/Amd.1 (MPEG-21 Mime Type) N9837 08/04 Archamps

FDAM ITTF Done

21 15 ISO/IEC 21000-15 (Security in Event Reporting) N9839 08/04 Archamps

FDIS ITTF TBP

21 16 ISO/IEC 21000-16 (MPEG-21 Binary Format) N7247 05/04 Busan FDIS ITTF FDIS 05/04/22 TBP21 5 ISO/IEC 21000-5 (Open Release Content Profile) N9687 08/01 Antalya FDAM ITTF TBPA 4 ISO/IEC 23000-4 (Musical Slide Show MAF) N9037 07/04 San Jose FDIS ITTF TBPA 4 ISO/IEC 23000-4 (Musical Slide Show MAF 2nd Ed.) N9843 08/04

ArchampsFDIS ITTF TBP

A 7 ISO/IEC 23000-7 (Open Access MAF) N9698 08/01 Antalya FDIS ITTF TBPA 8 ISO/IEC 23000-8 (Portabe Video AF) N9853 08/04

ArchampsFDIS ITTF TBP

A 9 ISO/IEC 23000-9 (Digital Multi. Broadcasting MAF) N9397 07/10 Shenzhen

FDIS ITTF TBP

A 9 ISO/IEC 23000-9/Cor.1 (Digital Multi. Broadcasting MAF)

N9854 08/04 Archamps

COR ITTF TBP

B 1 ISO/IEC 23001-1 (XML Binary Format) N7597 05/10 Nice FDIS ITTF TBPB 1 ISO/IEC 23001-1/Cor.1 (Misc. Editorial and technical

clar.)N8680 06/10

HangzhouCOR ITTF N/A

B 1 ISO/IEC 23001-1/Cor.2 (Misc. Editorial and technical clar.)

N9049 07/04 San Jose COR ITTF N/A

B 1 ISO/IEC 23001-1/Amd.1 (Reference Soft. & Conf.) N8886 07/01 Marrakech

FDAM ITTF N/A

B 1 ISO/IEC 23001-1/Amd.1 (Exten. On encoding of wild cards)

N9296 07/07 Lausanne

PDAM ITTF to be published N/A

B 2 ISO/IEC 23001-2 (Fragment Request Unit) N9051 07/04 San Jose FDIS ITTF TBPB 3 ISO/IEC 23001-3 (IPMP XML Messages) N9416 07/04 San Jose FDIS ITTF TBPE 1 ISO/IEC 23008-1 Architecture N8892 07/01

MarrakechFDAM ITTF N/A

E 2 ISO/IEC 23008-2 Multimedia API N8893 07/01 FDAM ITTF N/A

77

MarrakechE 3 ISO/IEC 23008-3 Component Model N8894 07/01

MarrakechFDAM ITTF N/A

E 4 ISO/IEC 23008-4 Ressource & Quality Management N8895 07/01 Marrakech

FDAM ITTF N/A

E 5 ISO/IEC 23008-5 Component Download N9053 07/04 San Jose FDAM ITTF N/AE 6 ISO/IEC 23008-6 Fault Management N9054 07/04 San Jose FDAM ITTF N/AE 7 ISO/IEC 23008-7 System Integrity Management N9055 07/04 San Jose FDAM ITTF N/A

29116 1 ISO/IEC 29116 Media Streaming MAF Protocols N9420 07/10 Shenzhen

FDAM ITTF N/A

78

19 Resolutions of Systems

Cf. WG11 resolution.

20 Contributions Reviewed by the Systems Subgroup

N° Title Authors15519 (IPTV) Liaison Statement from ITU-T SG 16 on IPTV [SC

29 N 9516] ITU-T SG 16 via SC29 Secretariat

15521 Architecture for the MPEG User Interface Framework Cyril ConcolatoJean Le FeuvreKyungMo Park

15522 Summary of Voting on ISO/IEC 13818-1:2007/FPDAM 3.2 [SC 29 N 9517]

SC29 Secretariat

15523 Summary of Voting on ISO/IEC FCD 23000-10 [SC 29 N 9518]

SC29 Secretariat

15533 Summary of Voting on ISO/IEC CD 14496-22 [2nd Edition]

SC29 Secretariat

15539 (Thank you) IEC NP: Multimedia systems and equipment -- Multimedia home network configuration -- Basic reference model

IEC TC 100 via SC29 Secretariat

15542 (BIFS Profile) Liaison Statement from TTA [SC 29 N 9559]

TTA via SC 29 Secretariat

15543 (Thank you) IEC CDV 60728-1-2 IEC TC 100 via SC29 Secretariat

15544 (IPTV) Liaison Statement from ITU-T SG 16 on MXW [SC 29 N 9564]

ITU-T SG 16 via SC 29 Secretariat

15550 New BIFS Profile for Interactive Digital Radio Benoît PellanYoung-Kwon LimCyril Concolato

15556 (Audio Book) IEC CD 62571 IEC TC 100 via SC 29 Secretariat

15560 Sensory Effects Metadata for RoSE Framework B.S ChoiSanghyun Joo

15561 User Sensory Preferences Metadata for RoSE Framework B.S ChoiSanghyun Joo

15562 Sensory Device Capabilities Metadata for RoSE Framework

Sanghyun JooB.S Choi

15563 Sensory Device Commands Metadata for RoSE Framework

Sanghyun JooB.S Choi

15571 (PA MAF) Liaison Statement from WG 1 WG 1 via SC 29 Secretariat15585 RoSE description schemes for realistic TV commercials Maeng-Sub Cho

Jin-Seo KimBon-Ki KooYong Soo Joo

79

N° Title AuthorsSang-Kyun Kim

15591 Proposals for MVC File Format Miska M. HannukselaYe-Kui WangYing Chen

15593 Proposed Text for White Paper of ISO/IEC 23000-6 Professional Archival Application Format

mailto:Hendrymailto:Munchurl%20Kimmailto:Noboru%20Haradamailto:Takehiro%20Moriya

15596 Proposed Text for Working Draft of ISO/IEC 23000-6 PA-AF Reference Software

mailto:Hendrymailto:Houari%20Sabirinmailto:Munchurl%20Kimmailto:Noboru%20Haradamailto:Takehiro%20Moriya

15600 On MVC File Format Karsten GrünebergThomas Schierl

15601 Additional Use Cases for UI Framework KyungMo ParkCyril ConcolatoJean Le Feuvre

15602 Analysis of MPEG-21 UED for Personalization Cyril ConcolatoJean Le FeuvreKyungMo Park

15603 First feedback/comments on the DCCI programmatic API for personalization

Cyril ConcolatoJean Le FeuvreKyungMo Park

15604 Addition information on the MPEG UI Framework Cyril ConcolatoJean Le FeuvreKyungMo Park

15611 File format support for reception of SRTP and MIKEY messages

Daniel CatreinPer Fröjdh

15612 Response to the call for technologies for RoSE Mark VerberktJean H.A. Gelissen (ed.)

15614 CD proposal of LASeR in IPTV Jaeyeon SongSeo-Young HwangYoung-Kwon Lim

15615 Response to the extended call for requirements for MPEG-V

Dirk BrokkenJean H.A. Gelissen

15617 Response to the extended call for requirements for MPEG-V

Jun HuJean H.A. Gelissen (ed.)

15622 Proposal for the Presentation of Structured Information Jihun ChaInjae LeeYoung-kwon LimHan-kyu LeeJinwoo Hong

15626 A proposal for technical specification of Interactive Music AF

Inseon JangHui Yong KimJeongil SeoKyeongok Kang

15631 Ontology for IP Media Networks (IPM-Net): A response to the MVCO CfP

Marc Gauvin et al.

15649 Timed Representation of Metadata for the Presentation of Christian Timmerer

80

N° Title AuthorsStructured Information (PSI) michael.ransburg@itec.uni-

klu.ac.at. Michael Ransburg15650 Possible Instantiations of the RoSE Framework Markus Waltl

Christian Timmerer15651 Response to Call for Proposals on RoSE: Sensory Effect

MetadataMarkus WaltlChristian Timmerer

15652 Response to Call for Proposals on RoSE: Sensory Device Capabilities

Markus WaltlChristian Timmerer

15659 Error in the ?FRext? extension to the AVC file format David Singer15664 Updated text and reference SW for ISO/IEC 23000-9

(DMB-AF)Hui Yong KimMyungSeok KiHanKyu LeeYong Han KimHouari SabirinMunchurl Kim

15665 Conformance file contribution for ISO/IEC 23000-9 (DMB-AF)

Hui Yong KimSeung Jun YangHanKyu LeeHyunsoon KimDaebok Kwon

15675 MPEG User Interface Framework and W3C WebApps Widgets

Diego GibellinoGiovanni Cordara

15676 Requirements for the MPEG UI Framework Diego GibellinoGiovanni Cordara

15677 LASeR Requirements for Person to Person Communication Services Signaling

Diego GibellinoGiovanni Cordara

15681 Proposal for RoSE Metadata Yasuaki TokumoTakuya IwanamiYoshiaki OgisawaShuichi WatanabeNorio Ito

15684 Study text of ISO/IEC 23000-11 FCD Stereoscopic Video Application Format

Next generation Broadcasting Forum (Korea)

15685 Workplan for ISO/IEC 23000-11 Conformance and Reference Software

Next generation Broadcasting Forum (Korea)

15686 Response to MXM Call for Proposals Walter Allasia et al.15687 Collection of MXM Use Cases Walter Allasia et al.15688 Proposal of MXM Technologies Walter Allasia et al.15689 Proposal of MXM API Walter Allasia et al.15690 Response to the extended call for requirements for MPEG-

V Esko DijkJean H. A. Gelissen

15693 Proposal for adding support of platform-independent language tag strings in the 'name' table.

Simon DanielsMichelle HillVladimir Levantovsky

15694 Proposal for adding support for left-to-right and right-to-left glyph alternatives.

Sairus Patel

15695 Preliminary comments on the 14496-12 PDAM David Singer

81

N° Title Authors15698 Proposing an Architecture for MPEG Media Value Chain

OntologyMiran ChoiMyung Gil JangHyunki Kim

15705 Update of ISO/IEC 23000-10/Amd1 WD2.0 Conformance and Reference Software

James AnnesleyHouari Sabirin

15710 iKlax Requirements for MPEG Interactive Music Owen LagadecFabien GallotLaurent Primaux

15712 Java software based on Mpeg7 schema including amendment ISO/IEC 15938-5:2003/Amd.3:2008

Tanya Beech

82

Annex G – Video report

Source: Jens Ohm and Gary Sullivan, Chairs

1 Development of AVC

The video subgroup jointly approved the ISO standard related output documents that were produced during the 28th JVT meeting which was held in parallel. Important work items in this context were

– Final work on conformance testing for New Professional Profiles and SVC (both FDAM)

– Improvement of reference software for SVC (Study of FPDAM)– Final work on MVC (FDAM)– Work on MVC software (PDAM) and conformance (WD)– Further work on the Cor.1 (Study of DCOR).

For two issues related to the corrigendum, clarification is expected during the October 2008 meeting: - Definition of level limits as discussed in M15558,- Designation of “constrained baseline” bitstreams and decoders in clause A.2.1.1 (which does this as a kind of naming convention, without explicitly defining conformance point(s)).

Documents reviewed:m15513 Summary of Voting on ISO/IEC 14496-4:2004/FPDAM 30 [SC 29 N

9481]SC29 Secretariat

m15532 Summary of Voting on ISO/IEC 14496-10:200X/FPDAM 1 SC29 Secretariatm15534 Summary of Voting on ISO/IEC 14496-4:2004/FPDAM 31 SC29 Secretariatm15558 JNB Comment on Text of ISO/IEC 14496-10:200X/DCOR1 (N9574) Teruhiko Suzuki

Documents approved:No. Title TBP Available

14496-4 Conformance testing9968 Disposition of Comments on ISO/IEC 14496-4:2004/FPDAM 30 N 08/07/259969 Text of ISO/IEC 14496-4:2004/FDAM 30 Conformance Testing

for New Profiles for Professional ApplicationsN 08/07/25

9970 Disposition of Comments on ISO/IEC 14496-4:2004/FPDAM 31 N 08/07/259971 Text of ISO/IEC 14496-4:2004/FDAM 31 Conformance Testing

for Scalable Video CodingN 08/10/01

9972 Working Draft 1 of ISO/IEC 14496-4:2004/Amd.38 Conformance Testing for Multiview Video Coding

N 08/08/31

14496-5 Reference Software 9973 Request for ISO/IEC 14496-5:2001/Amd.15 N 08/07/259974 Text of ISO/IEC 14496-5:2001/PDAM 15 Reference Software for

Multiview Video CodingN 08/10/01

9975 Study Text of ISO/IEC 14496-5:2001/FPDAM 19 Reference Software for Scalable Video Coding

N 08/08/01

14496-10 Advanced Video Coding9976 Study Text of ISO/IEC 14496-10:200X/DCOR 1 N 08/08/01

83

9977 Disposition of Comments on ISO/IEC 14496-10:200X/FPDAM 1 N 08/07/259978 Text of ISO/IEC 14496-10:200X/FDAM 1 Multiview Video

CodingN 08/10/01

2 MPEG-7 Visual and Photo Player MAF

2.1 MPEG-7 Visual related work in ArchampsThe MPEG-7 breakout group was active during the whole week. Input documents related to the Visual part in 15938-3 are listed in the table below.

m15605 List of Adjacent Clip Pairs in the VCE-7 Dataset Kota IwamotoRyoma Oami

m15606 Removal of Partially Identical Clips from the VCE-7 Dataset Kota IwamotoRyoma Oami

m15607 Camera Capturing of Video Clips for VCE-7 Robustness Test Kota IwamotoRyoma Oami

m15616 A Proposal on Conformance Testing for Photo Player Application Format

Ryoma Oami

m15623 Proposal on implementation Capturing on camera and Interlaced/Progressive conversion for VCE-7 modification

Weon-Geun OhJu-Kyong JinJun-Woo LeeDong-Seok Jeong

m15627 Cross verification results of Image Signature Karol Wnukowiczm15646 Improved Matching for Global Image Signature

Factor 7 speedup by using simplified Hamming-distance matching (0.3% loss in precision), no change to descriptor and extraction process

Paul BrasnettMiroslaw Bober

m15647 Proposed Improvements for Local Image SignatureBased on speeded-up matching as described for the global descriptor in 15646, it is possible to achieve more precision in a 4-stage hierarchical matching process, up to 80 localized features. Now, average precision including medium and heavy conditions is approx. 98%. Still most problems in case of heavy cropping.Decision to adopt the localized descriptor for Study of FPDAM (text to be provided by end of week). Further discussion whether more than 80 local features should be used, e.g. to allow even more heavy cropping in cases of high-resolution images.

Paul BrasnettMiroslaw Bober

m15658 Image Signature for Complex Conditions Weon-Geun OhAyoung ChoWon-Keun YangJun-Woo LeeDong-Seok Jeong

m15666 Validation Report for VCE-5VCE-5 did not exist. Therefore, this document which obviously contains outdated content was not considered.

Sangki KimHyobin LeeSangyoun Lee

m15670 Video content contribution for VCE-7 from KBS Geun-Soo ParkJu-Kyong JinWeon-Geun OhDong-Seok Jeong

m15671 Video content contribution for VCE-7 from Inha University Ju-Kyong JinWeon-Geun OhDong-Seok Jeong

m15673 Comments on the preliminary call for proposal for video signature Weon-Genu OhDaeil YoonHae-Kwang Kim

m15701 Image Signature for all modifications3D histogram signature (MGST feature, AP feature, Hue feature). In Addition, 2 versions of concentric circle image signature. Those are operated in 3-stage matching. Matching precision 96.4 % under all modifications.

Weon-Geun OhAyoung ChoWon-Keun YangJun-Woo LeeDong-Seok Jeong

m15702 Cross verification result for ETRI VCE-6 proposal Min-Jeong LeeHeung-Kyu Lee

84

A Study Text of ISO/IEC 15938-3:2001/FPDAM 3 Image Signature Tools (N9979) was issued. This contains the additional possibility to extract signatures from local image features, where up to 80 local Trace Transform features can be defined for prominent feature points as detected by scale-adaptive Harris corner and Laplacian edge detectors (see M15647). Fast matching is implemented as a hierarchical 4-stage process, using simplified Hamming distance. The performance (with same false alarm rate) was reported to be approx. 98% precision (average) including "medium" and "heavy" conditions.For the previous global signature descriptor, another speedup of the (non-normative) matching was achieved as well, which now enables to search 70 million images per second with only marginal loss in detection rate (under "light" conditions which are suitable for the global signature type, 99.3% precision are still achieved under the same negligible false alarm rate as before). The MPEG-7 Visual XM Document version 34.0 (N9982) contains these new non-normative fast matching procedures.A document “Use Cases of Visual Signature Tools” (N9980) was issued, listing various scenarios such as

• Metadata association (services annotating unknown content)• Signature-based search for duplicate content• Identification of lost or stolen content, e.g. museum catalogues• Sharing content in multi-user environment• Unknown object identification, e.g. buildings, animals, …

With regard to the subsequent Amd.4 of MPEG-7 Visual, the Call for Proposals on Video Signature Tools (N9981) was issued. Currently, over 100 hours of content are available from donations and download of freely available materials. The National Film and Television School (UK) has offered up to 200 hours of additional content (selection of shots that are usable for the given purpose is still pending / to be done). Therefore, it appears sure that sufficient amount of content (200 hours in total required) is now available or should be available in near future. The timeline is as follows:

• Pre-registration open since end of Hannover meeting, distribution of (currently< available) datasets starts immediately from different sites in Europe, Asia, US

• Update of CfP and final definition of dataset 08/10• Responses due 09/02, possibly WD• PDAM 09/04• FPDAM 09/10• FDAM 10/04

ISO/IEC 23000-3 / FPDAM 1 Photo Player MAF Reference Software (N9222 of July 2007 meeting) is now delivered and under ballot. The Working Draft of ISO/IEC 23000-3/Amd.2 Conformance Testing for Photo Player MAF (N9983) was started with following timeline:

– PDAM 08/10– FPDAM 09/02– FDAM 09/07

2.2 Output documents related to MPEG-7 Visual

No. Title TBP Available15938-3 Visual

9979 Study Text of ISO/IEC 15938-3:2001/FPDAM 3 Image Signature Tools

N 08/08/08

85

9980 Use Cases of MPEG-7 Visual Signature Tools Y 08/07/259981 Call for Proposals on Video Signature Tools Y 08/07/259982 MPEG-7 Visual XM Document version 34.0 N 08/08/08

23000-3 Photo Player Application Format9983 Working Draft of ISO/IEC 23000-3/Amd.2 Conformance

Testing for Photo Player MAFN 08/07/25

3 23002 MPEG-C Video Technologies

3.1 23001-4 and 23002-4 Reconfigurable Video Coding (RVC)

3.1.1 General status of work

The two parts related to RVC (ISO/IEC 23001-4 Codec Configuration Representation in MPEG-B and ISO/IEC FCD 23002-4 Video Tool Library in MPEG-C) were progressed into FCD status in April with editorial period, and delivered in time for the ballots, which will be closing before the October meeting (where it is planned to promote both parts for FDIS). The main issue of work during the week in the RVC breakout group was related to editorial improvements on both texts (see items below). Study documents were drafted. Main issues still to be resolved are the relationship of RVC-BSDL as defined in 23001-4 with BSDL (should it restrict the usage of BSDL elements that are not currently needed for RVC context?), and the proper definition of tools in 23002-4 (usually only input-output behaviour of FUs needs to be normative, but some FUs are described in a fashion of sequential algorithms internally; furthermore, careful checking is necessary about whether the FU descriptions are precisely equivalent to the elements of the MPEG standards from which they were drawn).

While the FDIS as planned for October will give full support only for MPEG-2 main profile, MPEG-4 simple profile and MPEG-4 AVC baseline profile, further tools for MPEG-4 advanced simple profile, AVC high profile and SVC will be supported in Amd.2, for which the second version of WD was issued. Likewise, WD 2 of software and conformance amendment (Amd.1) was also produced.

To clarify the relationships of MPEG and non-MPEG FUs / toolboxes that could both be used in the RVC context, a document entitled RVC vision (N9990) was issued which clearly expresses that only the elements defined by MPEG (in 23001-4 and 23002-4) are handled as MPEG compliant, while usage of non-MPEG tools is under sole responsibility of their respective users.

3.1.2 Assignment of editorsDocuments Editors

Study of FCD of 23001-4 (MPEG-B CCR) Gwo Giun, TK, Hyungyu, ChristopheStudy of FCD of 23002-4 (MPEG-C VTL) Yishin, TK, Hwa SeonRVC CE description Kazuo, Hyungyu, DandanWorkplan Christophe, Yishin, Conformance & RSM WD Gwo Giun, ChristopheExtension to VTL MikaelLiaison response & RVC Vision Euee, Hwa Seon, Dandan

86

3.1.3 Allocation of input contributions Study of FCDDoc. No. Titlem15559 Proposed update of FCD ISO/IEC 23002-4: Video Tool Library

(VTL)- Reviewed during the AhG meeting on Sunday

m15707 Comments on ISO/IEC 23002-4 FCD- Reviewed during the AhG meeting on Sunday

m15708 Comments on ISO/IEC 23001-4 FCD- Reviewed during the AhG meeting on Sunday

MPEG-B RelatedDoc. No. Titlem15549 Proposed network of functional units for AVC High Profile

- Some FUs are missing.- [Recommendation] Need to have a ‘top-level’ connections of FUs for

supported decoding configurations.M15630 New version of the BSDL2CALML parser in RVC

- Example to convert BSDL Schema representation to CAL(ML) parser.- [Discussion] BSDL vs. RVC BSDL

Some definitions of BSDL can be replaced with other definitions in BSDL.

Still there is a need for further experiment. CE till the next meeting.

- [Recommendation] to continue the work to complete the work till the next meeting as CE to review the first draft of CE on Thursday morning

m15663 CAVLC Validation Procedure and Implementation for AVS in RVC Framework- CA-2D VLD of AVS is given as example.- [Recommentation] continue as CE

M15679 DDL of Intra MPEG AVC decoder- FU network example of AVC decoder provided.- [Recommendation]

to include some ‘top-level’ decoder network in MPEG-B FCD Study io include DDL examples in RSM implementation

M15680 DDL Graph Editor- Can be used to provide a conformance testing of connection of FUs in the

future.- [Recommendation] to include this tool in RSM

MPEG-C related Doc. No. TitleM15662 Liaison response on N9787

- Reviewed during the AhG meeting on Sundaym15699 Modified FUID definition for multiple tool libraries

- [Recommendation] To put guidelines on registration of toolboxes in MPEG-B To modify FU naming convention according to the proposal in MPEG-C

87

m15703 Introduction of Token description in VTL- [Recommendation]

Token precedence will be studied further till the next meeting. Put token list description in VTL study. Further investigation on FU and Token description is needed till the next

meeting.

Study of FCD- Points identified for clarification:

1. Bitstream syntax and parsing description (BSPD)- Thorough comparison between BSDL-schema and RVC-BSDL schema is

needed. Core Experiment- What is added on top of BSDL-schema (i.e., port connections to FUs) needs

a precise description. Core Experiment- The current concept of RVC does not allow the on-the-fly generation of new

FUs with an exception of parser FU. Study of FCD (in introduction)- Example BSDL schema of one example decoder configuration (e.g., MPEG-

4 SP) in Annex (informative) pointer to MPEG-C for other examples.2. FU network description (FUND)

- (XML) Description of top-level decoder network of FUs for one example decoder configuration in Annex (informative): pointer to MPEG-C for other examples.

3. FUs in VTL- Separation of normative and nonnormative FUs in VTL- Diagram of top-level decoder network of FUs for decoder configuration for

the currently supported profiles and levels- Clear description of interfaces of FU- (XML) Descriptions of top-level decoder network of FUs for the supported

decoder configurations as example in Annex (informative)- Example BSDL schema of example decoder configuration of the currently

supported profiles and levels in Annex (informative)

Output Documents:

No. Title TBP Available23001-4 Codec Configuration Representation

9984 Study Text of ISO/IEC FCD 23001-4 Codec Configuration Representation

N 08/09/30

23002-4 Video Tool Library9985 Study Text of ISO/IEC FCD 23002-4 Video Tool Library N 08/09/309986 WD 2 of ISO/IEC 23002-4/Amd.1 (Conformance and Reference

Software)N 08/07/25

9987 WD 2 of ISO/IEC 23002-4/Amd.2 (Tools for MPEG-4 ASP, AVC HP and SVC)

N 08/07/25

9988 Description of Core Experiments in RVC N 08/08/089989 RVC Work Plan and FU Development Status N 08/07/259990 RVC Vision Y 08/07/25

88

4 Explorations – 3D Video

The goal of 3D video, as a first step towards a broader range of free-viewpoint (FTV) applications, is to generate interpolated views from available videos of multiview camera configurations. The target application is mostly seen for upcoming generations of (auto-) stereoscopic displays, for which only a low number (1) of video sequences shall be transmitted, but rendering of additional views shall be enabled by associated depth information. To make a next step towards development of such a system, a set of exploration experiments had been set up in Archamps, during which the available test sequences were used with the two available depth estimators and associated view interpolation methods. Various cases of sparseness (baseline distances between cameras to be taken from the dense set) were investigated. Experts viewing using stereoscopic displays was performed in Hannover. Three different display types (two stereoscopic, one autostereoscopic) were available (see N9992 for more details). A first glimpse at the results clearly indicated that only for the “light” case of small baseline distance, results without heavy artifacts could be obtained; therefore, the more intense experts viewing, that involved larger groups of people was only performed to this case. A high-level summary is given here:

a) Results on original views:Most sequences have been rated “good” for 3D viewing, except “Alt Moabit”, which is an outdoor scene with mostly far-away content. Some comments were made that could be helpful in case of future production of test material:

- Black background is OK when the foreground object has sufficient depth structure (e..g champagne tower)

- In general, sequences with more motion / less static background might be desirable (may have implication on encoding and rates to be defined per sequence)

- Depth structure was too low in one sequence (dog) – can be resolved by using different camera baseline

- Framing problem: Conflict of depth perception when the disparity at screen boundary is large

Conclusion: In general, the sequences are suitable for 3D viewing. As a general experience, it is necessary to get familiar with 3D data viewing.

b) Results on synthesized views:Currently, synthesized views (even for the “light” case) are not acceptable. Main problems are as follows:

- Flickering- Ringing- Ghosting- Temporal Instability- Boundary distortions

Conclusion: For the software frame work that is available (Depth Estimation /DE + View Synthesis /VS) the quality is not yet acceptable. It is expected that this situation can be highly improved by relatively simple measures until the next meeting. Before progressing with experiments on AVC/MVC-encoded sequences, further improvements are required for both DE and VS.

c) Judgement of displays:- Usually larger displays are considered better, but smaller displays had better depth

impression sometimes.

89

- It is necessary to clearly define viewing distance, depending on display size, only few people possible simultaneously, controlled seating positions

- Stereoscopic vs. autostereoscopic: Stereoscopic has less problems with individual adjustment. This should be the default display, autostereoscopic should also be checked if available, because this is the most likely target of the application (note: the interpolation artifacts are likewise visible on both stereoscopic and autostereoscopic diplays)

The next round of experts viewing is planned for the Busan meeting.

The most important step until then is to proceed with improving depth estimation and view synthesis. Those key points will be investigated in a collaborative approach within the next round of Exploration Experiments:

• Improve results of depth estimation (subpel, temporal consistency) – EE 1• Improve results of view synthesis (line projection from rectified images, filling of

holes, boundary filtering) – EE 2• Investigate alternative view synthesis from Layered Depth Video (LDV), using same

depth maps as from EE 1 – EE 3

The EEs will run separately (improving depth estimation and view synthesis) until 2 weeks before next meeting, then the participants will exchange results (software bin or src, depth maps etc.). Combinations of other, newly developed DE (bring depth maps) and VS algorithms can also be computed on-site at next meeting, after AHG reviews the separate results. The Common software basis will be maintained via the MPEG SVN repository.

Once the view synthesis results for the uncoded case provide sufficient quality, encoding experiments (using AVC/MVC both for videos and depth maps) will be performed with the purpose to select appropriate bit rates. This could at earliest start after the Busan meeting. Therefore, the shortest possible tentative timeline could be as follows:

• Until 08/10: Generate improved depth maps and interpolated view sequences from the test sets

• 08/10: Perform experts viewing with different stereoscopic displays, again decide about maturity of anchors

• 08/10: Draft CfP (internal)• Until 09/02: Perform experiments to decide about bit rates for the MVC-based video-plus-

depth anchors, selection of sequences• 09/02: Experts viewing again, preliminary CfP• Until 09/04: Refinement of test conditions• 09/04: Final CfP • 09/07: Responses due

Documents reviewed m15540 Depth Map Estimation Software version 3 Olgierd Stankiewicz

Krzysztof Wegnerm15553 Results of Exploration Experiment in 3D Video Coding for Dog

Data SetAljoscha SmolicYongzhe WangKarsten Mueller

m15573 3D Video Exploration Experiment on Baseline Length Dependency

Taka SenohKenji YamamotoRyutaro OiTomoyuki MishinaMakoto Okui

90

m15583 Results of Depth Estimation and View Synthesis on Doorflowers Test Data Set for EEs in 3D Video Coding

Shinya ShimizuHideaki Kimata

m15584 Experimental Results on Depth Estimation and View Synthesis with subpixel-precision

Shinya ShimizuHideaki Kimata

m15589 Exploration Experiments on seq 'Arrive book' & 'Alt-moabit' fons.bruls@philips.comlincoln.lobo@philips.com

m15590 Creation of LDV streams out of MV sequences fons.bruls@philips.comlincoln.lobo@philips.comrene.klein.gunnewiek@philips.com

m15594 Enhancement of Temporal Consistency for Multi-view Depth Map Estimation

sblee@gist.ac.kr (Sang-Beom Lee)hoyo@gist.ac.kr (Yo-Sung Ho)

m15595 Results of Exploration Experiment on View Synthesis leecheon@gist.ac.kr (Cheon Lee)hoyo@gist.ac.kr (Yo-Sung Ho)

m15597 Boundary Filtering on Synthesized Images for 3D Video leecheon@gist.ac.kr (Cheon Lee)hoyo@gist.ac.kr (Yo-Sung Ho)

m15599 Experimental Results of EE on LeavingLaptop sequence for MPEG-FTV

Gi-Mun UmGun BangNamho HurJinWoong Kim

m15620 Exploration Experiment results on 'Champagne_tower' and 'Pantomime' sequences

Ivana RadulovicPer Fröjdh

m15648 EE results on Leaving laptop Purvin PanditDong TianCristina Gomila

m15661 EE results on lovebird2 Jaewon SungJung Eun Lim

m15672 View Synthesis Software and assessment of its performance Mateusz GotfrydKrzysztof Wegnerdomanski@et.put.poznan.pl. Marek Doma?ski

m15674 EE results on lovebird1 sequence Patrick LopezGuillaume Boisson

m15696 Simple View Synthesis Dong TianPurvin PanditCristina Gomila

m15697 Experimental Results for Exploration Experiment in 3D Video Sehoon YeaKwan-Jung OhAnthony Vetro

Output documents:No. Title TBP Available9991 Description of Exploration Experiments in 3D Video Coding N 08/07/259992 Results of 3D Experts Viewing N 08/07/25

5 Explorations – New Challenges in Video Coding

A brainstorming session on topics of future video coding standardization was held on Tuesday afternoon (presentation of contributions as listed below), with a follow-up on Thursday morning. The main points of discussion are summarized in N9993. Possible application areas for higher-compression video are mainly seen in• High resolution HD and beyond (4Kx2K, potentially 8Kx4K) for Regular broadcast and

IPTV, Packaged media, Surveillance,P2P communication• Resolution from VGA up to beyond-HD for Mobile Broadcast and downloads

In addition, preliminary investigations were reportted about the performance of AVC and some modifications to it (Macroblock and transform block sizes, adaptive transforms, adaptive interpolation filters) showed possible improvements mainly for the cases of high rates and high resolutions.

First thoughts about requirements were mentioned as follows:

91

• Time line : Beyond 2012• (open) Should the next-generation video standard still be generic or application specific?• Color sampling: 4:2:0 and 4:4:4 (certainly no interlaced needed any more); Progressive

12, … , 60 fps, high frame rates beyond 60 could also happen; Display resolutions VGA … 4Kx2K, potentially 8Kx4K

• Compression: Two times over AVC HP desirable for the target application(s); at no point of the entire range should it be worse than existing standard(s).

• Complexity increase as compared to AVC shoudl matches what will be possible for implementation by the expected time of usage

• (open) Support for Stereo? Scalability? Lossless/near lossless?

As the next step, to face the challenges that emerging applications impose on the requirements of video coding standardization, it is planned to organize a full-day workshop in Korea prior to or during the meeting. The key intention of the workshop is to acquire solid information about the context in which video coding will be operating in the future, which will enable MPEG to draw conclusions for the needs and chances in video coding standardization during the next years and to start drafting three key documents: Technology context, applications and requirements for a new video coding standard. For this purpose it is planned to invite speakers on key topics and in addition select a variety of proposed contributions. The following topics will be considered:

1) Applications: Which video signal resolutions are expected, which data rates will be manageable, which networks/storage media will be dominant starting from the middle of the next decade for

a. Unicast and broadcast video/movie distribution,b. Wireless and mobile,c. Packaged media.

2) Next-Generation Networks (around the year 2015)a. Which data rates and quality of service characteristics are expected for

distribution over IP, WAN, IP-TV, wireless, mobile; unicast, multicast, broadcast, peer 2 peer, access and core networks?

b. Existence of approaches for transmission, modulation, channel coding etc. that could break existing barriers for terrestrial, satellite and cable broadcast, mobile applications; are there limits in terms of efficient usage of bandwidth and cost?

3) Video equipment: Availability of cameras, displays, projectors etc. (both for professional and consumer sectors) around the year 2015

a. Cameras: Resolution, color space, quality of lenses, noise characteristics for HD and beyond in particular, cost.

b. Displays/projectors: Resolution, color space, size, resolution of typical input signals, cost.

c. Human factors: What size/resolution is useful considering the properties of human visual system? How likely is it that people will put very large displays (beyond HD) into their houses?

4) Compression technologya. What are known limitations or missing functionality of current compression

technology, considering new applications? b. New compression methods that could overcome such limitations.c. Methods to evaluate performance: Visual quality, complexity.

92

Procedure:• Both invited and proposed contributions• Both MPEG and non-MPEG experts• Call for Contributions: 08/08/01• Responses: 08/09/05• Selection, final Program: 08/09/10• Workshop: 08/10/11 or t.b.d. (full day) in Busan or t.b.d.

Documents reviewed (see N9993 for detailed comments)

m15577 Requirements for next-generation video coding standard Shun-ichi SekiguchiYoshihisa YamadaYoshiaki KatoKohtaro AsaiTokumichi Murakami

m15704 Consideration on an approach for developing a new video codec Tomoyuki YamamotoTomoko AonoNorio Itoh

m15682 Industry Trends around Video Coding Jung Suk SuhKyong Sok Seo

m15579 Analysis for Ad Hoc Group on New Challenges in Video Coding Standardization

Kyohyuk LeeElena AlshinaJeonghoon ParkWoojin HanJunghye Min

m15580 Technical considerations for Ad Hoc Group on New Challenges in Video Coding Standardization

Kyohyuk LeeElena AlshinaJeonghoon ParkWoojin HanJunghye Min

m15578 On motion block size and partitions for 4:4:4 coding Shun-ichi SekiguchiShuichi YamagishiYusuke ItaniKohtaro AsaiTokumichi Murakami

Output documents:No. Title TBP Available9993 New Challenges in Video Coding Standardization N 08/07/259994 Workshop on New Challenges in Video Coding Standardization –

Call for ContributionsY 08/08/01

9995 Workshop on New Challenges in Video Coding Standardization –Program

Y 08/09/10

6 Other – Color conversion in case of multiple codecs in series

m15569 Proposal on standardization of a filter set for converting between 4:2:2/4:2:0 chrominance sampling

Distortions occur in case of concatenating several codecs with down/upsampling. New filter set is claimed to be capable avoiding this. Retains same phase position as conventional (“reference”) filter. Filters proposed are 8tap/4tap for down- and upsampling. Results: Improvement by 2.5 dB after 5 iterations (only one sequence presented).

Question: Will we need interlaced in the future? 4:4:4 and 4:2:0 could be sufficient.Answer: Similar approach can be designed for progressive.

Akira NakagawaKimihiko KazuiShunsuke Kobayashi

93

Question:What is meant by “reference” filter set? MPEG standards do not have any normative approach for MPEG down-/upsampling.Answer: Apparently the filters used in MPEG-4 VM.

Understanding of video group: So far, this was never standardized. To do it would require 1. A critical mass of companies requesting and 2. More evidence about the necessity (not just one sequence) 3. More understanding how typical this application case is in practice.

If at all, MPEG-C could be a home for such stuff, which seems to work somewhat across different video standards (similar to IDCT)

94

Annex H– JVT report

Source: Gary Sullivan and Jens Ohm, Chairs1. Documents of the JVT meeting 96

1.1. Input documents 961.1.1 Administrative input contributions.......................................................................961.1.2 Input liaison statements and parent-body inputs...................................................961.1.3 Non-administrative input contributions................................................................961.1.4 Late-registered input contributions, BoG reports, etc...........................................97

1.2. Late document availability 971.3. Withdrawn document registrations 981.4. Major output documents 98

JVT-AB200 Meeting report of the 28th JVT meeting (this document)..................................................98JVT-AB201-M (WG 11 N9969) Draft conformance testing for New Profiles for Professional Applications (T. Suzuki) [2008-07-25]...................................................................................................98JVT-AB202-M (WG 11 N9971) Draft conformance testing for SVC (V. Bottreau) [2008-10-01].......99JVT-AA203-M (WG 11 N9975) Draft reference software for SVC (H. Schwarz) [2008-08-01]..........99JVT-AA204 (WG 11 N9978) Joint draft multi-view video coding (MVC) [2008-10-01].....................99JVT-AA205-M (WG 11 N9976) ITU-T Rec. H.264 | ISO/IEC 14496-10 Advanced video coding defect report (G. Sullivan, H. Schwarz) [2008-08-01]............................................................................99JVT-AB206-M (WG 11 N9972) Draft conformance testing for MVC (A. Vetro et al.) [2008-08-31]. 99JVT-AA207-M (WG 11 N9974) Draft reference software for MVC (A. Vetro et al.) [2008-10-01]....99

1.5. JVT internal output documents 992. JVT administrative and liaison topics99

2.1. IPR policy reminder and update 992.2. Meeting opening and remarks by the chairmen 1012.3. JVT communication practices1022.4. Scheduling and logistics notes 1022.5. Administrative documents 102

JVT-AB000 List of documents of Hannover meeting.........................................................................102JVT-AB001 (AhG) [G. J. Sullivan, J.-R. Ohm, A. Luthra, T. Wiegand] AHG Report: Proj mgmt and errata......................................................................................................................................................103JVT-AB002 (AhG) [T. Wiegand, K. Suehring, A. Tourapis, T. Suzuki, G. J. Sullivan] AHG Report: JM text, ref soft, bitstream, conf...........................................................................................................103JVT-AB003 (AhG) [H. Schwarz, J. Vieron, T. Wiegand, M. Wien, A. Eleftheriadis, V. Bottreau] AHG Report: JSVM text, S/W, conf..............................................................................................................103JVT-AB004 (AhG) [A. Segall, T. Wiegand, Y.-J. Chiu] AHG Report: SVC bit depth, color gamut, and chroma format.......................................................................................................................................105JVT-AB005 (Ahg) [H. Kimata, A. Smolic, P. Pandit, A. Vetro, Y. Chen] AHG Report: MVC JD & JMVM text & software.........................................................................................................................105JVT-AB006 (AhG) [Y. Chen, S. Gao, Y.-J. Jeon] AHG Report: MVC JMVM coding tools..............107JVT-AB007-M (AhG) [G. J. Sullivan, A. Rodriguez, S. Narasimhan] AHG Report: Splicing operation...............................................................................................................................................................108

2.6. Closing session notes 1082.7. JVT liaison communications and parent-body communications 108

JVT-AB014 / M15538 [DVB TM-AVC] Incoming LS to WG 11 on Constrained Baseline...............108JVT-AB015 / M15554 [3GPP TSG SA4] Incoming LS to WG 11 on Constrained Baseline..............109Discussion of "Constrained Baseline" issue..........................................................................................110JVT-AB016 / M15711 [ATSC] Incoming LS to WG 11 on AVC Profiles..........................................110

3. AVC base specification, errata, and related topics 112JVT-AB010 / VCEG-AI07 (Errata) [HHI] ITU-T AAP Last Call comments on H.264(2007)/Cor.1. 112JVT-AB011 / VCEG-AI08 (Errata) [Microsoft] ITU-T AAP Last Call comments on H.264(2007)/Cor.1................................................................................................................................113JVT-AB012 / VCEG-AI09 (Errata) [Sony] ITU-T AAP Last Call comments on H.264(2007)/Cor.1 113

95

JVT-AB013 / M15558 (Errata) [JNB of WG11] WG 11 NB comments on ISO/IEC 14496-10:200X/DCOR1.......................................................................................................................113JVT-AB021 (Prop 2.2/3.1) [K. Kazui, A. Nakagawa, S. L. Bhavani, S. Kobayashi (Fujitsu)] Modification of POC type 1 specification.............................................................................................113JVT-AB036 (Errata 2.2.1/3.1) [Y.-K. Wang (Nokia)] SVC errata items.............................................114

4. Scalable video coding (SVC) 1154.1. SVC bit depth, color gamut, and chroma format scalability 115

JVT-AB029 (Req 2.2/3.1) [Y.-J. Chiu, H. Jiang, Y.-T. Peng, L. Xu (Intel)] Requirements for scalable video coding: color gamut scalability and bit depth scalability............................................................115

4.2. SVC Conformance 116JVT-AB023 (Ed....................................................................................................................................116Draft) [V. Bottreau (Thomson), A. Eleftheriadis (Vidyo)] SVC conformance testing.........................116

5. Multi-view coding (MVC) 1165.1. Comments on JD 116

JVT-AB020 (Prop 2.2/3.1) [Y.-J. Jeon, B.-M. Jeon (LG)] MVC comment on JD...............................116JVT-AB022 (Prop 2.0) [J. Huo, Y. Chang, M. Li, H. Yang (Xidian Univ.), S. Lin, S. Gao, L. Xiong (Huawei)] Comment on MVC JD 7.0...................................................................................................117JVT-AB024 (Prop 2.2.1/3.1) [Y. -K. Wang, Y. Chen, M. M. Hannuksela (Nokia)] Comments to MVC JD 7.0....................................................................................................................................................118JVT-AB028 (Ed. Draft) [A. Vetro (MERL), P. Pandit (Thomson), H. Kimata (NTT), A. Smolic (HHI), Y. -K. Wang (Nokia)] Editor's Input on MVC......................................................................................119

5.2. MVC profiles 119JVT-AB035 (Prop Prof 2.2/3.1) [H. Kimata (NTT), T. Nomura (Sharp), H. Nakamura (JVC), T. Itoh (Fujitsu)] On Multiview High profile....................................................................................................119JVT-AB037-L (Info) [A. Vetro (MERL)] MVC Profile/Level Definitions for Stereo........................121

5.3. MVC SEI 122JVT-AB025 (Info SEI) [M. Ji, Y. Chen, Y. -K. Wang, M. M. Hannuksela, H. Li (Nokia)] Showcase for non-required view component SEI message...................................................................................122JVT-AB026 (Info SEI) [M. Ji, Y. Chen, Y. -K. Wang, M. M. Hannuksela, H. Li (Nokia)] Showcase for view dependency structure SEI message.........................................................................................122JVT-AB027 (Info SEI) [M. Ji, Y. Chen, Y. -K. Wang, M. M. Hannuksela, H. Li (Nokia)] Showcase for operation point not present SEI message.........................................................................................123

5.4. MVC JMVM 124JVT-AB030 (Prop 2.2/3.1) [Y.-J. Jeon, B.-M. Jeon (LG), S. Gao, L. Xiong (Huawei)] Comments on JMVM 8.0.............................................................................................................................................124

5.5. MVC conformance testing 1245.6. MVC verification testing 125

6. AVC reference encoding methods 125JVT-AB031 (Ref soft 2.0/3.1) [W.-S. Kim, P. Pahalawatta, Z. Li, A. M. Tourapis (Dolby)] New Video Quality Metrics in JM reference software.............................................................................................125JVT-AB032 (Ref soft 2.0/3.1) [P. Pahalawatta, A. M. Tourapis (Dolby)] Reorg of Error Resilient RDO in the ref software..................................................................................................................................125JVT-AB033 (Ref soft 2.0/3.1) [A. Leontaris, A. M. Tourapis (Dolby)] Weighted Prediction Alternative to Adaptive Interpolation mechanisms..................................................................................................126JVT-AB034 (Ref soft 2.0/3.1) [E. Maani, L. Liu, A. M. Tourapis (Dolby)] JM Reference Software Enhancements........................................................................................................................................126

7. H.222.0 | MPEG-2 Systems extension for SVC 1268. JVT internal operating rules 1279. List of AHGs established 128

9.1. JVT project management and errata reporting 1289.2. JM Text, reference software, bitstream exchange and conformance 1299.3. SVC JSVM text, software and conformance 1299.4. SVC bit depth, and chroma format scalability 1299.5. MVC JD and JMVM text, software, and conformance 1299.6. Splicing operation 129

10. Future meeting plans 13011. Attendance 130

96

97

1 Documents of the JVT meeting

1.1 Input documents

1.1.1 Administrative input contributions

JVT-AB000 List of documents of Hannover meetingJVT-AB001-M (AhG) [G. J. Sullivan, J.-R. Ohm, A. Luthra, T. Wiegand] AHG Report: Proj mgmt and errataJVT-AB002-M (AhG) [T. Wiegand, K. Suehring, A. Tourapis, T. Suzuki, G. J. Sullivan] AHG Report: JM text, ref soft, bitstream, confJVT-AB003 (AhG) [H. Schwarz, J. Vieron, T. Wiegand, M. Wien, A. Eleftheriadis, V. Bottreau] AHG Report: JSVM text, S/W, confJVT-AB004 (AhG) [A. Segall, T. Wiegand, Y.-J. Chiu] AHG Report: SVC bit depth, color gamut, and chroma formatJVT-AB005 (Ahg) [H. Kimata, A. Smolic, P. Pandit, A. Vetro, Y. Chen] AHG Report: MVC JD & JMVM text & softwareJVT-AB006 (AhG) [Y. Chen, S. Gao, Y.-J. Jeon] AHG Report: MVC JMVM coding toolsJVT-AB007-M (AhG) [G. J. Sullivan, A. Rodriguez, S. Narasimhan] AHG Report: Splicing operation

1.1.2 Input liaison statements and parent-body inputsThe following ITU-T Q.6/16 and WG 11 parent-body input contributions were considered:

JVT-AB010 / VCEG-AI07 [HHI] ITU-T AAP Last Call comments on H.264(2007)/Cor.1JVT-AB011 / VCEG-AI08 [Microsoft] ITU-T AAP Last Call comments on H.264(2007)/Cor.1JVT-AB012 / VCEG-AI09 [Sony] ITU-T AAP Last Call comments on H.264(2007)/Cor.1JVT-AB013 / M15558 [JNB of WG11] WG 11 NB comments on ISO/IEC 14496-10:200X/DCOR1JVT-AB014 / M15538 [DVB TM-AVC] Incoming LS to WG 11 on Constrained BaselineJVT-AB015 / M15554 [3GPP TSG SA4] Incoming LS to WG 11 on Constrained BaselineJVT-AB016 / M15711 [ATSC] Incoming LS to WG 11 on AVC Profiles

1.1.3 Non-administrative input contributions

JVT-AB020 (Prop 2.2/3.1) [Y.-J. Jeon, B.-M. Jeon (LG)] MVC comment on JDJVT-AB021 (Prop 2.2/3.1) [K.Kazui, A.Nakagawa, S.L.Bhavani, S.Kobayashi (Fujitsu)] Modification of POC type 1 specificationJVT-AB022 (Prop 2.0) [J. Huo, Y. Chang, M. Li, H. Yang (Xidian Univ.), S. Lin, S. Gao, L. Xiong (Huawei)] Comment on MVC JD 7.0JVT-AB023 (Ed. Draft) [V. Bottreau (Thomson), A. Eleftheriadis (Vidyo)] SVC conformance testingJVT-AB024 (Prop 2.2.1/3.1) [Y. -K. Wang, Y. Chen, M. M. Hannuksela (Nokia)] Comments to MVC JD 7.0JVT-AB025 (Info SEI) [M. Ji, Y. Chen, Y. -K. Wang, M. M. Hannuksela, H. Li (Nokia)] Showcase for non-required view component SEI messageJVT-AB026 (Info SEI) [M. Ji, Y. Chen, Y. -K. Wang, M. M. Hannuksela, H. Li (Nokia)] Showcase for view dependency structure SEI message

98

JVT-AB027 (Info SEI) [M. Ji, Y. Chen, Y. -K. Wang, M. M. Hannuksela, H. Li (Nokia)] Showcase for operation point not present SEI messageJVT-AB028 (Ed. Draft) [A. Vetro (MERL), P. Pandit (Thomson), H. Kimata (NTT), A. Smolic (HHI), Y. -K. Wang (Nokia)] Editor's Input on MVCJVT-AB029 (Req 2.2/3.1) [Y.-J. Chiu, H. Jiang, Y.-T. Peng, L. Xu (Intel)] Requirements for scalable video coding: color gamut scalability and bit depth scalabilityJVT-AB030 (Prop 2.2/3.1) [Y.-J. Jeon, B.-M. Jeon (LG)] Comments on JMVM 8.0JVT-AB031 (Ref soft 2.0/3.1) [W.-S. Kim, P. Pahalawatta, Z. Li, A. M. Tourapis (Dolby)] New Video Quality Metrics in JM reference softwareJVT-AB032 (Ref soft 2.0/3.1) [P. Pahalawatta, A. M. Tourapis (Dolby)] Reorg of Error Resilient RDO in the ref softwareJVT-AB033 (Ref soft 2.0/3.1) [A. Leontaris, A. M. Tourapis (Dolby)] Weighted Prediction Alternative to Adaptive Interpolation mechanismsJVT-AB034 (Ref soft 2.0/3.1) [E. Maani, L. Liu, A. M. Tourapis (Dolby)] JM Reference Software EnhancementsJVT-AB035 (Prop Prof 2.0/3.1?) [H. Kimata (NTT), T. Nomura (Sharp), H. Nakamura (JVC), T. Itoh (Fujitsu)] On Multiview High profileJVT-AB036 (Errata 2.2.1/3.1) [Y.-K. Wang (Nokia)] SVC errata items

1.1.4 Late-registered input contributions, BoG reports, etc.

JVT-AB037-L (Info) [A. Vetro (MERL)] MVC Profile/Level Definitions for Stereo

1.2 Late document availabilityNon-administrative documents with document numbers suffixed in this report with "-L", "-Q", or "-M" were classified as late. Such documents will only be considered as information documents only (unless agreed otherwise by the group) if time permits, and consideration of them may be shifted to the end of the meeting as determined appropriate by the group.

For some time now, the JVT has agreed that no late-uploaded non-administrative (non-AHG-report, non-liaison, non-verification, non-errata-report, non-editor's draft) contribution would be presented without having a minimum of 4 JVT participants (from different other than that of the primary contribution author) recorded by name as supporting the allowance of such a presentation, in addition to a consensus of the general JVT membership to allow the presentation. Such support to allow a presentation is to be understood to not necessarily imply support of the adoption of the content of the late contribution, but only as a positive expression that the document should be allowed to be presented. Additionally, the provider of a presented late contribution shall send an email apology to the JVT email reflector. This rule does not apply to material requested by the JVT at the meeting (e.g., reports of JVT-authorized side activities).

JVT decision: Agreed.

Suffixes for contribution numbers in this report are explained below:– "-L" indicates a non-administrative contribution that was somewhat late but was available by

the second meeting day (contribution JVT-AB037 was in this category at this meeting).– "-Q" were more late than that (there were no contribution in this category at this meeting).– "-M" were still missing at the time of preparation of this draft of this report (there are no

contributions in this category for this meeting).– "-B" were break-out group discussion reports and other input requested during the meeting

Further suffixing by “V” indicates a contribution that contains a cross-verification of a proposal.99

On consideration of JVT-AB037An apology was sent.Supporting presentation were V. Bottreau, Y.-K. Wang, A. Eleftheriadis, and H. Schwarz.

There were no objections to presentations of late documents at this meeting.

It was noted that the situation surrounding the need for on-time availability of contributions has substantially improved since our lateness penalty rules were adopted.

1.3 Withdrawn document registrationsNone.

1.4 Major output documentsMajor output documents submitted to parent-body review included the following. (Dates listed are planned dates of availability.)

Review of missing outputs of last meeting:Prof prof reference software [ISO/IEC FDAM version (now done), JVT version]WD 1 of MVC reference software [JVT-AA212 ISO/IEC w9761]JMVM software [JVT-AA208 ISO/IEC w9763]

(Also, AVC Annex F to ISO/IEC secretariat needs editors' attention.)

Overview of outputs planned for this meetingErrata [Study status for ISO/IEC] (1 Aug)Prof prof conformance testing [FDAM for ISO/IEC, JVT?] (no editing period)Prof prof conformance testing DoCR on FPDAM ballot (no editing period)SVC conformance testing [FDAM for ISO/IEC, JVT] (1 Oct)SVC conformance DoCR on FPDAM ballot (no editing period)SVC reference software [Study status for ISO/IEC] (1 Aug – before ballot close)MVC text [FDAM for ISO/IEC] (1 Oct)MVC text DoCR on FPDAM ballot (no editing period)Draft 2 of MVC reference software [PDAM for ISO/IEC] (1 Oct)Draft 1 of MVC conformance [WD for ISO/IEC] (31 Aug)LS to ATSC (to coordinate with WG 11)LS to various orgs on MVC completion (no editing period)

Note that MPEG Systems plans to finalize SVC on ITU-T H.222.0 | ISO/IEC 13818-1 MPEG-2 Systems.

Notes on meeting resolutionsThank GNB for comments on SVC conf FDPAMThank ETRI, HHI, Orange, Sharp, Thomson, and Vidyo for providing bitstreams and

associated descriptions for inclusion in SVC conf FDAM

1.4.1.1.1 JVT-AB200 Meeting report of the 28th JVT meeting (this document)

1.4.1.1.2 JVT-AB201 -M (WG 11 N9969) Draft conformance testing for New Profiles for Professional Applications (T. Suzuki) [2008-07-25]

100

(Conveyed to WG 11 as "Text of ISO/IEC 14496-4:2004/FDAM 30 Conformance Testing for New Profiles for Professional Applications".)

1.4.1.1.3 JVT-AB202 -M (WG 11 N9971) Draft conformance testing for SVC (V. Bottreau) [2008-10-01]

(Conveyed to WG 11 as "Text of ISO/IEC 14496-4:2004/FDAM 31 Conformance Testing for Scalable Video Coding".)

1.4.1.1.4 JVT-AB203 -M (WG 11 N9975) Draft reference software for SVC (H. Schwarz) [2008-08-01]

(Conveyed to WG 11 as "Study Text of ISO/IEC 14496-5:2001/FPDAM 19 Reference Software for Scalable Video Coding".)

1.4.1.1.5 JVT-AB204 (WG 11 N9978) Joint draft multi-view video coding (MVC) [2008-10-01]

(Conveyed to WG 11 as "Text of ISO/IEC 14496-10:200X/FDAM 1 Multiview Video Coding".)

1.4.1.1.6 JVT-AB205 -M (WG 11 N9976) ITU-T Rec. H.264 | ISO/IEC 14496-10 Advanced video coding defect report (G. Sullivan, H. Schwarz) [2008-08-01]

(Conveyed to WG 11 as "Study Text of ISO/IEC 14496-10:200X/DCOR 1".)

1.4.1.1.7 JVT-AB206 -M (WG 11 N9972) Draft conformance testing for MVC (A. Vetro et al.) [2008-08-31]

(Conveyed to WG 11 as " Working Draft 1 of ISO/IEC 14496-4:2004/Amd.38 Conformance Testing for Multiview Video Coding".)

1.4.1.1.8 JVT-AB207 -M (WG 11 N9974) Draft reference software for MVC (A. Vetro et al.) [2008-10-01]

(Conveyed to WG 11 as " Text of ISO/IEC 14496-5:2001/PDAM 15 Reference Software for Multiview Video Coding".)

1.5 JVT internal output documentsJVT internal output documents included the following. (Dates listed are planned dates of availability.)

2 JVT administrative and liaison topics

2.1 IPR policy reminder and updateParticipants were reminded of the IPR policy established by the parent organizations of the JVT and were referred to the parent body web sites for further information. The IPR policy was summarized for the participants.

Participants were particularly reminded of the need to supply a completed JVT IPR status reporting form in all technical proposals for normative standardization. Participants were also reminded of the need to formally report patent rights to the top-level parent bodies (using the common reporting form found on the database listed below) and to make verbal and/or document

101

IPR reports within the JVT as necessary in the event that they are aware of unreported patents that are essential to implementation of a standard or of a draft standard under development.

The JVT chair noted that the top-level parent bodies have agreed upon a common patent policy among ITU-T, ITU-R, ISO, and IEC.

Some relevant links for organizational and IPR policy information are provided below:– http://www.itu.int/ITU-T/ipr/index.html (common patent policy for ITU-T, ITU-R, ISO, IEC

and guidelines and forms for formal reporting to the parent bodies)– http://ftp3.itu.int/av-arch/jvt-site (JVT contribution template for each meeting)– http://www.itu.int/ITU-T/studygroups/com16/jvt/index.html (JVT founding charter)– http://www.itu.int/ITU-T/dbase/patent/index.html (ITU-T IPR database)– http://www.itscj.ipsj.or.jp/sc29/29w7proc.htm (SC29 Procedures)

The JVT chair noted that the ITU TSB director's AHG on IPR had issued a clarification of the IPR reporting process for ITU-T standards, as follows (and as previously sent to the JVT email reflector), per SG 16 TD 327 (GEN/16):

“TSB has reported to the TSB Director’s IPR Ad Hoc Group that they are receiving Patent Statement and Licensing Declaration forms regarding technology submitted in Contributions that may not yet be incorporated in a draft new or revised Recommendation. The IPR Ad Hoc Group observes that, while disclosure of patent information is strongly encouraged as early as possible, the premature submission of Patent Statement and Licensing Declaration forms is not an appropriate tool for such purpose.

In cases where a contributor wishes to disclose patents related to technology in Contributions, this can be done in the Contributions themselves, or informed verbally or otherwise in written form to the technical group (e.g. a Rapporteur’s group), disclosure which should then be duly noted in the meeting report for future reference and record keeping.

It should be noted that the TSB may not be able to meaningfully classify Patent Statement and Licensing Declaration forms for technology in Contributions, since sometimes there are no means to identify the exact work item to which the disclosure applies, or there is no way to ascertain whether the proposal in a Contribution would be adopted into a draft Recommendation.

Therefore, patent holders should submit the Patent Statement and Licensing Declaration form at the time the patent holder believes that the patent is essential to the implementation of a draft or approved Recommendation.”

The JVT chair noted (as also previously remarked on the JVT email reflector) that since we are at the completion of the MVC amendment project, it was suggested that if anyone needs to report IPR on that topic and has not yet done so, now would be a good time to file formal notices to the parent bodies for any patent rights that are believed to be essential to the implementation of the MVC extensions (not to mention any notices not previously filed relating to the new SVC profiles, AVC professional profiles, or other previous projects).

It is suggested that, to enable proper interpretation of such formal notices, the MVC amendment should be clearly identified in such formal notices. For example, as “ITU-T Rec. H.264 and ISO/IEC 14496-10 Advanced video coding (2007 Ed.) Amendment 1 (2008): Multiview video

102

coding”. Notices pertaining to other efforts should be made with a similar degree of clarity of identification of the specific standardization work item to which the declaration pertains.

The chair invited participants to make any necessary verbal reports of previously-unreported IPR in draft standards under preparation and opened the floor for such reports: No such verbal reports were made.

2.2 Meeting opening and remarks by the chairmen

The meeting was opened at approximately 10:00 a.m. on Sunday 20 July 2008.

The JVT meeting will end by lunchtime on Friday 25 July at latest.Our goal for this meeting is to finish all major JVT business by noon on Thursday 24 July, leaving only perhaps some minor "tidying up" work after that.

Document handling and other working practices were reviewed for the participants.

A document template was attached to various email announcements and could also be found at http://ftp3.itu.int/av-arch/jvt-site/JVT-ABxxx.dot. It contained important instructions and policy information. Participants had been instructed to read it and use it as the basis of their contributions.

Documents were made available for download at http://ftp3.itu.int/av-arch/jvt-site/2008_07_Hannover.

The deadline was Wednesday 16 July 2008 for registrations and uploads.

The top areas of contributions were MVC and reports/suggestions for errata corrections.

At the opening session of the meeting, the JVT chairs reminded participants of the relevant IPR policy as described above, and reviewed the status and plans for the major projects under way in the JVT. The largest area of activity consisted of multi-view video coding (MVC) extensions of the ITU-T Rec. H.264 | ISO/IEC 14496-10 Advanced video coding (AVC) standard. SVC work was categorized as "phase 1" or "phase 2", depending on whether the work related to the recently-designed initial SVC amendment or to a potential future further SVC extension.

Opening remarks:– IPR policy reminder– Professional profiles – follow up work on reference software and conformance– SVC phase II – work areas included investigation of bit depth, color gamut, and chroma

format scalability and fine-granularity scalability– Multiview video coding (MVC) was a major project underway, with the goal of finishing the

amendment text for ISO/IEC as an output of this meeting– Corrigendum work is needed, and was a major priority for this meeting

Further work and additional needs on the development, standardization, and maintenance of the base specification and the recently-completed SVC and professional profiles, and of associated reference software and conformance specifications was noted.

The chair remarked that there were few late document uploads this time, and that the submitted documents seem to be generally adhering to the JVT guidelines in terms of formatting, filenames,

103

etc., which is a good development, although further improvement (particularly in the formatting conventions) is still needed. The JVT operating rules on that subject have helped.

2.3 JVT communication practicesJVT documents were available at http://ftp3.itu.int/av-arch/jvt-site.

These can also be accessed via ftp with the site name ftp3.itu.int, user ID avguest and password Avguest. Upon login, documents will then be found in the directory "jvt-site". Uploading of contributions is done by upload via ftp protocol to the "jvt-site/dropbox" directory using this account ID and password.

JVT email lists are managed through the site http://mailman.rwth-aachen.de/mailman/options/jvt-xyz, and to send email to one of these reflectors, the email address is "jvt-xyz@lists.rwth-aachen.de", where "xyz" corresponds to– "experts" for general experts group discussions– "bitstream" for bitstream exchange activities– "svc" for SVC work– "mvc" for MVC work

2.4 Scheduling and logistics notesInformation about the meeting, including participation registration information, had been made available at http://mpeg.tnt.uni-hannover.de/index.php.

Participants had been reminded of the need to be properly qualified to attend. Interested parties had been instructed to contact the JVT management team if they sought clarification of what proper qualification entails or if they needed help learning how to obtain such qualification.

JVT document registration and contribution archiving followed ordinary JVT practices.

Requests to register documents were handled by email to Gary Sullivan (gary.sullivan@ties.itu.int or garysull@microsoft.com).

The JVT work was suspended during plenary sessions of the ISO/IEC JTC 1/SC 29/WG 11 (MPEG) parent body.

Some “break-out group” (BoG) side activities and informal study efforts were conducted during the meeting. Documents produced by break-out group activities (if any) are listed in this report with the abbreviation “BoG” and are suffixed with "-B".

Note that the JVT has agreed that no late-uploaded (non-AHG-report, non-liaison, non-verification) contribution will be presented without having a minimum of 4 non-affiliated JVT participants from different organizations recorded by name as supporting the allowance of such a presentation, in addition to a consensus of the general JVT membership to allow the presentation. Additionally, the provider of a presented late contribution must send an email apology to the JVT email reflector. Additional details on this topic are described elsewhere in this report.

2.5 Administrative documents

Administrative & AHG report topics

104

2.5.1.1.1 JVT-AB000 List of documents of Hannover meeting

2.5.1.1.2 JVT-AB001 (AhG) [G. J. Sullivan, J.-R. Ohm, A. Luthra, T. Wiegand] AHG Report: Proj mgmt and errata

2.5.1.1.3 JVT-AB002 (AhG) [T. Wiegand, K. Suehring, A. Tourapis, T. Suzuki, G. J. Sullivan] AHG Report: JM text, ref soft, bitstream, conf

2.5.1.1.4 JVT-AB003 (AhG) [H. Schwarz, J. Vieron, T. Wiegand, M. Wien, A. Eleftheriadis, V. Bottreau] AHG Report: JSVM text, S/W, conf

This document presented the report of the AhG on JSVM text, JSVM software, and conformance.

The text of the Joint Scalable Video Model was not modified relative to JVT-X202 (JSVM-11).

The JSVM software has been improved relative to JVT-Y211/JVT-Z203. Known bugs have been fixed. Adoptions of the last JVT meeting and some new features (which were missing) have implemented into the software. The latest version of the JSVM software is JSVM 9.13.1 (CVS tag: JSVM_9_13_1).

Changes relative to JVT-Y211/JVT-Z203 (CVS tag: JSVM_9_12_2): Several bug fixes

o derivation of intra prediction modes in AVC rewrite modeo direct mode in enhancement layerso field picture coding (base layer only)

Several (minor) corrections related to decisions of the last JVT meeting in Genevao prefix NAL unit syntaxo removal of filler prefix NAL unitso fix in residual upsamplingo derivation of RestrictedSpatialResolutionChangeFlago I_BL mode in loopfilter of MBAFF frameso border extension before intra upsampling for interlaced

Correction of setting level_idc in encoder (included added support of level 1b) Full support of scaling matrices in encoder and decoder (including spatial & SNR

scalability and including a new encoder option for specifying scaling matrices) Full IPCM support in encoder and decoder (including spatial & SNR scalability) Correction of DPB implementation in decoder in particular regarding MMCO commands

for field pictures (more or less completely rewritten) Modification of coding order of pictures in encoder in particular for low-delay

configurations (supports "real" low-delay coding) Encoder support for (high-delay) hierarchical P pictures Encoder and decoder support for long-term pictures (requires smaller DPB for

hierarchical coding structures) Configuration file parameter for specifying the profile Check of profile constraints added in encoder Check of several level constraints added in encoder

o Maximum number of motion vectorso Minimum block size for bi-predictiono Maximum slice size for Scalable Baseline & Scalable High profileo Support of interlaced coding tools (frame_mbs_only_flag == 0)

105

o Support of CABAC & 8x8 transform in Scalable Baseline Some corrections in software manual

Required additions/corrections for future version: check/correction of SNR scalability with Mbaff frames (currently this is considered as

spatial scalability in the software) support of field pictures in scalable configurations in encoder (currently only correctly

supported in single-layer coding) addition of remaining profile/level constraints in encoder (add checks in decoder?) decoder support for AVC rewrite mode in connection with incomplete layer

representations (as adopted at the Geneva meeting in April 2008) error detection & concealment (without the restriction to two layers and fixed prediction

structures that was found in the previously implemented version)

Further desired improvements of the software: general improvement of encoder structure, including

o using same functions for P and B pictures ("key" and "non-key" pictures)o using same functions for "slice mode"o combine "motion estimation", "motion compensation", and "residual encoding"

support of more flexible encoder configurations, includingo GOP structures with non-dyadic prediction structureso combination of MGS and CGS codingo higher flexibility of "MGS vector mode"

In order to keep track of the changes in software development and to always provide an up-to-date version of the JSVM software, a CVS server for the JSVM software has been set up at the Rheinisch-Westfälische Technische Hochschule (RWTH) Aachen. The CVS server can be accessed using TortoiseCVS, WinCVS, or any other CVS client. The server is configured to allow read access only using the parameters specified in the table below. Write access to the JSVM software server is restricted to the JSVM software coordinators group.

authentication: pserverhost address: garcon.ient.rwth-aachen.depath: /cvs/jvtuser name: jvtuserpassword: jvt.Amd.2module name: jsvm or jsvm_red

Example 1 shows how the JSVM software can be accessed by using a command line CVS client.

Example 1: Accessing the JSVM software with a command line CVS clientcvs –d :pserver:jvtuser:jvt.Amd.2@garcon.ient.rwth-aachen.de:/cvs/jvt logincvs –d :pserver:jvtuser@garcon.ient.rwth-aachen.de:/cvs/jvt checkout jsvm

In Example 2, it is shown how a specific JSVM software version – specified by a tag (JSVM_9_8 in Example 2) – can be obtained using a command line CVS client. Note that co represents an abbreviation for the command checkout, which was used in Example 1.

Example 2: Accessing the JSVM software version with the tag JSVM_9_8 with a command line CVS clientcvs –d :pserver:jvtuser:jvt.Amd.2@garcon.ient.rwth-aachen.de:/cvs/jvt logincvs –d :pserver:jvtuser@garcon.ient.rwth-aachen.de:/cvs/jvt co –r JSVM_9_8 jsvm

It is possible to checkout only a reduced JSVM software package by using the module name jsvm_red instead of jsvm. In this case, the directories JSVM0-config-sample and MVC-Configs are omitted in the checkout, see Example 3.

106

Example 3: Accessing the JSVM software without the JSVM0 and MVC directories.cvs –d :pserver:jvtuser:jvt.Amd.2@garcon.ient.rwth-aachen.de:/cvs/jvt logincvs –d :pserver:jvtuser@garcon.ient.rwth-aachen.de:/cvs/jvt co jsvm_red

The CVS repository includes a JSVM software manual, which provides further information on the JSVM software.

The text of the conformance document "Draft conformance testing for SVC" was submitted as JVT-AA205. A revised version of the conformance draft was provided as input to this meeting as document JVT-AB023.

2.5.1.1.5 JVT-AB004 (AhG) [A. Segall, T. Wiegand, Y.-J. Chiu] AHG Report: SVC bit depth, color gamut, and chroma format

This contribution reported on activity for SVC bit depth, color gamut, and chroma format. The mandates of the AhG were: – Identify applications– Work out suggestions for detailed needs– Find/create test material– Study bit-depth reduction techniques, e.g., tone-mapping tools– Study color space and/or gamma conversion requirements– Study combined spatial and bit depth scalability– Define experiments and test conditions– Investigate software and text modification needs– Identify complexity issues

There was no activity reported on the reflector.It was noted that there was one relevant input contribution on the topic: JVT-AB029.

The AhG recommended the following: To review related contributions during the meeting To continue the AhG

2.5.1.1.6 JVT-AB005 (Ahg) [H. Kimata, A. Smolic, P. Pandit, A. Vetro, Y. Chen] AHG Report: MVC JD & JMVM text & software

At the Geneva meeting, JVT established the AhG on MVC JD and JMVM text and software with the following mandates:

1. Collect comments on draft, perform necessary editing and delivery.2. Maintain JMVM and JD document and collect comments on the text.3. Coordinate JD/JMVM software integration4. Coordinate bug-fixing process for the JD/JMVM software5. Maintain JD/JMVM software manual

The JMVM8 and JD7 were submitted to JVT as JVT-AA207 and JVT-AA209, respectively.

The JMVM8 text reflected changes described in the following contributions: JVT-AA028 [Huawei] Comment on Motion Skip JVT-AA031 [LG] High level syntax for motion skip mode JVT-AA047: Breakout Group Proposal for JMVM Motion Skip

107

It was reported that there had been several major changes made to the JD7 text. The changes were a result of input contributions and break-out group discussions during the Geneva meeting. The most significant changes are summarized below. Comments on JD [Ref: JVT-AA020 / JVT-AA021 / JVT-AA033 / JVT-AA046]

o Level limits and decoding resource requirements not be specified in terms of the number of views

o Bug fix to signal idr_pic_id in slice header (revised condition in 7.3.3 slice header syntax)

o Added text for SPS/PPS activation, NAL unit order/associations, detection of first VCL NAL unit

o Bug fix in NAL unit header SVC MVC extension syntax – no need to advance 3 byteso Remove max_num_view_depo Apply decoding process for POC independently for each viewo RPL construction process with discarded view components (text added to H.8.2)o Remove RPL construction for anchor pictures (text removed from H.8.2.1)o Specify sub-bitstream extraction for more than one target viewo For sub-bitstream extraction, added specification to ensure base view in output. o Assign SEI payload types

New SEI Messageso JVT-AA034: Non-required view component SEIo JVT-AA035: View dependency change SEI and operation point not present SEI

Other changes:o Aligned the structure of the syntax and semantics subclauses in Annex H to the base

spec – therefore, the syntax and semantics of NAL unit header extension and subset SPS, and the semantics of slice header, have been moved to Annex H.

o Updated Table 7-1 for description of different NAL unit types as well as VCL and VCL NAL units categarization, made corresponding changes in the base spec and Annex G.

o Added some new definitions, namely anchor access unit, anchor view component, decoded view component, IDR picture, IDR view component, inter-view prediction reference, inter-view reference index, non-anchor access unit, non-anchor picture, non-anchor view component, and reference picture. Removed the definition of V-IDR picture as it turned out to be useless in the new context. Also updated some of the existing definitions. Renamed inter-view only reference picture to inter-view only reference component.

o Updated NAL unit extension syntax (the order of syntax elements and name of the reserved bits syntax elements have been changed) and semantics, including some bug fixes (e.g. the first bit of the NAL unit header exttension shall be 1 for SVC and 0 for MVC, but was the other way round).

o In the subset SPS syntax, one bit equal to 1 was added before the syntax strucutre seq_parameter_set_mvc_extension( ), to make the subset SPS syntax compatible to the SVC subset SPS syntax specified in Annex G.

o Fixed the conditions related to slice_type in the ref_pic_list_reordering( ) syntax table.o Updated semantics for SPS MVC extension syntax elements and specified the

persistence and accuracy of these syntax elements.o Updated the reference picture list reordering semantics with both editorial

improvements and bug fixes – the bugs are related to the use of syntax element num_anchor_refs_lX[ i ].

o Updated the text for the reference picture list construction process, with both editorial improvemens and bug fixes – the bugs are related to the use of syntax elements num_anchor_refs_lX[ i ], anchor_ref_lX[ i ][ j ], num_non_anchor_refs_lX[ i ], and non-anchor_ref_lX[ i ][ j ] in subclause H.8.2.1.

108

o Updated the specification of the Multivew High profile regarding restriction to the base view bitstream and definition of the conforming decoders.

o Added exentions to semantics of AVC and SVC SEI messages (mainly regarding being not included or included in an MVC scalable nesting SEI message).

o Changed the name of scalable nesting SEI message to MVC scalable nesting SEI message to avoid using the same name as the one for SVC, and updated the semantics.

Some remaining open issues related to the JD text include: Revisit limit of 16 on max decoder frame buffering Review following text

o SPS/PPS activation, NAL unit order/associations, detection of first VCL NAL unito Sub-bitstream extraction processo All level limits

Semantics of profile, level and HRD parameters etc. in SPS and subset SPS and whether to signal additional sets of profile and level in SPS and subset SPS

Various editing notes in the text need to be resolved Consider relevant SVC errata [JVT-AA025]Resolved as reported elsewhere in this document.

The JMVM8 software had been delivered to the group on 6 June 2008 as JVT-AA208. This release contained:

High-level syntax changes to accommodate adoptions related to motion skip tool Software improvements and bug fixes

The JD reference software had also been produced, which reportedly corresponded to the JD text, i.e., no block level coding tools. This software was delivered on 6 June 2008 as JVT-AA212.

Some software issues that still need to be addressed were reported to include:1. Output order of views is not sequential or parallel2. Prepare validation scripts (work in progress)3. Provide support GOPsize=1 (with motion skip & IC)4. Trace file support for arbitrary view_id assignments

The AhG recommended1. To consider the input to this meeting in preparing future versions of the JMVM and JD2. To improve the manual created for the JD/JMVM software3. To follow the same software integration guidelines present in JSVM (repeated below)

2.5.1.1.7 JVT-AB006 (AhG) [Y. Chen, S. Gao, Y.-J. Jeon] AHG Report: MVC JMVM coding tools

The mandates of this AHG reported in the previous meeting are reused here. – Investigate simplification and improvement of current JMVM coding tools (IC and motion

skip)– Investigate techniques for single loop decoding to reduce complexity starting with motion

skip– Investigate approaches for enhancing MVC coding efficiency using spatial downsampling– Investigate low-complexity methods for mobile stereoscopic 3DTV applications– Investigate other potential approaches to achieving enhanced MVC capability– Coordinate software, test material, and experiment conditions for these techniques

109

– Evaluate performance of enhanced MVC proposals (including CAVLC operation in particular)

No email messages were reported to have been exchanged on this topic on the reflector.The only contribution identified by the AHG as relevant to this AHG in this meeting was JVT-AB030.

The AHG recommended to review this contribution and to discuss the mandates and the need for having such an AHG in the future.

2.5.1.1.8 JVT-AB007 -M (AhG) [G. J. Sullivan, A. Rodriguez, S. Narasimhan] AHG Report: Splicing operation

2.6 Closing session notes

In the closing session there were no requests to reopen discussions of preceding agenda topics and side activities recorded elsewhere in this report.

The JVT thanked its ISO/IEC JTC 1/SC 29/WG 11 (MPEG) parent body and the meeting organizers for hosting the 28th JVT meeting.

The meeting was closed at approximately 5:30 p.m. on Thursday 24 July 2008.

2.7 JVT liaison communications and parent-body communications

The JVT did not directly receive formal liaison communications at this meeting. However some JVT contributions were originated as National Body input liaison contributions to the WG 11 parent body as discussed below.

2.7.1.1.1 JVT-AB014 / M15538 [DVB TM-AVC] Incoming LS to WG 11 on Constrained Baseline

This document was an incoming liaison statement from DVB TM-AVC regarding constraints on AVC Baseline profile.

DVB TM-AVC indicated that they are pleased to learn that ISO/IEC JTC 1/SC 29/WG 11 has studied the references to using H.264/AVC in DVB applications, as specified in ETSI TS 102 005 and ETSI TS 101 154. They reported that these specifications have included the option to use H.264/AVC coding since 2005.

They indicated that they welcomed our provision of the "constraint_set1_flag" syntax element of H.264/AVC, to permit a hierarchy of strict supersets and subsets between the High, Main and Baseline profiles. This strict hierarchy was reported to be important in DVB applications, e.g. to ensure that bitstreams broadcast to mobile receiving devices may also be decoded by fixed SDTV or HDTV receivers. They stated that they are therefore happy to confirm that they have chosen to utilize the "constraint_set1_flag" syntax element, for the reasons explained in Annex A (informative) of TS 102 005. The relevant extracts were reproduced in the contribution, for our convenience.

110

The document does not directly address the topic of whether the JVT should define a "constrained baseline" capability or profile.

2.7.1.1.2 JVT-AB015 / M15554 [3GPP TSG SA4] Incoming LS to WG 11 on Constrained Baseline

This documents was an incoming liaison statement from 3GPP TSG-SA4 regarding constraints on AVC Baseline profile.

They report that they have indeed adopted AVC into four of their services: Packet-switched Streaming service (PSS), Multi-media Messaging Service (MMS), Multicast-Broadcast Multimedia Service (MBMS), and Multimedia Telephony Service for IMS (MTSI).

They report that they have examined their records and document archive, and there were two major motivations for asking that bitstreams be compatible with both Main and Baseline profiles:– there was a significant desire for broad bitstream interoperability, in particular that bitstreams

generated in or for 3G services should be broadly playable; specific mention was made of the desire to be able to play streams on set-top boxes and similar devices, which they expected would be Main profile;

– the tools that are present in Baseline but not in Main were mostly targeted towards error resilience, and in the environments in which errors do not occur, they add complexity without returning value.

Following on from point (a), they reported that they had some thought that in the future they might want to use Main profile (as terminals become more capable), and having the streams be Main-profile compatible would ease such an introduction.

Taking into consideration the following:1) that the AVC profiles do not ‘nest’, that is, bitstream compatibility with one profile

cannot be taken as implying compatibility with another;2) that there is no ‘compatibility list’ provided to indicate the compatibility of a bitstream

with multiple profiles (other than the constraint_set flags);3) that 3G bitstreams are reportedly probably most naturally considered as Baseline streams;4) that the JVT provided the means to signal compatibility with more than one profile, in the

part of the specification where profiles are signaled;they reportedly decided to ask that bitstreams be marked as Baseline, compatible with Main profile. They reported that they did not see any other way of doing this, and the way chosen used indicators provided in the AVC specification at the level of the signalling of profile and level. (For historical reasons, 3G specifications are reportedly written in terms of the decoder rather than the bitstream, but it was asserted to always be clear that decoders may exceed these requirements in any way.)

They reported that they appreciate the recent definition of a name for these bitstreams that are bi-compatible (“constrained baseline” streams). They indicated that they are not sure how to further improve the situation, as they are concerned that any change of signaling (e.g. to introduce a list) or profile (e.g. to introduce a new profile indication) could lead to incompatibility with existing terminals or bitstreams.

In summary, for our immediate purposes, the document indicates that they are pleased to have a definition of the "constrained baseline" name for a bitstream/capability class. It does not directly address the topic of whether the JVT should specify this configuration to be a profile (other than to say that they do not want a change of signaling – which no one was ever contemplating in any case).

111

2.7.1.1.3 Discussion of "Constrained Baseline" issueIn JVT discussions of JVT-AB014 and JVT-AB015 and the issues surrounding this topic, there was a desire expressed by the group to define a new Constrained Baseline profile corresponding to the capability/bitstream class currently drafted in the draft corrigendum as "constrained baseline". The envisioned benefits of defining such a profile would be

1) to enable implementations of the subset of capabilities currently-specified in these widely-deployed external standards to claim conformance to a profile of the standard by specification of a conformance point that corresponds to the capability set defined in these standards, and

2) to enable additional external specifications to specify selection of a profile of the standard which corresponds to a maximal compatibility subset of the capabilities of the existing profiles

3) to enable the specification of the video surveillance MAF in WG 11 to specify selection of this profile.

It was clear in this discussion that definition of such a profile would not involve any new value of profile_idc (or any other change of syntax relative to what is found in the DCOR as the definition of "constrained baseline"). This new profile should presumably be specified by the amendment approval process in ISO/IEC and the AAP process in ITU-T. ITU-T Consent could be achieved in October 2008 or February 2009.

Regarding the text of the DCOR, the group suggests leaving it as previously drafted, so that the new amendment would only need to modify the text to add the use of the terms "profile" and "conformance".

Agreed (to be coordinated with WG 11).

2.7.1.1.4 JVT-AB016 / M15711 [ATSC] Incoming LS to WG 11 on AVC Profiles

The ATSC reported that it is developing specifications for a new service to deliver video to mobile and handheld devices, known as ATSC M/H. A tentative decision has reportedly been made to employ AVC coding, Baseline Profile at level 1.3, with one picture format of 416 by 240 luma samples (WQVGA), with frame rates from 12.0 to 30 fps. These choices were made based on input from device manufacturers who indicate they can support early market entry of a large number of receiving devices.

Broadcasters have reportedly expressed interest in transmitting higher resolution (up to wide SDTV) pictures over ATSC M/H. A tentative decision has also reportedly been made that higher resolution may be handled by use of SVC.

However, concerns have reportedly been expressed that by restricting the video tools that may be used (e.g. no 'B' frames), and relying on SVC as a path to higher resolution, some inefficiency may be designed in that could lead to a long term under-utilization of precious data bandwidth. Before decisions are final, broadcasters would reportedly like to better understand the consequences to eventual bit rate possibilities.

ATSC would welcome any information that MPEG could provide to them as to the possible increased efficiency (compared to Baseline Profile, Level 1.3, 416x240 pixel image format constrained for SVC) that could be obtained by choosing a set of AVC tools that would give us more efficient coding (e.g. use of 'B' frames, weighted prediction, directly coding wide SDTV vs using SVC, etc.).

112

ATSC would like to reference a specific MPEG AVC Profile in the M/H specification. If a set of AVC tools that do not fit within an existing AVC Profile are the best solution for the M/H application, they ask if MPEG would consider defining a new Profile that ATSC could reference in its standards. If such a new profile option would be considered, they ask in what time frame this work could be completed.

Remark: It was suggested that the context of the intent was that picture aspect ratio would always be approximately 16:9, always have approximately square luma samples, and always be "progressive" scan. Further, it was suggested that the desire would be to have standardization completed in WG 11 and ATSC by the end of 2009, and to have devices actually deployed by that time. It was suggested that the total bit rate for the low-res and SD video might be about 0.5 Mbits/s.

Basic aspects of contribution:– Interest in greater coding efficiency than Baseline– Initial focus on 390-macroblock pictures, with longer term interest in SD– Some interest in SVC

Suggestion: Respond saying:

The use of the High profile may be appropriate. Our understanding is that very low cost, low power decoder implementations of the High profile are already available in the marketplace. For example, we have located product announcements for High profile decoding such as:– an implementation for 1920x1080p60 decoding that uses 160 mW,– an implementation quoting 1080p using 120 mW,– a reference to 3.5G and 4G mobile implementations of high bit rate High profile 1080p

decoding in 2009-2011,– an announcement referring to HD decoding using 45mW,Further such information should be discoverable with somewhat more study. Note that support for 1920x1080p60 would include support for a sample processing speed ratio that is higher by a factor of more than 40 relative to the requirements for 416x240x30.

Regarding compression capability, some information that we have received suggests that about a 40-60% bit rate savings for use of High profile rather than Baseline profile might be expected for material such as the 416x240 use that they describe (e.g., per JVT-N014 of Jan 2005, and we note that encoding technology for use of High profile features has advanced substantially further since that time).

If the High profile does not meet the needs of your application, we are prepared to collaborate further with you to study the subject and take appropriate action as necessary. Although we suggest that no new profile specification should be needed, in the event that this initial assessment is incorrect, the ISO/IEC approval process (and typical parallel ITU-T approval processing) for a new profile specification would ordinarily take 1-1.5 years after the decision to create a new profile and the determination of the detailed requirements of the profile design.

Selection of the High profile for lower resolution use would not preclude the use of scalable video coding (SVC) with this lower resolution video as the base layer, as the AVC specification includes a Scalable High profile that is specified to operated in that fashion.

We encourage further study and communication regarding the detailed application requirements, such as bit rates, image sizes, frame rates, etc. for the combined usage scenarios for the SD delivery in conjunction with WQVGA over ATSC M/H.

113

Agreed (to be coordinated with WG 11).

3 AVC base specification, errata, and related topicsThe latest prior errata reporting status was provided in JVT-Z210.

3.1.1.1.1 JVT-AB010 / VCEG-AI07 (Errata) [HHI] ITU-T AAP Last Call comments on H.264(2007)/Cor.1

This contribution contains various errata comments that were submitted as ITU-T AAP Last Call comments. Notes on particular topics in the contribution are provided below.

Regarding MMCO = 3, just delete "short-term" and add "(equal to 3 or 6)". In the following NOTE that contains "shall"s, change the "shall"s to "must"s and pluralize "field" at the end of the NOTE, and rephrase the extra NOTE as reviewed.

SPS activation for SVC – the SPS_id in the slice header can be different than the one in a BP SEI. The issue relates to the MGS feature. The precision of the position calculation depends on the level_idc, which may be different for different MGS layers. Two suggested approaches– use the level_idc of the layer with quality_id = 0 to determine the position calculation

precision (decouple the active SPS for HRD purposes from the active SPS for position calculation purposes)

– make the precision depend on frame size (width or height greater than 2048 or number of macroblocks greater than what's in 1920x1088 = 8160 Mbs) rather than level_idc.

Pick the first of those two options.

Active layer SPS should be activated by BP SEI – not just VCL NAL units. Agreed – seems obvious.

Removal of redundant constraint – yes – editorial.

Restriction for intermediate layers – yes – obvious.

Intra prediction constrained_intra_pred_flag and I_PCM – yes – obvious.

Clarification of overscan – minor reword – agreed.

4:2:2 and 4:4:4 – editorial/hypothetical – agreed.

Number of MVs per 2MB and bipred – 8x8 inference – touchy, but yes – agreed.

Motion constrained slice group SEI needs num_slice_groups_minus1 for parsing – add a NOTE suggesting to store the RBSP until the active PPS is known, then parse – agreed.

Two rewriting issues – no action needed on either item.

End of sequence NAL unit in SVC context – all layers must have IDR after that – agreed.

Persistence of SVC SEI messages – needs further study by editors. E.g., scalability information SEI persists forever – say that it ends if there's IDR at all layers.

114

Discretion given to editors for determining aspects not noted and finalizing according to their best understanding.

3.1.1.1.2 JVT-AB011 / VCEG-AI08 (Errata) [Microsoft] ITU-T AAP Last Call comments on H.264(2007)/Cor.1

This contribution contains various errata comments that were submitted as ITU-T AAP Last Call comments. Notes on particular topics in the contribution are provided below.

Comment 5(c): Seems to only be an issue when using Tools->Options->View-All, so it may not be necessary to fix.

Comment 5(k): Specify that the decoder shall ignore the content of the SEI message in those cases.

Comment 5(m): Re-examine aspects relating to "overscan", including in particular "do neither use".

Comment 5(n).i: We may have too many cases like that to try to fix them all, and in this case you can include the opening parenthesis in the search.

Comment 5(n).iii: May have already been fixed.

Comment 5(o): Maybe that's OK as-is.

Further details to be addressed in editing work.

3.1.1.1.3 JVT-AB012 / VCEG-AI09 (Errata) [Sony] ITU-T AAP Last Call comments on H.264(2007)/Cor.1

See discussion below regarding JVT-AB013.

3.1.1.1.4 JVT-AB013 / M15558 (Errata) [JNB of WG11] WG 11 NB comments on ISO/IEC 14496-10:200X/DCOR1

Discussed together with JVT-AB012.

These contributions advocate not to delete certain problematic level limits that had been specified to apply to (only) the first access unit of the bitstream. A.3.3.a and G.10.2.2.a: Number of slices in access unit 0. A.3.1.c, A.3.3.h, G.2.2.h: Number of bytes for access unit 0.

Remark: The problem of excess load possibility was sort of already there, since timing information could be stretched by an encoder to cause "hostile" bitstream characteristics.

JVT Disposition: These limits will not be entirely removed, however, they will not be made overly tight either – exact details are left to be worked out by the editors and interested parties and editors are to put their best effort outcome into the draft.

3.1.1.1.5 JVT-AB021 (Prop 2.2/3.1) [K. Kazui, A. Nakagawa, S. L. Bhavani, S. Kobayashi (Fujitsu)] Modification of POC type 1 specification

115

At the previous meeting in Geneva, JVT-AA022 it was asserted that the current specification of AVC does not always guarantee correct recovery of relative POC value when POC type 1 is used and a decoder starts the decoding process from a recovery point rather than an IDR picture. JVT-AA022 proposed three candidate actions to address the issue.

Remark: Because the semantics of the recovery point SEI message include a "promise" made to the decoder that the decoder can recover the correct pictures if it operates in a certain manner, therefore an encoder is not allowed to put the RP SEI message into the bitstream if such a use would create a non-recovery behavior. Agreed.

Since no prescription has been established in the text, the decoder should, in principle, able to initially guess any value of POC within the 32 bit range for the current picture and for any reference to a non-existing picture, and allocate a greater than 32 bit dynamic range to its POC estimate for subsequent delta accumulations and then everything must work properly once the recovery_frame_cnt has gone by. (It is also hypothetically possible to keep the value within a 32 bit range by adjusting the value of POC on every picture in the DPB by an offset whenever a value would otherwise be created that would violate the 32 bit range.)

It is the encoder's responsibility to ensure that no matter what value of POC the decoder initially guesses, once the recovery_frame_cnt has gone by, everything must work.

Add a NOTE to the spec to clarify this understanding.

The encoder must not (i.e. shall not) send a RP SEI message that would put the decoder into an undefined output state that persists beyond recovery_frame_cnt.

The RP SEI establishes a promise. The promise must be fulfilled.

Agreed.

3.1.1.1.6 JVT-AB036 (Errata 2.2.1/3.1) [Y.-K. Wang (Nokia)] SVC errata items

Some issues reported here were covered in the review of JVT-AB010.

Editor asked to study/resolve use of "RBSP" terminology relating to parameter sets. Agreed.

Editor to ensure proper specification of constraint on "active SPS" as well as "active layer SPS". Agreed.

Profile definitions – decoder conformance requirement for decoding ordinary AVC bitstreams should specify decoding of all ordinary compatible AVC bitstreams in a manner equivalent to what applies in Annex A. Agreed.

On restrictions to scalable nesting SEI message clarify that the "less than any of the particular values…" refers to the values of ( sei_dependency_id[i] << 4 ) + sei_quality_id[i], not the value of i. Agreed (insert commas around "for all present i" or otherwise restructure logic to clarify).

116

4 Scalable video coding (SVC)

4.1 SVC bit depth, color gamut, and chroma format scalability

4.1.1.1.1 JVT-AB029 (Req 2.2/3.1) [Y.-J. Chiu, H. Jiang, Y.-T. Peng, L. Xu (Intel)] Requirements for scalable video coding: color gamut scalability and bit depth scalability

This document considers a new application scenario for video coding in which color gamut scalability of consumer electronics product is asserted to be desired. The architecture of such a system design was presented, which includes modules of color gamut compression and color gamut expansion to achieve the color gamut scalability in the framework of SVC. Suggested requirements for color gamut scalability were described, and preliminary results that aim to demonstrate the benefits of the wide color gamut video at the receiver sides were shown. The document also suggests that higher bit depth formats are required for the video conveyed in the enhancement layer to increase the description of the level of color fidelity contained in the wide color gamut video.

Remark: Part of the asserted motivation is a quality assurance motivation, as opposed to an interoperability enabling motivation. Some systems will do a good job of gamut mapping if they receive out-of-gamut colors (and some will not) – that seems like a question of product quality assurance motivation rather than interoperability-enabling standardization motivation.

Counter-remark: But there is an issue here of trying to deploy new technology into a domain in which there is widespread use of existing technology that was not designed to accommodate the presence of the new signals.

The proponent indicated that there is a waste of bandwidth associated with sending wider color gamut representation to a limited-gamut receiver.

Question: But how much of a waste is that? Most scenes don't contain those extreme colors, and even for those that do, how many bits would be saved by mapping them to a narrower color gamut before encoding? Response from proponent: This is scene dependent – the bit rate savings potential may need study.

Envisioning a greater future emphasis on 4:4:4 coding and increased bit depths, the proponent indicated that the difference may become more important in such scenarios.

Examples were shown of pictures that look different, where the difference was asserted to be due to the limited gamut range of the BT.709 color primaries, coupled with a poor use of mapping (i.e., component-by-component clipping rather than proper color mapping) prior to limited-gamut display.

It was suggested that it would be preferable to design a transmitting system to perform the color mapping gamut limitation prior to encoding as a base layer, and then send the differences that extend the color gamut range as an enhancement layer.

Color gamut scalability had already been included in the scope of the relevant AhG work area.

Remark: Some of the demonstrated differences seem to have to do with 4:2:0 sampling rather than color gamut range.

117

Remark: We could offer a package of scalable features that would provide an enhancement of the sort that could not be provided by only increasing the bit rate/fidelity of the same representation. Consider:– extended gamut– increased bit depth– tone mapping– 4:4:4 enhancement of 4:2:0 or 4:2:2

Remark: Such an enhancement layer could be a separate business model as well as a separate enhancement bitstream.

Remark: What is the application? Responding remark: Potentially, optical disc (e.g. Blu-ray).

Remark: Why would such an application need scalability? Could someone just fit an extra single-layer bitstream on a Blu-ray disc.

JVT Disposition: Further study the requirements and determine the level of industry interest in such a scalable approach to delivery of these features.

4.2 SVC Conformance

4.2.1.1.1 JVT-AB023 (Ed.

4.2.1.1.2 Draft) [V. Bottreau (Thomson), A. Eleftheriadis (Vidyo)] SVC conformance testing

This contains changes proposed by the editors relative to JVT-AA205 (WG 11 N9755, no formal status in ITU-T), which was the output status of the previous meeting.

Section numbering was corrected to start at 30. Some corrections and updates about particular bitstreams were provided.

Latest bitstream collection status: 55 (75%) of the total of 73 planned bitstreams are available; another 7 bitstreams (10%) are expected to be delivered imminently. More verification of bitstream validity is desired (only verified by JSVM)

Preparation of DoCR to be done.

5 Multi-view coding (MVC)

5.1 Comments on JD

5.1.1.1.1 JVT-AB020 (Prop 2.2/3.1) [Y.-J. Jeon, B.-M. Jeon (LG)] MVC comment on JD

118

This contribution provided a comment on the MVC JD7.0 that was asserted to be editorial. It was asserted that the current specification does not clearly specify the decoding process of all the view components of the access unit. To clarify and specify the decoding process of all view components of the access unit, a comment describing the decoding process according to VOIdx (view order index) is presented.

JVT Disposition: The proponent was asked to work with the editors to clarify the text as necessary (without technical change). Done.

5.1.1.1.2 JVT-AB022 (Prop 2.0) [J. Huo, Y. Chang, M. Li, H. Yang (Xidian Univ.), S. Lin, S. Gao, L. Xiong (Huawei)] Comment on MVC JD 7.0

Two comments on the MVC JD7.0 were provided in this contribution. The first proposed change was related to the view dependency change SEI message, and a modification was proposed that was asserted to relate to compatibility with the sequence parameter set MVC extension.

IPR status clarification (verbal): The IPR declaration (box 2.0) in the contribution applies to both contributing organizations.

The first proposed change was to replace the lower index of a "for" loop – changing it from 0 to 1 (skipping over view 0). View 0 is the base view, which does not have dependencies, so its inclusion in the syntax loop was concluded to be an error.

JVT decision: Adopted (excess "{ }" curly brackets around single statements in syntax table will also be removed).

The second proposed change was related to the non-required view component SEI message, and a derivation method was proposed for the decoder to derive the non-required view component so that the explicit transmission of the SEI message for every related access unit could be avoided.

It was proposed to suggest that encoders not express dependencies in non-required view SEI messages that would be redundant under the assumption that decoders will be able to infer those dependencies (by recognizing conditions establishing which other components are non-required components, so that the transmission of redundant information can be avoided).

Concern: Dependency is made from SEI messages of other access units. Deriving the information at the decoder may not be simple and require dependency information beyond the SEI message itself.

Remarks: Proposal is to encourage not sending some SEI messages by depending on inferred relationships established from SEI messages of other access units. It was commented that some of these relationships that would need to be inferred might not be so easily derived. It was further commented that the current SEI message semantics would already allow such information to be inferred by a decoder – the text just does not include any remark pointing out this fact. Remark: The degree of redundancy expressed by use of the existing SEI message is already under the control of the encoder.

Suggestion: Have off-line study [Miska, Ye-Kui, and proponent] to consider whether providing only some additional non-normative remarks to point out what the decoder may be able to infer when some information is not directly expressed in the syntax. This discussion was held, and the subject was then further discussed by the group as a whole.

119

After this off-line study, some text suggested by the proponent was discussed.

Remark: This is about encouraging decoders to derive a relationship that they can already derive if they wish – so it may not be necessary to explicitly point out that this is possible.

Question: How much coding efficiency improvement would result from the encoder not sending redundant expressions of dependencies? It seems to be a very small amount of bits. Remark: And it is not easy to describe this extra dependency derivation.

Remark: There may actually be a benefit in terms of loss resilience and simple design functionality by simply having the minor degree of redundancy in the bitstream.

Although the proposal may be valid in the abstract sense, the foreseen benefit seems very minor, the envisioned decoder processing would need to become more sophisticated and possibly less robust, and when considering the need to finish the specification so quickly, it seems most prudent not to take action in this regard.

5.1.1.1.3 JVT-AB024 (Prop 2.2.1/3.1) [Y. -K. Wang, Y. Chen, M. M. Hannuksela (Nokia)] Comments to MVC JD 7.0

This document proposed to 1) remove the active view information SEI message from the MVC specification, and 2) address extraction of SEI messages in the sub-bitstream extraction process, which was not addressed in the latest MVC draft.

On active view information SEI message: It was proposed to remove the active view information SEI message. This SEI message was designed be included in the bitstream to indicate which views are the target output views, such that the target output views can be known from the bitstream. However, if the same MVC bitstream is used at a different operation point, then it was asserted that the content of the SEI message must be changed. It was asserted that this implies that for multicast with receivers using different operation points, some network elements between the sender and the receivers must change or insert active view information SEI messages into the outgoing sub-bitstreams. Due to this reason (among others), it was reportedly decided not to use this means to derive the set of target output views in the HRD specification in the MVC JD.

Suggestion: In the semantics of the SEI message, we can indicate that target view information may be conveyed by other means determined by the application, and that the determination of what to do in response to the content of the SEI message, if present, is determined by the application.

Suggestion: Remove the SEI message, specify that the target output views are determined by the application (by means not specified in this Specification) and that in the absence of any selection of target output views by the application, there shall be one target output view which is the base view. JVT decision: Agreed.

Definition of "target output view" needs editing work to express that well. See below.

Also add remarks as necessary to other new SEI messages, in the spirit of what is stated for, e.g., the film grain characteristics SEI message, that the actual decoder response to the SEI message is not normatively specified. JVT decision: Agreed.

On the sub-bitstream extraction process: The extraction process proposed in the editors' input (JVT-AB028) does not address SEI messages. In our opinion, all the information needed for

120

possibly further bitstream subsets, e.g. picture timing and buffering period SEI messages, should be retained after extraction and the extraction process should be appended accordingly. A note could be added to state that real applications can do extraction in other ways, e.g. to keep only those SEI messages required for certain operation points that are likely to be used. JVT decision: Agreed.

5.1.1.1.4 JVT-AB028 (Ed. Draft) [A. Vetro (MERL), P. Pandit (Thomson), H. Kimata (NTT), A. Smolic (HHI), Y. -K. Wang (Nokia)] Editor's Input on MVC

This document included editors’ input on the draft MVC specification. An important addition was the signaling of HRD parameters for bitstream subsets, along with related changes to the HRD subclauses. Other revisions include changes to the MVC scalable nesting SEI to enable signaling of HRD parameters. Some topics reported as bugs in the sub-bitstream extraction process had also reportedly been resolved, the semantics of SPS extension had reportedly been clarified, and some definitions had been added.

Regarding HRD, the MVC editors recommended that the approach documented in this contribution be adopted.

It was recommended that the revisions in the attached document be reviewed in detail in preparation for JD8 output.

The contribution was reviewed, various minor issues (typographical formatting, use of "if" versus "when", a space preceding a syntax structure parenthesis, etc.) were noted and recorded by the editors to be addressed.

JVT decision: Adopted (including suggestions described in included Powerpoint presentation deck – with minor modifications as recorded by the editors during the review) with number of views and max_dec_frame_buffering issues dealt with as discussed below in section on JVT-AB035.

5.2 MVC profiles

5.2.1.1.1 JVT-AB035 (Prop Prof 2.2/3.1) [H. Kimata (NTT), T. Nomura (Sharp), H. Nakamura (JVC), T. Itoh (Fujitsu)] On Multiview High profile

A revised version will be uploaded to clarify the IPR statement status. Done.

Target applications and comments on the related requirements of level constraints of Multiview High Profile were presented, relative to the current MVC draft.

Target applications for Multiview High Profile were discussed. Target applications were described as interactive video applications, such as panorama video and FTV / free viewpoint video, as well as multi-view 3D video. In addition, it was discussed how to use MVC in those applications, and parameters such as the number of views were discussed. Based on these parameters, comments were made on the level constraints of Multiview High Profile, relative to what is specified in the current MVC draft.

Particular points raised in the contribution:

121

– Requirements on the number of views to be decoded (see presentation slide with that title). Addressed by actions noted elsewhere.

– Limitation of 16 on max_dec_frame_buffering. Is this an expression of a limit on a capacity of storing pictures (each of which may contain multiple view components) or is it a limit on a capacity of storing view components? Remark: In the current draft, it is the latter. Let's keep that convention. This becomes part of the discussion of structuring of level definitions. See below.

– The value of num_views_minus1: In H.7.4.2.1.4 (Sequence parameter set MVC extension semantics), it was reported that there is a NOTE 2 for num_views_minus1, as follows: "NOTE 2 - This value should be changed by the sub-bitstream extraction process as specified in subclause H.8.3 to correspond with the exact number of views in a bitstream subset." Because NumViews reportedly affects the level constraints, it was suggested to change this to a normative specification. Remark: this syntax element should be understood to express an upper bound rather than an exact representation of the characteristics of the bitstream subset. JVT decision: Agreed – clarify in text.Question: Should we make this a u(n) rather than a ue(v) to enable changing the value without changing the coded number of bits (with n-1 signaled)? Remark: Wait – a loop counter depends on this value and the specified process will not work correctly if the value is changed.Conclusion: So the quoted NOTE should be removed. JVT decision: Agreed.Question: Change num_views_minus1 to num_views_minus2? No.

– The value of level_idc: Do we allow changing the value of level_idc by the sub-bitstream extraction process? See below.

– Calculations in the a) and b) level constraints: It was reported that there are calculations using mvcScaleFactor in a) and b) level constraints, as follows: Max( NumViews * PicSizeInMbs mvcScaleFactor * MaxMBPS, fR ). Does mvcScaleFactor apply to MaxMBPS? If so, it was suggested to change this to Max( NumViews * PicSizeInMbs (mvcScaleFactor * MaxMBPS), fR ). JVT Decision: Agreed.

– Calculations in the p) and q) level constraints: In the p) level constraint for VCL HRD parameters, NumViews is not multiplied for calculating BitRate[ SchedSelIdx ], however, in the q) level constraint for NAL HRD parameters, NumViews is multiplied for calculating BitRate[ SchedSelIdx ]. Clarification is needed if this is correct. JVT Decision: Agreed that this expression should not depend on NumViews, so condition "q" should be changed.

Suggestion: Any level definition for MVC should include capability of decoding at least two views of the corresponding type found as an ordinary AVC capability for the same level. This way the ordinary understanding of the capability associated with a level will still apply to the multiview case. (We did something like this in the SVC case.) Responsive remark from an editor: That's what the mvcScaleFactor does.

Suggestion: Add another dimension to level definitions to express view quantity capability, e.g., a level 3.2.x decoder can decode up to x views, where x is an integer greater than 1, with a DPB capacity that multiplies by x, max bit rate is R*(1+0.75*(x-1)) and CPB capacity C*(1+0.75*(x-1)), and limits on other things such as max_dec_frame_buffering may depend similarly on x. When x is not provided for a decoder capability description, a value of 2 would be implied for x. No – let's try not to go there if possible. Another amendment could address this later if necessary.

By inspecting the high-level syntax of a bitstream, it should be possible to determine that a decoder that conforms to some specified profile@level is required to be able to consume some well-defined subset of the bitstream and output some well-defined set of target views. Agreed.

122

In the absence of a selection of a set of target views by external means (not specified in the Specification), the selected set of target views is considered to be the base view. Agreed.

In the current draft, in the "main SPS" part of the "subset SPS", the profile_idc and level_idc indicate a decoder P@L that can consume the entire bitstream and output all views in it. This information will always be there. (Thus there needs to be some profile@level that is capable of consuming and outputting all views of the entire bitstream.) Suggestion: Let's change that. In an application there may never be a need to decode all views. Suggestion: Let's impose P@L constraints only on extracted subsets, and make the "global" P@L indication optional. In the absence of the global P@L indicator, we would specify conformance in terms of conformance of extracted subsets, not complete bitstreams. That seems agreed.

Each view that is present in the bitstream must be decodable (and outputable) by some profile@level decoder that is specified in the bitstream that consumes the subset of the bitstream associated with that view. Agreed.

The profile_idc and level_idc in the SPS extension part of the subset SPS for the view identifies that profile@level. Agreed.

Move operation point level_idc indications from SEI into SPS extension. Editor given discretion to draft syntax. Agreed.

For a coded video sequence, the number of views that are output per access unit is a constant. Agreed.

We are designing the profiles and levels based on the expectation that some cross-view dependencies will be present in the bitstream, i.e., MVC is being used for more than a simulcast multiplex. Agreed.

mvcScaleFactor = 2. Agreed.

NumViews is a number derived from the dependency tree for the operation point. Agreed.

Note: A coded video sequence is from IDR to IDR. There's a flag in the NAL unit header extension called an anchor_pic_flag to indicate an "anchor access unit". An anchor access unit seems to be essentially the same thing as a random access point SEI message with recovery_frame_cnt equal to 1.

Level limit on upper bound on max_dec_frame_buffering (within the larger Min( A, B ) expression as B), is Max(1, Ceil( log2( NumViews ) ) ) * 16. Agreed.

5.2.1.1.2 JVT-AB037 -L (Info) [A. Vetro (MERL)] MVC Profile/Level Definitions for Stereo

This informative contribution highlights reported benefits of MVC for stereo applications relative to other options such as simulcast and stereo interleaving. The suitability of the currently defined Multiview High profile and corresponding level limits is also considered.

There has been increased momentum recently in the production of 3D content for cinema applications; for the most part, this has been limited to stereo content. There are also a variety of display technologies on the market that support 3DTV, each offering a different viewing experience and having different input requirements. More specifically, stereoscopic displays

123

support stereo content and require glasses, while auto-stereoscopic displays avoid the need for glasses by rendering view-dependent stereo pairs for a multitude of viewing angles.

There are also a wide range of standardization bodies and consortia considering 3D, including Blu-Ray Disc Association, ATSC, SMPTE and 3D@Home, to name a few. It was suggested that MPEG/JVT should consider opening up liaison communications with these bodies.

The current market needs for stereo content could be satisfied with MVC. This would also be an appropriate format for future extensions to support auto-stereoscopic displays, either with the existing Multiview High profile or a backward compatible extension that includes information such as depth as part of the format.

AVC "stereo video SEI" has stereo capability, but requires some system and decoder adaptation to support decoding. MVC bitstreams can be decoded by legacy decoders and can operate in legacy system designs (provided no buffering constraints are violated).

A hypothetical new Level 4.3 was suggested to be considered for MVC purposes (perhaps not taking into account the mvcScaleFactor).

When considering a simulcast approach, note that this doubles the full bit rate and CPB and DPB capacity requirements of the decoders.

Remark: Many devices already include full dual decoder capability for PIP support.

Liaison communication suggestion: Drafted in side activity and later reviewed and approved.

5.3 MVC SEI

5.3.1.1.1 JVT-AB025 (Info SEI) [M. Ji, Y. Chen, Y. -K. Wang, M. M. Hannuksela, H. Li (Nokia)] Showcase for non-required view component SEI message

At the Geneva meeting, a non-required view component SEI message (JVT-AA034) was adopted into Joint Draft 7.0 of MVC. It specifies the view components that are not required for decoding a view. In this contribution, a showcase for the non-required view component SEI message was presented.

Example decoder operation was demonstrated with decoding of substantially fewer view components when the SEI message is recognized.

JVT disposition: The showcase is considered adequate to demonstrate the usefulness of this SEI message.

5.3.1.1.2 JVT-AB026 (Info SEI) [M. Ji, Y. Chen, Y. -K. Wang, M. M. Hannuksela, H. Li (Nokia)] Showcase for view dependency structure SEI message

At the Geneva meeting, a view dependency change SEI message (JVT-AA035) was adopted into Joint Draft 7.0 of MVC. It specifies the changes of the view dependency, and the changed dependency is a subset of the view dependency specified in the active sequence parameter set. In this contribution, a showcase for the view dependency change SEI message was presented.

124

Example decoder operation was demonstrated with decoding of substantially fewer view components when the SEI message is recognized.

JVT disposition: The showcase is considered adequate to demonstrate the usefulness of this SEI message.

5.3.1.1.3 JVT-AB027 (Info SEI) [M. Ji, Y. Chen, Y. -K. Wang, M. M. Hannuksela, H. Li (Nokia)] Showcase for operation point not present SEI message

At the Geneva meeting, an "operation point not present" SEI message (JVT-AA035) was adopted into Joint Draft 7.0 of MVC. It indicates those operation points that are no longer present after a certain point in bitstream order. In this contribution, a showcase for the operation point not present SEI message was presented.

The SEI message indicates that some view is not present in the bitstream.

Question: Is this SEI message to indicate a situation that should not actually intentionally occur (a decoder operating in an application with a selection of target views such that some selected target views are missing from the bitstream)? Responsive remark: Perhaps – or perhaps this message is intended to be a way to try to prevent such a situation from happening or to enable the detection of such a condition as an error condition (e.g. when a system-level indication/negotiation establishes an expectation that is contradicted or indicated as an exception by the SEI message). Remark: Some potential uses seem philosophically questionable, as this could be an SEI message designed to operate in a situation that perhaps should not actually be allowed to occur (i.e., a decoder operating with some selection of a target view that is not actually available in the bitstream).

Remark: A similar situation occurs for an SVC case, and there is a similar SEI message called a "layers not present" SEI message. Responsive remark: When presented with a conforming bitstream, the SVC spec says to decode what is present, not to guess that because the (potentially perfectly conforming) bitstream has characteristics that differ from what the decoder has been designed to expect, the decoder can do something different from what the standard says that it shall do in response to the conforming bitstream.

Remark: The question appears to be, in some potential uses, whether a decoder might be allowed to act as if there is something wrong with the bitstream when the bitstream is actually a conforming bitstream, and whether we should supply information to help decoders in such situations to exhibit better behavior. However, possibly there may be an indication/negotiation at the system level that the bitstream should have certain properties, or perhaps the SEI message can be the way to indicate the actual properties of the bitstream within the application environment.

The topic was further discussed. It was decided that such an SEI message is just a description of the characteristics of the (conforming) bitstream and that this ability to explicitly describe these characteristics appears likely to be useful in creating more robust decoders, by providing decoders with a description of the properties that the bitstream has (or should have if no data has been lost – which would enable a decoder to check whether the received data actually matches the described properties – such that a lack of a match would be an error condition). As long as the semantics of such an SEI message do not specifically refer to enabling an intentional non-conforming bitstream state (i.e. they are only a description of the properties of a conforming bitstream), there should be no problem with defining such an SEI message.

The fact that the decoder should not be placed into a situation (e.g. by external means at the systems level) in which it expects some data to be present in the bitstream means that the

125

availability of such SEI data that points out an absence of particular data subsets in the bitstream could be valuable in such a system environment as a check to ensure that external negotiations of bitstream properties match the internal properties of the actual delivered bitstream (or as the way established in an application environment to indicate what subset of the maximal set negotiated by external means at the system level is actually not present).

JVT disposition: The showcase is considered adequate to demonstrate the usefulness of this SEI message.

5.4 MVC JMVM

5.4.1.1.1 JVT-AB030 (Prop 2.2/3.1) [Y.-J. Jeon, B.-M. Jeon (LG), S. Gao, L. Xiong (Huawei)] Comments on JMVM 8.0

At the last meeting, a one bit flag, non_anchor_ref_lX_sample_pred_flag, was adopted to allow different view dependencies for inter-view sample prediction (ISP) and motion skip (MS). From this, the view dependencies for interview sample prediction and motion skip can be set differently.

In some old JMVM, the dependencies for ISP and MS were the same. At the last meeting, there were proposals to change that, and a flag was created for the SPS. Flag = 0 indicates not used for ISP but used for MS; Flag = 1 indicates used for ISP and may or may not used for MS.

Flag is called non_anchor_ref_lX_sample_pred_flag.

Remark: There may be an issue with common conditions or software, but not with the draft spec. ISP is allowed for P views for non-anchor pictures, although that capability is not used in the common conditions.

Proponent wants to be able to determine if a particular view is used for MS. Remark: Why? What is important to know, for single-loop decoding purposes, is only whether a view is used for ISP, not whether it is used for MS.

Off-line study was conducted to determine if there is a spec problem or a common conditions problem or a software problem or no problem and the topic was discussed further. It was concluded that no action is needed to address this issue.

5.5 MVC conformance testingRemark: Hypothetically, it might be possible to write a tool to construct multi-view conformance test sequences from ordinary AVC conformance test sequences.

Volunteers to provide bitstreams: Mitsubishi, Nokia, NTT, Thomson

Thoughts on desired functionality coverage:– Dependency structures (simulcast, P views, B views, temporal prediction structures, only

inter-view prediction, only anchor cross-view prediction, independent non-base view)– Use of anchor/non-anchor functionality (with and without exhibiting open GOP prediction

behavior, with different dependency structures for anchors than for other points)– Variation of number of views (e.g. 2, 3, 8)– Different vs. shared subset SPSs– Large value of max_num_ref_frames

126

– Reference picture list reordering– Bitstreams prior to extraction of operation point data subsets– Various extracted operation point subsets of such bitstreams– Some SEI message examples– MVC VUI– Bitstreams that have characteristics that change at IDR access units (e.g. operation point view

subsets)

5.6 MVC verification testing

This topic has not been discussed much in previous JVT discussions. It was noted that the project began after a rigorous subjective test effort to establish whether a substantial benefit could be demonstrated from the use of MVC. The basic design capability (in terms of picture coding tools and enabled dependencies) has not changed since that test in terms of coding efficiency capability. Thus the JVT considers the prior subjective test to suffice as a verification of the coding efficiency benefit of the design. Agreed.

6 AVC reference encoding methods

6.1.1.1.1 JVT-AB031 (Ref soft 2.0/3.1) [W.-S. Kim, P. Pahalawatta, Z. Li, A. M. Tourapis (Dolby)] New Video Quality Metrics in JM reference software

The H.264/AVC JM reference software currently only provides encoder distortion information using Mean Square Error (MSE) based error metrics. The computation is also constrained by the color format of the source sequence. It is claimed that such metrics do not model the human visual system very accurately. In this contribution the reference software is extended to support additional distortion metrics in the encoder such as the Structural Similarity Index (SSIM), the Multi-scale SSIM (MS-SSIM), and distortion computation in different color spaces such as RGB. The introduced code is claimed to be very flexible and could be further extended in the future with additional distortion metrics and could also consider different color spaces if so desired.

It is implemented such that the user of the JM encoder provides in addition to PSNR an SSIM value as output per picture. Average SSIM and also MS-SSIM values are output for the entire video sequence.ITU-R 601 is used for color conversion in case the measurement is done for RGB.

JVT decision: Adopt.

6.1.1.1.2 JVT-AB032 (Ref soft 2.0/3.1) [P. Pahalawatta, A. M. Tourapis (Dolby)] Reorg of Error Resilient RDO in the ref software

This document describes several major problems in the existing implementation of error resilient rate distortion optimization (ER-RDO) in the H.264/AVC reference software. It is presented that the existing code had to be significantly revamped in order to provide useful results. The document describes the steps taken to remedy some of the issues and improve the usability of the code, and provides simulation results using the corrected implementation. The motivation for this work is that the ER-RDO is a very useful component for improving the error resiliency of compressed AVC content. Fixing the implementation and improving its usability will greatly enhance the ability to further study rate distortion optimization schemes under lossy conditions.

127

Current implementation does not support B slices, and color distortion measurement. Planned to be available in next release.

Results have been presented showing that at 0% packet loss rate, the result is identical to the normal RDO. For 1% packet loss rate, an improvement of 3dB is reported.

JVT decision: Adopt.

Question on ER-RDO for JSVM. Needs checking.

6.1.1.1.3 JVT-AB033 (Ref soft 2.0/3.1) [A. Leontaris, A. M. Tourapis (Dolby)] Weighted Prediction Alternative to Adaptive Interpolation mechanisms

It is claimed that many proposals have been presented suggesting that H.264/AVC could be improved by the use of different interpolation mechanisms from the one currently supported in the reference software. In this contribution evidence is provided that one may consider simple tricks using the weighted prediction process, which is already supported by the standard, to emulate these mechanisms and achieve similar improvements.

Methods for use of the existing weighted prediction syntax are presented. Tried IPPP, IBBPBBP, and hier. B picture structures.

Results are reported in the IPPP setting for the case when the most recent reference picture is duplicated using RPLR syntax and assigned an offset of -1. Average bit-rate reductions are shown to be 4.65 for HD, 0.92% for CIF and 0.79% for QCIF.

Results are reported for the IBBP setting with list 0 unchanged and a similar modification was applied for list 1 as in IPPP. Average bit-rate reductions are shown to be 2.58% for HD, 0.68% for CIF and 0.87% for QCIF.

For hier. B pictures, the method is applied when coding reference P and reference B pictures. Average bit-rate reductions are shown to be 2.67% for HD, 1.06% for CIF and 1.38% for QCIF.

Contribution noted. Further work encouraged.

6.1.1.1.4 JVT-AB034 (Ref soft 2.0/3.1) [E. Maani, L. Liu, A. M. Tourapis (Dolby)] JM Reference Software Enhancements

In this contribution several enhancements that have been introduced into the H.264/AVC JM reference software, are presented. The enhancements include proper support of Adaptive Rounding for the low complexity rate distortion optimized mode decision, and support of bi-predictive motion estimation for partitions smaller than 16x16, among others.

Contribution noted. Further work encouraged.

7 H.222.0 | MPEG-2 Systems extension for SVC

Design features: - T-STD / P-STD model slightly extended: No additional buffer requirement- Transport of AVC in its own PID- Prefix NAL units are part of AVC PID- SVC “part” of AVC stream in one or more PIDs- New stream type 0x1F for SVC sub-bitstreams

128

- Hierarchy_Descriptor for dependency indications- New SVC_Extension_Descriptor for scalability information- Access unit delimiter (AUD) like NAL unit in SVC sub-bitstreams - Access unit reassembly based on DTS and SVC AUD- For the temporal scalability case, a pointer to DTS of “lower” sub-bitstream is added, if

needed- SVC subset SPS and SVC PPS go into SVC PID - SVC-related SEI messages may go into SVC sub-bitstream, requires in-Access Unit re-

ordering

Status:All open issues and NB comments addressed. Some editing still required. Final draft of text of ISO/IEC 13818-1:2007/FDAM3 with 3 weeks editing period.

The text of the current draft was briefly reviewed. Implementation available? yes, by FT and HHI. Will be presented at 16:00 (Thursday).

The JVT has approved the document.

8 JVT internal operating rulesJVT decision: The following clarifications/adjustments of JVT operating rules have been adopted.

The JVT decided that participants shall to refrain from long (=more than 4 Minutes) presentations of their proposal, if the results of their coding efficiency experiments have provided less than 2% bit-rate on average (or equivalently 0.1 dB gain on average).

Presentations should also not use "cherry picking" of results for summary reporting in abstracts and presentations. Summary reports must be true summaries – not highlights of best results while ignoring worst results.

Regarding late contributions: Due to our difficulties with a large quantity of late-submitted contributions at previous meetings, the JVT has agreed that for its next meeting, no late-uploaded (non-AHG-report, non-liaison, non-verification) contribution will be presented without having a minimum of 4 JVT participants (working for separate organizations other than that of the primary contribution author) recorded by name as supporting the allowance of such a presentation, in addition to a consensus of the general JVT membership to allow the presentation. Such support to allow a presentation is to be understood to not necessarily imply support of the adoption of the content of the late contribution, but only as a positive expression that the document should be allowed to be presented. Additionally, the provider of such a presented late contribution shall send an email apology to the JVT email reflector. This rule does not apply to material requested by the JVT at the meeting (e.g., reports of JVT-authorized "break out group" side activities).

For all contributions that have presentation material that is used to present them to the group (e.g., PowerPoint presentations), the presentation material should be provided along with the written contribution (within the same zip container file). PDF is preferred over PPT for presentations when the PPT filesize is large and there is no need for the slide deck to be editable by others.

All submissions must be made in JVT-ABxxx.zip format with the word docs, excel sheets and other information being in the zip container. The document must contain an abstract and be accompanied with an e-mail notification containing title, authors and abstract (identical to the one

129

in the doc) which is no longer than 200 words and no shorter than 25 words and is written in 3rd person language in a manner that does not express endorsement of the content of the document.

On filenames inside of .zip containers – use a filename so that if someone takes the files out of the zip container, they would still know what contribution they came from. Every file (or directory) in the .zip container for document JVT-ABxxx should start with JVT-ABxxx. Example: JVT-ABxxx.doc (main document), JVT-ABxxx_presentation.pdf, JVT-ABxxx_results1.xls, etc.

When providing additional or revised files, do not include copies of files that were already included in the prior .zip archive for the same contribution and do not re-use the same filenames without adding revision numbers (r1, r2, etc.) – this saves us needing to worry about whether the files someone obtains with the same filenames are the same or different.

Independent verification (necessary for adoption of a proposal) is provided either througha) independent implementation by 1 or more organization different than that of the

proponent based on the textual description (after adoption, both decoder source code versions must be made publicly available along with one encoder version), or

b) providing source code to all CE participants prior to the meeting (CEs can only be joined at the meeting, when the CE is created. CEs are created at each meeting and last until the next meeting.)

Simply running binary executables provided by a proponent is not ordinarily considered independent verification. Source code should be provided and used, and the verifying party should invest a proper degree of effort to ensure that the “verification” they perform is a meaningful and professional study with significant depth rather than just a perfunctory procedural formality.

For every SEI message and every syntax element that are currently in the SVC/MVC draft, a showcase has to be provided in order to retain it in the JSVM/JMVM/JD. If such a showcase is not provided at the next meeting for an SEI message or parts of it, the SEI message or the respective parts will be removed from the JSVM/JMVM/JD. The source code and executables for the showcase must be made available.

When Core Experiments (CEs) are to be established, a first CE description should be available at the last day of the meeting (or at least within a few days). Changes of the CE description are only allowed until 3 weeks prior to the next meeting. These changes must be of evolutionary characteristic relative to the input documents on which the CE is based and must be agreed by those who contributed the respective input document(s) or be added as an option.

Contributions that are proposals of new technology that was not what was described as being tested in a CE (even if related to the tested technology) should not indicate that they are CE documents in their title and abstract.

9 List of AHGs establishedThe following JVT “ad hoc groups” (AHGs) were established to progress work on identified topics until the next meeting of the JVT.

9.1 JVT project management and errata reportingDiscussion: jvt-experts@lists.rwth-aachen.de

130

Chair: Gary Sullivan, Jens Rainer Ohm, Ajay Luthra, and Thomas WiegandMandates:– Collect errata reports on standards under management of JVT– Coordinate overall interim JVT progress– Prepare status information for JVT status reporting

9.2 JM Text, reference software, bitstream exchange and conformanceDiscussion: jvt-experts@lists.rwth-aachen.deChair: Thomas Wiegand, Karsten Sühring, Alexis Tourapis, Teruhiko Suzuki, Gary SullivanMandates:– Maintain and update JM algorithm description text– Maintain and update JM reference software and its usage manual– Facilitate exchange of test bitstreams to aid interoperability testing– Collect bitstreams for inclusion in (non-SVC, non-MVC) Conformance specifications– Identify and correct problems in Conformance specifications and associated bitstreams

9.3 SVC JSVM text, software and conformanceDiscussion: jvt-svc@lists.rwth-aachen.deChair: Heiko Schwarz, Jérome Vieron, Thomas Wiegand, Mathias Wien, Alex Eleftheriadis, Vincent BottreauMandates:– Edit and deliver improved JSVM text– Coordinate JSVM software integration– Coordinate bug-fixing process for the JSVM software– Maintain JSVM software manual– Plan, edit, and collect bitstreams for SVC conformance specification

9.4 SVC bit depth, and chroma format scalabilityDiscussion: jvt-svc@lists.rwth-aachen.deChair: Andrew Segall, Thomas WiegandMandates:– Identify applications– Work out suggestions for detailed needs– Find/create test material– Study bit-depth reduction techniques, e.g., tone-mapping tools– Study color space and/or gamma conversion requirements– Define experiments and test conditions– Investigate software and text modification needs– Identify complexity issues

9.5 MVC JD and JMVM text, software, and conformanceDiscussion: jvt-mvc@lists.rwth-aachen.deChair: Hideaki Kimata, Aljoscha Smolić, Purvin Pandit, Anthony Vetro, Ying ChenMandates:– Collect comments on draft, perform necessary editing and delivery.– Maintain JMVM and JD document and collect comments on the text.– Coordinate JD/JMVM software integration

131

– Coordinate bug-fixing process for the JD/JMVM software– Maintain JD/JMVM software manual– Plan, edit, and collect bitstreams for MVC conformance specification

9.6 Splicing operationDiscussion: jvt-experts@lists.rwth-aachen.deChair: Gary Sullivan, Arturo Rodriguez, Sam NarasimhanMandates:– Study the use of bitstream splicing in applications– Investigate potential needs for SEI data to aid in splicing operations, including consideration

of JVT-Z040, JVT-Z041, and JVT-Z042 and the issues raised in their discussion– Study the implications of ITU-T Rec. J.181 and the draft new ITU-T Rec. J.h-dpi– Gather information about activities of other relevant organizations regarding the

development of specifications relating to bitstream splicing

10 Future meeting plans

The JVT chairmen proposed to hold the 29th JVT meeting during 13-17 October 2008 under WG 11 auspices in Busan, KR; and the 30th JVT meeting during 29 January – 3 February 2009 under ITU-T SG 16 auspices in Geneva, CH.

11 AttendancePersons registered to attend the meeting, as recorded by a sign-in sheet circulated during the meeting, were the following (90 listed participants): 1. Bang, Gun (ETRI)2. Bivolarski, Lazar Malinov (Logitech)3. Bottreau, Vincent (Thomson R&D France)4. Carballeira, Pablo (Univ. Polit. de Madrid)5. Chen, Peisong (Qualcomm)6. Chen, Ying (Tampere Univ. Tech.)7. Cheng, Ka Man Carmen (ASTRI)8. Chiu, Yi-Jen (Intel)9. Choi, Hae-Chul (ETRI)10. Chujoh, Takeshi (Toshiba)11. Cieplinski, Leszek (Mitsubishi Electric)12. de Haan, Wiebe (Philips)13. Ding, Dandan (Zhejiang Univ.)14. Divorra, Òscar (Thomson)15. Domański, Marek (Poznań Univ. Tech.)16. Duenas, Alberto (W&W Communications)17. Eleftheriadis, Alex (Layered Media)18. Even, Roni (Polycom)19. Feng, Yue (Univ. Glasgow)20. Fukushima, Shigeru (JVC)21. Hannuksela, Miska (Nokia)22. Haque, Munsi (Motorola)23. Haskell, Barry (Apple)24. Ho, Yo-Sung (GIST)

132

25. Hsiang, Shih-Ta (Motorola)26. Huo, Junyan (Xidian Univ.)27. Husak, Walt (Dolby Labs)28. Itoh, Takashi (Fujitsu Labs)29. Jeon, Byeong-Moon (LG Electronics)30. Jeon, Byeungwoo (Sungkyunkwan Univ. - SKKU)31. Jeon, Yongjoon (LG Electronics)32. Karczewicz, Marta (Qualcomm)33. Kazui, Kimihiko (Fujitsu)34. Kiang, Chiew Tuan (Inst. Infocomm. Res.)35. Kim, Myoung-Jin (Soongsil Univ.)36. Kimata, Hideaki (NTT)37. Klimansewski, Krynxtox (Poznań Univ. Tech.)38. Kogure, Tokuyo (Univ. Tokyo)39. Lee, Cheon (GIST)40. Lee, Yung-Lyul (Sejong Univ.)41. Lim, Jung Eun (LG Electronics)42. Lin, Sixin (Huawei)43. Luthra, Ajay (Motorola)44. Ma, Siwei (Peking Univ.)45. Motta, Giovanni (Qualcomm)46. Nakamura, Katsuyuki (Hitachi)47. Nishi, Takahiro (Panasonic)48. Oh, Seoung-Jun (Kwangwoon Univ.)49. Ohm, Jens-Rainer (RWTH Aachen Univ.)50. Pandit, Purvin (Thomson)51. Pateux, Stephane (Orange - France Telecom)52. Qi, Yingyong (Qualcomm)53. Ridge, Justin (Nokia)54. Sakazume, Satoru (JVC)55. Saito, Shohei (Hitachi)56. Schwarz, Heiko (Fraunhofer HHI)57. Segall, Andrew (Sharp Labs USA)58. Sekiguchi, Shun-ichi (Mitsubishi Electric)59. Senoh, Takanori (Univ. Tokyo)60. Shi, Xiaojin (Apple)61. Shimizu, Shinya (NTT)62. Sim, Donggyu (Kwangwoon Univ.)63. Singer, David (Apple)64. Stankiewicz, Olgierd (Poznań Univ. Tech.)65. Sullivan, Gary (Microsoft Corp.)66. Sun, Huifang (Mitsubishi Electric)67. Sung, Jaewon (LG Electronics)68. Suzuki, Teruhiko (Sony)69. Tan, Thiow Keng (NTT DoCoMo)70. Tanizawa, Akiyuki (Toshiba / Mitsubishi Electric)71. Thoma, Herbert (Fraunhofer IIS)72. Tian, Dong (Thomson)73. Tourapis, Alexandros (Dolby Labs)74. Tung, Yi-Shin (MStar Semi.)75. Vermeirsch, Kenneth (Ghent Univ.)76. Vetro, Anthony (Mitsubishi Electric)77. Wang, Ye-Kui (Nokia)

133

78. Wiegand, Thomas (Fraunhofer HHI)79. Wittmann, Steffen (Panasonic)80. Won, Kwanghyun (SKKU)81. Xiong, Lianhuan (Huawei)82. Yamakage, Tomoo (Toshiba)83. Yamamoto, Tomoyuki (Sharp)84. Yamasaki, Takahiro (Oki Electric Industry)85. Yao, Wei (I2R)86. Yashima, Yoshiyuki (NTT)87. Yea, Sehoon (MERL)88. Yoo, Jeong-Ju (ETRI)89. Yu, Haoping (Huawei)90. Yu, Lu (Zhejiang Univ.)

134

Annex I – Audio report

Source: Schuyler Quackenbush, Chair, Audio Subgroup1 Opening of the meeting.........................................................................................................1342 Administrative matters...........................................................................................................134

2.1 Communications from the Chair 1342.2 Approval of agenda and allocation of contributions 1342.3 Creation of Task Groups 1342.4 Approval of previous meeting report 1342.5 Review of AHG reports 1342.6 Joint meetings 1342.7 Received National Body Comments and Liaison matters 134

3 Record of AhG meetings.......................................................................................................1353.1 AhG Meeting on SAOC, Unified Speech and Audio Sunday 1000-1700 135

3.1.1 Unified Speech and Audio 0900-1400........................................................................1353.1.2 SAOC 1400-1800........................................................................................................139

4 Plenary presentations.............................................................................................................1395 Task group activities..............................................................................................................140

5.1 Joint meetings and documents from other groups 1405.1.1 MPEG standards for Gaming.......................................................................................1405.1.2 Interactive Music AF, M15626....................................................................................1405.1.3 Proposed Audio profiles for ALS, SLS.......................................................................141

5.2 Task Group discussions 1415.2.1 MPEG-2 and MPEG-4 audio, conformance, reference software................................1415.2.2 MPEG-4 AAC Enhanced Low Delay..........................................................................1445.2.3 MPEG-D SAOC..........................................................................................................1455.2.4 MPEG-D Unified Speech and Audio..........................................................................146

6 Meeting deliverables..............................................................................................................1477 Responses to Liaison and NB comments...............................................................................148

7.1 Recommendations for final plenary 1487.2 Establishment of Ad-hoc Groups 1487.3 Approval of output documents 1487.4 Press statement 148

8 Future activities.....................................................................................................................1488.1 Schedule of future meetings 1488.2 Agenda for next meeting 1488.3 All other business 1488.4 Closing of the meeting 148

Annex A Participants...............................................................................................................149Annex B Audio Contributions and Schedule...........................................................................151Annex C Task Groups.............................................................................................................155Annex D Output Documents....................................................................................................156Annex E Agenda for the 85th MPEG Audio Meeting..............................................................157

135

1 Opening of the meetingThe MPEG Audio Subgroup meeting was held during the 85th meeting of WG11, July 21- 25, Hannover, DE. The list of participants is given in Annex A.

2 Administrative matters2.1 Communications from the ChairThe Chair summarised the issues raised at the Sunday evening Chair’s meeting, proposed task groups for the week, and proposed agenda items for discussion in Audio plenary.

2.2 Approval of agenda and allocation of contributionsThe agenda and schedule for the meeting was discussed, edited and approved. It shows the documents contributed to this meeting and presented to the Audio Subgroup, either in the task groups or in Audio plenary. The Chair brought relevant documents from Requirements, Systems to the attention of the group. It was revised in the course of the week to reflect the progress of the meeting, and the final version is shown in Annex B.

2.3 Creation of Task GroupsTask groups were convened for the duration of the MPEG meeting, as shown in Annex C. Results of task group activities are reported below.

2.4 Approval of previous meeting reportThe 84th Audio Subgroup meeting report was registered as a contribution, and was approved.

2.5 Review of AHG reportsThere were no requests to review any of the AHG reports.

2.6 Joint meetingsThe joint meetings with Audio for the week are shown below:Groups What Where Day TimeAll MPEG standards for Gaming Plenary Wed 1100-

1200Sys., Audio, Req.

Interactive Music AF, M15626 Audio Wed 1600-1700

Audio, Req. Proposed Audio profiles for ALS, SLS

Audio Thu 1100-1130

2.7 Received National Body Comments and Liaison mattersThe NB Comments and Liaison documents for the meeting that require a response are as shown below.No. Title Topic Response bym15261 Liaison Statement from ITU-T SG 16 Enhanced Low

Delay AACSchnell

m15516 Liaison Statement from ITU-T SG 16 full band audio coding

Schnell

m15555 IEC 61937-10 Digital Audio Interface ALS over IEC 61937-10

Quackenbush

m15551 FRNB comment on the Unified Speech and Audio Coding Exploration Activity

USAC Quackenbush

136

m15720 KNB comment on the Unified Speech and Audio Coding Exploration Activity

USAC Quackenbush

3 Record of AhG meetings3.1 AhG Meeting on SAOC, Unified Speech and Audio Sunday 1000-17003.1.1 Unified Speech and Audio 0900-1400

Test Site ReportsThe first set of presentations reported on the test site listening facilities. These were very straightforward and factual, and in each case there was no discussion to record. Kristofer Kjörling, Dolby, presentedm15545 Speech and Audio listening test lab report from Dolby Kristofer Kjörling

Anisse Taleb, Ericsson, presentedm15618 Speech and Audio listening test lab report (Ericsson) Anisse Taleb

Taejin Lee, ETRI, presentedm15570 Unified speech and audio coding listening test report from

ETRITaejin LeeSeungkwon BeackMinje KimKyeongok Kang

Herve Taddei, Huawei, presentedm15678 Audio Report on the subjective testing of Unified

Speech and Audio Coding proposals at HuaweiLijing XuHerve Taddei

Pierrick Philippe, France Telecom, presentedm15655 France Telecom listening test results for the CfP on

Unified Speech and Audio CodingPierrick PhilippeDavid Virette

Markus Multrus, FhG, presentedm15619 Report on USAC Subjective Tests at Fraunhofer IIS Test

SiteMarkus MultrusRalf Geiger

Dong Soo Kim, LGE, presentedm15581 Report on the USAC listening test at LGE Dong Soo Kim

Sungyong YoonJaehyun LimHyun-Kook LeeHenney OhYang-Won Jung

Werner Oomen, Philips, presentedm15548 Speech and Audio listening test lab report from Philips Werner Oomen

Jeroen Koppens

Eunmi Oh, Samsung, presentedm15567 Listening test results for Unified Speech and Audio

Coding from SamsungEunmi OhMiyoung KimJungHoe Kim

Oliver Wuebbolt, Thomson, presentedm15565 Speech & Audio - Listening Test, Report & Results -

ThomsonJohannes Boehm Oliver Wuebbolt Florian Keiler

Roch Lefebvre, VoiceAge, presented137

m15608 Report on USAC subjective tests at VoiceAge test site Roch Lefebvre

System DescriptionsThe next set of presentations reported on the proponent system architectures.Kristofer Kjörling, Dolby, presentedm15547 Technical description of the Dolby Philips proposal for the

speech and audio work- itemKristofer KjörlingWerner OomenJonas SamuelssonLars VillemoesBarbara ReschErik SchuijersPontus Carlsson

The Dolby/Philips system builds on HE-AAC V2 architecture, but adding prediction-based time domain processing elements. The tools in HE-AAC V2 have been slightly modified so as to offer additional compression performance for the diverse speech and audio content. The MDCT permits a number of window lengths and block sizes, in which all transform bins have equal bandwidth. All AAC-LC tools were available in the core coder. The codec delay can be as much as 1.2 seconds, which is due primarily to encoder look-ahead and blocking into super-frames.Taejin Lee, ETRI, presentedm15568 Technical description of the ETRI proposal for the unified

speech and audio codingTaejin LeeSeungkwon BeackMinje KimKyeongok KangHochong ParkYoungcheol Park

The ETRI system combined the individual tools from AMR-WB+ and HE-AAC V2 to create a new codec, with modifications to the tools as needed to address the coding of diverse content types. It used two processing models: Steady State using linear prediction coding tools, and Complex State using transform coding tools. There is a very flexible signal state decision module that results in a hard decision to use one of the two processing models for each block. Bernhard Grill, FhG, presentedm15621 Technical Decsription of the Fraunhofer IIS Submission

for the CfP on USACMarkus MultrusRalf GeigerBernhard GrillNikolaus RettelbachMax Neuendorf

The FhG system is a collaboration between Fraunhover IIS and VoiceAge. The system combines elements from MPEG Surround, the SBR tool, AAC and ACELP linear prediction coding. The tools were modified as appropriate for better performance for coding diverse speech and audio content. MPEG Surround is used for stereo processing, although it can easily be extended for processing multi-channel signals. In the submission it only uses a single OTT box. The SBR technology employed the same filterbank as MPEG Surround, but was enhanced to support very low cross-over frequencies. It can be switched off for high-bitrate operation. The core coder is comprised of a Linear Prediction tool and a MDCT Transform coder or Time-Domain coder. In the core coder, the Linear Prediction tools can be activated on a block-by-block basis or can always be active. The LP tool is followed by either a time-domain coding tool (ACELP) or a frequency-domain coding tool (AAC). At high bitrates the system is virtually identical to AAC. The AAC tool uses an improved entropy coder and optionally uses time-warping for improved performance on speech signals.The possible configurations of the core coder are:State Stage 1 Stage 2

1 LPC Time-Domain residual coder2 LPC MDCT residual coder3 LPC

offMDCT Coder

138

Philippe Gournay, VoiceAge, presentedm15609 Technical Description of the VoiceAge Candidate for

USACRoch Lefebvre

The VoiceAge system is a collaboration between Fraunhover IIS and VoiceAge. The decoder is essentially the same system as was presented in the FhG contribution. The time-domain core coding tool is the AMR-WB ACELP coding tool.The LPC coding tool is typically switched on for speech-like signals. In this case, the core coder can switch between time-domain (ACELP) and frequency-domain coding of the residual (TCX) on a block-by-block basis. If the LPC coding tool is switched off, the coder uses frequency-domain coding. At high bitrates the codec is very similar to AAC. The VoiceAge encoder employed a different psychoacoustic model, SBR tool and MDCT coder. The MDCT did not employ time-warping.The complexity of the decoder is no more than 1.8 times that of HE-AAC V2.

Dong Soo Kim, LGE, presentedm15582 LGE submission to Unified Speech & Audio Coding Dong Soo Kim

Sungyong YoonJaehyun LimHyun-Kook Lee

The LG system switched between three coding modules for coding speech-rich signals, music-rich and mixed speech and music. The speech-rich coder employs a modified AMR-WB+ tools, music-rich coder used a modified HE-AAC V2 tools and mixed coder uses a residual coding scheme. The decoder employs a delay compensation process so that the system can switch between coding modes on a block-by-block basis. JungHoe Kim, Samusng, presentedm15564 Response to CfP on unified speech and audio coding Eunmi Oh

JungHoe KimMiyoung KimKiHyun ChooHosang Sung

The presentation noted that coding of music signals is most effective using atransform coder with perceptual threshold for shaping the quantization noise while coding of speech signals is most effective using a linear predictive speech model. The Samsung system uses a non-uniform bandwidth MDCT tool and any of the T/F information can be coded be either the high-temporal resolution tool or HE-AAC like quantization tools. In addition, it uses a TNS tool, a SBR tool and a parametric stereo tool. The high-temporal resolution tool is only used at the lower bitrates. In discussion it was noted that, without considering quantization errors, the variable T/F MDCT tool operates such that time-domain aliasing is always cancelled.Oliver Wuebbolt, Thomson, presentedm15566 Speech & Audio - Description of Technology of the

Thomson proposalFlorian KeilerOliver WuebboltJohannes Boehm

The Thomson system uses a speech/audio switch to select either a time-domain coding tool or a frequency-domain coding tool in the core coder. In addition, it incorporates SBR and Parametric Stereo coding tools. Analysis of Listening Test DataThe final set of presentations reported on analysis of the listening test data.Werner Oomen, Philips, presentedm15546 Analysis of speech and audio listening test data Werner Oomen

Kristofer KjörlingHeiko Purnhagen

This contribution presents the Philips and Dolby experts analysis of the listening test data. The data was analyzed to determine if the requirements as specified in the Evaluation document were met, for both 95% and 99% confidence intervals. The results showed that systems 2, 4, 8, 10 and 11 were promising systems with respect to the Requirements analysis.Taejin Lee, ETRI, presentedm15613 Analysis of unified speech and audio coding listening test Taejin Lee

139

results Seungkwon BeackMinje KimKyeongok Kang

This contribution presents an analysis of the Figure of Merit statistics. It presents a count of how often each system has the highest mean performance for each test and each signal category. Its conclusion is that there is no dominant best system.Pierrick Philippe, France Telecom R&D, presentedm15656 France Telecom contribution to the analysis of the

listening test results following the CfP on Unified Speech and Audio Coding

Pierrick PhilippeDavid Virette

This contribution presented graphs of system performance as compared to VC. For each signal category it performed single-sided T-tests with respect to the best performing systemCategory System with best mean score

S 4, but not different from performance of 10S+M 2 is best

M 10, but not different from performance of 11The overall conclusions are that systems 2, 4, 8, 10 and 11 all seem promising for this new work.Ralf Geiger, FhG, presentedm15625 Analysis of USAC Listening Test Data Frederik Nagel

Ralf GeigerMax NeuendorfMarkus Multrus

The contribution first presents the calculation of VC for each test and each category.For the Requirement that the New Technology be no worse than VC, only sys10 and sys11 meet the requirements for very test and every category for both the 95% and 99% levels of significance.For the Figure of Merit, only sys10 and sys11 have a non-negative “d” statistic for all tests, at the 95% level of significance. When averaged over all tests, only sys2, sys10 and sys11 have a non-negative “d” statistic, at the 95% level of significance, but sys10 has the best mean “d” statistic, but this mean value is not different from that of sys11 at the 95% level of significance.Roch Lefebvre, VoiceAge, presentedm15610 Analysis of Combined Listening Test Results for USAC Roch Lefebvre

This contribution presents a number of interesting views of the test results based on ranking of the proponent mean scores based on test, signal category and signal. The overall conclusion is that sys10 is the best overall proposal, followed closely by sys11.Eunmi Oh, Samsung, presented a statistical analysis of listening test data, which was provided in contribution m15567. It presented a table showing which systems had the best performance by test and signal category, and also showed the systems whose performance were not different from the best. It concluded that there is no dominant system when performance is viewed by test and signal category. Systems sys2, sys4, sys8, sys10 and sys11 all seem promising. Frederik Nagel, FhG, noted that presenting a table of results based on best mean score might be misleading, in that several systems may have mean scores that are not different from the best at the 95% level of significance.Dong Soo Kim, LG, presented m15713 USAC listening test analysis from LGE Dong Soo Kim

Sungyong YoonThis contribution presents a statistical analysis of listening test data. This was registered as m15713 and was uploaded on Sunday July 20. For the Requirements, it showed that only sys10 and sys11 pass the Requirements for all tests and all signal categories. Furthermore, it noted that sys4 passed the Requirements most often for speech category signals and sys2 passed the Requirements most often for mixed category signals. It presents a Figure of Merit analysis by signal, sys2, sys10 and sys11 all have similarly good performance.Review of AhG ReportThe AhG Chairs presented the AhG report and proposed

140

To use France Telecom R&D mono/stereo graphs of performance with respect to VC, but removing LP anchors, AMR-WB+ and HE-AAC-V2.

And additionally summarize the test results as sys10 and sys11 are the best or not different from the best for almost every bitrates (mono

and stereo) and content types sys2, sys4 and sys8 are the best or not different from the best for many bitrates (mono and

stereo) and content types

3.1.2 SAOC 1400-1800

CE: Separation of real-environment signalsOsamu Shimada, NEC, made short presentation that reminder the Audio experts the framework for and meaning of test1 and test2 in this core experiment.Jeongil Seo, ETRI, presented the test1 results inm15572 Listening Test Report for CE on separating real-

environment signals into multiple objects from ETRIJeongil SeoSeungkwon BeackKyeongok Kang

Yang-Won Jung, LG, presented the test1 results in m15586 Listening test reports for CE on separating real-

environment signals Yang-Won JungHenney OhDong Soo KimSungyong Yoon

Leonid Terentiev , FhG, presented the test1 results in m15632 Listening test report for CE on separating real-

environment signals into multiple objects for the MPEG SAOC system

Leonid Terentiev Cornelia Falch Oliver Hellmuth Johannes Hilpert

The contribution showed that all listeners in Test1 had at best “no preference” and at worst “did not prefer” the proposed technology. There was considerable discussion on the slide which presented mean score for all listeners in Test 1. Osamu Shimada, NEC, presentedm15574 Listening test results of Test 1 for SAOC CE on

separating real-environment signals into multiple objectsOsamu ShimadaToshiyuki NomuraAkihiko SugiyamaOsamu Hoshuyama

The set of contributions were discussed. The Chair noted that averaging over listener responses may obscure the individual’s intent rather than minimize the noise in the listener responses. It was decided that a break-out group will consider how best to interpret the data we have at this meeting and report back later in the week.

4 Plenary presentationsThe Chair reviewed the Liaison documents and reviewed initial drafts of responsesThe Chair reviewed the current and target location of Audio reference software, as shown in the following table:Code Modules Responsible Party Target LocationMPEG-1MPEG-2MPEG-4

FhG FhG CVS server

ALS LG SVN serverSLS I2R SVN serverMPEG Surround Dolby/FhG/Philips FhG CVS serverSAOC FhG FhG CVS serverMPEG-7 FhG IDMT SVN server

141

The Chair presented documents m15688 and m15689 on MXM to the Audio Subgroup members.The Chair discussed the issue of ER bistream syntax specification (as in ER AAC-LD) versus reference code implementation. It was decided that a task group of the Audio Chair, Ralph Sperschneider, FhG, and Markus Schnell, FhG, will investigate and report back.The Chair presented N9900, New Directions in Audio Standardization. Karlheinz Brandenburg, FhG, noted that before proceeding with any new standardization effort, MPEG should:

Confirm the need for the standard. For example, that it is truly responsive to the needs of identified customers.

Consider whether MPEG is the correct body for the standardization effort.

5 Task group activities5.1 Joint meetings and documents from other groups5.1.1 MPEG standards for Gaming

MPEG-4 media steams are compressed, which permits easy storage and, more importantly, easy transmission. On-line games offer MPEG an opportunity.The gaming industry does not embrace open standards, but does use defacto standards (e.g. PS3 or X-Box platforms). However, at the rendering level, 99 percent of games today use either OpenGL or DirectX. It was noted that what is needed is contacts to gaming industry, for example to learn to how audio is treated within the game engine and understand what needs the gaming industry might have.Game architecture can be roughly represented by the following flowchart:

Content → Game Engine → Rendering API (e.g. OpenGL, DirectX) → Drivers and presentationIt appears that HE-AAC or USAC streams for audio objects, which are rendered using with SAOC and MPEG Surround (including binaural rendering) could map onto this flowchart. As another example, MP3 technology in Flash might be extended to support SAOC / MPEG Surround. This may be particularly appropriate for simple PC-based network games.Gaming uses middleware to leverage their resources, particularly as a means to be portable across gaming platforms. This potential interface to standardized technology could represent an opportunityIn order to increase awareness of and contacts into the gaming industry audio experts might

Attend gaming conferences (are there such things)? Contact industry associations, e.g. Game Academy (in Berlin)

Finally, it would be a very beneficial exercise to construct a detailed block diagram of a specific networked gaming platform and map onto it possible MPEG audio technology.

5.1.2 Interactive Music AF, M15626

M15710 - RequirementsThe presentation emphasized that interactive music permits a very new user experience. For example, several mixes of a song could be presented. Interactivity options are represented via a graph concept and supports tracks (objects), volume, equalization, specialization. The main contribution is the notion of constraints on the user experience (i.e. possible mixes). There is strong support among artists for the concept of constraints, where such constraints can be

Constraints on tracks selected Constraints on volume of tracks or relative volume of tracks Constraints on equalization of tracks

There are three components of Interactive Music AF: Metadata Presets and Constraints Audio representation

142

Audio experts noted that SAOC could be an excellent coded representation for applications in which the audio information flows across a narrowband transmission channel (e.g. streaming to a mobile phone). Juergen Schmidt, Thomson, noted that MPEG-4 BIFS could be used to implement many of the mixing functionalities. The Systems Chair noted that BIFS does not have extensive support for the concept of saving and retrieving presets.The Audio Chair noted that there should be a requirement that the solution should be able to operate in a way that the audio information is retrieved via a relatively narrow-band communication channel.The Audio Chair noted that the current requirements are captured in N9840, MAF under considerations. These requirements, as augmented by contributions and contributions from this joint meeting, will be reviewed Friday at 11:30 in the Requirements room.M15626 – MAF under consideration. Inseon Jang, ETRI, presented the technical details of the Interactive Music AF. The AF used a specialization of the MPEG-4 FF with two new boxes: Preset Container Box and Preset Box. The AF FF has the brand “im01.” The Preset Box contains the mix information associated with the relevant tracks. The presentation further explained how the metadata is to be stored in the MPEG-4 File.

5.1.3 Proposed Audio profiles for ALS, SLS

Ralf Geiger, FhG, presented the proposed profile for SLS. The consensus of the experts in the joint meeting was to incorporate the profile definition into PDAM to MPEG-4 Audio. Takehiro Moriya, NTT, presented the proposed profile for SLS. The consensus of the experts in the joint meeting was to incorporate the profile definition into a WD of an amendment to MPEG-4 Audio. The Audio and Requirements Chairs requested that at next MPEG meeting there be available

Some positive statement or feedback from ARIB concerning intent to adopt this profile The contact names of business unit persons at companies that intend to adopt the profile Ideas for a profile name

5.2 Task Group discussions5.2.1 MPEG-2 and MPEG-4 audio, conformance, reference software

MPEG-2 and MPEG-4New ProfilesTakehiro Moriya, NTT, presentedm15660 Proposal for MPEG-4 ALS profile/levels Takehiro Moriya

Tilman LiebchenYasushige NakayamaToshiyuki NomuraNoboru HaradaYutaka Kamamoto

This proposes a profile that incorporates a limited set of tools from the ALS specification. A set of levels is defined that addresses scoping of complexity. A figure was presented that motivates the selected set of tools and limitations based on the compression/complexity tradeoff. Complexity figures were based on an ARM9 fixed-point platform and the presenter noted that BGMC coding was division intensive such that it is quite expensive on a fixed-point.There was considerable discussion. Tilman Liebchen, LG, assured that ARIB is seriously moving ahead with this service. The Chair noted that ARIB’s interest would be limited to Level 1 and suggested at this time to limit the proposed profile to include only that level. Yuriy Reznik, Qualcomm suggested that a liaison could be sent to IFPI requesting information on interest in other levels for this profile (e.g. for portable player or consumer music archives).It was the consensus of the group to draft an output document and to review it with the Requirements group. Given a favourable review, this will be issued as a Working Draft of a new amendment to 14496-3.

143

Yuriy Reznik, Qualcomm, presentedm15715 Comment on proposal for MPEG-4 ALS profiles/levels Yuriy Reznik

This contribution noted that the complexity figures in the previous contribution, m15660, appear to be inconsistent with those in N7686, “Verification Report on MPEG-4 ALS.” These differences will be resolved in a task group that will report back to the Audio Subgroup.Ralf Geiger, FhG, presentedm15628 Proposed new profile for MPEG-4 SLS Ralf Geiger

Ralph SperschneiderVirgilio Bacigalupo

This contribution requests the creation of a new profile “HD-AAC” that includes the MPEG-4 AAC-LC and SLS audio object types and supports up to two channels, 96 kHz sampling rate and 24 bit word length. The tools in the SLS audio object type were restricted to exclude CBAC. Eunmi Oh, Samsung, questioned the complexity figures provided by FhG to motivate exclusion of the CBAC tools and indicated that Samsung internal results are different. The Chair requested that FhG make available to the group its complexity data and that, if possible, Samsung make available to the group its complexity data. The Chair proposes that the profile definition, as in the contribution, be reviewed by Requirements. However, a consensus position in the Audio Subgroup on the complexity figures that motivate the tool exclusion must be reached prior to inclusion of the profile into a Working Draft of a new amendment to 14496-3. DiscussionAfter some discussion in closing Audio plenary, it was determined that if both ALS and SLS profiles issue as WD at this meeting, they will progress to FDAM at the 89th meeting and the progressing to PDAM at this meeting does not advance the FDAM date. It is the understanding of the Audio Subgroup experts that additional information on the performance of CBAC will be available at the 86th meeting and the issue of whether or not this tool is included in the proposed SLS profile will be resolved at that meeting.CorrigendumRalf Geiger, FhG, presentedm15629 Proposed Corrigendum on MPEG-4 SLS Ralf Geiger

Ralph SperschneiderVirgilio Bacigalupo

This document requests technical changes: Change coding of lle_ics_length in the text to conform to coding of lle_ics_length as in

the reference software. Change the function of read_bits() in the reference software so that it conforms to what is

stated in the text and change one conformance stream and decoded waveform.

Eunmi Oh, Samsung, noted that the proposed fix for read_bits() may not be actually correct. Samsung experts will review and get back to the group. The Chair suggested that, after further break-out work, the proposed DCOR text be brought forward for further review. Andreas Schneider, Dolby, presentedm15638 proposed correction to MPEG-2 SBR conformance Andreas Schneider

This contribution pointed that certain conformance data for MPEG-4 AAC (in which SBR is used) were corrected, but that the corresponding conformance data in MPEG-2 AAC were never corrected. It was the consensus of the Audio Subgroup to issue at this meeting a DCOR to MPEG-2 Conformance.Andreas Schneider, Dolby, presentedTm15640 proposed correction of the MPEG-4 HE AAC v2 profile Andreas Schneider

his contribution pointed out that mono and stereo mixdown elements are excluded from AAC and HE-AAC profiles but not HE-AAC V2 profile. It is proposed that this restriction be added to the V2 profile. It was the consensus of the Audio Subgroup to issue at this meeting a DCOR to MPEG-4 Audio.

144

Andreas Schneider, Dolby, presentedm15639 proposed clarification for MPEG-2 and MPEG-4 AAC Andreas Schneider

Karsten Linzmeier

The contribution proposes to align the MPEG-2 and MPEG-4 text with the reference software. It was the consensus of the Audio Subgroup to issue at this meeting a DCOR to MPEG-2 Audio and to add the correction for this issue to the DCOR to MPEG-4 Audio associated with the previous contribution.960/1024 block lengthAndreas Schneider, Dolby, presentedm15641 further considerations regarding the 960 transform length

in the AAC profile, the HE AAC profile and the HE AAC v2 profile

Andreas Schneider

The contribution reviewed the external specifications that use one block length or the other the reference source code available (or not available) for guiding implementers risk of leakage of content from block-length “island” to the other

Ralph Sperschneider, FhG, presentedm15645 Overhead consideration for an AAC decoder that supports

both frame lengths compared to an AAC decoder that supports only one frame length

Bernhard GrillMarc GayerMarkus MultrusJohannes HilpertRalph Sperschneider

The contribution gives an analysis of the relative complexity of implementing 1024 vs 960 block length AAC decoders.DiscussionThere are two alternatives:

1. Remove 960 block length from the AAC and HE-AAC profile.2. Keep the current profiles and request that manufacturers implement both block lengths.

This education effort must include enhancing conformance and reference software to support 960 block length.

Dave Singer, Apple, noted that the real goal is to minimize the confusion in the marketplace when DAB 960 block length content becomes available in the “Internet download” marketplace. Experts should investigate whether DAB bitstreams can be saved to an external storage device.After considerable discussion, all agreed that one way forward is:

Minimize the number of 960 block length bitstreams Maximize the number of new dual-block block length decoders

And that another way forward is: Restrict decoders to 1024 block lengths (960 for DAB and similar special applications) Educate 960 block length content producers that they must transocode to 1024 block

length in order to make content available outside their integrated systems.

Yasushige Nakayama, NHK, presentedm15598 Proposal of work plan for a 3D multichannel audio

configuration Yasushige Nakayama

This contribution notes external standards that specify mapping from audio channels to loudspeakers. It further presented relevant points from the draft technical broadcasting standard from ARIB (Japan), which include 22.2 channel broadcast using AAC or ALS coding technology. To support this initiative, NHK requests that MPEG extend AAC-LC to signal a mapping of up to 22.2 audio channels to the associated loudspeakers. In order for this to align with the ARIB schedule, they request FDIS by October 2009.Audio Chair noted that it would be most desirable to have a general audio channel to loudspeaker mapping, and that a BIFS scene might support such a channel mapping.Karlheinz Brandenburg, Fraunhofer Ilmenau, noted that there are many loudspeaker configuration that should be addressed, including:

145

5.1 7.2 16 channel (US theatres) 22.2 (NHK) Higher-order Ambisonics Wavefield synthesis

Juergen Schmidt, Thomson, made a presentation on how Audio BIFS might be used to address audio channel to output loudspeaker mappings. BIFS is a tree-based organization. The BIFS stream specifies the node tree and the mapping and further manages the connections from compressed stream to audio composition.A rather free-form set of notes from that presentation follows:

AudioChannnelConfig nodeLabels input channelsSee Channel Configuration Table in 14496-3Parametric channel oriented configuration

Generic format with no limitationsBIFS scene decoder can be unbounded in complexity. However profiles and levels can be used to limit complexity to be very low. This could use the following

Sound2D AudioChannelConfig AudioSource

Decoder instancesVery simple BIFS decoderSee Abv3_Aac06a.txt BIFS conformance dataWay forwardDefine new profile and level to meet this application and keep bitrate and complexity low.Streaming format

Use MPEG-4 Systems Use “Carousell” to enable break-in

The Audio Chair noted that it would be appropriate to ask the Systems Chair if Laser can support 22.2 channel audio.It was decided to create an AhG mandate to continue this work, consisting of at least the following interested experts:

Jurgen Schmidt, ThomsonSchuyler Quackenbush, Audio Research LabsKarlheinz Brandenburg, Fraunhofer Ilmenau,Yasushige Nakayama, NHK Tilman Liebchen, LG

5.2.2 MPEG-4 AAC Enhanced Low Delay

Markus Schnell, FhG, presented a high-level overview ofm15637 Proposed ELD Verification Test Report Markus Schnell

The Chair indicated that he plans for a detailed presentation of the report results in closing plenary. The report was made available to all interested experts for a more careful review.Markus Schnell, FhG, presentedm15642 Update on Conformance for AAC-ELD Markus Schnell

This contribution proposes Correction of frame length flag in one conformance data file (frame length is signalled as

512, but is actually 480) New naming convention for existing AAC-LD conformance data

And also proposed to create new conformance data files for the 480 frame lengthIt was the consensus of the Audio Subgroup to

146

Issue the renaming corrections for AAC-LD as a DCOR Issue the remaining propoals as a Study on ISO/IEC 14496-4:2004/FDAM XX, AAC-

ELD, OAFI and additional AAC Conformance

5.2.3 MPEG-D SAOC

Yang-Won Jung, LG, presentedm15588 Comments on SAOC operation modes and module Yang-Won Jung

Henney Oh

This contribution notes that there a number of “missing” modes in SAOC operation, and presents a table summarizing the currently supported modes and the proposed “missing” modes. Discussion was deferred until after the next presentation.Oliver Hellmuth, FhG. presentedm15634 Proposal for adoption of additional downmix / upmix

scenarios for the MPEG SAOC systemhel @ iis.fraunhofer.dehlp @ iis.fraunhofer.demun @ iis.fraunhofer.defch @ iis.fraunhofer.detev @ iis.fraunhofer.deheiko.purnhagen @ dolby.comJENGD @ dolby.comjeroen.koppens @ philips.com

This contribution proposes adding the same modes to SAOC as was proposed in the previous contribution. A mathematical description of the SAOC processing for the missing modes was presented. Furthermore, it proposes to explicitly describe how a SAOC decoder can be connected to a MPEG Surround decoder by means of a stream of unquantized parameters. Listening test data was presented that show that two of the missing modes implemented via an SAOC decoder operate as well as the implementation of SAOC transcoder plus MPEG Surround decoder. All modes except stereo to binaural have software implementation.It was the consensus of the Audio Subgroup that all modes except stereo to binaural processing be incorporated into the CD text. Also, that the text describing how a SAOC decoder can be connected to a MPEG Surround decoder by means of a stream of unquantized parameters be incorporated into the CD text.Leonid Terentiev, FhG, presentedm15636 Proposal for the file-based storage of rendering

information for the MPEG SAOC systemJonas EngdegårdLeonid TerentievCornelia FalchOliver HellmuthJohannes Hilpert

The contribution presents a format for storing and retrieving the rendering information. It was the consensus of the Audio Subgroup to incorporate this text into the SAOC CD text.Osamu Shimada, NEC, presentedm15576 A Proposal on preset functionality for teleconferencing

applicationOsamu ShimadaKeisuke MasatokiToshiyuki NomuraAkihiko SugiyamaOsamu HoshuyamaHiroshi Saruwatari

This contribution proposes to derive lateralization from the “cross-talk” of participants in a multi-microphone teleconferencing setting. It proposes that presets should be dynamic in time and frequency. This permits the decoder to reconstruct the original microphone signals, but still enable manipulation of the actual objects.The Audio Subgroup welcomes additional information at the next meeting.Leonid Terentiev, FhG, presentedm15633 Additional information on the mono downmix mode for the

enhanced Karaoke / Solo processing for the MPEG SAOC system

Leonid TerentievCornelia FalchOliver HellmuthJohannes Hilpert

FhG will be able to provide processed signals for informal listening. The Chair suggested that this topic be brought up again Thursday afternoon of the MPEG week. Heiko Purnhagen, Dolby, presented

147

m15635 Report on corrections for the MPEG SAOC CD text Leonid TerentievCornelia FalchOliver HellmuthJohannes HilpertHeiko PurnhagenJonas EngdegårdJeroen Koppens

This contribution presents Editorial corrections to the SAOC CD text. Minor technical “bug-fixes” to the CD text. New syntax text that clearly indicates that meta-data strings can be UTF-8 byte strings. Proposed solution for instability in SAOC processing noted at the 84th Meeting.

It was the consensus of the Audio Subgroup to adopt all aspects of the contribution into the SAOC CD text.Yang-Won Jung, LGE, presentedm15587 Proposed syntax revision for redundancy reduction in

SAOCYang-Won JungHenney Oh

The contribution proposes syntax revisions that reduce the number of required bits in the SAOC audioSpecificConfig() header. Heiko Purnhagen, Dolby, noted that the proposed syntax was too restrictive and could not support the flexibility in the SAOC CD text. He agreed to draft alternate syntax text that captures the improvement in coding efficiency. This would include an example of bitrate savings in a typical application. No decision on this contribution is made at this time, but the topic will be revisited when the group reviewed the text from Dolby.After subsequent discussion, it was the consensus of the Audio Subgroup to adopt the technology as it was in the presentation to the Audio Subgroup. Jeongil Seo, ETRI, presentedm15592 Proposal for support of the additional downmix by MPEG

SAOCJeongil SeoSeungkwon BeackKyeongok KangKwangki Kim

The proposal shows how to adapt the artistic downmix gain concept from MPEG Surround to SAOC for the purpose of using a “Mastered Mix” to drive a SAOC decoder. The concept is proposed to be a new core experiment. A break-out will discuss the proposal and report back. Osamu Shimada, NEC, presentedm15575 Listening test results of Test 2 for SAOC CE on

separating real-environment signals into multiple objectsOsamu ShimadaToshiyuki NomuraAkihiko SugiyamaOsamu Hoshuyama

5.2.4 MPEG-D Unified Speech and Audio

The Audio Chair presentedm15644 Draft Report on Unified Speech and Audio Coding Call for

Proposals SubmissionsSchuyler Quackenbush

He envisions that summary statements and figures capturing the consensus view of the outcome of the CfP listening tests be inserted into this framework, that listening test data be included in the zip archive and the document issues as an output. The Audio Chair presented the FNB commentm15551 FRNB comment on the Unified Speech and Audio Coding

Exploration ActivityPierrick Philippe on behalf of the FRNB

The Chair drafted response to this NB comment and this was presented and discussed. There was no consensus that it fully addressed the FNB comment. It was decided to address the issues raised as an AhG activity with the goal of fully addressing the concerns raised at the next MPEG meeting.The Audio Chair noted that the following KNB comment was presented in Wednesday plenary session.m15720 KNB comment on the Unified Speech and

Audio Coding Exploration ActivityJeong Ju Yoo on behalf of the KNB

148

The Chair drafted response to this NB comment and this was discussed and accepted by representatives of the Korean National Body, based largely on the text in the Report on Unified Speech and Audio Coding Call for Proposals Submissions.The Audio Chair presented a version of the Report on Unified Speech and Audio Coding Call for Proposals Submissions that contained an analysis of the subjective data and an identification of the RM0 technology. As a first action in the RM process, a possible merge of sys2 and sys4 technology into sys10 will be investigated. After considerable discussion on key paragraphs in this document, a final version was achieved that gained the consensus approval of the Audio Subgroup. Discussions in final plenaryThe Audio Chair presented text that described a process that audio experts could use to develop a reference-quality USAC Reference Source Code encoder. Schuyler Quackenbush, Audio Research Labs, expressed the following point of view on this topic:

At the 86th MPEG meeting the following reference source code will be available for the Unified Speech and Audio Coding work:

Normative reference source code for the decoding process. Informative reference source code for the encoding process. Encoder source code

need only produce a bitstream that is consistent with the normative decoder bitstream syntax.

Subsequent to the 86th meeting, audio experts can use the encoder source as a foundation for an open and cooperative software development project in which source code modules from HE-AAC V2, AMR-WB+ and RM0 normative decoder source code are incorporated into the Encoder reference source code.Typically, in current practice, CE modules under test are incorporated into the RM0 proponent encoder via object-modules conforming to an agreed-upon API. The process outlined above for creating USAC encoder reference software can result in the USAC reference software encoder being as good as or better than the RM0 proponent encoder.

Experts from Huawei, Ericsson, Nokia, LG, France Telecom R&D, Qualcomm and Polycom, expressed the following point of view on this topic:

In order to facilitate the integration of relevant technologies in Core experiments, they should be conducted on a single reference source code for both encoder and decoder that is made available for each interested party in the MPEG audio subgroup. This reference code should be of sufficient quality and available before the start of the core experiment process. The encoder code should have the following characteristics: Part of the encoder code should be made available (e,.g. signal path, MDCT, CELP

parts) Parts which are felts sensitive by the proponents of the RM0 could be delivered as

libraries with the appropriate API and kept up to date with the latest Reference Model. The binary modules could be replaced by source code if felt appropriate.

The Audio Chair notes that there are WG11 documents that define the CE process and hence CE work can commence at the 86th meeting.

6 Meeting deliverables

7 Responses to Liaison and NB commentsThe responses to Liaison and NB comments were prepared and approved.

7.1 Recommendations for final plenaryThe Audio recommendations were presented and approved.

149

7.2 Establishment of Ad-hoc GroupsThe following ad-hoc groups were established by the Audio subgroup:

No. Title Mtg10053 AHG on Audio Standards Maintenance No10054 AHG on Unified Speech and Audio Coding and SAOC Yes

7.3 Approval of output documentsAll output documents, shown in Annex D, were presented in Audio plenary and were approved.

7.4 Press statementThe Audio contribution to the press statement was reviewed and approved via email.

8 Future activities8.1 Schedule of future meetingsAd Hoc group meetings are indicated in Section 7.2. Unless otherwise indicated, Ad Hoc group meetings will be held at the location of the next MPEG meeting on the weekend preceding that meeting.

8.2 Agenda for next meetingThe agenda for the next MPEG meeting is shown in Annex E.

8.3 All other businessThere was none.

8.4 Closing of the meeting The 85th Audio Subgroup meeting was adjourned Friday at 14:00. Run to lunch!

150

Annex A Participants

First Name Last Name Country AffiliationVirgilio Bacigalupo Germany Fraunhofer IISJohannes Boehm DE ThomsonTi Eu Chan SG I2RSascha Disch Germany Leibniz University HanoverBernd Edler DE University of HannoverRoni Even IL PolycomQi Fengyan Germany Huawei TechnologiesLouis Fielder USA Dolby LabsRalf Geiger DE Fraunhofer IISPhilippe Gournay Canada VoiceAge Corp. / Univ. of SherbrookeBernhard Grill DE Fraunhofer IISOliver Hellmuth DE Fraunhofer IISJin Woo Hong KR ETRIHaibin Huang SG I2RYang-Won Jung KR LG ElectronicsKyeong Ok Kang Korea ETRIFlorian Keiler Germany ThomsonKei Kikuiri JP NTT DOCOMODong Soo Kim KR LG ElectronicsJunghoe Kim KR Samsung AITKristofer Kjörling SE DolbyTaejin Lee KR ETRIRoch Lefebvre Canada VoiceAge Corp. / Univ. of SherbrookeTerentiev Leonid DE Fraunhofer IISTe Li SG I2RTilman Liebchen DE LG ElectronicsTakehiro Moriya JP NTTMarkus Multrus DE Fraunhofer IISFrederik Nagel Germany Fraunhofer IISYasushige Nakayama JP NHKMax Neuendorf Germany Fraunhofer IISToshiyuki Nomura JP NECTakeshi Norimatsu JP PanasonicEunmi Oh KR SamsungHenney Oh KR LG ElectronicsWerner Oomen NL Philips Applied TechnologiesHee-Suk Pang KR Sejong UniversityHochong Park KR Kwangwoon UniversityYoung-cheol Park KR Yonsei UniversityPierrick Philippe FR France Telecom R&DHeiko Purnhagen SE DolbySchuyler Quackenbush USA ARLYuriy Reznik USA QualcommRedwan Salami Canada VoiceAge Corporation

151

Andreas Schneider DE DolbyMarkus Schnell DE Fraunhofer IISStephan Schreiner Germany Fraunhofer IISGerald Schuller Germany Fraunhofer IDMTJeongil Seo KR ETRIOsamu Shimada JP NECRalph Sperschneider DE Fraunhofer IISAkihiko Sugiyama JP NECHerve Taddei DE Huawei TechnologiesAnisse Taleb SE Ericsson ABTai Hou Tng Singapore Institute for Infocomm ResearchDavid Virette FR France Telecom R&DOliver Wuebbolt DE ThomsonSungyong Yoon KR LG ElectronicsHuan Zhou SG Panasonic Singapore LaboratoriesYongwei Zhu Singapore Institute for Infcomm Resarch

152

Annex B Audio Contributions and Schedule

Day / Time Task GroupSunday0900-1500 AhG: Unified Speech and Audio Codingm15545 Speech and Audio listening test lab report from Dolby Kristofer Kjörling

m15618 Speech and Audio listening test lab report (Ericsson) Anisse Taleb

m15570 Unified speech and audio coding listening test report from ETRI Taejin Lee

m15678 Audio Report on the subjective testing of Unified Speech and Audio Coding proposals at Huawei

Seungkwon Beack

m15655 France Telecom listening test results for the CfP on Unified Speech and Audio Coding

Minje Kim

m15619 Report on USAC Subjective Tests at Fraunhofer IIS Test Site Kyeongok Kang

m15581 Report on the USAC listening test at LGE Lijing Xu

m15548 Speech and Audio listening test lab report from Philips Herve Taddei

m15567 Listening test results for Unified Speech and Audio Coding from Samsung Pierrick Philippe

m15565 Speech & Audio - Listening Test, Report & Results - Thomson David Virette

m15608 Report on USAC subjective tests at VoiceAge test site Markus Multrus

m15547 Technical description of the Dolby Philips proposal for the speech and audio work- item

Ralf Geiger

m15568 Technical description of the ETRI proposal for the unified speech and audio coding

Dong Soo Kim

m15621 Technical Decsription of the Fraunhofer IIS Submission for the CfP on USAC Sungyong Yoon

m15582 LGE submission to Unified Speech & Audio Coding Jaehyun Lim

m15564 Response to CfP on unified speech and audio coding Hyun-Kook Lee

m15566 Speech & Audio - Description of Technology of the Thomson proposal Henney Oh

m15609 Technical Description of the VoiceAge Candidate for USAC Yang-Won Jung

1200-1300 Lunch Werner Oomen

m15546 Analysis of speech and audio listening test data Jeroen Koppens

m15613 Analysis of unified speech and audio coding listening test results Eunmi Oh

m15656 France Telecom contribution to the analysis of the listening test results following the CfP on Unified Speech and Audio Coding

Miyoung Kim

m15625 Analysis of USAC Listening Test Data JungHoe Kim

m15610 Analysis of Combined Listening Test Results for USAC Johannes Boehm

m15713 Audio USAC listenig test analysis from LGE Oliver Wuebbolt

1500-1700 AhG: SAOC Florian Keiler

m15572 Listening Test Report for CE on separating real-environment signals into multiple objects from ETRI

Roch Lefebvre

m15632 Listening test report for CE on separating real-environment signals into multiple objects for the MPEG SAOC system

Kristofer Kjörling

m15586 Listening test reports for CE on separating real-environment signals Werner Oomen

m15574 Listening test results of Test 1 for SAOC CE on separating real-environment signals into multiple objects

Jonas Samuelsson

Review of AhG Report Lars Villemoes

m15500 Ad Hoc Group on Unified Speech and Audio Coding, SAOC and AAC-ELD Barbara Resch

1800- Chairs Meeting (K17) Erik Schuijers

Pontus Carlsson

153

Monday Taejin Lee

0900-1230 MPEG Plenary Seungkwon Beack

1300-1400 Lunch Minje Kim

1400-1430 Audio Plenary Kyeongok Kang

Welcome Hochong Park

Sunday Chairs meeting Youngcheol Park

Main topics for the week Markus Multrus

General Ralf Geiger

m15643 84th MPEG Audio Report Bernhard Grill

m15499 Ad Hoc Group on Audio Standards Maintenance Nikolaus Rettelbach

m15500 Ad Hoc Group on Unified Speech and Audio Coding, SAOC and AAC-ELD Max Neuendorf

1430-1700 Plenary Activities Dong Soo Kim

USAC Sungyong Yoon

m15644 Draft Report on Unified Speech and Audio Coding Call for Proposals Submissions

Jaehyun Lim

m15551 FRNB comment on the Unified Speech and Audio Coding Exploration Activity Hyun-Kook Lee

Liaison Responses Eunmi Oh

Audio Reference SoftwareALS – FTP on TUBSLS – at I2R, move to SVNMPEG7 – FhG-IDMTMPS – FhGSAOC – FhG

JungHoe Kim

MXM (m15688, m15689) Miyoung Kim

DoC and Text on 14496-5:2001/FDAM 20 KiHyun Choo

ER (e.g. ER AAC-LD) bistream syntax specification vs reference code implementation

Hosang Sung

1630-1700 MPEG-4 ALS Florian Keiler

m15660 Proposal for MPEG-4 ALS profile/levels Oliver Wuebbolt

m15715 Comment on proposal for MPEG-4 ALS profiles/levels Johannes Boehm

1800- HoD Meeting Roch Lefebvre

Tuesday Werner Oomen

0900-1300 MPEG-2 and MPEG-4 Kristofer Kjörling

m15637 Proposed ELD Verification Test Report Heiko Purnhagen

m15628 Proposed new profile for MPEG-4 SLS Taejin Lee

m15629 Proposed Corrigendum on MPEG-4 SLS Seungkwon Beack

m15640 proposed correction of the MPEG-4 HE AAC v2 profile Minje Kim

m15638 proposed correction to MPEG-2 SBR conformance Kyeongok Kang

m15639 proposed clarification for MPEG-2 and MPEG-4 AAC Pierrick Philippe

m15642 Update on Conformance for AAC-ELD David Virette

m15588 Comments on SAOC operation modes and module Frederik Nagel

m15634 Proposal for adoption of additional downmix / upmix scenarios for the MPEG SAOC system

Ralf Geiger

154

1300-1400 Lunch Max Neuendorf

m15641 further considerations regarding the 960 transform length in the AAC profile, the HE AAC profile and the HE AAC v2 profile

Markus Multrus

m15645 Overhead consideration for an AAC decoder that supports both frame lengths compared to an AAC decoder that supports only one frame length

Roch Lefebvre

SAOC Dong Soo Kim

m15636 Proposal for the file-based storage of rendering information for the MPEG SAOC system

Sungyong Yoon

m15576 A Proposal on preset functionality for teleconferencing application

1900- Chairs Meeting (K17) Jeongil Seo

Seungkwon Beack

Wednesday Kyeongok Kang

0900-1100 MPEG Plenary Leonid Terentiev

1100-1200 Joint Meeting at PlenaryMPEG for Gaming

Cornelia Falch

1200-1300 MPEG-2 Oliver Hellmuth

m15598 Proposal of work plan for a 3D multichannel audio configuration Johannes Hilpert

1300-1400 Lunch Yang-Won Jung

1400 USAC Henney Oh

m15720 KNB comment on the Unified Speech and Audio Coding Exploration Activity

Dong Soo Kim

1400-1600 SAOC Sungyong Yoon

m15633 Additional information on the mono downmix mode for the enhanced Karaoke / Solo processing for the MPEG SAOC system

Osamu Shimada

m15635 Report on corrections for the MPEG SAOC CD text Toshiyuki Nomura

m15587 Proposed syntax revision for redundancy reduction in SAOC Akihiko Sugiyama

m15592 Proposal for support of the additional downmix by MPEG SAOC Osamu Hoshuyama

1600-1700Joint Meeting at AudioInteractive Music AF m15710 (req), m15626 (tech)

1730-1830 Core Experiment framework for USAC S. Quackenbush, Eunmi Oh

1900 - Social (starts 19:30)

Thursday0900-1300 Task Group Activities

USAC1100-1130 Review of proposed ALS and SLS profiles

USAC1200-1300 Open issues in SAOC CEs

1300-1400 Lunch

1700-1730 Review of N9900 New Directions in Audio Standardization Schuyler Quackenbush

1500-1600 USAC output documents R. Sperschneider

Open issues in SAOC CEs S. Quackenbush, Eunmi

155

Ohm15575 Listening test results of Test 2 for SAOC CE on separating real-environment

signals into multiple objects

1800- Chairs Meeting Schuyler Quackenbush

Pierrick Philippe on behalf of the FRNB

Friday0900-1300 Audio plenary

Remarks on Thursday Chairs meetingRecommendations for final plenaryEstablishment of new Ad-hoc groupsAhG MandatesGet document numbers Takehiro Moriya

1000 Approve Responses to NB comments and Liaison Tilman Liebchen

1030 Approval of output documents Yasushige Nakayama

Review of Audio presentation to MPEG plenary Toshiyuki Nomura

Agenda for next meeting Noboru Harada

A.O.B. Yutaka Kamamoto

Closing of the Audio meeting Yuriy Reznik

1300-1400 Lunch1400- MPEG Plenary

156

Annex C Task Groups

1. MPEG-2 and MPEG-4 audio, conformance, reference software2. MPEG-4 AAC-ELD Verification Test Report3. MPEG-D SAOC4. MPEG-D Unified Speech and Audio Coding

157

Annex D Output DocumentsNo. Title TBP Available

13818-4 Conformance testing10030 ISO/IEC 13818-4:2004/Amd 2:2005/DCOR 2, AAC Conformance No 08/07/25No. Title TBP Available

13818-7 Advanced Audio Coding10031 ISO/IEC 13818-7:2006/DCOR 1, AAC No 08/07/25No. Title TBP Available

14496-3 Audio10032 Report on the Verification Test of MPEG-4 AAC-ELD YES 08/07/2510033 WD on New Profiles for ALS and SLS No 08/07/2510034 ISO/IEC 14496-3:2005/DCOR 6, AAC No 08/07/25

10035 ISO/IEC 14496-3:2005/AMD 2:2006/DCOR 4, HE-AAC V2 Profile

No 08/07/25

10036 ISO/IEC 14496-3:2005/AMD 3:2006/DCOR 2, SLS No 08/07/2510037 ISO/IEC 14496-3:2005/AMD 9:2008/DCOR 1, AAC-ELD No 08/07/25

10038 Considerations regarding the 960 frame length in the MPEG-4 AAC family of profiles

No 08/07/25

No. Title TBP Available14496-4 Conformance testing

10039 ISO/IEC 14496-4:2004/DCOR 6, AAC-LD No 08/07/25

10040 Study on ISO/IEC 14496-4:2004/PDAM 36, AAC-ELD, OAFI and additional AAC Conformance

No 08/07/25

10041 Proposed ISO/IEC 14496-26, Audio Conformance No 08/07/25

10042 ISO/IEC 14496-4:2004/AMD13:200x/DCOR 2, AAC-LD bitstreams

No 08/07/25

No. Title TBP Available14496-5 Reference Software

10043 DoC on ISO/IEC 14496-5:2001/FPDAM 20, MPEG-1 and -2 on MPEG-4

No 08/07/25

10044 ISO/IEC 14496-5:2001/FDAM 20, MPEG-1 and -2 on MPEG-4 No 08/09/12No. Title TBP Available

23003-2 SAOC10045 Study on ISO/IEC CD 23003-2:200x, Spatial Audio Object Coding No 08/08/1510046 Status and Workplan on SAOC Core Experiments No 08/07/25No. Title TBP Available

23003-3 Unified Speech and Audio Coding10047 Report on Unified Speech and Audio Coding Call for Proposals No 08/07/25No. Title TBP Available

Liaison Statements10049 Liaison response to ITU-T SG 16 (m15261, m15516) No 08/07/2510050 Liaison response to IEC TC 100 (m15555) No 08/07/25No. Title TBP Available

Responses to National Bodies10051 Response to FNB (m15720) No 08/07/2510052 Response to KNB (m15551) No 08/07/25

158

Annex E Agenda for the 86th MPEG Audio Meeting

Agenda Item1. Opening of the meeting2. Administrative matters

2.1. Communications from the Chair2.2. Approval of agenda and allocation of contributions2.3. Review of task groups and mandates2.4. Approval of previous meeting report2.5. Review of AhG reports 2.6. Joint meetings2.7. Received national body comments and liaison matters

3. Plenary issues4. Task group activities

4.1. Spatial Audio Object Coding4.2. Unified Speech and Audio Coding4.3. MPEG Maintenance, including MPEG-1, MPEG-2, MPEG-4, SMR and MPEG

Surround issues5. Discussion of unallocated contributions6. Meeting deliverables

6.1. Responses to Liaison and NB comments6.2. Recommendations for final plenary6.3. Establishment of new Ad-hoc groups6.4. Approval of output documents6.5. Press statement

7. Future activities8. Agenda for next meeting9. A.O.B10. Closing of the meeting

159

Annex J – 3DG report

Source: Marius Preda (Institut TELECOM)

3DGC meeting reportHannover, July, 2008

1 Opening of the meeting

1.1 Approval of the agendaThe agenda is approved.

1.2 Goals for the weekThe goals of this week are: Review SC-3DMC contributions and issue the associated WD (2.0) and CE Discuss the software status for SC-3DMC Review the votes Discuss FAMC RefSoftware and Conformance Compile and test reference software Check the validity and re-generate when necessary conformance data for 3DGC Investigate future developments of MPEG 3D Graphics Compression

1.3 Standards from 3DGC

Std Pt Edit Project Description CfP WDCD/

PDAMFCD/

FPDAMFDIS/FDAM

4 4 2004 Amd.32 FAMC conformance

07/04 07/10 08/04 08/10

4 4 2004 Amd.33 Multiresolution profile conformance

07/04 07/10 08/07 09/01

4 4 2004 Amd.34 3DGC Model Conformance

08/01 08/07 09/01

4 4 Amd.39 Scene partitioning Conformance

4 5 2001 Amd.21 FAMC reference software

07/04 07/10 08/04 08/10

4 5 2001 Amd.22 3DG Compr. Model RefSof

06/07 08/01 08/07 09/01

4 5 Amd.25 Scene partitioning Reference software

4 11 2005 Amd.6 Scene partitioning 08/01 08/04 08/104 16 2006 Amd.2 FAMC 07/07 08/01 08/07

160

Std Pt Edit Project Description CfP WDCD/

PDAMFCD/

FPDAMFDIS/FDAM

4 16 2006 2nd Ed./Cor.2

Node code table 08/07 09/01

4 16 2006 Amd.4 Scalable Complexity 3D Mesh Compression

08/01 08/10 09/01 09/07

4 16 200x 3rd Ed. AFX 07/10 09/01Delayed to

include the COR

4 25 200x 1st Ed. 3D Graphics Compression model

07/04 07/10 08/04 08/10

1.4 Room allocation3DGC: K17

161

1.5 Allocation of contributionsN° Title Schedule ActivityD1 Monday D1

MPEG Plenary D1 09:00~11:30

MPEG General

Lunch Break D1 13:00~14:00

3DG Plenary D1 14:00~15:30

3DG General

Roll call, Agenda, Goals, FAQ, etc., Marius PredaStatus of www.mpeg-3dgc.com Patrick Gioia

m15498 Report of AHG on 3DGC documents, experiments and software maintenance

Patrick Gioia, Francisco Moran

Validation session for the RefSoft and test data set

Francisco Moran

Validation session for the conformance data set Marius Preda

Results of voting- ISO/IEC 14496-16:2006/FPDAM 2: (approved).

Marius Preda

Coffee Break 15:30~16:00

3DG Plenary 16:00 – 18:00

m15441 Reference software of OctreeImage and PointTexture

Jeong-Hwan AhnShinjun LeeGyeongJa Jang

m15683 Encoder implementation for FAMC Khaled Mamou

162

N° Title Schedule ActivityTitus Zaharia Marius Preda Francoise Prêteux

m15691Source code for WaveletSubdivisionSurfaces and Footprint-Based Coding

Patrick GioiaJérôme Royan

MPEG-V and impact on group activities Marius PredaMXM and impact on group activities Marius Preda

D2 Tuesday D2Scalable Complexity 3D Mesh Encoding (SC-3DMC)- review of the contributions

D2 09:00~12:00

m15669 A Proposal on Quantization of 3D Mesh Coding

Seungwook LeeBonki KooByungjun KimEuee S. Jang

09:00-09:30

m15654 Update of the API for 3D compression benchmark with MyMultimediaWorld.com

Benoit le BonhommeMarius PredaFrancoise Prêteux

9:30-10:00

Joint meeting on MXM and MPEG-V (Systems room) 10:00 – 11:30

m15654 Update of the API for 3D compression benchmark with MyMultimediaWorld.com (continuation of discussion)

Benoit le BonhommeMarius PredaFrancoise

11:30-12:00

163

PrêteuxLunch Break D2 12:00~14:00Scalable Complexity 3D Mesh Encoding (SC-3DMC) D2 14:00~18:00

m15653 TFAN software description

Khaled MamouTitus ZahariaMarius PredaFrancoise Prêteux

14:00-14:30

m15667 CE Report on the SC3DMC

Seungwook LeeBonki KooDaiyong KimEuee S. Jang

14:30-15:30

Coffee Break 15:30~16:00

m15668 Editorial and Technical Comments on Working Draft of SC3DMC

Seungwook LeeBonki KooKyoungsoo SonEuee S. Jang

16:00-18:00

Fixes on the reference software Francisco Moran

D3 Wednesday D3MPEG Plenary D3 09:00~11:00Gaming (joint with all MPEG) 11:00~12:00

Lunch Break D3 13:00~14:00MXM Architecture and API Filippo

Chiariglione 14:00 – 15:40Coffee Break 15:40~16:00AFX Amd.4 16:00 – 16:30

164

SC-3DMC Editing Seungwook LeeP25 Jeong-Hwan 16:30~17:00P25 ref software status and conformanceAFX Amd.4 16:30~17:30SC-3DMC Editing Seungwook LeeMPEG-V 17:30~18:00Clarification on the interchange format between the virtual worlds Jean Gelissen

D4 Thursday D4AFX Reference Software 09:00~09:30Results on checking reference encoders 3DMC Daiyong Kim

Amd.4 SC-3DMC 09:30~10:30Edit of the CE SeungwookRefSoft and Conformance 10:30~11:30

Test the RefSoft on the test data Francisco Moran

Plan for the conformance data Marius PredaAmd.2 FAMC Marius Preda 11:30 – 12:00Part 16 AMD2 FAMC EditingLunch BreakP11 SP Patrick Gioia 15:00 – 15:10ISO/IEC 14496-11 AMD6Amd.3 MRZ Patrick Gioia 15:10 – 15:20MRZ Conformance P16 Marius Preda3rd Edition4 weeks editing period 15:20 – 15:30

SC-3DMC Editing WD2.0OK editor notes added for what is still to be done Seungwook 15:30 – 16:30

165

P16 Cor1 Marius Preda 16:30 – 16: 45ISO/IEC 14496-16 2nd Ed. Amd.1 Cor.2 P25 Marius Preda3DGCM Conformance Editing3DGCM RefSoft Editing

D5 Friday D53DG output documents preparation D4 09:00~12:00 3DG General

AhGs and resolutions all

Lunch Break D5 12:00~14:00

MPEG Plenary D5 14:00~ MPEG General

166

1.6 Attendance listName Country CompanyMarius Preda France Institut TELECOMPatrick Gioia France OrangeLabsFrancisco Morán Burgos Spain UPMKarsten Muller Germany FHG-HHISeung Wook Lee Korea ETRIEuee S. Jang Korea Hanyang Univ.Byoungjun Kim Korea Hanyang Univ.Mingxiao Chen Korea Hanyang Univ.Itaru Kaneko JapanJeong-Hwan Ahn Korea SamsungNikolce Stefanoski Germany University of Hannover

2 General issues

2.1 General discussion

2.1.1 Reference SoftwareIt is recalled that the source code of both decoder AND encoder should be provided as part of the Reference Software for all technologies to be adopted in MPEG standards. Moreover, not providing the complete software for a published technology shall conduct to the removal of the corresponding technical specification from the standard.

2.1.2 Web siteOrangeLabs proposed a new version of the web site, now available at www.mpeg-3dgc.com. The goal of the web site is to disseminate the group activities (documents, software and demonstration), to maintain the FAQ and to be active in providing answers through the use of the Forum. 3DGC contributors are kindly asked to check the web-site and provide comments.

3 AFX (14496-16) related activities

3.1 Scalable Complexity 3D Mesh Compression (14496-16 Amd.4)

Title A Proposal on Quantization of 3D Mesh CodingAuthors Seungwook Lee, Bonki Koo, Byungjun Kim, Euee S. Jang

Summary Quantization algorithm described in 3DMC specification is different from the one implemented in IM1. In addition the inverse quantization equations described in the 3DMC specification is wrong. This contribution recommends using the algorithm described in the textual document, to change IM1 accordingly and to correct the

167

equations. The contribution also contains the corrected version of the reference software.

Resolution

Resolution: accepted.The corrections for 3DMC specification are integrated in the current Cor.2 of 14496-16:2006/Amd.D1. Update the proposed software on the SVN.

Title Update of the API for 3D compression benchmark with MyMultimediaWorld.com

Authors Benoit le Bonhomme, Marius Preda, Francoise Prêteux

Summary

A new version of the API is proposed in order to easy the use of MMW.com. The encoding parameters can be set in a textual file, that will be provided together with the encoder. The performances issues were discussed and libraries are compiled in Release mode

Resolution

Accepted. The new API will be used in the rest of experiments on SC-3DMC

Title TFAN software descriptionAuthors Khaled Mamou, Titus Zaharia, Marius Preda, Françoise Prêteux

SummaryThe contribution presents the encoder and decoder classes and diagrams for TFAN. It is currently integrated in MMW.com benchmarking platform.

Resolution Accepted.

Title CE Report on the SC3DMCAuthors Seungwook Lee, Bonki Koo, Daiyong Kim, Euee S. Jang

Summary

The contribution presents a set of evaluation results for the following methods: SVA with Binary Arithmetic Coding, SVA with Arithmetic Coding, SVA with Binarization, Quantization Only. The results were obtained on an independent platform.

Resolution

Accepted. Action Point: Integrate the encoder and decoder for the four methods in MMW.com API.

3.1.1 Scene partitioning (14496-11 Amd.6)SP is followed as a joint activity between Systems and 3DGC. The technology is integrated in Part 11. There was no joint meeting with Systems on this topic during this meeting.SP activity on conformance and reference software is initiated.

3.2 Profiles (14496-16 AMD3)

Title MRZ Conformance Authors Patrick Gioia,

Summary No need to update the textual specification; need to update the files (delay due to bugs in the refsoft)

168

Resolution Generate the bitstreams by using the current RefSoft

3.3 Maintenance

3.3.1 Node TemplatesTitle Node Templates V7 and V8

Authors

Summary

Generating IM1 code and BIFS tables from node templates is not solved yet. For this version of the reference software BIFS table was produced by Mikael's scripts but the IM1 code was created manually

Resolution

1. Use GPAC for creating the node tables2. Update GPAC for being able to generate IM1 code

3.3.2 AFX 3rd EditionThe document was updated during the week. However, editing is not finished (an editing period of 4 weeks was accepted).

3.4 Dataset and benchmarking

For Scalable Complexity 3D Mesh Coding, the www.MyMultimediaWorld.com will be used for benchmarking.

3.5 Software

Title Reference software of OctreeImage and PointTextureAuthors Jeong-Hwan Ahn, Shinjun Lee, GyeongJa Jang

Summary Donation of encoders for OctreeImage and PointTexture

Resolution

- compilation of the software is validated- accept the two encoders for becoming Reference Software- commit the two modules on the SVN (mandate of the AhG)

Title Encoder implementation for FAMCAuthors Khaled Mamou, Titus Zaharia, Marius Preda, Francoise Prêteux

Summary Donation of encoders for FAMC

Resolution

- compilation of the software is validated- accept the encoder for becoming Reference Software- commit the software on the SVN (mandate of the AhG)

Title Source code for WaveletSubdivisionSurfaces and Footprint-Based Coding

Authors Patrick Gioia, Jérôme Royan

Summary Donation of encoders for WaveletSubdivisionSurfaces and Footprint-Based Coding

169

Resolution

- compilation of the software is validated- accept the encodesr for becoming Reference Software- commit the two modules on the SVN (mandate of the AhG)

Title Results on checking reference encoders 3DMCAuthors Daiyong Kim

Summary

3MDC correction was done in encoder and decoderFAMC Encoder was compiled and tested succesfulWSS encoder was compiledFootPrint Encoder was compiled

Resolution

Action Points:3DMC (similar for FAMC, WSS, FootPrint)1. Standalone version of the encoder to be committed in /MPEG-4/standalone/trunk/3D/AFX/3DMC-Encoder2. Standalone version of the decoder to be commited in /MPEG-4/standalone/trunk/3D/AFX/3DMC-Decoder3. Integrated version of the decoder to be commited in /MPEG-4/im1/trunk/IM1Decoders/AFX/3DMC4. Remove the 3DMC encoder from /MPEG-4/im1/trunk/IM1Decoders/AFX/3DMC5. Make the same correction in P25 (Encoder and Decoder)

Title Test the RefSoft on the test dataAuthors Francisco Moran

Summary

- encoders and players (debug and release) done- methods from NodeStub.cpp were commented- test files were regenerated (it lacks BBA, FootPrint, Shadow)

Resolution

Action Points:1. Francisco prepares the RefSoft2. Marius commits it on the SVN3. Commit corrections on the 3DMC (Daiyong)4. Khaled commits FAMC and the test files for FAMC5. Marius commits test files for BBA6. Patrick commits test files for FP

Title Plan for the conformance dataAuthors Marius Preda

Summary

Resolution

Action Points:- Create the Conformance directory on the SVN (Marius)- Create directories for each tool (Marius)- Each directory contains all the uncompressed files necessary to produce the bitstreams as well as the compressed files- Take all the conformance documents for AFX and check the status on each file- When files fail, initial providers are asked to regenerate them - Issue the corrigendum(s) for conformance

170

3.6 PromotionsTitle Special Session on 3D Graphics Compression in ICIP08

Authors Karsten Muller, Marius Preda

Summary A special session on 3D graphics compression will be organized in ICIP 2008.

Resolution -

3.6.1 Web SiteTitle Status of www.mpeg-3dgc.com

Authors Patrick Gioia

Summary The web site is in beta version but no improvement was done since the last meeting

Resolution

Action Point:Patrick Gioia will ask more actively contributions for demos from individual parties.

3.7 Future

3.7.1 MPEG-V - Information Exchange with Virtual Worlds (formally Metaverse)

Title MPEG-V and impact on group activitiesAuthors Marius Preda

Summary Informal discussion on possible impact of MPEG-V activities on technologies developed by 3DG group

Resolution

Action Point:Actively monitor and participate in setting the current documents for this standard (currently in a Requirements phase)

3.7.2 MXM

Title MXM and impact on group activitiesAuthors Marius Preda

Summary Informal discussion on possible impact of MXM activities on technologies developed by 3DG group

Resolution

Action Point:Actively participate in proposing a complete API for accessing 3D graphics tools.

Title MXM Architecture and APIAuthors Filippo Chiarliglione

Summary - presentation of the Chillout Project- review of the 3D API for MXM

Resolution

Action Point:Investigate on the JAVA wrapper for the MPEG-4 GT (JNA/JNI may be the solution)Update the API for supporting creating 3D graphics content.

171

3.7.3 Future of 3D Graphics CompressionNo discussion during the meeting in this issue

4 3D Graphics Compression Model (14496-25) activities

4.1 Textual specificationNo modifications.

4.2 Software and conformance

Title P25 ref software status and conformanceAuthors Jeong-Hwan Ahn

Summary FAMC encoder/decoder is included. Conformance document was updated to include FAMC and IC

Resolution

Action Points:Commit the MP25 on MPEG SVNIntegrate IC encode and decoderAdd the files for FAMC and IC in the conformance data set

5 Output documents and Resolutions of 3DGC

5.1 Part 4 Conformance testing

5.1.1 The 3DGC subgroup recommends approval of the following documentsNo. Title TBP Available

14496-4 Conformance testing10029 Text of ISO/IEC 14496-4:2004/FPDAM 33 (MultiResolution

Profile Conformance)No 08/07/25

10019 DOCR on ISO/IEC 14496-4:2004/PDAM 34 No 08/07/2510013 Text of ISO/IEC 14496-4:2004/FPDAM 34 (3DG Compression

Model Conformance)No 08/07/25

10014 Request for ISO/IEC 14496-4:2004/Amd.39 (Scene Partitioning Conformance)

No 08/07/25

5.2 Part 5 Reference Software

5.2.1 The 3DGC subgroup recommends approval of the following documentsNo. Title TBP Available

172

14496-5 Reference Software 10023 DOCR on ISO/IEC 14496-5:2001/PDAM 22 No 08/07/2510015 Text of ISO/IEC 14496-5:2001/FPDAM 22 (3DG Compression

Model Reference Software)No 08/07/25

10016 Request for ISO/IEC 14496-5:2001/Amd.25 (Scene Partitioning Reference Software)

No 08/07/25

5.3 Part 16 Animation Framework eXtension (AFX)

5.3.1 The 3DGC subgroup recommends approval of the following documentsNo. Title TBP Available

14496-16 Animation Framework eXtension (AFX)10017 Text of ISO/IEC 14496-16:2006/FDAM 2 (Frame based Animation

Mesh Compression)No 08/07/25

10018 Text of WD2.0 of ISO/IEC 14496-16:2006/Amd.4 (Scalable Complexity 3D Mesh Compression)

No 08/07/25

10020 Study Text of ISO/IEC 14496-16:2006/Amd.1:2007/COR2 No 08/07/2510021 WD4.0 of AFX 3rd Edition No 08/08/2510022 CE on Scalable Complexity 3D Mesh Coding No 08/07/25

5.4 Part 25 3D Graphics Compression Model

5.4.1 The 3DGC subgroup recommends approval of the following documentsNo. Title TBP Available

14496-25 3D Graphics Compression Model

5.5 Establishment of 3DGC Ad-Hoc Groups10060 AHG on 3DGC documents, software maintenance and core experimentsMandate: 1. Ensure the correct migration of the Reference Software on the SVN provided

by Elysium2. Coordinate 3DGC related conformance and reference software3. Maintain and edit 3DGC documents 4. Coordinate editing of the www.mpeg-3dgc.com web site 5. Conduct the experiments in Scalable Complexity Mesh Compression

Chairmen: Patrick GioiaFrancisco Morán Burgos

Duration: Until 86th MeetingMeetings Sunday before 86th meetingReflector: mpeg-3dgc AT gti. ssr. upm. esSubscribe: http://www.gti.ssr.upm.es/mailman/listinfo/mpeg-3dgc

6 Closing of the MeetingSee you in Busan.

173

174