1 · web view9419 doc on text of iso/iec fcd 29116-1 media streaming maf protocol 9420 text of...

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 N9331Shenzhen, CN – October 2007

Source: Leonardo Chiariglione Title: Report of 82nd meetingStatus

Report of 82nd meeting..........................................................................................................................1Annex A – Attendance list...................................................................................................................2Annex B – Agenda...............................................................................................................................3Annex C – Input contributions.............................................................................................................4Annex D – Output documents..............................................................................................................5Annex E – Systems report....................................................................................................................6Annex F – MDS report.........................................................................................................................7Annex G – Video report.......................................................................................................................8Annex H – JVT report..........................................................................................................................9Annex I – Audio report.......................................................................................................................10Annex J – 3DG report.........................................................................................................................11

Report of 82nd meeting

1 OpeningThe 82nd MPEG Meeting was hosted by Huawei Technologies Co., Ltd. on 22 – 26 October 2007 atMarco Polo Shenzhen Hotel, Shenzhen, China.

2 Roll call of participantsAnnex 1 gives the attendance list

3 Approval of agendaAnnex 2 gives the agenda adopted

4 Allocation of contributionsAnnex 3 Gives the list of documents submitted.

1

5 Communications from ConvenorThe Convenor announced that the sudden resignation of the Requirements chair, the closeness of completion of the MDS work program and the general need to optimise the use of meeting facilities required the streamlining of the working group organisation.For the 82nd meeting the following was implemented:

Old organisation New organisationRequirements Will be handled by the individual groupsSystems Will continue including MDS activitiesMDS Will transfer its remaining work program to SystemsVideo Will continue including Test and ISG activitiesJVT Will continueAudio Will continue3DG Will continueTest Will transfer its work program to VideoISG Will transfer its work program to VideoLiaisons Activities will be handled by the individual groups

6 Report of previous meeting This was approved

7 Processing of NB Position PapersNational Body documents were processed and responses provided where appropriate

8 Work plan management

8.1 Media coding

8.1.1 MPEG-4 Visual Simple Profile Level 6The following document was approved

9432 Text of ISO/IEC 14496-2:2004/FDAM4 Simple Profile Level 6

8.1.2 Simple Studio Profile Levels 5 and 6The following documents were approved

9434 Request for ISO/IEC 14496-2:2004/Amd.59435 Text of ISO/IEC 14496-2:2004/PDAM5 Simple Studio Profile Levels 5 and 6

8.1.3 MPEG-4 Audio 4th editionThe following document was approved

9500 ISO/IEC 14496-3:200x, Fourth Edition

8.1.4 AAC-ELDThe following documents were approved

2

9498 DoC on ISO/IEC 14496-3:2005/FPDAM 9, AAC-ELD9499 ISO/IEC 14496-3:2005/FDAM 9, AAC-ELD9502 Proposed Workplan on AAC-ELD Verification Test

8.1.5 Scalable Video CodingThe following documents were approved

9482 Draft Report on SVC Verification Tests 9483 SVC Verification Test Plan Version 2

8.1.6 Multiview Video CodingThe following documents were approved

9543 Requirements and Application Descriptions for MVC9445 Study Text of ISO/IEC 14496-10:200X/PDAM 1 Multiview Video Coding9446 Joint Multiview Video Model (JMVM) 69447 JMVM 6 Software

8.1.7 AFX 3rd editionThe following document was approved

9540 WD 1.0 of AFX 3rd Edition

8.1.8 Frame-based Animated Mesh compressionThe following document was approved

9535 Study Text of ISO/IEC 14496-16:2006/PDAM2 (Frame-based Animated Mesh Compression)

8.1.9 3D MultiResolution ProfileThe following document was approved

9536 Text of ISO/IEC 14496-16:2006/FPDAM3 (3D MultiResolution Profile)

8.1.10 Scene partitioningThe following documents were approved

9537 Request for amendment of ISO/IEC 14496-16:2006 (Scene Partitioning)

9538 WD1.0 of ISO/IEC 14496-16:2006 AMD 4 (Scene Partitioning)

3

8.1.11 Integer IDCT Accuracy TestingThe following documents were approved

9454 Disposition of Comments on ISO/IEC 23002-1/FPDAM19455 Text of ISO/IEC 23002-1/FDAM1 Software for Integer IDCT Accuracy Testing

8.1.12 Fixed point 8x8 DCT/IDCTThe following documents were approved

9456 Disposition of Comments on ISO/IEC FCD 23002-29457 Text of ISO/IEC FDIS 23002-2 Fixed-point 88 inverse discrete cosine transform and

discrete cosine transform

8.1.13 Video Tool LibraryThe following documents were approved

9458 Text of CD ISO/IEC 23002-4 Video Tool Library9459 Additional components of Video Tool Library Extensions v.1.09460 Description of Core Experiments in RVC9461 RVC Simulation Model (RSM) V6.09462 RVC Work Plan9463 RVC Conformance Testing Working Draft 3.09464 Description of Exploration Experiments in RVC9465 Methodologies for Video Toolbox Extension

8.1.14 Spatial Audio Object CodingThe following documents were approved

9517 WD on ISO/IEC 23003-2:200x, SAOC text and reference software9518 Status and Workplan on SAOC Core Experiments

8.1.15 Free Viewpoint TV codingThe following documents were approved

9466 Applications and Requirements of FTV9467 FTV Test Cases and Evaluation9468 Call for Contributions on FTV Test Material

8.1.16 Unified speech and audio codingThe following documents were approved

9519 Call for Proposals on Unified Speech and Audio Coding

9520 Draft Evaluation Guidelines for Speech and Audio Coding CfP

9521 Report on Evidence for Unified Speech and Audio Coding

4

9522 Workplan for Candidate Test Items

8.1.17 Representation of sensory effect informationThe following documents were approved

9426 Context and Objectives: Framework for Representation of Sensory Effects Information9427 Call for Requirements on Framework for Representation of Sensory Effects

Information

8.1.18 Post Production Deliverable FormatsThe following documents were approved

9428 Context and Objectives: MPEG Post Production Deliverable Formats9429 Draft Requirements for MPEG Post Production Deliverable Formats

8.1.19 Representation of Information exchanged between Virtual WorldsThe following documents were approved

9424 Context and Objectives : Information exchange with Virtual Worlds 9425 Proposal for a new work item – Information exchange with Virtual

Worlds

8.2 Composition coding

8.2.1 Lightweight Scene RepresentationThe following documents were approved

9383 DoC on ISO/IEC 14496-20/FPDAM 2 (SVGT1.2 Support)9384 Text of ISO/IEC 14496-20/FDAM 2 (SVGT1.2 Support)9385 Text of ISO/IEC 14496-20:200x/2nd Ed. (1st Ed. + Cor 1 + Amd.1 + Cor. 2)9386 IuC for LASeR

8.3 Description coding

8.3.1 New Visual Descriptions ExtensionsThe following documents were approved

9451 MPEG-7 Visual XM Document version 32.09452 Description of Core Experiments for MPEG-7 New Visual Extensions

8.3.2 Visual Signature ToolsThe following document was approved

9450 Working Draft 1.0 of ISO/IEC 15938-3:2001/Amd.3 Visual Signature Tools

5

8.3.3 Improvements to Geographic DescriptorThe following document was approved

9338 ISO/IEC 15938-5:2003/FDAM 3 Improvements to Geographic Descriptor

8.3.4 MPEG-7 Query FormatThe following documents were approved

9340 DoC of ISO/IEC CD 15938-12 MPEG Query Format9341 ISO/IEC FCD 15938-12 MPEG Query Format

8.4 IPMP

8.4.1 REL ORC (Open Release Content) ProfileThe following documents were approved

8.4.2IPM

P XML MessagesThe following documents were approved

9415 DoC on ISO/IEC FCD 23001-3 (IPMP XML Messages)9416 Text of ISO/IEC FDIS 23001-3 (IPMP XML Messages)

8.5 Digital Item

8.5.1 Security in Event ReportingThe following documents were approved

9347 DoC on ISO/IEC 21000-15/PDAM1 Security in Event Reporting9348 ISO/IEC 21000-15/FPDAM1 Security in Event Reporting

8.6 Transport and File formats

8.6.1 Registration Authority for ObjectType and StreamType indication and SLConfig descriptor values

The following documents were approved

9552 Request for ISO/IEC 14496-1/Amd49553 Text of ISO/IEC 14496-1/PDAM4 Registration Authority for ObjectType and

StreamType indication and SLConfig descriptor values

9343 Preliminary DoC on ISO/IEC 21000-5/FPDAM3 Open Release Content Profile9344 Request for change of title of ISO/IEC 21000-5/AMD39345 Study Text of ISO/IEC 21000-5/FPDAM3 Open Access Content Profile9346 MPEG-21 REL Profiles Software Implementation Plan v.8

6

8.6.2 Carriage of SVC in MPEG-2 SystemsThe following documents were approved

9366 DoC of ISO/IEC 13818-1:2007/PDAM3 Carriage of SVC in MPEG-2 Systems9367 Text of ISO/IEC 13818-1:2007/FPDAM3 Carriage of SVC in MPEG-2 Systems

8.6.3 Transport of MPEG Surround data in AACThe following document was approved

9501 Proposed Overview of Transport of AAC, HE-AAC and MPEG Surround in MPEG-2 Systems

8.6.4 MP4FF box for Original Audio File InformationThe following documents were approved

9496 DoC on ISO/IEC 14496-3:2005/FPDAM 8, MP4FF Box for Original Audio File Information

9497 ISO/IEC 14496-3:2005/FDAM 8, MP4FF Box for Original Audio File Information

8.6.5 ISO Base Media File FormatThe following documents were approved

9378 Revised TuC on ISO/IEC 14496-129379 Guidelines for building on the Part 12 ISO Base Media File Format

8.6.6 Digital Item File FormatThe following documents were approved

9387 DoC on ISO/IEC 21000-9/ PDAM1 MP21 Mime Type9388 Text of ISO/IEC 21000-9/ FPDAM1 MP21 Mime Type

8.6.7 Digital Item StreamingThe following documents were approved

9351 DoC of ISO/IEC 21000-18/FPDAM1 Simple Fragmentation Rule9352 Text of ISO/IEC 21000-18/FDAM1 Simple Fragmentation Rule

8.7 Multimedia architecture

8.7.1 Codec Configuration RepresentationThe following document was approved

9453 Text of ISO/IEC CD 23001-4 Codec Configuration Representation

7

8.7.2 3D Graphics Compression ModelThe following document was approved

9542 Text of CD of ISO/IEC 14496-25

8.7.3 Media Streaming MAF ProtocolsThe following documents were approved

9419 DoC on Text of ISO/IEC FCD 29116-1 Media Streaming MAF Protocol9420 Text of ISO/IEC FDIS 29116-1/Media Streaming MAF Protocol

8.7.4 Extensible Multimedia PlatformThe following document was approved

9423 Content and Objectives : MXM – A project to exploit MPEG standards in tune with industry practices and needs

8.8 Application formats

8.8.1 GeneralThe following documents were approved

9421 MAF Overview Document9422 MAF Overview Presentation

8.8.2 Musical Slide Show Application FormatThe following documents were approved

9389 Text of ISO/IEC FCD 23000-4 Musical Slide Show 2nd Edition9390 Request for ISO/IEC 23000-4:200x/Amd.1 MSS Application Format Conf. and Ref.

Software9391 Text of ISO/IEC 23000-4:200x/PDAM1 MSS Application Format Conf. and Ref.

Software

8.8.3 Media Streaming Application FormatThe following documents were approved

9353 DoC of ISO/IEC FCD 23000-5 Media Streaming Application Format9354 Request for change of title of ISO/IEC 23000-59355 Text of ISO/IEC FDIS 23000-5 Media Streaming Application Format

8.8.4 Professional Archival Application FormatThe following documents were approved

8

9392 Requirements on Professional Archival Application Format9393 Text of ISO/IEC 23000-6/WD1.0 Professional Archival Application Format

8.8.5 Open Access Application FormatThe following documents were approved

9356 Preliminary DoC of ISO/IEC FCD 23000-7 Open Release Application Format9357 Request for Change of Title of ISO/IEC 23000-79358 Study Text of ISO/IEC FCD 23000-7 Open Access Application Format

8.8.6 Portable Video Player MAFThe following documents were approved

9394 DoC on ISO/IEC CD 23000-8 Portable Video Application Format9395 Text of ISO/IEC FCD 23000-8 Portable Video Application Format

8.8.7 Digital Multimedia Broadcasting Application FormatThe following documents were approved

9396 DoC on ISO/IEC FCD 23000-9 (DMB Application Format)9397 Text of ISO/IEC 23000-9/FDIS (DMB Application Format)9398 Workplan for DMB Application Format Reference

Software9544 RER on TTA and ETSI references in ISO/IEC 23000-9

8.8.8 Video Surveillance Application FormatThe following documents were approved

9399 Draft DoC on ISO/IEC CD 23000-10 (Video Surveillance Application Format)9412 Study Text of ISO/IEC CD 23000-10 (Video Surveillance Application Format)

8.8.9 Video Stereoscopic Application FormatThe following documents were approved

9413 Request for Subdivision of ISO/IEC 230009414 Text of ISO/IEC 23000-11/WD1.0 (Stereoscopic Video Application Format)

8.9 Reference implementation

8.9.1 Symbolic Music Representation Reference Software

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

9

9511 DoC on ISO/IEC 14496-5:2001/PDAM 20, MPEG-1 and -2 on MPEG-49512 ISO/IEC 14496-5:2001/FPDAM 20, MPEG-1 and -2 on MPEG-4

8.9.3 Reference Hardware DescriptionThe following document was approved

9431 ISO/IEC TR 14496-9 3rd Edition Reference Hardware Description

8.9.4 New Profiles for Professional Applications Reference SoftwareThe following documents were approved

9443 Disposition of Comments on ISO/IEC 14496-5:2001/PDAM 18 Reference Software for New Profiles for Professional Applications

9444 Text of ISO/IEC 14496-5:2001/FPDAM 18 Reference Software for New Profiles for Professional Applications

8.9.5 Geometry and Shadow Reference Software The following document was approved

9547 Text of ISO/IEC 14496-5:2001/ FDAM13 (Geometry and Shadow RefSoft)

8.9.6 Frame-based Animated Mesh Compression Reference SoftwareThe following document was approved

9532 PDAM of ISO/IEC 14496-5:2001 AMD21 (FAMC RefSoft)

8.9.7 3DGMC Reference SoftwareThe following documents were approved

9533 Request for amendment of ISO/IEC 14496-5:2001 (3DGCM RefSoft)

9534 WD1.0 of ISO/IEC 14496-5:2001 AMD22 (3DGCM RefSoft)

8.9.8 Open Font Format Reference SoftwareThe following documents were approved

9376 Request for ISO/IEC 14496-5/Amd.14 Open Font Format Reference Software9377 Text of ISO/IEC 14496-5/PDAM14 Open Font Format Reference Software

8.9.9 MPEG-21 Reference SoftwareThe following documents were approved

9551 Request for minor enhancement of ISO/IEC 21000-89484 ISO/IEC 21000-8/PDAM1Reference Software

10

8.9.10 MPEG Surround Reference SoftwareThe following document was approved

9516 Study on ISO/IEC 23003-1:2007/FPDAM 2, Reference Software

8.9.11 M3W Reference SoftwareThe following document was approved

9417 Study Text of ISO/IEC CD 23004-8 Reference Software and Conformance9418 M3W Reference Software and Conformance Plan

8.10 Conformance

8.10.1 MPEG-4 Visual Simple Profile Level 6 ConformanceThe following document was approved

9438 Text of ISO/IEC 14496-4:2004/FDAM28 Visual Simple Profile Level 6 Conformance Testing

8.10.2 Simple Studio Profile Levels 5 and 6 ConformanceThe following documents were approved

9439 Request for ISO/IEC 14496-4:2004/Amd.359440 Text of ISO/IEC 14496-4:2004/PDAM35 Simple Studio Profile Levels 5 and 6

Conformance Testing

8.10.3 New Profiles for Professional Applications ConformanceThe following documents were approved

9441 Disposition of Comments on ISO/IEC 14496-4:2004/PDAM 30 Conformance Testing for New Profiles for Professional Applications

9442 Text of ISO/IEC 14496-4:2004/FPDAM 30 Conformance Testing for New Profiles for Professional Applications

8.10.4 File Format ConformanceThe following document was approved

9370 Text of ISO/IEC 14496-4/FDAM 24 File Format Conformance

8.10.5 Geometry & Shadow ConformanceThe following document was approved

11

9546 Text of ISO/IEC 14496-4:2004/ FDAM21 (Geometry and Shadow Conformance)

8.10.6 Frame-based Animated Mesh Compression ConformanceThe following document was approved

9528 PDAM of ISO/IEC 14496-4:2004 AMD32 (FAMC Conformance)

8.10.7 MultiResolution Profile ConformanceThe following document was approved

9529 PDAM of ISO/IEC 14496-4:2004 AMD33 (MultiResolution Profile Conformance)

8.10.8 3DGCM ConformanceThe following documents were approved

9530 Request for Amendment of ISO/IEC 14496-4:2004 (3DGCM Conformance)

9531 WD 1.0 of ISO/IEC 14496-4:2004 AMD34 (3DGCM Conformance)

8.10.9 Synthesized Texture ConformanceThe following documents were approved

9554 DoC of ISO/IEC 14496-4 FPDAM 23 Synthesized Texture Conformance9369 Text of ISO/IEC 14496-4/FDAM 23 Synthesized Texture Conformance

8.10.10 Laser ConformanceThe following documents were approved

9371 DoC on ISO/IEC 14496-4/FPDAM 25 LASeR & SAF V1 Conformance

9372 Text of ISO/IEC 14496-4/FDAM 25 LASeR & SAF V1 Conformance9374 DoC on ISO/IEC 14496-4/PDAM 27 LASeR V2 Conformance9375 Text of ISO/IEC 14496-4/FPDAM 27 LASeR V2 Conformance

8.10.11 Open Font Format ConformanceThe following document was approved

9373 Text of ISO/IEC 14496-4/FPDAM 26 Open Font Format Conformance

8.10.12 Improvements to Geographic Descriptor ConformanceThe following document was approved

12

9339 ISO/IEC 15938-7:2003/FDAM 4 Improvements to geographic descriptor conformance

8.10.13 MPEG Surround ConformanceThe following document was approved

9515 Study on ISO/IEC 23003-1:2007/FPDAM 1, Conformance

8.10.14 M3W ConformanceThe following document was approved

9417 Study Text of ISO/IEC CD 23004-8 Reference Software and Conformance9418 M3W Reference Software and Conformance Plan

8.11 Maintenance

8.11.1 Systems coding standardsThe following documents were approved

9365 Text ISO/IEC 13818-1:2007/Cor.1.2 Reference to AVC standard9368 Text of ISO/IEC 13818-1:2007/Cor.2 WD1.0 related to the carriage of AVC 9381 DoC on ISO/IEC 14496-20/DCOR2 9382 Text of ISO/IEC 14496-20/COR2

8.11.2 Video coding standardsThe following documents were approved

9433 Text of ISO/IEC 14496-2:2004/DCOR3 on level 4 Simple Studio Profile9436 Text of ISO/IEC 14496-4:2004/COR4 Correction of visual bitstreams9437 Text of ISO/IEC 14496-4:2004/Amd.1/COR2 Correction of visual bitstreams

8.11.3 Audio coding standardsThe following documents were approved

9490 DoC on ISO/IEC 14496-3:2005/DCOR 5, DST and MP3on4 and LTP9491 ISO/IEC 14496-3:2005/Cor. 5, DST and MP3on4 and LTP9492 DoC on ISO/IEC 14496-3:2006/Amd. 2:2006/DCOR 3, ALS9493 ISO/IEC 14496-3:2006/Amd. 2:2006/Cor. 3, ALS9495 ISO/IEC 14496-3:2005/Amd. 3:2006/Cor. 1, SLS9503 DoC on ISO/IEC 14496-4:2004/DCOR 5, Audio Corrections9504 ISO/IEC 14496-4:2004/Cor. 5, Audio Corrections9505 ISO/IEC 14496-4:2004/Amd 8/DCOR 1, SBR conformance testing

9506 DoC on ISO/IEC 14496-4:2004/Amd 13/DCOR 1, New bitstreams for LD-AAC profile coders

13

9507 ISO/IEC 14496-4:2004/Amd 13/Cor 1, New bitstreams for LD-AAC profile coders9508 Status of BSAC Conformance

9509 DoC on ISO/IEC 14496-5:2001/Amd. 10:2007/DCOR 1, BSAC in SLS and ALS Corrections

9510 ISO/IEC 14496-5:2001/Amd. 10:2007/Cor. 1, BSAC in SLS and ALS Corrections9513 DoC on ISO/IEC 23003-1:2007/DCOR 19514 ISO/IEC 23003-1:2007/Cor. 1

8.11.4 MDS standardsThe following documents were approved

9349 DoC on ISO/IEC 21000-15/DCOR19350 ISO/IEC 21000-15/COR1

9 Organisation of this meeting

9.1 Tasks for subgroupsTasks were assigned as given in the table below

Systems2 1 3 Carriage of SVC4 4 22 Audio BIFS conformance

23 Synthesised texture conformance24 File format conformance25 Laser v1 conformance26 Open Font Format Conformance27 Laser v.2 conformance

5 14 Open Font Format Reference Software16 Symbolic Music Representation Reference Software17 Laser Reference Software

12 MPEG-2 FF15 1 SVC File Format20 1 Lightweight Scene Representation

1 Laser profiling21 9 1 Mime type registrationA 4 1 Musical Slide Show MAF conformance & RS

2 Protected Musical Slide Show MAF8 Portable Video Player MAF9 DMB MAF

10 Video Surveillance MAFStereoscopic MAF

B 3 IPMP XML messagesE 8 M3W Reference Software and Conformance29116 1 MS MAF ProtocolsU MPEG eXtensible MiddlewareV Information exchange with virtual worldsW Framework for representation of sensory effects informationX Post production delivery format

14

Y Joint management of content description and presentationIPTV

MDS7 12 Query Format

SchemasProfessional video deliverables

21 2 Revisiting DID5 REL amendment OAC6 Media value chain ontologies8 1 Reference software

18 1 Digital Item StreamingSchemas

A 5 Media Streaming MAF6 Professional Archival MAF7 OA MAF

Video4 2 4 Simple Profile level 67 3 3 Visual Signature Tools

3 Video augmentation by metadataA 3 1 Photo Player Reference Software

2 Photo Player ConformanceColour

B 4 Codec Configuration DescriptionC 2 Fixed-point 8x8 IDCT and DCTC 3 Stereoscopic video

4 Video Tool Library4 1 Video Tool Library Conformance

FTVJVT 4 New AVC Profiles for Professional Applications Conformance

New AVC Profiles for Professional Applications Reference SWScalable Video Coding ConformanceScalable Video Coding Reference SW

10 2 Scalable Video Coding1 Multi-View Video Coding

Audio 4 3 8 MP4 box for original audio file information3 9 AAC-ELD4 20 SLS conformance

29 SMR Conformance5 16 SMR Reference Software

15 BSAC and SLS Reference Software20 MPEG-1/-2 on MPEG-4 reference software

D 1 1 MPEG Surround Reference Software2 MPEG Surround Conformance3 Spatial Audio Object Coding

X Audio and Speech Coding3DG

4 4 32 FAMC (Frame based Animated Mesh Compress.) Conformance21 Geometry and shadow Conformance32 Multiresolution profile conformance

15

5 21 FAMC (Frame based Animated Mesh Compress.) Reference software13 Geometry and shadow Reference Software21 Multiresolution profile Reference Software

16 2 Frame-based animated mesh compression3 3D Multiresolution profile4 Space partitioning

25 3D Graphics Compression modelMetaverse

Test4 10 3 SVC verification tests

ISG4 9 2 Reference Hardware Description

3 Reference Hardware Description7 6 Reference software

LiaisonJPEG

9.2 Joint meetingsThe following joint meetings were held

Groups What Day Where TimeVid, Sys BSDL Wed Vid Seoul 14:00-15:00Vid, Sys AVC & SVC on MP2 Wed Vid 14:00-15:30

10 WG management

10.1 Terms of referenceThe following document was approved

9400 Terms of reference

10.2 EditorsThe following document was approved

9405 Editors of MPEG standards

10.3 LiaisonsThe following liaison documents were issued

9359 Response to DMP Regarding Open Access Application Format9360 Response to WG1 regarding Professional Archival MAF9361 Response to WG1 regarding the MPEG Query Format9480 Response to DVB on File Format

16

9481 Response to ITU IPTV FG on MPEG technology for IPTV9548 Liaison to SMPTE on Professional Archival MAF9545 Liaison to ISO/IEC JTC1 SC27 on Video Surveillance Application Format9469 Liaison Statement to ITU-T SG 16 re Video Coding Work and Video Metadata9470 Liaison Statement to JTC 1/SC 37 re Face Data Interchange Format9471 Liaison Statement to AVS re RVC 9472 Liaison Statement to DECSDP re CoSME Overview9473 Liaison Statement to SMPTE re RVC9527 Liaison Statements by JVT9523 Liaison Statement to ITU-T SG 169524 Liaison Statement to IEC on CD 62516

10.4 Ad hoc groupsThe following ad hoc goups were established

9487 Ad Hoc Group on Application Format

9488 Ad Hoc Group on Digital Item Presentation

9486 Ad Hoc Group on MPEG File Formats

9485 Ad Hoc Group on Scene Representation

9540 AFX 3rd Edition

9494 AHG on 3DG documents, experiments and software maintenance

9525 AHG on Audio Standards Maintenance

9478 AHG on Free-Viewpoint Television

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

9550 AHG on MPEG Query Format

9476 AHG on MPEG-7 Visual

9448 AHG on Professional Archival Application Format

9475 AHG on Reconfigurable Video Coding

9549 AHG on Requirements for MPEG Post Production Deliverable Formats

9449 AHG on Requirements of Media Value Chains Ontologies

9489 AHG on SVC Verification Test

9526 AHG on Unified Speech and Audio Coding and SAOC

9477 AHG on Video Augmentation by Metadata

10.5 Asset management

10.5.1 Reference softwareThe following document was approved

9406 Software assets

17

10.5.2 Conformance The following document was approved

9407 Conformance assets

10.5.3 Test materialThe following document was approved

9408 Content assets

10.5.4 URIThe following document was approved

9409 URI assets

10.6 IPR management The following document was approved

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

10.7 Work planThe following documents were approved

9401 MPEG Standards9402 Table of unpublished FDISs9403 Work plan and time line

11 Administrative matters

11.1 Schedule of future MPEG meetingsThe following meeting schedule was approved

# City Country yy mm dd-dd82 Shenzhen CN 07 10 22-2683 Antalya TR 08 01 14-1884 Archamps FR 08 04-05 28-0285 Hannover DE 08 07 21-2586 Seoul KR 08 10 13-1787 09 01 19-2388 09 04 20-248990 Xian CN 09 10 26-30

18

11.2 Promotional activitiesThe following document was approved

9333 Shenzhen press release

12 Resolutions of this meetingThese were approved

13 A.O.BThere was no other business

14 ClosingMeeting closed at 2007/10/26T22:45

19

Annex A – Attendance list

First Name Last Name company CountryIan Burnett University of Wollongong AustraliaChristian Timmerer Klagenfurt University AustriaRik Van De Walle Ghent University - IBBT BelgiumJan De Cock Ghent University BelgiumSaar De Zutter Ghent University - IBBT BelgiumStijn Notebaert Ghent University - IBBT BelgiumKenneth Vermeirsch Ghent University - IBBT BelgiumLu Yu Zhejiang University ChinaHoi Ming Wong ASTRI, HK ChinaXiaozhen Zheng Huawei ChinaJianru Xue Xi'an Jiaotong University ChinaWei Xiao Huawei ChinaXin Jin The Chinese University of Hong Kong ChinaWang Jing Huawei ChinaYu-Wen Huang MediaTek ChinaJianghong Yu National Source Coding Center ChinaKa Man Carmen Cheng ASTRI, HK ChinaKun-Bin Lee MediaTek ChinaXun Guo MediaTek(Beijing) ChinaWeiguo Chen GE ChinaShawmin Lei MediaTek ChinaXiaozhong Xu Tsinghua University ChinaYun He Tsinghua University ChinaPing Yang Tsinghua University ChinaHaitao Yang Xidian University ChinaJunyan Huo Xidian university ChinaYilin Chang Xidian University ChinaWuzhou Zhan Huawei ChinaZhijie Yang Broadcom Corp. ChinaLidong Xu Intel China, Ltd. ChinaGuizhong Liu Xi'an Jiaotong University ChinaXianzhong Li Freescale ChinaShang Shidong Freescale ChinaYONGYING GAO Thomson Corporate Research Beijing ChinaYuwen WU Thomson Corporate Research Beijing ChinaSheng Shine Tencent ChinaHongbo Zhu Arcsoft ChinaShan Guo Huawei ChinaMingchen Han Huawei ChinaChangcai Lai Huawei ChinaZhibin Li Huawei ChinaJinchun Yang Huawei ChinaRenlong He Ningbo University ChinaGangyi Jiang Ningbo University ChinaYou Yang Ningbo University China

20

Bin Ye Ningbo University ChinaSuxing Liu Shanghai University ChinaJiyuan Lu Sun Yat Sen University ChinaZhu Gang Tsinghua University ChinaZhanwei Liu Xi'an Jiaotong University ChinaFeifei Ren Xi'an Jiaotong University ChinaSijia Chen Zhejiang University ChinaDandan Ding Zhejiang University ChinaJiangpeng Wang Zhejiang University ChinaHongfei Ma Huawei ChinaLijing Xu Huawei ChinaDeming Zhang Huawei ChinaYue Lang Huawei ChinaHonggang Qi JDL ChinaPeng Zhan Huawei ChinaLihua Zhu Thomson ChinaWen Gao Beijing University ChinaWenhai Wu Huawei ChinaYe-Kui Wang Nokia FinlandYing Chen Tampere University of Technology FinlandJani Lainema Nokia FinlandKemal Ugur Nokia FinlandMauri vaananen Nokia FinlandJoel Jung Orange - France Telecom R&D FrancePierrick Philippe Orange Labs FranceDavid Virette France Telecom FranceBertrand Berthelot France Telecom FranceMarc Guez Vucher SCPP FranceStephane Pateux Orange Labs FrancePatrick Gioia France Telecom FranceVincent Bottreau Thomson R&D FranceJerome Vieron Thomson R&D FranceMickael Raulet INSA de Rennes FranceOlivier Deforges IETR/INSA de Rennes FranceJean-claude Dufourd STREAMEZZO FranceFrançoise Preteux GET/INT FranceMarius Preda GET/INT FranceArnaud Bourge NXP SEMICONDUCTORS FranceSylvain Devillers France Telecom FranceAvaro Olivier Streamezzo FranceIngo Wolf Deutsche Telekom GermanyBernhard Grill Fraunhofer IIS GermanyGero Baese Siemens GermanyKarsten Mueller Fraunhofer HHI GermanyRalf Geiger Fraunhofer IIS GermanyMarkus Multrus Fraunhofer IIS GermanyOliver Hellmuth Fraunhofer IIS GermanyMarkus Schnell Fraunhofer IIS GermanyTilman Liebchen LG Electronics GermanyMartin Winken Fraunhofer HHI Germany

21

Jens-Rainer Ohm RWTH Aachen University GermanyMario Doeller University of Passau GermanyAndreas Schneider Coding Technologies GmbH GermanyHeiko Schwarz Fraunhofer HHI GermanyOliver Wuebbolt Thomson GermanyMathias Wien RWTH Aachen University GermanyMatthias Gruhne Fraunhofer IDMT GermanyThomas Wedi Panasonic GermanySteffen Wittmann Panasonic GermanyRalph Sperschneider Fraunhofer IIS GermanyNikolce Stefanoski Leibniz Universität Hannover GermanyTobias Oelbaum Technische Universität München GermanyFlorian Schreiner Technische Universität München GermanyThomas Wiegand Fraunhofer HHI GermanyGiovanni Cordara Telecom Italia ItalySabina Brufani Sisvel ItalyLeonardo Chiariglione CEDEO ItalyThiow Keng Tan NTT DoCoMo, Inc. JapanTeruhiko Suzuki Sony Corp. JapanTakashi Ito Fujitsu Laboratories Ltd. JapanYoshihisa Yamada Mitsubishi Electric JapanShunichi Sekiguchi Mitsubishi Electric JapanKohtaro Asai Mitsubishi Electric JapanMasashi Takahashi Hitachi, Ltd. JapanTokumichi Murakami Mitsubishi Electric JapanHiroya Nakamura JVC JapanTakeshi Chujoh Toshiba Corporation JapanTakanori Senoh NICT JapanTomoo Yamakage TOSHIBA Corporation JapanAkiyuki Tanizawa TOSHIBA JapanShimada Osamu NEC Corporation JapanTakahiro Yamasaki Oki Electric Industry Co., Ltd. JapanToshiyuki Nomura NEC JapanRyoma Oami NEC Corporation JapanKota Iwamoto NEC Corporation JapanShiodera Taichiro Toshiba Corporation JapanToshiaki Fujii Nagoya University JapanTakehiro Moriya NTT JapanNoboru Harada NTT JapanSei Naito KDDI Corporation JapanTomonobu Yoshino KDDI Corporation JapanMasayuki Tainimoto Nagoya University JapanTakuyo Kogure Matsushita Electric Ind. Co. Ltd JapanYukiko Ogura IPSJ/ITSCJ JapanMasanori Sano NHK JapanYoshiyuki Yashima NTT JapanSatoshi Ito TOSHIBA JapanShinya Shimizu NTT JapanKaneko Itaru Tokyo Polytechnic Univ JapanTomoyuki Yamamoto Sharp Corporation Japan

22

Tsukuba Takeshi Sharp Corporation JapanYukihiro Bandoh NTT JapanTAKESHI NORIMATSU Matsushita Electric (Panasonic) JapanYasuhiro Toguri Sony Corporation JapanJun Matsumoto Sony JapanMasayuki Nishiguchi Sony JapanHideaki Kimata NTT JapanSebastien Brangoulo Joost Technologies B.V. NetherlandsYann Bodo Joost Technologies B.V. NetherlandsWerner Oomen Philips Applied Technologies NetherlandsErik Schuijers Philips Applied Technologies NetherlandsJean H.A. Gelissen Philips Research NetherlandsWilhelmus Bruls Philips NetherlandsLincoln Sampaio Lobo Philips Applied Technologies NetherlandsArild Fuldseth Tandberg NorwayGisle Bjontegaard Tandberg NorwayRobert Kolodynski Telekomunikacja Polska PolandMuczko Marian Telekomunikacja Polska PolandKwangki Kim Information and Communications

UniversityR.O. Korea

Minsoo Hahn Information and Communications University

R.O. Korea

Sang-Kyun Kim Myongji University R.O. KoreaDong Soo Kim LG Electronics R.O. KoreaHee-Suk Pang LG Electronics R.O. KoreaPark Seung-Wook LG Electronics R.O. KoreaByeong-Moon Jeon LG Electronics R.O. KoreaYong Joon Jeon LG Electronics R.O. KoreaJoonyoung Park LG Electronics R.O. KoreaByeungwoo Jeon SKKU R.O. KoreaDong-Seok Jeong Inha University R.O. KoreaHyeong-Yong Jeon Chungnam National University. R.O. KoreaJiho Park KETI R.O. KoreaWeongeun Oh ETRI R.O. KoreaByeongho Choi KETI R.O. KoreaSeoyoung Hwang Samsung Electronics Co., LTD. R.O. KoreaHwaseon Shin KETI R.O. KoreaChi Jung Hwang ChungNam National University R.O. KoreaJie Jia Sejong University R.O. KoreaSungyong Yoon LG Electronics R.O. KoreaTaehyun Kim DRM inside R.O. KoreaIk-Hwan Cho Inha University R.O. KoreaJeong-Hwan Ahn Samsung AIT R.O. KoreaDong-Hoon Han Sejong university R.O. KoreaMiran Choi ETRI R.O. KoreaDaeyeon Kim Sejong University R.O. KoreaYung-Lyul Lee Sejong University R.O. KoreaYoonjin Lee kyungHee University R.O. KoreaEuee Seon Jang Hanyang University R.O. KoreaMaeng Sub Cho ETRI R.O. Korea

23

Yo-Sung Ho GIST R.O. KoreaJin-Seo Kim ETRI R.O. KoreaTaebeom Lim KETI R.O. KoreaZanming He Hanyang University R.O. KoreaHyungyu Kim Hanyang University R.O. KoreaGwang Hoon Park Kyung Hee University R.O. KoreaDoug Young Suh Kyung Hee University R.O. KoreaKwan-Jung Oh GIST R.O. KoreaJaebum Jun Hanyang University R.O. KoreaSinwook Lee Hanyang University R.O. KoreaDong-Gyu Sim Kwangwoon University R.O. KoreaKyuheon Kim Kyunghee University R.O. KoreaDaiyong Kim Hanyang University R.O. KoreaJeong Ju Yoo ETRI R.O. KoreaMin Woo Park Kyung Hee University R.O. KoreaHenney Oh LG Electronics R.O. KoreaKyung Yong Kim Kyung Hee University R.O. KoreaDae Il Yoon Sejong University R.O. KoreaEunmi Oh Samsung AIT R.O. KoreaHae Kwang Kim Sejong University. R.O. KoreaWu Wei Sejong University. R.O. KoreaAyoung Cho Inha university R.O. KoreaHui Yong Kim ETRI R.O. KoreaKyoungro Yoon Konkuk University R.O. KoreaSeo Jeongil ETRI R.O. KoreaTaejin Lee ETRI R.O. KoreaChungku Lee Humax Co., Ltd. R.O. KoreaMuhammad Syah Houari

Sabirin Information and Communications University

R.O. Korea

Munchurl Kim Information and Communications University

R.O. Korea

Shinjee Pyo Information and Communications University

R.O. Korea

Seung-yong Shim Sejong University R.O. KoreaHendry Tan Information and Communications


Chan Won Seo Sejong University R.O. KoreaJoo-Hee Moon Sejon University R.O. KoreaHui-Zi Cui Sejon University R.O. KoreaMin-Cheol Park Sejon University R.O. KoreaYoung Jeo Yoo Sejong University R.O. KoreaJong Lak Kim DSP Group R.O. KoreaDong Hoon Jeong DSP Group R.O. KoreaYoungo Park Samsung Electronics CO., LTD. R.O. KoreaJAMES LEE KETI R.O. KoreaJae-Gon Kim Korea Aerospace University R.O. KoreaJong Ki Han Sejong University R.O. KoreaHyoung-Mee Park Sejon University R.O. KoreaSEOK-PIL LEE KETI R.O. KoreaHayoon Kim SK Telecom R.O. Korea

24

Yung-Ki Lee Sejong University R.O. KoreaHyouk Jean Cha LG Electronics R.O. KoreaDongHwan Park LG Electronics R.O. KoreaCheonhak Ku LG Electronics R.O. KoreaJin Seok Im LG Electronics R.O. KoreaJeongyeon Lim SK Telecom R.O. KoreaJihun Cha ETRI/Korea R.O. KoreaHochong Park Kwangwoon University R.O. KoreaBumshi Lee Information and Communications


Jae Seob Shin Pixtree Technologies, Inc. R.O. KoreaSung-Moon Chun ECT Inc., R.O. KoreaSeanae Pakr Kwanagwoon Univ. R.O. KoreaJeong-Hyu Yang LG Electronics R.O. KoreaSeyoon Jeong ETRI R.O. KoreaJung Won Kang ETRI R.O. KoreaSung Min Kim Dongguk University R.O. KoreaJoongRock Kim Yonsei University R.O. KoreaHyon-Gon Choo ETRI R.O. KoreaYong Han Kim University of Seoul R.O. KoreaChang Ahn Kwangwoon University R.O. KoreaSu-Yeol Jeon Kwangwoon University R.O. KoreaKim Jongyoun net&tv Inc. R.O. KoreaSang Bae Chon Seoul National University R.O. KoreaMingu Lee Seoul National University R.O. KoreaHaechul Choi ETRI R.O. KoreaYungho Choi Koukuk University R.O. KoreaSangMi Kim Sejong University R.O. KoreaYong-goo Kim Yonsei University R.O. KoreaJinwoong Kim ETRI R.O. KoreaMiyoung Kim Samsung R.O. KoreaSukhee Cho ETRI R.O. KoreaEun Young Chang ETRI R.O. KoreaBumsuk Choi ETRI R.O. KoreaSanghyun Joo ETRI R.O. KoreaKugjin Yun ETRI R.O. KoreaSeoung-Jun Oh Kwang-woon University R.O. KoreaYoung-Kwon Lim net&tv Inc. R.O. KoreaYongtae Kim Samsung Electronics R.O. KoreaJin Pil Kim LG Electronics R.O. KoreaWei Yao Institute for Infocomm Research SingaporeHaibin Huang Institute for Infocomm Research SingaporeTe Li Institute for Infocomm Research SingaporeLekha Chaisorn Institute for Infocomm Research SingaporeMen Huang Lee Panasonic Singapore Laboratories SingaporeKok Seng Chong Panasonic Singapore Laboratories SingaporeDajun Wu Institute for Infocomm Research SingaporeSua Hong NEO Panasonic Singapore Laboratories SingaporeSusanto Rahardja Institute for Infocomm Research SingaporeRuben Tous Universitat Politinica de Catalunya (UPC) Spain

25

Victor Miguel Barbero

Universidad Politnica de Madrid Spain

Pablo Carballeira Universidad Politecnica de Madrid SpainLeonardo Lizcano Telefonica R&D SpainPer Frojdh Ericsson SwedenRickard Sjoberg Ericsson SwedenKristofer Kjoerling Coding Technologies AB SwedenHeiko Purnhagen Coding Technologies AB SwedenTaleb Anisse Ericsson SwedenMattavelli Marco EPFL SwitzerlandTouradj Ebrahimi EPEL SwitzerlandPaul Brasnett Mitsubishi Electric ITE United KingdomTanya Beech QinetiQ United KingdomCatherine Grant Nine Tiles United KingdomNilsson Mike British Telecommunications plc United KingdomPanagiotis Koudoumakis Queen Mary University London United KingdomNikola Sprljan Mitsubishi Electric United KingdomJessop Paul IFPI United KingdomMiroslaw Bober Mitsubishi Electric ITE-VIL United KingdomJames Annesley Kingston University United KingdomSchuyler Quackenbush Audio Research Labs United StatesHuifang Sun Mitsubishi Electric Research Labs United StatesVladimir Levantovsky Monotype Imaging Inc. United StatesDavid Singer Apple United StatesYi-Jen Chiu Intel Corp. United StatesMinhua Zhou Texas Instruments United StatesJesus Sampedro Polycom, Inc. United StatesArturo Rodriguez Scientifc Atlanta, a Cisco Company United StatesMichael Horowitz Layered Media Inc. United StatesShih-Ta Hsiang Motorola, Inc. United StatesYi-Shin Tung Hon Hai Precision Ind. United StatesSehoon Yea MERL United StatesHaoping Yu Thomson United StatesAndrew Segall Sharp United StatesGary Sullivan Microsoft Corp. United StatesShan Liu Mitsubishi Electric United StatesAnthony Vetro Mitsubishi Electric United StatesYan Ye Qualcomm Inc United StatesOnur Guleryuz DoCoMo Communications Laboratories United StatesXianglin Wang Nokia United StatesYeping Su Sharp Labs of America United StatesPeng Yin Thomson United StatesXin Wang ContentGuard, Inc. United StatesAlex Eleftheriadis Layered Media, Inc. United StatesHuipin Zhang CISCO SYSTEMS, INC United StatesMohamed Mansour Texas Instruments Inc. United StatesDong Tian Thomson United StatesPankaj Topiwala FastVDO United StatesRidge Justin Nokia United StatesWo Chang NIST United States

26

Gwo Giun (Chris) Lee National Cheng Kung University United StatesJulie Friedman Hot Potato, Inc. United StatesMunsi Haque Intel Corporation United StatesJiancong Luo Thomson United StatesZhongli He Freescale Semiconductor United StatesPengjun Huang Qualcomm Inc. United StatesWalt Husak Dolby Labs United StatesYi-Wen Chen ITRI Internation Inc./NCTU United Statespatrick rault Quartics United StatesAndrew Tescher Microsoft United StatesLulin Chen Omneon Video Networks United StatesYong Yu Broadcom Corp United StatesFaisal Ishtiav Motorola, Inc. United StatesMarta Karczewilz Qualcomm United StatesJun Zhang Santa Clara University United StatesSam Narasimhan Motorola United StatesAjay Luthra Motorola United StatesHaitao Guo Apple United States

27

Annex B – Agenda

Item 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 1 Media coding 2 MPEG-4 Visual Simple Profile Level 6 3 AAC-ELD 4 New Profiles for Professional Applications 5 Scalable Video Coding 6 Multiview Video Coding 7 Geometry and Shadow 8 Binary Format for XML (Prefixes and Wild Card extensions) 9 Bitstream Syntax Description Language 10 Fixed point implementation of DCT/IDCT 11 Video Tool Library 12 Spatial Audio Object Coding 13 Free Viewpoint TV coding 14 Audio and speech coding 15 Ontology 16Video coding exploration 2 Composition coding 1 Lightweight Scene Representation 3 Description coding 1 Schema definition 2 Visual Descriptions Extensions 3 Visual Signature Tools 4 Technologies for digital photo management using MPEG-7 visual tools 5 Improvements to Geographic Descriptor 6 MPEG-7 Query Format 4 Systems support 1 Fragment Request Unit 5 IPMP 1 REL MAM (Mobile And optical Media) Profile 2 REL DAC (Dissemination And Capture) Profile 3 REL ORC (Open Release Content) Profile 4 IPMP XML Messages 6 Digital Item 1 Schema files for MPEG-21 standards 2 Security in Event Reporting 3 Review of DI 7 Transport and File formats 1 Carriage of SVC in MPEG-2 Systems

28

2 Transport of MPEG Surround data in AAC 3 MP4FF box for Original Audio File Information 4 File Format extensions for Description of Timed Metadata 5 Flute Hint Track 6 AVC File Format extensions for FRExt 7 AVC File Format extensions for SVC 8 AVC File Format extensions for MVC 9 Digital Item File Format 10 Digital Item Streaming 8 Multimedia architecture 1 Codec Configuration Representation 2 3D Graphics Compression Models 3 Media Streaming MAF Protocols 4 IPTV 5 Extensible Multimedia Platform 6 Metaverse 9 Application formats 1 Musical Slide Show Application Format 2 Media Streaming Application Format 3 Professional Archival MAF 4 Open Release Application Format 5 Portable Video Player MAF 6 Digital Multimedia Broadcasting Application Format 7 Video Surveillance MAF 8 Stereoscopic MAF 9 Cross media interactive presentation 10 Reference implementation 1 Symbolic Music Representation Reference Software 2 MPEG-1 and -2 on MPEG-4 Reference Software 3 BSAC Extensions Reference Software 4 Reference Hardware Description 5 New Profiles for Professional Applications Reference Software 6 SVC Reference Software 7 File Format Reference Software 8 Geometry and Shadow Reference Software 9 Frame-based Animated Mesh Compression Reference Software 10 MPEG-J GFX Reference Software 11 LASeR Reference Software 12 Open Font Format Reference Software 13 MPEG-7 Systems Reference Software 14 MPEG-21 REL Reference Software 15 Photo Player MAF Reference Software 16 Musical Slide Show MAF Reference Software 17 Binary MPEG format for XML Reference Software 18 Prefixes and wild card extensions Reference Software 19 MPEG Surround Reference Software 20 M3W Reference Software 11 Conformance 1 Audio BIFS v3 Conformance 2 Symbolic Music Representation Conformance 3 MPEG-4 Visual Simple Profile Level 6 Conformance

29

4 New Profiles for Professional Applications Conformance 5 SVC Profiles Conformance 6 MPEG-1 and -2 Audio in MPEG-4 Conformance 7 BSAC Conformance 8 1-bit Oversampled Audio Conformance 9 Audio Scalable to Lossless Conformance 10 File Format Conformance 11 Geometry & Shadow Conformance 12 Frame-based Animated Mesh Compression Conformance 13 MultiResolution Profile Conformance 14 Synthesized Texture Conformance 15 MPEG-J GFX Conformance 16 Laser Conformance 17 Open Font Format Conformance 18 Perceptual 3D Shape Conformance 19 Improvements to Geographic Descriptor Conformance 20 Binary MPEG format for XML Conformance 21 MPEG Surround Conformance 22 M3W Conformance 23 Video Tool Library Conformance 12 Maintenance 1 Systems coding standards 2 Video coding standards 3 Audio coding standards 4 Visual description coding standards 5 Audio description coding standards 6 MDS standards 9 Organisation of this meeting 1 Tasks for subgroups 2 Joint meetings 10 WG management 1 Terms of reference 2 Officers 3 Editors 4 Liaisons 5 Work item assignment 6 Ad hoc groups 7 Asset management 1 Reference software 2 Conformance 3 Test material 4 URI 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

30

Annex C – Input contributions

No. Authors Title

14766 Wo Chang Document Register for SC29/WG11 Meeting Shenzhen, China

14767 Hideaki Kimata Karsten Müller AHG on FTV (Free Viewpoint Television)

14768 Jaime Delgado Marc Gauvin AHG on Requirements for Rights Ontology

14769 Kyoungro YoonMario Doeller AHG on MPEG Query Format

14770 Giovanni Cordara Gerrard Drury AHG on Review of the MPEG-21 DI

14771 Robert Turney Marco Mattavelli

AHG on MPEG-4 Part 9 Reference Hardware Description Phase 2 and 3

14772

Tobias Oelbaum Mathias WienVincent BottreauNathalie CammasAlex Eleftheriadis

AHG on SVC Verification Test

14773 Yi-Shin Tung Chung-Neng Wang

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

14774 Euee S. Jang Yoshihisa Yamada AHG on Reconfigurable Video Coding

14775Miroslaw BoberRyoma OamiRobert O'Callaghan

AHG on MPEG-7 Visual and Photo Player MAF

14776Miroslaw BoberJens-Rainer OhmThomas Wiegand

AHG on Video Annotation

14777 R. Sperschneider AHG on Audio Standards Maintenance

14778 S. Quackenbush Eunmi Oh AHG on AAC-ELD, Speech and Audio Exploration and SAOC

14779 Jens-Rainer Ohm Fons Bruls AHG on investigating Video Standards by applications

14780 Young-Kwon Lim Jean Lefeuvre Ad Hoc Group on Scene Representation

14781 David Singer Ad Hoc Group on MPEG File Formats

14782Young-Kwon Lim Hui Yong KimJean Cha

Ad Hoc Group on MAF Under Development in Systems

14783 Jeong-Hwan Ahn AHG on 3DG documents, experiments and software maintenance

32

http://mpeg.nist.gov/reg/_update.php?docnum=14783

mailto:??


mailto:??


mailto:[email protected]

http://mpeg.nist.gov/mpeg/docs/82_Shenzhen/contrib/m14781.zip


mailto:??


mailto:??


mailto:??


mailto:??



mailto:??


mailto:??


mailto:??



mailto:??


mailto:??



mailto:??


mailto:??


mailto:??


mailto:??


mailto:??




http://mpeg.nist.gov/reg/_list82.php?k=6,kv=1

http://mpeg.nist.gov/reg/_list82.php?k=5,kv=1

Ning Lu

14784 Sylvain Devillers Update on MPEG Profiles and Levels URIs

14785 WG 1 via SC 29 Secretariat Liaison Statement from WG 1 [SC 29 N 8657]


14787 ITTF via SC 29 Secretariat

Table of Replies on ISO/IEC 14496-4:2004/FDAM 15 [SC 29 N 8674]

14788 ITU-T SG 16 via SC 29 Secretariat Liaison Statement from ITU-T SG 16 [SC 29 N 8676]


14790 IEC TC 100 via SC 29 Secretariat IEC CD 62516 [SC 29 N 8678]

14791 IEC TC 100 via SC 29 Secretariat IEC NP: 100/1269/NP [SC 29 N 8693]



14793 SC 29 Secretariat Summary of Voting on ISO/IEC 13818-1:200X/DCOR 1.2 [SC 29 N 8698]

14794 SC 29 Secretariat Summary of Voting on ISO/IEC 14496-3:2005/DCOR 5 [SC 29 N 8699]


14796 SC 29 Secretariat Summary of Voting on ISO/IEC 14496-5:2001/Amd.10:2007/DCOR 1 [SC 29 N 8702]

14797 SC 29 Secretariat Summary of Voting on ISO/IEC 14496-5:2001/PDAM 20 [SC 29 N 8703]


14799 SC 29 Secretariat Summary of Voting on ISO/IEC 21000-9:2005/PDAM 1 [SC 29 N 8705]

14800 ITTF via SC 29 Secretariat Table of Replies on ISO/IEC FDIS 23004-1 [SC 29 N 8706]



14803 FG IPTV via SC 29 Secretariat

Liaison Statement from ITU-T IPTV Focus Group (FG IPTV) [SC 29 N 8711]

14804 IEC TC 100 via SC 29 IEC CDV 62503 [SC 29 N 8723]

33






















































































Secretariat

14805 SC 29 Secretariat Summary of Voting on ISO/IEC CD 23000-8 [SC 29 N 8726]

14806 JTC 1/SC 37 via SC 29 Secretariat ISO/IEC 19794-5/PDAM 2 [SC 29 N 8728]

14807 SC 29 Secretariat Summary of Voting on ISO/IEC 21000-15:2006/DCOR 1

14808 SC 29 Secretariat Summary of Voting on ISO/IEC CD 15938-12

14809 SC 29 Secretariat Summary of Voting on ISO/IEC 14496-4:2004/PDAM 26

14810 SC 29 Secretariat Summary of Voting on ISO/IEC 14496-2:2004/FPDAM 4







14817 SC 29 Secretariat Summary of Voting on ISO/IEC FCD 23001-3









14826 SC 29 Secretariat Summary of Voting on ISO/IEC 14496-4:2004/Amd.1:2005/DCOR 2









14835 SC 29 Secretariat Summary of Voting on ISO/IEC CD 23000-4 2nd Edition

34








































































































14840 SC 29 Secretariat Summary of Voting on ISO/IEC 23003-1/FPDAM 1

14841 SC 29 Secretariat Summary of Voting on ISO/IEC 21000-18/FPDAM 1






14847 SC 29 Secretariat Summary of Voting on ISO/IEC 13818-1:200X/PDAM 3



14850 DMP via SC 29 Secretariat Liaison Statement from the Digital Media Project [SC 29 N 8734]



14852 Jean-Claude Dufourd FNB comments on LASeR AMD2


Table of Replies on ISO/IEC 13818-1:200X/FDAM 2 [SC 29 N 8757]


14855 IEC TC 100 via SC 29 Secretariat IEC CDV 62227 [SC 29 N 8770]

14856

Heiko PurnhagenJeroen KoppensMatthias NeusingerKristofer Kjörling

Further corrections to MPEG Surround DCOR1

14857 Beech ISO/IEC 15938-5:2003/FDAM 3

14858 Beech ISO/IEC 15938-7:2003/FDAM 4

14859 Christian Timmereron behalf of the CE Report of Core Experiment on Digital Item Semantics

14860 Andreas Schneider Update on MPEG Surround conformance

14861

Gwo Giun LeeHe-Yuan LinMing-Jiun WangRong-Lai LaiYuan-Long Cheng

RVC FUs of motion vector reconstruction for AVC

35















mailto:Tanya



mailto:Tanya






































































14862 Swedish NB via SC 29 Secretariat

Swedish NB comments on IEC CD 62516 [m14790 (SC 29 N 8678)]

14863 JNB JNB comment on video coding standards for beyond HDTV applications

14864Kenji OtoiYoshihisa YamadaKohtaro Asai

Proposed text of the RVC FUs for MPEG-4 AVC High Profile tools

14865 German NB via SC 29 Secretariat

German NB comments on IEC CD 62516 [m14790 (SC 29 N 8678)]

14866 Jeong-Hwan Ahn Proposed Text of ISOIEC 14496-4-2004 FDAM21 (Geometry & Shadow)

14867 Simon DanielsVladimir Levantovsky Open Font Format Reference Software Implementation

14868 Teruhiko Suzuki Proposal of new level for MPEG-2 video

14869 Teruhiko Suzuki Proposal of new levels for MPEG-4 visual studio profile

14870 Thomas SchierlThomas Wiegand On SVC over MPEG 2 Transport Stream

14871

Miran ChoiHee-Cheol SeoHyunki KimMyung-Gil JangSoojong LimJeong HeoKyoungro Yoon

Proposal for System Messages in MPEG-7 Query Format

14872

Miran ChoiHee-Cheol SeoHyunki KimMyung-Gil JangSoojong LimJeong HeoKyoungro Yoon

Proposal for Fieldtype ID in MPEG-7 Query Format

14873 Christophe LucarzDave Parlour Serialized version of some MPEG-4 SP FUs

14874

Christophe LucarzJoseph Thomas-Kerr Marco MattavelliIan Burnett

A systematic procedure for the generation of a CAL parser from BDSL in the RVC framework - result CE 1.1

14875 Andy Tescher for USNB USNB Contribution: issues relating to carriage of AVC (ISO/IEC 14496-10) bitstreams in MPEG-2 Systems streams

14876 Andy Tescher for USNB USNB Contribution: Remarks on multi-view and free-viewpoint video coding work (MVC/FTV)

14877 Andy Tescher for USNB USNB Contribution: Soundfield reproduction technology

14878 Andy Tescher for USNB USNB Contribution: Profiles for ALS that meet industry needs

36


mailto:[email protected];







































































14879

Taka senohKenji YamamotoRyutaro OiTomoyuki MishinaMakoto Okui

Consideration of FTV image generation from image+depth

14880 Patrick GioiaLinda Pagès Report on CE2: Space Partitioning

14881Seoyoung Hwang Jaeyeon SongYoung-Kwon Lim

LASeR in IPTV

14882 Schuyler Quackenbush 81st MPEG Audio Report

14883 ITTF via SC 29 Secretariat Table of Replies on ISO/IEC 14496-10:2005/FDAM 2





14888Masayuki TanimotoToshiaki FujiiKazuyoshi Suzuki

Multi-view depth map of Rena and Akko&Kayo

14889Masayuki TanimotoToshiaki FujiiKazuyoshi Suzuki

Experiment of view synthesis using multi-view depth

14890 Yukihiro Nishida Request for extending the levels of MPEG4 AVC

14891 Nikolce StefanoskiJörn Ostermann

Proposed corrections and changes to ISO/IEC 14496-16:2006/PDAM2 (FAMC)

14892 James AnnesleyJames Orwell

Visual Surveillance Multimedia Application Format: Reference Software

14893

Houari SabirinJames AnnesleyMunchurl KimJames Orwell

Visual Surveillance Multimedia Application Format: MPEG-7 Profile

14894 James OrwellJames Annesley

Visual Surveillance Multimedia Application Format: Summary Document

14895 Julie Lofton Proposal for Standardization of Content Deliverables for Professionally Produced Film, TV, Video

14896 David Singer Relating Composition and Decoding Times in ISO Files

14897 David Singer Guidelines for building on the Part 12 ISO Base Media File Format Specification

37


















































































14898 David Singer On the MVC file format

14899 David Singer Video depth and parallax in ISO files

14900

Sanghyun JooBumsuk ChoiHaeryong LeeKwangro ParkMunchurl KimJaegon Kim

A Service Framework of Device-Rendered Sensible Media for Enriched Experiences

14901

Gary SullivanYuriy ReznikArianne HindsLu Yu

ISO/IEC 23002-2 FCD (Updated with Editor's Input)

14902

Hee-Cheol SeoMiran ChoiHyunki KimMyung-Gil JangSoojong LimJeong HeoKyoungro Yoon

IndicatorType for MPEG-7 Query Format

14903Blagica Jovanova Marius PredaFrancoise Preteux

Compression Results for BBA on COLLADA Animation

14904Ivica ArsovMarius Preda Francoise Preteux

Support for multiple texture coordinates and additional attributes per vertex in 3DMC

14905

Blagica Jovanova Cyril Concolato Jean Le FeuvreMarius Preda

Storage of XML documents and associated media resources in the ISO file format

14906Marius Preda Francisco MoranFrancoise Preteux

MPEG-4 3D Graphics in Metaverse

14907

Sang-ki Kim Joongrack Kim Jinkyu HwangSangyoun LeeMyung Gil JangHyun Ki KimJeong Heo

CE Report for VCE-5

14908 Jeongil SeoSeungkwon BeackKyeongok KangKwangki KimMinsoo Hahn

Comments on SAOC architecture for MBO

14909 Dae Il Yoon Video signature

38





mailto:

mailto:

mailto:


mailto:

mailto:



















































Jie JiaWei WuHae Kwang KimWeon Geun Oh


14911 3GPP2 via SC 29 Secretariat Liaison Statement from 3GPP2 [SC 29 N 8819]

14912 SC 29 Secretariat Liaison Statement from DVB [SC 29 N 8823]

14913Hyeong-yong JeonChi-jung HwangWeon-geun Oh

An Image Identifier Based on Feature Points for Complex Conditions

14914 Next Generation Broadcasting Forum Revised requirements of the Stereoscopic MAF

14915 Next Generation Broadcasting Forum Proposal for technical specification of Stereoscopic MAF

14916

Shun-ichi SekiguchiShuichi YamagishiYoshihisa YamadaKohtaro AsaiTokumichi Murakami

On adaptive chroma sampling for 4:4:4 video coding

14917Steffen KampMichael EvertzMathias Wien

Decoder Side Motion Vector Derivation

14918 Mathias Wien Verification of SVC Verification Test Streams

14919

Mario DoellerMatthias GruhneIngo Wolf Heiko Studt

Naming inconsistencies in MPQF and proposal for decoupling of other metadata standards

14920 Shinya ShimizuHideaki Kimata View generation from neighboring two videos and two depth maps

14921Mario DoellerMatthias GruhneIngo Wolf

Enhancement of QueryByExample Type in MPQF

14922Hyouk Jean ChaTae Hyeon KimJisoo Hong

Proposed text of ISO/IEC 23000-4/PDAM1 Musical slide show MAF: Conformance and Reference software

14923Hyouk Jean ChaTae Hyeon KimHerbert Thoma

Proposed text of ISO/IEC 23000-8/FCD Portable video player MAF

14924 Ingo WolfRubén TousGiovanni CordaraJaime Delgado

Introduction of a Data Model for MPQF

39



































































Mario DoellerMatthias Gruhne

14925 Bertrand BerthelotVincent Bottreau On transport of SVC over MPEG-2 TS

14926 Kota IwamotoRyoma Oami On the Modification Process of VCE-7

14927 Kota IwamotoRyoma Oami Contribution to the Video Dataset for VCE-7

14928 Tilman Liebchen Proposed Text of ISO/IEC 14496-3:2005/Amd.2:2006/COR 3, ALS

14929

Dandan DingMarco MattavelliChristophe LucarzLu Yu

Classification of Tokens for FUs of MPEG-4 SP and MPEG-4/AVC in RVC Framework

14930 Fons BrulsLincoln Lobo On Transport of Scalable Video over MPEG-2 TS

14931

Dandan DingLu YuMarco MattavelliHonggang QiWen GaoTiejun Huang

A RVC Framework and Tokens Definition Proposed for AVS JiZhun Profile

14932

Sunyoung LeeHyungyu KimSinwook LeeJaebum JunSi Kyung KimChungku YieEuee S. Jang

Results of RVC CE 1.1

14933

Sinwook LeeJaebum JunByoungjun KimChungku YieEuee S. Jang

Results of RVC CE 1.2: CDDL

14934

Khaled MamouHeiner KirchhofferNikolce Stefanoski Detlev MarpeKarsten MüllerJörn OstermannTitus ZahariaFrançoise Prêteux

FAMC decoder software description

14935 Giseok SonDaiyong KimHyungyu KimEuee S. Jang

Simple and Fast Compression of 3D Meshes

40







mailto:


mailto:







































14936

Khaled MamouHeiner KirchhofferNikolce StefanoskiDetlev MarpeKarsten MüllerJörn OstermannTitus ZahariaFrançoise Prêteux

FAMC decoder conformance

14937Christian Timmerer(on behalf of Austrian NB)

Austrian NB comments on ISO/IEC 21000-9/PDAM 1

14938Christian Timmerer(on behalf of Austrian NB)

Austrian NB comments on ISO/IEC 21000-15/DCOR 1

14939

Jin-Seo KimMaeng-Sub ChoBon-Ki KooSang-Kyun Kim

Specification Investigation for Consistent Color Reproduction

14940


Application Scenarios and Derived Requirements for Color Reproduction MAF

14941

Jihun ChaInjae LeeKyungAe MoonYoung-kwon Lim

Editorial Comments on LASeR 2nd Edition

14942

Dandan DingLu YuHonggang QiTiejun HuangWen Gao

Further RVC Exploration Experiments Report on New 8x8 Inverse Transform and Quantization Tools

14943Noboru HaradaTakehiro MoriyaYutaka Kamamoto

Responce to CfR of PA-MAF

14944Noboru HaradaTakehiro MoriyaYutaka Kamamoto

Proposed text to WD of PA-MAF

14945Hyon-Gon ChooSang-kwon ShinJeho Nam

Updated IPMP Interface for ISO/IEC 23004-8 Reference Software

14946Masanori SanoHideki SumiyoshiNobuyuki Yagi

Some thoughts on data model for MPQF

14947Hyon-Gon ChooFilippo ChiariglioneNaito Joji

Editor Study on ISO/IEC 29116-1 Media Streaming MAF Protocols

41






















































mailto:

14948 Hyon-Gon ChooFilippo Chiariglione Editor Study on ISO/IEC 23001-3 IPMP XML Messages

14949 Kawakita Axi-Vision Camera: Real-time depth-mapping HDTV camera

14950 Ryoma Oami A proposal on MPEG-7 metadata structure for Portable Video Player MAF

14951 Ryoma Oami A proposal on MPEG-7 metadata structure for Video Surveillance MAF

14952Akio IshikawaSei NaitoShigeyuki Sakazawa

Walk-Through Experience using Ray Space Representation toward Free Viewpoint TV

14953 Jean Le Feuvre Comments on Space Partitioning CE

14954HendryHouari SabirinMunchurl Kim

Response to Call for Requirements on PA-MAF

14955

HendryHouari SabirinMunchurl KimNoboru HaradaTakehiro Moriya

Technical Contribution to Development of PA-MAF

14956

Weon-Geun OhAyoung ChoIk-Hwan ChoWon-Keun YangJu-Kyong JinJun-Woo LeeDong-Seok Jeong

Concentric circle partition-based image signature

14957

Rubén TousGiovanni Cordara Jaime DelgadoGianluca Francini

Supporting JOINs and segment-level retrieval in MPQF

14958Khaled MamouTitus ZahariaFrançoise Prêteux

Progress report on the FAMC integration into the MPEG-4 RefSoft

14959

Miyoung KimEunmi OhJungHoe KimHosang SungKiHyun Choo

Further evidence on Joint Speech and Audio Coding

14960

Dong-Seok JeongJu-Kyong JinSang-Il NaDong-Jin Seo

Proposal on the Implementation of VCE-7 Analog VCR Recording & Recapture Modification

14961 Marco Mattavelli Dave Parlour Jorn Janneck

CAL Coding Practice Guide

42































































Ian Miller

14962 Filippo ChiariglioneHyon-Gon Choo Editors Study of ISO/IEC 23000-5 Media Streaming Player

14963Hui Yong KimHyon-Gon ChooMunchurl Kim

(Editors' Input) Proposed Text of ISO/IEC 23000-9 FDIS MAF for DMB

14964 Jens-Rainer Ohm Responses received on Visual Signature Tools CfP

14965

Maxime PelcatMickaël RauletOlivier DéforgesMédéric BlestelJean-François Nezan

Implementing SVC from RVC AVC: description of the specific SVC FUs.

14966

Hui Yong KimMyungSeok KiGun BangYong Han Kim

Updated MPEG-2 TS Encapsulation Method for ISO/IEC 23000-9 MAF for DMB

14967 Giovanni CordaraGerrard Drury Review of CE on DI Semantics

14968

Hui Yong KimSeung Jun YangHeekyung LeeMunchurl Kim

Updated schema and xml samples for the restricted TV-Anytime metadata in ISO/IEC 23000-9 MAF for DMB

14969 Matthias GruhneAndre Begau Suggestions of a new QueryByXQueryType

14970

Matthias GruhneMario DoellerInfo WolfAndre Begau

Suggested changes of the MPEG QF output description

14971 Anisse TalebManuel Briand Comments on draft CfP on Speech and Audio Coding

14972

Dandan DingHonggang QiShanshan OuLu YuTiejun HuangWen Gao

Text Description of RVC FUs for Intra Prediction of AVS JiZhun Profile

14973 Pierrick PhilippeDavid Virette Proposal for MPEG-4 AAC ELD Verification Tests

14974Andreas HoelzerJeroen KoppensLeif Sehlstrom

SAOC Reference software

14975 Sadahiro YasuraHiroya NakamuraMotoharu Ueda

Requirements for FTV Audio

43













































































14976

B.S. ChoiSinji PyoHouari SabirinMunchurl KimSanghyun JooHaeRyong Lee KwangRo Park

Device Control Information Metadata Schema for Device-Rendered Sensible Media

14977 Karol Wnukowicz Cross verification result of Image Signature (VCE-6)

14978 Pierrick Philippe David Virette

Listening test results on block Switching Core Experiment for ELD-AAC

14979 Pierrick Philippe David Virette Proposed changes to ELD AAC

14980 Pierrick Philippe David Virette Comments on Speech and Audio Coding Activity

14981

Matthieu Wipliez Ghislain RoquierMickaël RauletJean-François NezanMarco MattavelliIan Miller

Status of CAL2C code generation

14982 Birman Editor's study of 14496-4:2004/PDAM.23 Synthesized Texture Conformance

14983 Paul BrasnettMiroslaw Bober Proposed Improvements to Image Signature XM 31.0

14984 Fredrik HennPer Ekstrand

CT cross-check of FT and FhG versions of block-switching for AAC-ELD

14985

Oliver HellmuthJürgen HerreLeonid TerentievAndreas HölzerCornelia FalchJohannes Hilpert

Proposed Improvement for MPEG SAOC

14986 Klaus Peichl Proposed correction to SBR conformance testing

14987

Weon-Geun Oh Won-Keun YangIk-Hwan Cho Dong-Seok Jeong

Comments for the current geometrical modification of MPEG-7 VCE-6

14988Heiko Purnhagen Alexander GroeschelHolger Hoerich

Proposed clarification for MPEG-4 Audio

14989 J. EngdegårdH. PurnhagenB. ReschL. VillemoesC. Falch

Proposed SAOC Working Draft Document

44
































































O. HellmuthJ. HerreJ. HilpertA. HölzerL. TerentievJ. BreebaartJ. Koppens

14990Kenneth VermeirschSaar De ZutterRik Van de Walle

Digital Item Adaptation – Universal Constraints Description tools parser

14991Saar De ZutterJan De CockRik Van de Walle

Contribution to summary and 1-pager of Conformance: MPEG-21

14992Saar De ZutterJan De CockRik Van de Walle

Update to summary and 1-pager of Reference Software: MPEG-21

14993 Per EkstrandFredrik Henn Proposed minor modification of AAC-ELD

14994

Yo-Sung HoSang-Beom LeeKwan-Jung OhCheon Lee

Depth Map Generation for FTV

14995 Jean-Claude Dufourd Editor's study of LASeR DCOR2

14996

Yo-Sung HoSang-Tae NaKwan-Jung OhCheon Lee

Depth Coding and Virtual View Synthesis for FTV

14997 Jean-Claude Dufourd Editor's study of LASeR FPDAM2

14998

Markus SchnellRalf GeigerMarkus SchmidtTobias Albert

Cross Check of blockswitching for AAC ELD

14999 Markus SchnellRalf Geiger Proposed changes on ELD

15000 Markus Schnell Proposed Signaling Extension for AAC ELD

15001 Markus SchnellRalf Geiger Proposal for MPEG-4 ER AAC ELD Verification Test

15002 Ye-Kui WangMiska M. Hannuksela On the SVC file format

15003 Florian Schreiner Editor’s Study Text of ISO/IEC FCD 23000-7

15004 Florian Schreiner Contribution to MPEG-21 REL ORC Profile Ref SW: REL Interpreter

15005 Florian Schreiner Contribution to MPEG-21 REL ORC Profile Ref Sw: License Creator

45


































































15006 Schuyler Quackenbush Draft CfP for Speech and Audio Coding

15007

Gary J. SullivanJens-Rainer OhmThomas WiegandAjay Luthra

Meeting Report of the 24th JVT Meeting (29 June – 5 July, 2007, Geneva, CH)

15008

Yuriy ReznikRavi ChivukulaJeff HuangNaveen Srinivasamurthy

Proposed informative addition to AAC ELD

15009

Osamu ShimadaToshiyuki NomuraAkihiko SugiyamaOsamu Hoshuyama

Information on an additional SAOC functionality of separating real-environment signals into multiple objects

15010

Henney OhYang-Wong JungDong-Geum LeeHong-Goo Kang

Listening Test Reports on Block Switching CE for AAC-ELD

15011Eunmi OhJungHoe KimMiyoung Kim

Thoughts on Joint speech and audio coding

15012 Tobias Oelbaum Subjective results for the SVC Verification Test

15013Takuyo KogureKohtaro Asaion behalf of DECSDP

CoSME Overview

15014 Gerrard DruryJoseph Thomas-Kerr

Contribution to ISO/IEC 21000-18 MPEG-21 DIS Reference Software

15015 Gero Bäse on behalf of GNB GNB comments on ISO/IEC CD 23000-10

15016 Niels Rump Comments on N9325

15017Justin RidgeJani LainemaSoren Friis

Proposed text of ISO/IEC 14496-2:2004/FDAM4 Simple Profile Level 6

15018Justin RidgeJani LainemaSoren Friis

Proposed text of ISO/IEC 14496-4:2004/FDAM28 Visual Simple Profile Level 6 Conformance Testing

15019 Jim Aldridge UK NB comments on ISO/IEC CD 23000-10

46





























































Annex D – Output documents

No. Source Title

9328 Convener List of Documents from the Shenzhen, China Meeting

9329 Convener Resolutions of the Shenzhen, China

9330 Convener List of AHGs Established at the 82nd Meeting in Shenzhen, China

9331 Convener Report of the 82st Meeting in Shenzhen, China

9332 Convener Guidelines for Electronic Distribution of MPEG and WG 11 Document

9333 Convener Press Release of the 82nd Meeting in Shenzhen, China

9334 Convener Meeting Notice of the 83rd Meeting in Antalya Turkey

9335 HoD Guide for WG 11 Meeting Hosts

9336 HoD MPEG 101

9337 MDS MPEG-7 Schema Files

9338 MDS ISO/IEC 15938-5:2003/FDAM 3 Improvements to Geographic Descriptor

9339 MDS ISO/IEC 15938-7:2003/FDAM 4 Improvements to geographic descriptor conformance

9340 MDS DoC of ISO/IEC 15938-12 CD MPEG Query Format

9341 MDS ISO/IEC 15938-12 FCD MPEG Query Format

9342 MDS MPEG-21 Schema Files

9343 MDS Preliminary DoC on ISO/IEC 21000-5:2004/FPDAM 3

9344 MDS Request for change of title of ISO/IEC 21000-5 AMD/3

9345 MDS Study Text of ISO/IEC 21000-5:2004/FPDAM 3: OAC (Open Access Content) Profile

9346 MDS MPEG-21 REL Profiles Software Implementation Plan v.8

9347 MDS DoC on ISO/IEC 21000-15 PDAM/1 Security in Event Reporting

9348 MDS Text of ISO/IEC 21000-15:2006/FPDAM 1: Security in Event Reporting

9349 MDS DoC on ISO/IEC 21000-15 COR/1

9350 MDS ISO/IEC 21000-15 COR/1

9351 MDS DoC of ISO/IEC FPDAM/1 21000-18 Simple Fragmentation Rule

9352 MDS Text of ISO/IEC FDAM/1 21000-18 Simple Fragmentation Rule

9353 MDS DoC of ISO/IEC FCD 23000-5 Media Streaming Player

9354 MDS Request for change of title of ISO/IEC 23000-5

9355 MDS Text of ISO/IEC FDIS 23000-5 Media Streaming Application Format

9356 MDS DoC of ISO/IEC FCD 23000-7 Open Release Application Format

9357 MDS Request for Change of Title of ISO/IEC 23000-7

47

http://mpeg.nist.gov/reg/_listwg11_69.php?k=3,kv=1



9358 MDS Text of ISO/IEC FDIS 23000-7 Open Access Application Format

9359 MDS Response to DMP Regarding Open Access Application Format

9360 MDS Response to WG1 regarding Professional Archival MAF

9361 MDS Response to WG1 regarding the MPEG Query Format

9362 MDS ‘Summary of’ and ‘1 pager’ for MPEG-21 Conformance

9363 MDS ‘Summary of’ and ‘1 pager’ for MPEG-21 Reference Software

9364 MDS ISO/IEC PDAM/1 21000-8 Reference Software

9365 Systems Text ISO/IEC 13818-1:2007/Cor.1.2 Reference to AVC specification

9366 Systems DoC of ISO/IEC 13818-1:2007/PDAM3 Carriage of SVC in MPEG-2 Systems

9367 Systems Text of ISO/IEC 13818-1:2007/FPDAM3 Carriage of SVC in MPEG-2 Systems

9368 Systems Text of ISO/IEC 13818-1:2007/Cor.2 WD1.0 related to the carriage of AVC

9369 Systems Text of ISO/IEC 14496-4/FDAM 23 Synthesized Texture Conformance

9370 Systems Text of ISO/IEC 14496-4/FDAM 24 File Format Conformance

9371 Systems DoC on ISO/IEC 14496-4/FPDAM 25 LASeR & SAF V1 Conformance

9372 Systems Text of ISO/IEC 14496-4/FDAM 25 LASeR & SAF V1 Conformance

9373 Systems Text of ISO/IEC 14496-4/FPDAM 26 Open Font Format Conformance

9374 Systems DoC on ISO/IEC 14496-4/PDAM 27 LASeR V2 Conformance

9375 Systems Text of ISO/IEC 14496-4/FPDAM 27 LASeR V2 Conformance

9376 Systems Request for ISO/IEC 14496-5/Amd.14 Open Font Format Reference Software

9377 Systems Text of ISO/IEC 14496-5/Amd.14 Open Font Format Reference Software

9378 Systems Revised TuC on ISO/IEC 14496-12

9379 Systems Guidelines for building on the Part 12 ISO Base Media File Format

9380 Systems LASeR Requirements

9381 Systems DoC on ISO/IEC 14496-20/DCOR2

9382 Systems Text of ISO/IEC 14496-20/COR2

9383 Systems DoC on ISO/IEC 14496-20/FPDAM 2 (SVGT1.2 Support)

9384 Systems Text of ISO/IEC 14496-20/FDAM 2 (SVGT1.2 Support)

9385 Systems Text of ISO/IEC 14496-20:200x/FDIS (1st Ed. + Cor 1 + Amd.1 + Cor. 2)

9386 Systems IuC for LASeR

9387 Systems DoC on ISO/IEC 21000-9/ PDAM1 MP21 Mime Type

9388 Systems Text of ISO/IEC 21000-9/ FPDAM1 MP21 Mime Type

48

9389 Systems Text of ISO/IEC 23000-4/FCD Musical Slide Show 2nd Edition

9390 Systems Request for ISO/IEC 23000-4:200x/Amd.1 MSS Application Format Conf. and Ref. Software

9391 Systems Text of ISO/IEC 23000-4:200x/PDAM1 MSS Application Format Conf. and Ref. Software

9392 Systems Requirements on Professional Archival Application Format

9393 Systems Text of ISO/IEC 23000-6/WD1.0 Professional Archival Application Format

9394 Systems Draft DoC on ISO/IEC 23000-8/CD Portable Video Application Format

9395 Systems Study Text of ISO/IEC 23000-8/FCD Portable Video Application Format

9396 Systems DoC on ISO/IEC 23000-9/FCD (DMB Application Format)

9397 Systems Text of ISO/IEC 23000-9/FDIS (MAF Application Format)

9398 Systems Workplan for DMB Application Format Reference Software

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

9400 Convener Terms of Reference

9401 Convener MPEG Standards

9402 Convener Table of unpublished FDIS

9403 Convener Work plan and time line

9404 Convener Work item assignment

9405 Convener MPEG Standard Editors

9406 Convener Software assets

9407 Convener Conformance assets

9408 Convener Content assets

9409 Convener URI assets

9410 Convener Standards under development for which a call for patent statements is issued

9411 Convener List of Organisations with which MPEG entertains liaisons

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

9413 Systems Request for Subdivision of ISO/IEC 23000

9414 Systems Text of ISO/IEC 23000-11/WD1.0 (Stereoscopic Video Application Format)

9415 Systems DoC on ISO/IEC 23001-3/FCD (IPMP XML Messages)

9416 Systems Text of ISO/IEC 23001-3/FDIS (IPMP XML Messages)

9417 Systems Study Text of ISO/IEC 23004-8/CD Reference Software and Conformance

9418 Systems M3W Reference Software and Conformance Plan

9419 Systems DoC on Text of ISO/IEC 29116-1/FCD Media Streaming MAF Protocol

49

9420 Systems Text of ISO/IEC 29116-1/FDIS Media Streaming MAF Protocol

9421 Systems MAF Overview Document

9422 Systems MAF Overview Presentation

9423 Systems Content and Objectives : MXM – A project to exploit MPEG standards in tune with industry practices and needs

9424 Systems Context and Objectives : Information exchange with Virtual Worlds

9425 Systems Proposal for a new work item – Information exchange with Virtual Worlds

9426 Systems Context and Objectives : Service Framework for Representation of Sensory Effects

9427 Systems Call for Requirements on Service Framework for Representation of Sensory Effects

9428 Systems Context and Objectives : MPEG Post Production Deliverable Formats

9429 Systems Draft Requirements for MPEG Post Production Deliverable Formats

9430 Systems MPEG URI Assets

9431 ISG ISO/IEC TR 14496-9 3rd Edition Reference Hardware Description

9432 Video Text of ISO/IEC 14496-2:2004/FDAM4 Simple Profile Level 6

9433 Video Text of ISO/IEC 14496-2:2004/DCOR3

9434 Video Request for ISO/IEC 14496-2:2004/Amd.5

9435 Video Text of ISO/IEC 14496-2:2004/PDAM5 Simple Studio Profile Levels 5 and 6

9436 Video Text of ISO/IEC 14496-4:2004/COR4

9437 Video Text of ISO/IEC 14496-4:2004/Amd.1/COR2

9438 Video Text of ISO/IEC 14496-4:2004/FDAM28 Visual Simple Profile Level 6 Conformance Testing

9439 Video Request for ISO/IEC 14496-4:2004/Amd.35

9440 Video Text of ISO/IEC 14496-4:2004/PDAM35 Simple Studio Profile Levels 5 and 6 Conformance Testing

9441 Video Disposition of Comments on ISO/IEC 14496-4:2004/PDAM 30

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

9443 Video Disposition of Comments on ISO/IEC 14496-5:2001/PDAM 18

9444 Video Text of ISO/IEC 14496-5:2001/FPDAM 18 Reference Software for New Profiles for Professional Applications

9445 Video Study Text of ISO/IEC 14496-10:200X/PDAM 1 Multiview Video Coding

9446 Video Joint Multiview Video Model (JMVM) 6

9447 Video JMVM 6 Software

9448 Convener AHG on Professional Archival Application Format

9449 Convener AHG on Requirements of Media Value Chains Ontologies

50

9450 Video Working Draft 1.0 of ISO/IEC 15938-3:2001/Amd.3 Visual Signature Tools

9451 Video MPEG-7 Visual XM Document version 32.0

9452 Video Description of Core Experiments for MPEG-7 New Visual Extensions

9453 Video Text of ISO/IEC CD 23001-4 Codec Configuration Representation

9454 Video Disposition of Comments on ISO/IEC 23002-1/FPDAM1

9455 Video Text of ISO/IEC 23002-1/FDAM1 Software for Integer IDCT Accuracy Testing

9456 Video Disposition of Comments on ISO/IEC FCD 23002-2

9457 Video Text of ISO/IEC FDIS 23002-2 Fixed-point Implementation of 8x8 IDCT and DCT

9458 Video Text of CD ISO/IEC 23002-4 Video Tool Library

9459 Video WD 1 of Video Tool Library Extensions

9460 Video Description of Core Experiments in RVC

9461 Video RVC Simulation Model (RSM) V6.0

9462 Video RVC Work Plan

9463 Video RVC Conformance Testing Working Draft 3.0

9464 Video Description of Exploration Experiments in RVC

9465 Video Methodologies for Video Toolbox Extension

9466 Video Applications and Requirements of FTV

9467 Video FTV Test Cases and Evaluation

9468 Video Call for Contributions on FTV Test Sequences

9469 Convener Liaison Statement to ITU-T SG 16 re Video Coding Work and Video Metadata

9470 Convener Liaison Statement to JTC 1/SC 37 re Face Data Interchange Format

9471 Convener Liaison Statement to AVS re RVC

9472 Convener Liaison Statement to DECSDP re CoSME Overview

9473 Convener Liaison Statement to SMPTE

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

9475 Convener AHG on Reconfigurable Video Coding

9476 Convener AHG on MPEG-7 Visual

9477 Convener AHG on Video Augmentation by Metadata

9478 Convener AHG on Free-Viewpoint Television

9479 Systems Introduction to MPEG Binary XML

9480 Convener Liaison to DVB on File Format

9481 Convener Liaison to ITU IPTV FG on MPEG technology for IPTV

9482 Testing Draft SVC Verification Test Report

9483 Testing SVC Verification Test Plan Version 2.0

51

9484 Systems ISO/IEC PDAM/1 21000-8 Reference Software

9485 Convener Ad Hoc Group on Scene Representation

9486 Convener Ad Hoc Group on MPEG File Formats

9487 Convener Ad Hoc Group on Application Format

9488 Convener Ad Hoc Group on Digital Item Presentation

9489 Convener AHG on SVC Verification Test

9490 Audio DoC on ISO/IEC 14496-3:2005/DCOR 5

9491 Audio ISO/IEC 14496-3:2005/Cor. 5, DST and MP3on4 and LTP

9492 Audio DoC on ISO/IEC 14496-3:2006/Amd. 2:2006/DCOR 3

9493 Audio ISO/IEC 14496-3:2006/Amd. 2:2006/Cor. 3, ALS

9494 Convener AHG on 3DG documents, experiments and software maintenance

9495 Audio ISO/IEC 14496-3:2005/Amd. 3:2006/Cor. 1

9496 Audio DoC on ISO/IEC 14496-3:2005/FPDAM 8

9497 Audio ISO/IEC 14496-3:2005/FDAM 8, MP4FF Box for Original Audio File Information

9498 Audio DoC on ISO/IEC 14496-3:2005/FPDAM 9

9499 Audio ISO/IEC 14496-3:2005/FDAM 9, AAC-ELD

9500 Audio ISO/IEC 14496-3:200x, Fourth Edition

9501 Audio Proposed Overview of Transport of AAC, HE-AAC and MPEG Surround in MPEG-2 Systems

9502 Audio Proposed Workplan on AAC-ELD Verification Test


9504 Audio ISO/IEC 14496-4:2004/Cor. 5, Audio Corrections

9505 Audio ISO/IEC 14496-4:2004/Amd 8/DCOR 1, SBR conformance testing

9506 Audio DoC on ISO/IEC 14496-4:2004/Amd 13/DCOR 1

9507 Audio ISO/IEC 14496-4:2004/Amd 13/Cor 1, New bitstreams for LD-AAC profile coders

9508 Audio Status of BSAC Conformance

9509 Audio DoC on ISO/IEC 14496-5:2001/Amd. 10:2007/DCOR 1

9510 Audio ISO/IEC 14496-5:2001/Amd. 10:2007/Cor. 1, BSAC in SLS and ALS Corrections

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

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


9514 Audio ISO/IEC 23003-1:2007/Cor. 1

9515 Audio Study on ISO/IEC 23003-1:2007/FPDAM 1, Conformance

9516 Audio Study on ISO/IEC 23003-1:2007/FPDAM 2, Reference Software

9517 Audio WD on ISO/IEC 23003-2:200x, SAOC text and reference software

9518 Audio Status and Workplan on SAOC Core Experiments

52

9519 Audio Call for Proposals on Unified Speech and Audio Coding

9520 Audio Draft Evaluation Guidelines for Speech and Audio Call

9521 Audio Report on Evidence for Unified Speech and Audio Coding

9522 Audio Workplan for Candidate Test Items

9523 Convener Liaison Statement to ITU-T SG 16

9524 Convener Liaison Statement to IEC on CD 62516

9525 Convener AHG on Audio Standards Maintenance

9526 Convener AHG on Unified Speech and Audio Coding and SAOC

9527 Convener Liaison statements by JVT

9528 3DGC PDAM of ISO/IEC 14496-4:2004 AMD32 (FAMC Conformance)

9529 3DGC PDAM of ISO/IEC 14496-4:2004 AMD33 (MultiResolution Profile Conformance)

9530 3DGC Request for Amendment of ISO/IEC 14496-4:2004 (3DGCM Conformance)

9531 3DGC WD 1.0 of ISO/IEC 14496-4:2004 AMD34 (3DGCM Conformance)

9532 3DGC PDAM of ISO/IEC 14496-5:2001 AMD21 (FAMC RefSoft)

9533 3DGC Request for amendment of ISO/IEC 14496-5:2001 (3DGCM RefSoft)

9534 3DGC WD1.0 of ISO/IEC 14496-5:2001 AMD22 (3DGCM RefSoft)

9535 3DGC Study on Text of ISO/IEC 14496-16:2006/PDAM2 (Frame-based Animated Mesh Compression)

9536 3DGC Text of ISO/IEC 14496-16:2006/FPDAM3 (3D MultiResolution Profile)

9537 3DGC Request for amendment of ISO/IEC 14496-16:2006 (Scene Partitioning)

9538 3DGC WD1.0 of ISO/IEC 14496-16:2006 (Scene Partitioning)

9539 3DGC Text of ISO/IEC 14496-16:2006/AMD1.Corr1 (3DMC Extension Correction)

9540 3DGC AFX 3rd Edition

9541 3DGC 3D Graphics Core Experiments Description

9542 3DGC Text of CD of ISO/IEC 14496-25

9543 Video Requirements and Application Descriptions for MVC

9544 Systems RER on TTA and ETSI references in ISO/IEC 23000-9

9545 Convener Liaison to ISO/IEC JTC1 SC27 on Video Surveillance Application Format

9546 3DGC Text of ISO/IEC 14496-4:2004/ FDAM21 (Geometry and Shadow Conformance)

9547 3DGC Text of ISO/IEC 14496-5:2001/ FDAM13 (Geometry and Shadow RefSoft)

9548 Systems Response to SMPTE on Professional Archival MAF

9549 Convener 14.1.1 AHG on Requirements for MPEG Post Production Deliverable Formats

9550 Convener 14.1.2 AHG on MPEG Query Format

9551 Systems Request for minor enhancement of ISO/IEC 21000-8

9552 Systems Request for ISO/IEC 14496-1/Amd4

9553 Systems Text of ISO/IEC 14496-1/PDAM4 Registration Authority for OjectType and

53

StreamType Indication and SLConfig descriptor values

9554 Systems DoC of ISO/IEC 14496-4 FPDAM23 Syntherized Texture Conformance

54

Annex E – Systems report

Source: Olivier Avaro, Chair

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

Contributors: Ian S. Burnett, David Singer (Apple), Young-Kwon Lim (Net&TV), Jean Gelissen (Philips), Gero Baese (Siemens), Thomas Wiegand (HHI)

15 OverviewThe main outputs of the meeting from the MDS and Systems Sub-group perspective are:

No. TitleX 13818-1 MPEG-2 Systems9365 Text ISO/IEC 13818-1:2007/Cor.1 Reference to AVC standard9366 DoC of ISO/IEC 13818-1:2007/PDAM3 Carriage of SVC in MPEG-2 Systems9367 Text of ISO/IEC 13818-1:2007/FPDAM3 Carriage of SVC in MPEG-2 Systems9368 Text of ISO/IEC 13818-1:2007/Cor.2 WD1.0 related to the carriage of AVC X 14496-1 MPEG-4 Systems9552 Request for ISO/IEC 14496-1/Amd.49553 Text of ISO/IEC 14496-1/PDAM 4 Registration Authority for ObjectType and Streamtype

Indication and SLConfigValuesX 14496-4 Conformance testing9554 DoC on ISO/IEC 14496-4/FPDAM 23 Synthesized Texture Conformance9369 Text of ISO/IEC 14496-4/FDAM 23 Synthesized Texture Conformance9370 Text of ISO/IEC 14496-4/FDAM 24 File Format Conformance9371 DoC on ISO/IEC 14496-4/FPDAM 25 LASeR & SAF V1 Conformance9372 Text of ISO/IEC 14496-4/FDAM 25 LASeR & SAF V1 Conformance9373 Text of ISO/IEC 14496-4/FPDAM 26 Open Font Format Conformance9374 DoC on ISO/IEC 14496-4/PDAM 27 LASeR V2 Conformance9375 Text of ISO/IEC 14496-4/FPDAM 27 LASeR V2 ConformanceX 14496-5 Reference Software9376 Request for ISO/IEC 14496-5/Amd.14 Open Font Format Reference Software9377 Text of ISO/IEC 14496-5/PDAM14 Open Font Format Reference SoftwareX 14496-12 ISO Base Media File Format9378 Revised TuC on ISO/IEC 14496-129379 Guidelines for building on the Part 12 ISO Base Media File FormatX 14496-20 Lightweight Application Scene Representation9380 LASeR Requirements9381 DoC on ISO/IEC 14496-20/DCOR29382 Text of ISO/IEC 14496-20/COR29383 DoC on ISO/IEC 14496-20/FPDAM 2 (SVGT1.2 Support)9384 Text of ISO/IEC 14496-20/FDAM 2 (SVGT1.2 Support)9385 Text of ISO/IEC 14496-20:200x/FDIS (1st Ed. + Cor 1 + Amd.1 + Cor. 2)9386 IuC for LASeRX 15938-12 MPEG Query Format9340 DoC of ISO/IEC CD 15938-12 MPEG Query Format9341 ISO/IEC FCD 15938-12 MPEG Query FormatX 21000-5 Rights Expression Language

55

9343 Preliminary DoC on ISO/IEC 21000-5/FPDAM3 Open Release Content Profile9344 Request for change of title of ISO/IEC 21000-5/AMD39345 Study Text of ISO/IEC 21000-5/FPDAM3 Open Access Content Profile9346 MPEG-21 REL Profiles Software Implementation Plan v.8 X 21000-8 Reference Software9551 Request for minor enhancement of ISO/IEC 21000-89484 ISO/IEC 21000-8/PDAM1Reference SoftwareX 21000-9 MPEG 21 Mime Type9387 DoC on ISO/IEC 21000-9/ PDAM1 MP21 Mime Type9388 Text of ISO/IEC 21000-9/ FPDAM1 MP21 Mime TypeX 21000-15 Event Reporting9347 DoC on ISO/IEC 21000-15/PDAM1 Security in Event Reporting9348 ISO/IEC 21000-15/FPDAM1 Security in Event Reporting9349 DoC on ISO/IEC 21000-15/DCOR19350 ISO/IEC 21000-15/COR1 X 21000-18 Digital Item Streaming9351 DoC of ISO/IEC 21000-18/FPDAM1 Simple Fragmentation Rule9352 Text of ISO/IEC 21000-18/FDAM1 Simple Fragmentation RuleX 23000 General9421 MAF Overview Document9422 MAF Overview PresentationX 23000-4 Musical Slide Show Application Format9389 Text of ISO/IEC FCD 23000-4 Musical Slide Show 2nd Edition9390 Request for ISO/IEC 23000-4:200x/Amd.1 MSS Application Format Conf. and Ref. Software9391 Text of ISO/IEC 23000-4:200x/PDAM1 MSS Application Format Conf. and Ref. SoftwareX 23000-5 Media Streaming Application Format9353 DoC of ISO/IEC FCD 23000-5 Media Streaming Application Format9354 Request for change of title of ISO/IEC 23000-59355 Text of ISO/IEC FDIS 23000-5 Media Streaming Application FormatX 23000-6 Professional Archival Application Format9392 Requirements on Professional Archival Application Format9393 Text of ISO/IEC 23000-6/WD1.0 Professional Archival Application FormatX 23000-7 Open Access Application Format9356 Preliminary DoC of ISO/IEC FCD 23000-7 Open Release Application Format9357 Request for Change of Title of ISO/IEC 23000-79358 Study Text of ISO/IEC FCD 23000-7 Open Access Application FormatX 23000-8 Portable Video Application Format9394 DoC on ISO/IEC 23000-8/CD Portable Video Application Format9395 Text of ISO/IEC 23000-8/FCD Portable Video Application FormatX 23000-9 Digital Multimedia Broadcasting Application Format9396 DoC on ISO/IEC 23000-9/FCD (DMB Application Format)9397 Text of ISO/IEC 23000-9/FDIS (MAF Application Format)9398 Workplan for DMB Application Format Reference Software9544 RER on TTA and ETSI references in ISO/IEC 23000-9X 23000-10 Video Surveillance Application Format9399 Draft DoC on ISO/IEC CD 23000-10 (Video Surveillance Application Format)9412 Study Text of ISO/IEC CD 23000-10 (Video Surveillance Application Format)X 23000-11 Stereoscopic Video Application Format9413 Request for Subdivision of ISO/IEC 230009414 Text of ISO/IEC 23000-11/WD1.0 (Stereoscopic Video Application Format)X 23001-1 Binary MPEG Format for XML9479 Introduction to MPEG Binary XMLX 23001-3 IPMP XML Messages9415 DoC on ISO/IEC FCD 23001-3 (IPMP XML Messages)9416 Text of ISO/IEC FDIS 23001-3 (IPMP XML Messages)

56

X 23004-8 Reference Software9417 Study Text of ISO/IEC 23004-8/CD Reference Software and Conformance9418 M3W Reference Software and Conformance PlanX 29116-1 Media Streaming MAF Protocol 9419 DoC on Text of ISO/IEC FCD 29116-1 Media Streaming MAF Protocol9420 Text of ISO/IEC FDIS 29116-1/Media Streaming MAF ProtocolX Exploration9423 Content and Objectives : MXM – A project to exploit MPEG standards in tune with industry

practices and needs9424 Context and Objectives : Information exchange with Virtual Worlds 9425 Proposal for a new work item – Information exchange with Virtual Worlds9426 Context and Objectives : Framework for Representation of Sensory Effects Information9427 Call for Requirements on Framework for Representation of Sensory Effects Information9428 Context and Objectives : MPEG Post Production Deliverable Formats9429 Draft Requirements for MPEG Post Production Deliverable Formats9410 MPEG URI AssetsX Liaison9480 Response to DVB on File Format9481 Response to ITU IPTV FG on MPEG technology for IPTV9548 Response to SMPTE on Professional Archival MAF9545 Liaison to ISO/IEC JTC1 SC27 on Video Surveillance Application Format

16 General issues

16.1 GeneralThe meeting report from Lausanne has been approved.The following demonstrations have been made:

None.

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

2 1 2006 Amd.3 SVC in MPEG-2 Systems 07/07 07/10 08/042 1 2006 Cor.2 Transport of AVC

Specification07/10 08/07

4 1 200x Amd.4 Registration Authority 07/10 08/04 08/074 4 2007 Amd.26 Open Font Format

Conformance07/04 07/10 08/04

4 4 2007 Amd.27 LASeR Amd.1 Conformance

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

4 5 2007 Amd.14 Open Font Format Ref. Soft 07/10 08/04 08/10 09/014 5 2007 Amd.16 Symbolic Music Rep. Ref.

Soft06/10 07/01 07/07 08/01

4 5 2007 Amd.17 LASeR Ref. Soft 06/10 07/01 07/07 08/014 15 2005 Amd.2 SCV File Format Extensions 05/10 06/07 07/07 08/017 12 2008 1st Ed. MPEG Query Format 07/10 08/0421 5 200x Amd.3 Open Release Content

Profile08/01

21 8 200x Amd.1 Minor Enhancement 07/10 08/04 08/0721 9 200x Amd.1 MP21 Mime Type 07/04 07/10 08/0121 15 200x Amd.1 Security in Even Reporting 08/04

57

A 4 200x 2nd Ed. MSS MAF Conf. and Soft 07/07 07/10 08/01 08/04A 4 200x 2nd Ed. Protected Musical Slide

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

A 7 200x 1st Ed. Open Access Application Format

08/01

A 8 200x 1st Ed. Portable Video Player MAF 06/10 07/04 07/10 08/01A 10 200x 1st Ed. Video Surveillance MAF 07/04 07/07 08/01 08/07E 8 200x 1st Ed. Ref. Soft. and Conformance 07/01 07/07 08/01 08/07X 1 200x 1st Ed. MPEG eXtensible

MiddlewareTDB

58

16.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 ShenzhenB 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

59

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

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

60

16.4 Mailing Lists Reminder

Topic Information Kindly Managed by

General Systems

List

Liste Reflector : [email protected]:

http://lists.uni-klu.ac.at/mailman/listinfo/gen-sysmailto:[email protected]?subject=subscribe

List-Archive: http://lists.uni-klu.ac.at/pipermail/gen-sysList-Help: mailto:[email protected]?subject=help

University of Klagenfurt

BiM


http://lists.uni-klu.ac.at/mailman/listinfo/mpeg7-sysmailto:[email protected]?subject=subscribe

List-Archive: http://lists.uni-klu.ac.at/pipermail/mpeg7-sysList-Help: mailto:[email protected]?subject=help


File Format


http://lists.uni-klu.ac.at/mailman/listinfo/mp4-sysmailto:[email protected]?subject=subscribe

List-Archive: http://lists.uni-klu.ac.at/pipermail/mp4-sysList-Help: mailto:[email protected]?subject=help


LASeR


http://lists.uni-klu.ac.at/mailman/listinfo/mpeg-lasermailto:[email protected]?subject=subscribe

List-Archive: http://lists.uni-klu.ac.at/pipermail/mpeg-laserList-Help: mailto:[email protected]?subject=help


MAF

Liste Reflector : [email protected]:http://lists.uni-klu.ac.at/mailman/listinfo/maf-sysmailto:[email protected]?subject=subscribeList-Archive: http://lists.uni-klu.ac.at/pipermail/maf-sysList-Help: mailto:[email protected]?subject=help


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: [email protected]


61



http://lists.uni-klu.ac.at/mailman/listinfo/isoff-transport

mailto:[email protected]?subject=help


mailto:[email protected]?subject=subscribe

http://lists.uni-klu.ac.at/mailman/listinfo/maf-sys




http://lists.uni-klu.ac.at/pipermail/mpeg-laser



http://lists.uni-klu.ac.at/mailman/listinfo/mpeg-laser




http://lists.uni-klu.ac.at/pipermail/mp4-sys



http://lists.uni-klu.ac.at/mailman/listinfo/mp4-sys




http://lists.uni-klu.ac.at/pipermail/mpeg7-sys



http://lists.uni-klu.ac.at/mailman/listinfo/mpeg7-sys




http://lists.uni-klu.ac.at/pipermail/gen-sys



http://lists.uni-klu.ac.at/mailman/listinfo/gen-sys


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

16.5 FAQThe FAQ were updated as needed.

16.6 AOBNone.

17 MPEG-2 Systems (13818-1)

17.1 13818-1:2005 DCOR.1.2

17.1.1 Topics1. Reference to AVC

17.1.2 ContributionsM14793: Summary of Voting on ISO/IEC 13818-1:200X/DCOR 1.2 [SC 29 N 8698]. No comment. Document promoted to final stage.

Technical Work in Progress.

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

17.2.1 Topics2. Transport of Scalable Video Coding

17.2.2 ContributionsM14847, M14870, M14925, M14930 : All taken into account to produce specification text. Detailed disposition are listed below.

Uses of SVC in MPEG2-TS Applications:Backwards-compatible extensionRate shapingSelective encryption

FNB comments

1. SVC NAL units in base layer ES: NUT 14 adopted NUT 20 not agreed at this point. Needs to work out a clear proposal when multiple video descriptors are present in one elementary stream wrt their association to NAL units.

2. Add an additional descriptor to the AVC video descriptor that also carries the information carried in the SVC descriptor: Proposal: Split current SVC descriptor into AVC part and extension adopted

3. Editorial comments: not discussed, discretion given to the editors

62

http://lists.uni-klu.ac.at/mailman/private/isoff-transport/

General remark: Clarify the use of “defined” in amendment

GNB comments

1. Definition of video sub-bitstream : Not adopted. Instead the group decided to allow the NAL units that belong to temporal enhancements to be present in their own elementary stream. For that, the presence of DTS and PTS values is mandated. All NAL units that belong to the same AU have the same value of DTS and PTS.

2. Editorial commentsTechnical Work in Progress.

17.3 13818-1:2005 DCOR.2

17.3.1 Topics1. Coorigendum on the carriage of AVC

17.3.2 ContributionsM14875: USNB Contribution: issues relating to carriage of AVC (ISO/IEC 14496-10) bitstreams in MPEG-2 Systems streams. Noted. Decision to issue WD of Cor. To the Systems specification.


18 MPEG-4 Conformance (14496-4)

18.1 14496-4 Amd.23

18.1.1 Topics1. Synthesized Texture Conformance

18.1.2 ContributionsM14982: Editor's study of 14496-4:2004/PDAM.23 Synthesized Texture Conformance. Used as input to produce final text.M14818: Summary of Voting on ISO/IEC 14496-4:2004/FPDAM 23. No comment was made.


18.2 14496-4 Amd.24

18.2.1 Topics1. File Format Conformance

18.2.2 ContributionsM14812: Summary of Voting on ISO/IEC 14496-4:2004/FPDAM 24. No comment. Specification progressed to final stage. Good work, people!


63

18.3 14496-4 Amd.25 LASeR V1 Conformance

18.3.1 Topics1. LASeR Conformance

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


18.4 14496-4 Amd.26 Open Font Format Conformance

18.4.1 Topics2. Open Font Format Conformance

18.4.2 ContributionsM14809: Summary of Voting on ISO/IEC 14496-4:2004/PDAM 26. No comment. Document progressed to FPDAM.


18.5 14496-4 Amd.27 LASeR V2 Conformance

18.5.1 Topics1. LASeR V2 Conformance

18.5.2 ContributionsM14836 : Summary of Voting on ISO/IEC 14496-4:2004/PDAM 27. See DoC. Document progressed to FPDAM.


19 MPEG-4 Reference Software (14496-5)

19.1 14496-5 Amd.14

19.1.1 Topics1. Open Font Format Reference Software

19.1.2 ContributionsM14867 : Open Font Format Reference Software Implementation.


19.2 14496-5 Amd.16

19.2.1 Topics1. Symbolic Music Representation Reference Software

19.2.2 ContributionsNone.

64


19.3 14496-5 Amd.17

19.3.1 Topics1. LASeR Reference Software



20 ISO File Format (14496-12)

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

20.2 MPEG-2 Transport Streams in MP4 filesThe file format group is considering the storage of MPEG-2 transport streams in the ISO Base Media File Format family. Currently there are two specifications: the DMB MAF (ISO/IEC 23000-9) and the DVB proposal supplied in liaison. We welcome contributions on the harmonization of these in a general structure that can be adopted into an amendment of ISO/IEC 14496-12. The file format group believes that a hint track approach, as shown by these specifications, is right. The proposals should:a) provide a basis from which both the DMB MAF specifications and the DVB file format specifications could be derived, possibly by profiling the tools in the harmonized specification, and/or by extending it in non-conflicting and non-overlapping ways.b) consider specifically the needs of a transmission format, and a recording format.

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

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

20.5 14496-12/Amd.2

20.5.1 Topics1. Flute Hint Track

65

20.5.2 14966 Updated MPEG-2 TS for the DMB MAFThank you. There was concern expressed about the ‘offset’ fields in the sample entries, both defining offset ‘from where’ and also that that provided an unusual link between the sample entry and the stream. However, it seems that this method of storage is not needed for either PMT or OD, and therefore we could remove the modes using these offset fields.There was a minor comment on the duration field for one-sample TS storage (permitting but not requiring the value 0 for ‘unspecified duration’).

20.5.3 14897 (Apple) Deriving from part 12In MAF session Tuesday morning. Comments and improvements welcome. We might need text encouraging people not to copy the file format definitions, but instead just provide values for the parameters?There is an existing annex in the specification on this subject; that material should be incorporated into the white paper, and perhaps the white paper should be re-introduced into the specification by way of an upcoming amendment.

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

20.5.5 14905 (Var) Storage of XML and associated media resourcesWe think we can do this roughly as follows:inside meta-box

data references0 (self)1 #ffp(track_ID=2)2 #ffp(track_ID=3)

item location

10 dref index 1, offset=0, length=011 dref index 2, offset=0, length=0

item name

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

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

20.5.6 14896 (Apple) Composition and decoding timesThank you. The meeting points out that this box is still useful even with old-style unsigned CTS offsets. The editor to put this into the TuC for part 12,

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

66

We would like to incorporate 14496-12:2005 and Corrigenda 1 through 3 and Amendments 1 and 2 (these are all final or published), and make this 14496-12:2008, perhaps. There is a need for a new integrated edition, either with or without a re-structure.One idea is to split chapter 8 (box definitions), with separate chapters for files, movies, tracks, movie fragments, and so on.


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

21.1 14496-15:2004/Amd.2

21.1.1 Topics1. SVC File Format Extensions

21.1.2 15002 (Nokia) On the SVC File FormatThank you for the very detailed read. The editors should work together to provide an editor’s draft input to the next meeting, dealing with the editorial and consistency issues, and we understand Finland will submit an NB comment supporting such an editor’s draft.The basic technical changes outlined in the cover note seem acceptable.

21.1.3 12059 (Nokia) Buffering parameters in the AVC File FormatThis was held over from Busan. “12059 Storage of AVC buffering parameters in AVC file format

Ye-Kui WangMiska M. Hannuksela

Held over to next meeting to manage with the SVC file format, if that is an amendment. Align with 3GPP so we don’t have two slightly different ways to do the same thing in the industry.”Editors to incorporate this.

21.1.4 In EmailWe have some inconsistency with the alignment of extractors in time, in the text. From Karsten Gruenberg:

We found some inconsistency in the definition of the extractors and their alignment with other samples.In subclause A.6.1 (sample alignment of extractors) of w9283-svc-ff--avc-amd2-fpdam.doc,there is the following definition:Samples containing extractors _must_ be temporally aligned (in decoding time) with a sample in the track from which they extract. In contrast to that, Figure F.5 in the informative Annex F illustrates an example of 'overlapped samples' where the extractor at sample no. 1 is not aligned with any sample in the referenced track #0. This case typically shows up if an extractor references a layer representing a subset of the scalable bit stream at a lower frame rate. This may be a typical use case, thus it should not be restricted as done in A.6.1.

We suggest to change the text (paragraph 6. in subclause A.6.1) to:

All the tracks in the group sharing the same scalable base must share the same timescale, and samples that belong to temporal level zero and contain extractors must be temporally aligned (in

67

decoding time) with a sample belonging to temporal level zero in the track from which they extract. Samples belonging to other temporal levels may contain extractors referencing non-aligned samples indicated by the sample_offset field (as defined in subclause B.3).

Accordingly, the second hanging paragraph in B.3.3 (Semantics of the Extractor) should be changed to:

track_ref_index: Specifies the index of the track reference of type 'scal' to use to find the track from which to extract data. The sample in that track from which data is extracted is temporally aligned or nearest preceding in the media decoding timeline, adjusted by an offset given by sample_offset as specified below, with the sample containing the Extractor. The first track reference has the index value 1; the value 0 is reserved.

Editors should also handle this. This is indeed an error.


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

21.2.1 Topics1. MVC File Format Extensions

21.2.2 14898 (Apple) MVC File Format considerationsThis document raises, essentially, the high-level question: what are the specific problems and opportunities for the file-format level of MVC? We welcome more contributions asking questions at this level (and proposing answers).Discussion of this brought up the following:a) should the inter_view_dependency flag be reflected in the sample dependency table?b) would SP and SI pictures enable view switching and view ‘entry’ (random access)?c) how do we mark viewIDRs?No changes to the TuC at this meeting.Technical Work in Progress.

22 LASeR (14496-20)

22.1 14496-20/Amd. 2

22.1.1 Topics1. Lightweight Application Scene Representation (SGVT1.2 Support)

22.1.2 ContributionsM14780 : Ad Hoc Group on Scene Representation. Noted.M14814 : Summary of Voting on ISO/IEC 14496-20:2006/FPDAM 2. See DoC.M14852 : FNB comments on LASeR AMD2. See DoC.M14997 : Editor's study of LASeR FPDAM2. Taken as input to produce final text.

M14941 : Editorial Comments on LASeR 2nd Edition. Taken into account in the 2nd edition.


68

22.2 14496-20/Cor 2

22.2.1 Topics1. Profile Removal

22.2.2 ContributionsM14798 : Summary of Voting on ISO/IEC 14496-20:2006/DCOR 2 [SC 29 N 8704]. See DoC.M14995 : Editor's study of LASeR DCOR2. Taken as input for the production of the final document.


23 21000-9 MPEG-21 File Format

23.1 MPEG-21 File Format Amendment

23.1.1 Topics1. Mime Type

23.1.2 14799 Summary of votingAll approved. Good work, people!

23.1.3 14937 Austria NB CommentsAustria is an O-member and cannot submit comments. However, they have some comments, which were well received and incorporated into the next balloted document. We need a 3-letter file extension; “m21” seems to be available, even if it is associated currently with star clusters and assault rifles.

24 21000-14 Conformance

24.1 MPEG-21 File Format Conformance

24.1.1 Topics1. Conformance


25 MPEG-A MAF (23000)

25.1 23000-4 Musical Slide Show MAF

M14782: Ad Hoc Group on MAF Under Development in Systems. Noted.M14897: Guidelines for building on the Part 12 ISO Base Media File Format Specification. Noted. The Systems subgroup thanks David Singer for contributing this document which would be used as reference for further using the ISO Base File Format.

69

25.2 23000-4 Musical Slide Show MAF

25.2.1 Topics1. Protected Musical Slide Show MAF

25.2.2 ContributionsM14835 : Summary of Voting on ISO/IEC CD 23000-4 2nd Edition. No comment. Document was promoted to FCD stage.

M14922 : Proposed text of ISO/IEC 23000-4/PDAM1 Musical slide show MAF: Conformance and Reference software. Used as the basis to produce PDAM text.


25.3 23000-8 Portable Video Player MAF

25.3.1 Topics1. Portable Video Player MAF

25.3.2 ContributionsM14805 : Summary of Voting on ISO/IEC CD 23000-8 [SC 29 N 8726]. See DoC.M14923: Proposed text of ISO/IEC 23000-8/FCD Portable video player MAF. Taken as starting point for producing FCD text.M14950: A proposal on MPEG-7 metadata structure for Portable Video Player MAF. Accepted.


25.4 23000-9 Digital Multimedia Broadcasting MAF

25.4.1 Topics1. Digital Multimedia Broadcasting MAF

25.4.2 ContributionsM14845 : Summary of Voting on ISO/IEC FCD 23000-9. See DoC.M14963 : (Editors' Input) Proposed Text of ISO/IEC 23000-9 FDIS MAF for DMB. Taken as input to produce FDIS text.M14968: Updated schema and xml samples for the restricted TV-Anytime metadata in ISO/IEC 23000-9 MAF for DMB. Accepted an integratd in FDIS.


25.5 23000-10 Video Surveillance MAF

25.5.1 Topics1. Video Surveillance MAF 1st Edition

25.5.2 ContributionsM14844, M15015, M15019: Summary of Voting on ISO/IEC CD 23000-10. See DoC (including as well late comments from GNB).M14951: A proposal on MPEG-7 metadata structure for Video Surveillance MAF. Integrated in text of the FCD.M14894: Visual Surveillance Multimedia Application Format: Summary Document. Noted.M14892: Visual Surveillance Multimedia Application Format: Reference Software. Noted. Will be taken as starting point for production of reference software.

70


26 MPEG-B

26.1 23001-1 Binary Format Cor.2

26.1.1 Topics1. Misc. Editorial Corrections on MPEG-B Part 1



26.2 23001-3 Binary to XML Mapping of IPMP-X

26.2.1 Topics1. Binary to XML Mapping of IPMP-X

26.2.2 ContributionsM14817: Summary of Voting on ISO/IEC FCD 23001-3. All comments processed and incorporated in text of FDIS.M14948 : Editor Study on ISO/IEC 23001-3 IPMP XML Messages. Taken as a start for the publication of FDIS.


27 MPEG-E Multimedia Middleware (23004)

27.1 Multimedia Middleware

27.1.1 Topics1. MPEG Multimedia Middleware

27.1.2 ContributionsM14838: Summary of Voting on ISO/IEC CD 23004-8. No comment. A study was produced at the Shenzhen meeting.


71

28 Supplementary Media Technology (29116-1)

28.1 Media Streaming MAF Protocols

28.1.1 Topics1. Media Streaming MAF Protocols

28.1.2 ContributionsM14820 : Summary of Voting on ISO/IEC FCD 29116-1. See DoC.M14947 : Editor Study on ISO/IEC 29116-1 Media Streaming MAF Protocols. Taken as a starting point to produce final text.


29 Requirements and Exploration

29.1 MAFMAF Overview :Document reviewed and updated.

M14914: Revised requirements of the Stereoscopic MAF. Taken as input to update the MAF Overview document. M14915: Proposal for technical specification of Stereoscopic MAF. Noted.

M14940: Application scenarios and derived requirements of Color reproduction MAF. Proposal to extend MPEG-7 DS to improve color reproduction (to be dealt by the Video group). Possibility to extend the file format to describe where color information is stored in a codec independent fashion.

29.2 IPTVM14881 : LASeR in IPTV. Requirement has been accepted and will be document in the requirement document. Before starting technical work on the activity, the Systems group wants to build a bigger picture of what will be the value proposition of MPEG in the IPTV space.

29.3 Standing DocumentsM14784: MPEG Profiles and Levels URI. Taken as input to produce standing document on MPEG URI Assets.

29.4 New Proposals

29.4.1 Proposal for Standardization of Service Framework of Device-Rendered SensibleM14900: A Service Framework of Device-Rendered Sensible Media for Enriched Experiences. Proposal for DCI Schema and DRESS Media Application Format. Decision to start an activity in this area. Taken as a basis to produce a document describing: Context, Objectives, Use Cases, and Requirements. The document will also mention the various standardization bodies acting in this space and with whom we may consider to liaise.

M14976: Device Control Information Metadata Schema for Device-Rendered Sensible Media. Noted.

72

29.4.2 Proposal for Standardization of Content Deliverables for Professionally Produced Film, TV, VideoM14895: Proposal for Standardization of Content Deliverables for Professionally Produced Film, TV, Video. Taken as a basis to produce a document describing: Context, Objectives, Use Cases, and Requirements.

29.4.3 Proposal for Standardization of Interfaces with Virtual Worlds Production of a Context, Objectives, Use cases and requirements document from previous inputs.

30 LiaisonM14912: Liaison Statement from DVB [SC 29 N 8823]. See liaison response to DVB.M14803: Liaison Statement from ITU-T IPTV Focus Group (FG IPTV) [SC 29 N 8711]. See liaison response to IPTV.

31 Detailed Notes on MDS Related Documents

These contemporaneous notes summarise the input documents submitted to the MDS subgroup. These were discussed on the Monday and Tuesday of the MPEG meeting. Details of related activities and on-going activities can be found in the Systems subgroup report for the meeting.

MDS recommends that work on the review of MPEG-21 Digital Items should cease at this meeting. However it is noted that future work in Systems or new industry driven requirements may lead to the work area again becoming active.

OR MAF (14h00 - 15h00) MDS Room Tokyo




InputsThese contributions are the NB comments and a liaison from DMP requesting a name change for the MAF.

ActionsMDS accepted the proposal of a name change and concluded that ‘Open Access MAF’ be used as the MAF name in future.DoCs to be produced and FDIS of Open Access MAF, AMD/3 of the OAC Profile of REL will be output documents. 1500

3 Florian Schreiner Editor’s Study Text of ISO/IEC FCD 23000-715004 Florian Schreiner Contribution to MPEG-21 REL ORC Profile Ref SW: REL

73













Interpreter


InputsChanges were made to the DID section – One Component in an Item, One resource within a Component and Component was removed from Descriptor. Examples were added and minor editorial work was carried out.The software modules for the profile were described and were accepted as Reference software for the REL profile required for this MAF. The code is written in Java and uses the JAXB framework. This software will also be integrated to the MPEG-21 REL software and added to the Amendment raised at this meeting.ActionsMDS accepted the changes to the document and the new reference software modules. The full reference software for the MAF will be available at the next meeting. MPEG-7 Query Format (15h00 - 17h00) MDS Room Tokyo


14871Miran Choi Hee-Cheol Seo Hyunki Kim Myung-Gil Jang Soojong Lim Jeong Heo Kyoungro Yoon

Proposal for System Messages in MPEG-7 Query Format

14872Miran Choi Hee-Cheol Seo Hyunki Kim Myung-Gil Jang Soojong Lim Jeong Heo Kyoungro Yoon

Proposal for Fieldtype ID in MPEG-7 Query Format

14902Hee-Cheol Seo Miran Choi Hyunki Kim Myung-Gil Jang Soojong Lim Jeong Heo Kyoungro Yoon


14919 Mario Doeller Matthias Gruhne Ingo Wolf Heiko Studt


14921 Mario Doeller Matthias Gruhne Ingo Wolf

Enhancement of QueryByExample Type in MPQF

14924Ingo Wolf Rubén Tous Giovanni Cordara Jaime Delgado Mario Doeller Matthias Gruhne


14946 Masanori Sano Hideki Sumiyoshi Nobuyuki Yagi

Some thoughts on data model for MPQF

14957Rubén Tous Giovanni Cordara Jaime Delgado Gianluca Francini


14969 Matthias Gruhne Andre Begau

Suggestions of a new QueryByXQueryType

14970 Matthias Gruhne Mario Doeller Info Wolf Andre Begau



More complete details on these documents and treatment are in the AHG/BOG report for MPEG Query Format (attached).

InputsFirstly MDS considered the National Body comments on the CD.

Actions

74
































MDS is removing all references to the MPEG-7 schema in MQF. Other changes are in the DoC but the latter is important for other MPEG-7 applications – the schema is too complex touse in its entirety or for small sets of description tools.

InputsM14969 was then considered. This is an input from a European Project that wishes to use MQF. They propose QuerybyExtendedXQuery which allows complete XQuery usage in MQF.

ActionsConcerns were expressed regarding interoperability. This is because the output query format is not used. It was felt that this is a fundamental change in the architecture of MQF. It was felt that this is a repeat of original discussions on the XQuery based proposal for MQF. It was suggested that if there are Amendments to MQF that this functionality might be useful in an interoperable form. The advantage of MQF is the ability to do Similarity searches.

Inputsm14902 & m14957

ActionsThese two proposals were integrated and a Join proposal will be integrated into the standard

Inputm14871

ActionThis proposal was modified in a minor way by the AHG and then incorporated into the FCD

Inputm14872 & m14970

ActionThese two documents propose minor changes in the output field format of MQF. For m14872, two types – ID and IDRef were created to avoid cross referencingFor m14970, extra examples etc will be added to the standard.

InputM14919 discusses naming inconsistencies and decoupling

ActionDecoupling is removed and inconsistencies were removed. The data model etc will be cleaned up.

14990

Kenneth Vermeirsch Saar De Zutter Rik Van de Walle


InputA JAVA 5 implementation of a UCD parser. A demo project parses a DI file and then serialises it back to std out. It also parses a UCD-QoS file and operates on that. The authors showed a demo.ActionMDS decided to add this module to the MPEG-21 Reference software – it will be added to teh amendment being raised at this meeting.1499

1 Saar De Zutter Jan De Cock Rik Van de Walle

Contribution to summary and 1-pager of Conformance: MPEG-21

75





14992 Saar De Zutter Jan De Cock Rik Van de Walle

Update to summary and 1-pager of Reference Software: MPEG-21

InputTwo contributions and updates to the MPEG web site which provides information on MPEG standards.

ActionMDS recommended these be added to the MPEG Technologies web site

15014 Gerrard Drury Joseph Thomas-Kerr

Contribution to ISO/IEC 21000-18 MPEG-21 DIS Reference Software

InputThis input provides reference and utility software modules for MPEG-21 Digital Item Streaming (part 18). The modules also cover the amendment (Simple Fragmentation Rule).

ActionThese modules will be added to the current amendment of the reference software.

14768 Jaime Delgado Marc Gauvin

AHG on Requirements for Rights Ontology

15016 Niels Rump Comments on N9325

InputThere were two inputs – the AHG report (presented by Ruben Tous) and input 15016 presented by Xin Wang.The primary outcome of the AHG was that machine readable representations are a useful part of semantic metadata standards. M15016 summarised the RDD status in MPEG-21. The comments basically summarised are that requirements can be met by RDD/DII or are not relevant. The machine readability was discussed previously and is not advisable because of immaturity of tools e.g. reasoners.

Action1. Invite MPEG experts to submit inputs to the next meeting on Machine Readable

representations of the ISO/IEC 21000-6 Rights Data Dictionary.

2. We will probably continue the ‘ontology’ activity as an AHG on Requirements for Media Value Chain Ontologies. MDS requested Ruben Tous to clarify possible participation with current Chairs of the AHG. We will revisit this matter when we have a reply (on Thursday).

14895 Julie Lofton

Proposal for Standardization of Content Deliverables for Professionally Produced Film, TV, Video

InputThis input proposes standardisation in the area of Production metadata and packages for information related to TV and movie production.ActionThe proposal was well received and was discussed in 2 sessions. It was determined that the work is distinct from the professional archival work. It was suggested that the work become MPEG-

76












M(ovie). MDS/Systems group will work on a full set of Requirements for the output of this meeting.

14943

Noboru Harada Takehiro Moriya Yutaka Kamamoto Responce to CfR of PA-MAF

14954 Hendry Houari Sabirin Munchurl Kim Response to Call for Requirements on PA-MAF

14955

Hendry Houari Sabirin Munchurl Kim Noboru Harada Takehiro Moriya

Technical Contribution to Development of PA-MAF

14944

Noboru Harada Takehiro Moriya Yutaka Kamamoto Proposed text to WD of PA-MAF


InputM14943 -14955 are responses to the Call for Requirements and will be used by a break out group to create a set of Requirements. M14786 was considered and the relevance of the WG1 work to MPEG’s was noted. Actionm14943 -14955 will be used by a break out group to create a set of Requirements. MDS will prepare (in a BoG) a liaison to WG1 regarding potential joint work and them joining a MPEG AHG. Further, MPEG experts will be attending the next JPEG meeting in Kobe where WG1 will meet next.

14893

Houari Sabirin James Annesley Munchurl Kim James Orwell

Visual Surveillance Multimedia Application Format: MPEG-7 Profile

InputThis input looks at the Visual Surveillance MAF usage of MPEG-7.ActionIt seems that a lot of this MAF is solving issues with the binary file format that would be better solved using Digital Item Technology.

14900

Sanghyun Joo Bumsuk Choi Haeryong Lee Kwangro Park Munchurl Kim Jaegon Kim

A Service Framework of Device-Rendered Sensible Media for Enriched Experiences

InputThis input was held over to the joint Systems/MDS activity sessions on Wednesday afternoon.

MDS activities in the latter half of the Week

Two MDS activities occurred on the Thursday morning – the first a discussion on the Rights Ontology activity and the second preparation of Requirements for Post Production Deliverables (see m14895). The former resulted in a modification of the work and the creation of the new AHG on Media Value Chain Ontologies (see MPEG outputs). The latter work generated a set of Draft requirements for the post-production work (see output documents from Systems).

77












32 Latest References and Publication Status

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 11 ISO/IEC 13818-1:2003 (IPMP on 2) N5607 03/03 Pattaya Published 2003/12 Proposed

78

4 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 Hangzhou

COR ITTF to be published N/A

79

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


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


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


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


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


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


4 5 ISO/IEC 14496-1:200x/Amd.12 (File Format) N9020 07/04 San Jose 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 Redmond

FDAM ITTF Integration in 1st

Ed.Proposed

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

FDAM 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 N8657 06/10 FDAM ITTF TBP80

Representation Hangzhou4 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


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.1 (Description of timed metadata)

N8659 06/10 Hangzhou

FDAM ITTF 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


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 Editing

N/A

4 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 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

81

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


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

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

FDIS ITTF FDIS 05/01/21 Done

21 16 ISO/IEC 21000-16 (MPEG-21 Binary Format) N7247 05/04 Busan FDIS ITTF FDIS 05/04/22 TBPA 1 ISO/IEC 23000-4 (Musical Slide Show MAF) N9037 07/04 San Jose FDIS ITTF TBPA 1 ISO/IEC 23000-9 (Digital Multi. Broadcasting MAF) N9397 07/10

ShenzhenFDIS 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


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

N9049 07/04 San Jose COR ITTF N/A

82

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


B 2 ISO/IEC 23001-1 (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 Marrakech

FDAM ITTF N/A

E 3 ISO/IEC 23008-3 Component Model N8894 07/01 Marrakech

FDAM 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

83

33 Resolutions of Systems

Cf. WG11 resolution.

34 Contributions Reviewed by the Systems Subgroup

N° Title Authors14780 Ad Hoc Group on Scene Representation Young-Kwon Lim

Jean Lefeuvre 14781 Ad Hoc Group on MPEG File Formats David Singer14782 Ad Hoc Group on MAF Under Development in

SystemsYoung-Kwon Lim Hui Yong KimJean Cha

14784 MPEG Profiles and Levels URI Sylvain Devillers14793 Summary of Voting on ISO/IEC

13818-1:200X/DCOR 1.2 [SC 29 N 8698]SC 29 Secretariat

14798 Summary of Voting on ISO/IEC 14496-20:2006/DCOR 2 [SC 29 N 8704]

SC 29 Secretariat

14799 Summary of Voting on ISO/IEC 21000-9:2005/PDAM 1 [SC 29 N 8705]

SC 29 Secretariat

14799 Summary of Voting on ISO/IEC 21000-9:2005/PDAM 1 [SC 29 N 8705]

SC 29 Secretariat

14803 Liaison Statement from ITU-T IPTV Focus Group (FG IPTV) [SC 29 N 8711]

FG IPTV via SC 29 Secretariat





14805 Summary of Voting on ISO/IEC CD 23000-8 [SC 29 N 8726]

SC 29 Secretariat

14809 Summary of Voting on ISO/IEC 14496-4:2004/PDAM 26

SC 29 Secretariat

14812 Summary of Voting on ISO/IEC 14496-4:2004/FPDAM 24

SC 29 Secretariat

14814 Summary of Voting on ISO/IEC 14496-20:2006/FPDAM 2

SC 29 Secretariat

14817 Summary of Voting on ISO/IEC FCD 23001-3 SC 29 Secretariat14818 Summary of Voting on ISO/IEC

14496-4:2004/FPDAM 23SC 29 Secretariat

14820 Summary of Voting on ISO/IEC FCD 29116-1 SC 29 Secretariat14825 Summary of Voting on ISO/IEC

14496-4:2004/FPDAM 25SC 29 Secretariat

14835 Summary of Voting on ISO/IEC CD 23000-4 2nd Edition

SC 29 Secretariat

14836 Summary of Voting on ISO/IEC 14496-4:2004/PDAM 27

SC 29 Secretariat

84

N° Title Authors14838 Summary of Voting on ISO/IEC CD 23004-8 SC 29 Secretariat14844 Summary of Voting on ISO/IEC CD 23000-10 SC 29 Secretariat14845 Summary of Voting on ISO/IEC FCD 23000-9 SC 29 Secretariat14847 Summary of Voting on ISO/IEC

13818-1:200X/PDAM 3SC 29 Secretariat

14847 Summary of Voting on ISO/IEC 13818-1:200X/PDAM 3

SC 29 Secretariat

14852 FNB comments on LASeR AMD2 Jean-Claude Dufourd14867 Open Font Format Reference Software

ImplementationSimon DanielsVladimir Levantovsky

14870 On SVC over MPEG 2 Transport Stream Thomas SchierlThomas Wiegand

14870 On SVC over MPEG 2 Transport Stream Thomas SchierlThomas Wiegand

14875 USNB Contribution: issues relating to carriage of AVC (ISO/IEC 14496-10) bitstreams in MPEG-2 Systems streams

Andy Tescher for USNB

14875 USNB Contribution: issues relating to carriage of AVC (ISO/IEC 14496-10) bitstreams in MPEG-2 Systems streams

Andy Tescher for USNB

14881 LASeR in IPTV Seoyoung Hwang Jaeyeon SongYoung-Kwon Lim

14892 Visual Surveillance Multimedia Application Format: Reference Software

James AnnesleyJames Orwell

14894 Visual Surveillance Multimedia Application Format: Summary Document

James OrwellJames Annesley

14895 Proposal for Standardization of Content Deliverables for Professionally Produced Film, TV, Video

Julie Lofton

14896 Relating Composition and Decoding Times in ISO Files

David Singer

14897 Guidelines for building on the Part 12 ISO Base Media File Format Specification

David Singer

14897 Guidelines for building on the Part 12 ISO Base Media File Format Specification

David Singer

14898 On the MVC file format David Singer14899 Video depth and parallax in ISO files David Singer14900 A Service Framework of Device-Rendered

Sensible Media for Enriched ExperiencesSanghyun Joo et al.

14905 Storage of XML documents and associated media resources in the ISO file format

Blagica Jovanova Cyril Concolato Jean Le FeuvreMarius Preda

14912 Liaison Statement from DVB [SC 29 N 8823] SC 29 Secretariat14912 Liaison Statement from DVB [SC 29 N 8823] SC 29 Secretariat14912 Liaison Statement from DVB [SC 29 N 8823] SC 29 Secretariat14914 Revised requirements of the Stereoscopic MAF Next Generation Broadcasting

Forum

85







N° Title Authors14915 Proposal for technical specification of

Stereoscopic MAFNext Generation Broadcasting Forum

14922 Proposed text of ISO/IEC 23000-4/PDAM1 Musical slide show MAF: Conformance and Reference software

Hyouk Jean ChaTae Hyeon KimJisoo Hong

14923 Proposed text of ISO/IEC 23000-8/FCD Portable video player MAF

Hyouk Jean ChaTae Hyeon KimHerbert Thoma

14925 On transport of SVC over MPEG-2 TS Bertrand BerthelotVincent Bottreau

14925 On transport of SVC over MPEG-2 TS Bertrand BerthelotVincent Bottreau

14930 On Transport of Scalable Video over MPEG-2 TS Fons BrulsLincoln Lobo

14930 On Transport of Scalable Video over MPEG-2 TS Fons BrulsLincoln Lobo

14937 Austrian NB comments on ISO/IEC 21000-9/PDAM

Chistian Timmerer

14940 Application scenarios and derived requirements of Color reproduction MAF

Sangkyun Kim

14941 Editorial Comments on LASeR 2nd Edition Jihun ChaInjae LeeKyungAe MoonYoung-kwon Lim

14947 Editor Study on ISO/IEC 29116-1 Media Streaming MAF Protocols

Hyon-Gon ChooFilippo ChiariglioneNaito Joji

14948 Editor Study on ISO/IEC 23001-3 IPMP XML Messages

Hyon-Gon ChooFilippo Chiariglione

14950 A proposal on MPEG-7 metadata structure for Portable Video Player MAF

Ryoma Oami

14951 A proposal on MPEG-7 metadata structure for Video Surveillance MAF

Ryoma Oami

14963 (Editors' Input) Proposed Text of ISO/IEC 23000-9 FDIS MAF for DMB

Hui Yong KimHyon-Gon ChooMunchurl Kim

14966 Updated MPEG-2 TS Encapsulation Method for ISO/IEC 23000-9 MAF for DMB

Hui Yong KimMyungSeok KiGun BangYong Han Kim

14968 Updated schema and xml samples for the restricted TV-Anytime metadata in ISO/IEC 23000-9 MAF for DMB

Hui Yong KimSeung Jun YangHeekyung LeeMunchurl Kim

14976 Device Control Information Metadata Schema for Device-Rendered Sensible Media

B.S. Choi et al.

14982 Editor's study of 14496-4:2004/PDAM.23 Synthesized Texture Conformance

Birman

14995 Editor's study of LASeR DCOR2 Jean-Claude Dufourd

86












N° Title Authors14997 Editor's study of LASeR FPDAM2 Jean-Claude Dufourd15002 On the SVC file format Ye-Kui Wang

Miska M. Hannuksela15013 CoSME Overview Takuyo Kogure

Kohtaro Asaion behalf of DECSDP

15015 GNB comments on ISO/IEC CD 23000-10 Gero Bäse on behalf of GNB15019 UK NB comments on ISO/IEC CD 23000-10 Jim Aldridge

35 Contributions Reviewed by the MDS Subgroup

N° Title Authors14769 Kyoungro Yoon Mario Doeller AHG on MPEG Query Format14770 Giovanni Cordara Gerrard Drury AHG on Review of the MPEG-

21 DI

14859 Christian Timmerer on behalf of the CE Report of Core Experiment on Digital Item Semantics

14967 Giovanni Cordara Gerrard Drury Review of CE on DI Semantics14807 SC 29 Secretariat Summary of Voting on ISO/IEC

21000-15:2006/DCOR 114834 SC 29 Secretariat Summary of Voting on ISO/IEC

21000-15:2006/PDAM 114841 SC 29 Secretariat Summary of Voting on ISO/IEC

21000-18/FPDAM 114937 Christian Timmerer (on behalf of Austrian NB) Austrian NB comments on

ISO/IEC 21000-9/PDAM 114938 Christian Timmerer (on behalf of Austrian NB) Austrian NB comments on

ISO/IEC 21000-15/DCOR 115003 Florian Schreiner Editor’s Study Text of ISO/IEC

FCD 23000-715004 Florian Schreiner Contribution to MPEG-21 REL

ORC Profile Ref SW: REL Interpreter






14871 Miran Choi Hee-Cheol Seo Hyunki Kim Myung- Proposal for System Messages

87















































mailto:??


mailto:??



Gil Jang Soojong Lim Jeong Heo Kyoungro Yoon in MPEG-7 Query Format14872 Miran Choi Hee-Cheol Seo Hyunki Kim Myung-

Gil Jang Soojong Lim Jeong Heo Kyoungro Yoon Proposal for Fieldtype ID in MPEG-7 Query Format

14902 Hee-Cheol Seo Miran Choi Hyunki Kim Myung-Gil Jang Soojong Lim Jeong Heo Kyoungro Yoon


14919 Mario Doeller Matthias Gruhne Ingo Wolf Heiko Studt


14921 Mario Doeller Matthias Gruhne Ingo Wolf Enhancement of QueryByExample Type in MPQF

14924 Ingo Wolf Rubén Tous Giovanni Cordara Jaime Delgado Mario Doeller Matthias Gruhne


14946 Masanori Sano Hideki Sumiyoshi Nobuyuki Yagi Some thoughts on data model for MPQF

14957 Rubén Tous Giovanni Cordara Jaime Delgado Gianluca Francini


14969 Matthias Gruhne Andre Begau Suggestions of a new QueryByXQueryType

14970 Matthias Gruhne Mario Doeller Info Wolf Andre Begau



14962 Filippo Chiariglione Hyon-Gon Choo Editors Study of ISO/IEC 23000-5 Media Streaming Player


14990 Kenneth Vermeirsch Saar De Zutter Rik Van de Walle


14991 Saar De Zutter Jan De Cock Rik Van de Walle Contribution to summary and 1-pager of Conformance: MPEG-21

14992 Saar De Zutter Jan De Cock Rik Van de Walle Update to summary and 1-pager of Reference Software: MPEG-21

15014 Gerrard Drury Joseph Thomas-Kerr Contribution to ISO/IEC 21000-18 MPEG-21 DIS Reference Software

14768 Jaime Delgado Marc Gauvin AHG on Requirements for Rights Ontology

88












































Annex F – Video report

Source: Jens-Rainer Ohm, Gary J. Sullivan, Marco Mattavelli

1 MPEG-4 Visual Simple Profile Level 6The specification text and conformance part related to the new level 6 (720p resolution) of MPEG-4 Visual Simple Profile have progressed as expected. No comments were made by NBs, but minor editorial improvements were made based on editors’ input.

Documents reviewed:



15017 Justin Ridge, Jani Lainema, Soren Friis

Proposed text of ISO/IEC 14496-2:2004/FDAM4 Simple Profile Level 6

15018 Justin Ridge, Jani Lainema, Soren Friis

Proposed text of ISO/IEC 14496-4:2004/FDAM28 Visual Simple Profile Level 6 Conformance Testing

Documents approved:No. Title TBP Available

14496-2 Visual9432 Text of ISO/IEC 14496-2:2004/FDAM4 Simple Profile Level 6 N 07/11/029438 Text of ISO/IEC 14496-4:2004/FDAM28 Visual Simple Profile

Level 6 Conformance TestingN 07/11/02

2 MPEG-4 Video Conformance CorrigendaCorrigenda related to some erroneous bitstreams and misplacements between the 2004 edition and Amd.1 were progressed. No NB comments had been received.

Documents reviewed:




14496-4 Conformance testing9436 Text of ISO/IEC 14496-4:2004/COR4 N 07/11/029437 Text of ISO/IEC 14496-4:2004/Amd.1/COR2 N 07/11/02

89

3 Video Standards Support for larger FormatsA request for support of larger formats in existing video standards (13818-2, 14496-2, 14496-10) was made by the JNB (M14863). It is mentioned that formats such as 1920x1080 with up to 120/240 fps progressive, 4kx2k/60p, 8kx4k/60p are being prepared/discussed in industry and standardization bodies such as SMPTE. It should be avoided that proprietary definitions appear in the market, and it was therefore suggested MPEG should start consideration of defining additional profiles/levels rather soon.

In the subsequent discussion, it was emphasized that the technical specification of levels requires definition of other aspects in addition to supported frame sizes and frame rates. In terms of minimizing decoder complexity, parameters such as maximum allowable buffer sizes, bit rates of the compressed representation, restrictions on slice structure use, or restrictions on specific tools are also important and require careful consideration (e.g. to support parallel decoding of large frame sizes). Some of these values may also be different for consumer or professional applications. National bodies are therefore requested to provide more information toward specification of such parameters. This could best be studied on the basis of implementation plans and use cases. Timelines and expectations for appearance of such high-resolution formats in the market would be helpful to allow possible extension of standards in a timely fashion.

More concrete proposals were made as follows:M14868: Propose to define support for 1920x1080/60p. It is mentioned that the demand for MPEG-2 comes in particular by software-based solutions where AVC may not be usable for complexity reasons. Further application examples could be camcorders, eventually distribution. Clarifications were requested on the following issues:

- Should there be a limitation of not supporting interlaced tools at that level? - More clarity about the application scope and industry support (currently one company only)

would be desirable- Further study on possibly supporting higher frame rates.

M14869: MPEG-4 simple studio profile currently supports up to 1080/60p (level 4). A request was made to define new levels 5 and 6, supporting 4KxK/24p and /60p, respectively. Furthermore, in level 4, it was suggested that the maximum bit rate should be reduced to 1.35 Gbps (from currently 1.8 Gbps). In general, it is reportedly obvious that these larger formats are needed in professional applications that are targeted by the studio profiles. The following comment was made: It would be useful to restrict frame sizes to a certain minimum frame height (current MPEG-4 Visual would allow to have 16-pixel high frames, which would impose overly burdens on the padding process in decoders). It was therefore decided to issue a PDAM on new levels (and another one on related conformance), as well as a DCOR on the reduced bit rate of level 4.

M14890: This contribution is less concrete in requesting technical specifications than the two previous ones. The proponent mentions that current consideration is introduction of higher resolution formats (4Kx2K being the first beyond 1080p) in the consumer markets not earlier than 2011, and 8Kx4K even beyond that time. It was raised during the discussion that AVC already has 3 top levels for which nobody has implemented decoding devices yet. MPEG&JVT are interested to hear more about such developments, but currently it appears too early to go for a concrete definition of new levels.

Documents reviewed:14863 JNB JNB comment on video coding standards for

beyond HDTV applicationsThe video subgroup thanks the JNB for the

90

comments on developing video coding standards for beyond current HDTV capabilities. We are always prepared to extend existing standards by specifying additional profiles and levels in a timely fashion to appropriately serve industry and application needs. However, the technical specification of levels requires definition of other aspects in addition to supported frame sizes and frame rates, which could simply be drawn from specifications of other standardization bodies such as ITU-R and SMPTE. In terms of minimizing decoder complexity, parameters such as maximum allowable buffer sizes, bit rates of the compressed representation, restrictions on slice structure use, or restrictions on specific tools are also important and require careful consideration. We therefore request national bodies to provide more information toward specification of such parameters. This could best be studied on the basis of implementation plans and use cases. We would further be interested to learn more about the timelines and expectations for appearance of such high-resolution formats in the market. Regarding particular proposals on levels for higher-resolution formats, WG 11 has started work on one corrigendum and one amendment of ISO/IEC 14496-2 (to define and correct Simple Studio Profile levels 4-6).

14868 Teruhiko Suzuki Proposal of new level for MPEG-2 video

14869 Teruhiko Suzuki Proposal of new levels for MPEG-4 visual studio profile

14890(=JVT-Y035)

Yukihiro Nishida Request for extending the levels of MPEG4 AVC


14496-2 Visual9434 Request for ISO/IEC 14496-2:2004/Amd.5 N 07/10/269435 Text of ISO/IEC 14496-2:2004/PDAM5 Simple Studio Profile

Levels 5 and 6N 07/11/09

9439 Request for ISO/IEC 14496-4:2004/Amd.35 N 07/10/269440 Text of ISO/IEC 14496-4:2004/PDAM35 Simple Studio Profile

Levels 5 and 6 Conformance TestingN 07/11/09

4 Development of AVC The video subgroup jointly approved the ISO standard related output documents that were produced during the 25th JVT meeting which was held in parallel. Important work items in this context were as follows

– SVC verification tests– Update of MVC PDAM

91

– Preparation of software and conformance PDAM for New Professional Profiles– Preparation of software and conformance PDAM for Scalable Video Coding

Regarding SVC verification tests, a first round of testing was performed prior to the Shenzhen meeting, showing promising results for the test cases of Scalable High and Scalable High Intra profiles, particularly– same visual quality with only slight increase (5-10 %) in data rate as compared to non-scalable

coding at same (highest) rate and resolution;– clear decrease in data rate (up to 40 %) as compared to simulcast transmission with different

spatial resolutions.Those results are included in the draft test report (N9482). For the testing of the scalable baseline profile (both communication and broadcast scenarios), as well as cases of combined scalability in scalable high profile, further tests will be performed until the next meeting (see N9483), where the final test report will be issued.

Documents reviewed:




15007

Gary J. Sullivan, Jens-Rainer Ohm,Thomas Wiegand, Ajay Luthra

Meeting Report of the 24th JVT Meeting (29 June – 5 July, 2007, Geneva, CH)

15012 Tobias Oelbaum Subjective Results for the SVC Verification Test14918 Mathias Wien Verification of SVC Verification Test Streams


14496-4 Conformance testing9441 Disposition of Comments on ISO/IEC 14496-4:2004/PDAM 30 N 07/10/269442 Text of ISO/IEC 14496-4:2004/FPDAM 30 Conformance Testing

for New Profiles for Professional ApplicationsN 07/11/30

14496-5 Reference Software 9443 Disposition of Comments on ISO/IEC 14496-5:2001/PDAM 18 N 07/10/269444 Text of ISO/IEC 14496-5:2001/FPDAM 18 Reference Software for

New Profiles for Professional ApplicationsN 07/11/30

14496-10 Advanced Video Coding9543 Requirements and Application Descriptions for MVC N 07/10/269445 Study Text of ISO/IEC 14496-10:200X/PDAM 1 Multiview Video

CodingN 07/11/09

9446 Joint Multiview Video Model (JMVM) 6 N 07/11/099447 JMVM 6 Software N 07/11/309482 Draft Report on SVC Verification Tests N 07/11/099483 SVC Verification Test Plan Version 2 N 07/11/16

92

5 MPEG-7 Visual

5.1 MPEG-7 Visual related work in ShenzhenThe 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. All these documents were reviewed and discussed.

14907 Sangyoun Lee Report of core experiment VCE-5

14909

Dae Il Yoon, Jie Jia, Wei Wu, Hae Kwang Kim, Weon Geun Oh

Video signature

14913Hyeong-yong Jeon, Chi-jung Hwang, Weon-geun Oh

An Image Identifier Based on Feature Points for Complex Conditions

14926 Kota Iwamoto, Ryoma Oami On the Modification Process of VCE-7

14927 Kota Iwamoto Ryoma Oami Contribution to the Video Dataset for VCE-7

14956

Weon-Geun Oh, Ayoung Cho, Ik-Hwan Cho, Won-Keun Yang, Ju-Kyong Jin, Jun-Woo Lee, Dong-Seok Jeong

Concentric circle partition-based image signature

14960Dong-Seok Jeong, Ju-Kyong Jin, Sang-Il Na, Dong-Jin Seo

Proposal on the Implementation of VCE-7 Analog VCR Recording & Recapture Modification

14964 Jens-Rainer Ohm Responses received on Visual Signature Tools CfP

14977 Karol Wnukowicz Cross verification result of Image Signature (VCE-6)

14983 Paul Brasnett, Miroslaw Bober

Proposed Improvements to Image Signature XM 31.0

14987 Weon-Geun Oh, Ik-Hwan Cho, Dong-Seok Jeong

Comments for the current geometrical modification of MPEG-7 VCE-6

On major work item has been the review of responses received on the Call for Proposals on Visual Signature Tools. Two proposals were received (as documented in M14964):

– Proposal 1 (=14983): This is an improved version of the algorithm currently in the XM. Based on trace transform, projection to theta-axis, Fourier transform, log, difference between neighbored coefficients, binarization into 1008 bit. Scalable version: Splitting into subsets. Matching by Hamming distance. Correct detection at 0.05 ppm (1-recall) 99.59% in CE, 99.49% in CfP. No difference in descriptor, but different subset of 512 bits was used in these two cases. Proponent reports post experiments with 354 bits, which gave 99.65% correct detection.

– Proposal 2 (=14956): Based on differences (radially 16+32 and in 36 angular directions) within circular neighborhoods. Depending on difference above or below a threshold, a binary description is extracted. Descriptor size is 392 bits, actually used size 354 bits, the remaining bits always zero, correct detection rate 99.65% under CfP conditions. Current version of descriptor is not scalable.

Regarding results, extraction and matching complexity as well as compactness of the description, both methods could be regarded as completely equivalent. This is true for the simple conditions as described in the context of the CfP. It was therefore decided to perform additional comparison

93

considering the “light complex conditions” for rotation, translation and cropping as currently under investigation in VCE 6. Mutual crosschecks were performed by the proponents. The results of this additional testing under 10 ppm false matches were as follows (proposal #1 vs. #2):

– Rotation 10%: 100% vs. 100%– Translation 10%: 0.98% vs. 0.19%– Cropping 90%: 57.5% vs. 0.9%

This indicates that proposal #1 has slight advantages as compared to proposal #2. Even though far from perfectly matching the cropped case, at least some of the images would be found using a comparably simple technique (more advanced technology for the entire “complex conditions” is currently being explored in VCE 6). The changes as made in the proposal are therefore promoted to WD. For further testing in VCE 6, concentration on only complex conditions will be made, since the simple conditions seems to work practically perfectly.

Progress was made in collecting test material for preparation of the CfP on video signatures (VCE 7). Further offers were brought only during the Shenzhen meeting. It will be decided after the next round of CE 7 during the January meeting whether the content available is sufficient to run the video signature CfP as planned (see below).

The following timeline is planned for the ongoing work on visual signatures: Image Signature

PDAM: 2008/01 FPDAM: 2008/04 FDAM: 2008/10 AMD: 2009/01

Video Signature Collection of video test data: 2007.10.10 Finalisation of experimental conditions / Final Call for Proposals: 2008.01.18 Submission deadline: 2008.04.16 (by 23.59 Hours GMT) Evaluation of answers: 2008.04.26 – 05.02 (During the 84th MPEG meeting and the

weekend before: proponents are strongly advised to present their proposals in person.)

PDAM: 2008/04 FPDAM: 2008/10 FDAM: 2009/04 AMD: 2009/07

Other work items:– VCE 5: Core experiment on using MPEG-7 face recognition technology is ongoing.– 23000-3 Amd.1: One incompatibility in the software for PP MAF, regarding the BiM

interface, was resolved in the meantime.– Video augmentation by metadata: This topic was treated in an AHG, which was not very

active before the Shenzhen meeting, but is expected to bring more evidence aout the importance of this topic next time.

5.2 Output documents related to MPEG-7 Visual

No. Title TBP Available15938-3 Visual

9450 Working Draft 1.0 of ISO/IEC 15938-3:2001/Amd.3 Visual Signature Tools

N 07/11/16

94

9451 MPEG-7 Visual XM Document version 32.0 N 07/10/269452 Description of Core Experiments for MPEG-7 New Visual

ExtensionsN 07/10/26

6 23002 MPEG-C Video Technologies

6.1 23002-1 and 23002-2Both Amd.1 of ISO/IEC 23001-1 (software for testing IDCT accuracy) and the new part ISO/IEC 23002-2 (Integer IDCT/DCT) reached their final stages in MPEG. NB comments were requesting for appropriate editorial improvements, which was observed when the final documents were edited.

For 23002-2, a change of title is requested (removing “implementation” from the previous title).

Documents reviewed:14821 SC 29 Secretariat Summary of Voting on ISO/IEC FCD 23002-2


14901 Gary Sullivan, Yuriy Reznik, Arianne Hinds

ISO/IEC 23002-2 FCD (Updated with Editor's Input)


23002-1 Accuracy specification for implementation of integer-output IDCT

9454 Disposition of Comments on ISO/IEC 23002-1/FPDAM1 N 07/10/269455 Text of ISO/IEC 23002-1/FDAM1 Software for Integer IDCT

Accuracy TestingN 07/11/23

23002-2 Fixed point 8x8 DCT/IDCT9456 Disposition of Comments on ISO/IEC FCD 23002-2 N 07/11/239457 Text of ISO/IEC FDIS 23002-2 Fixed-point 88 inverse discrete

cosine transform and discrete cosine transformN 07/12/07

6.2 23001-4 and 23002-4 Reconfigurable Video Coding (RVC)The RVC break-out group was active all week from Monday to Thursday. The major work items were:

• Major step forward, CD for both parts. The group has approved the promotion to CD of the current two WDs.

– The CD includes the specification of bitstream syntax using MPEG-21 BSDL specification and the description of codec configuration using DDL in uncompressed form. Compression of decoder description and bitstream syntax description are currently not included, since further study in CE are needed to select standard BiM technology or a specific technology providing higher compression and/or other functionality.

• Text of ISO/IEC CD 23001-4 Codec Configuration Representation (N9453)– The current text has been amended adding contributions from documents: M14874,

M14961 and adding the specification of CAL language as informative annex. See below for more details on the content of the mentioned contributions.

• Text of CD ISO/IEC 23002-4 Video Tool Library (N9458)

95

– The current text has been amended including contributions from: M14861, M14864, M14873, M14929, M14965. See table below for a summary of each individual contributions

• WD 1 of Video Tool Library Extensions (N9459)– Contains those MPEG standard tools which were not yet sufficiently tested or are

incomplete by description• The description of Core Experiments in RVC has been updated (N9460)

– CE1- Decoder Description Language – it consist of a very detailed investigation of benefit for higher compression of description (BSDL/BiM vs. CDDL) and the possibility of synthesizing directly a parser from a compressed description.

– CE2 - Abstract FU description – it describes ongoing developments and testing of toolbox components

• RVC Simulation Model (RSM) V6.0 (N9461)– New FU implementations and tools have been included and added from

contributions: M14861, M14873, M1864. – The reference SW implementation written in CAL of the MPEG toolbox will

probably become a separate part of standard.• RVC Work Plan (N9462) document has been updated including all new new submissions of

FUs in textual descriptions, in SW implementations in CAL and under development. Worplan of SW and HDL generator tools has been revised considering the actual development commitments.

• RVC Conformance Testing Working Draft 3.0 (N9463)– It is currently used to specify the precise testing of FUs as separate components. It

will need to evolve so as to consider conformance of codec configurations with exiting profiles and levels for MPEG-2, MPEG-4 codecs.

– It is also expected to evolve into separate part of the standard.• Description of Exploration Experiments in RVC (N9464)

– Further investigation about running RVC with non-MPEG tools, in particular with non-compatible interfaces.

• Methodologies for Video Toolbox Extension (N9464)– Includes results and examples from past EEs.

Documents reviewed:

14861

Gwo Giun Lee, He-Yuan Lin, Ming-Jiun Wang, Rong-Lai Lai, Yuan-Long Cheng

RVC FUs of motion vector reconstruction for AVCThe contribution reports the architecture in terms of FUs for the reconstruction of motion vectors for AVC.

14864 Kenji Otoi, Yoshihisa Yamada, Kohtaro Asai

Proposed text of the RVC FUs for MPEG-4 AVC High Profile toolsThis contribution presents textual description for FUs implementing the AVC High profile.

14873 Christophe Lucarz Dave Parlour

Serialized version of some MPEG-4 SP FUs The contribution provides the textual description and the CAL SW implementation of FUs necessary for the configuration of the MPEG-4 SP in form of “serial” architecture. In other words FUs that process sequentially 8x8 blocks for 420 and for 422 and 444 extension of the SP profile.

14874 Christophe Lucarz, Joseph A systematic procedure for the generation of a

96

Thomas-Kerr, Marco Mattavelli, Ian Burnett

CAL parser from BDSL in the RVC frameworkThe contribution describes some results of Core experiment 1.1.In particular it is shown how a XSLT script can process a BSDL syntax description and can geerate a CAL actor that is actually able to parse any bitstreams compliant with the BSDL syntax description. So far three BSDL syntactic construct can successfully be processed by the XSLT script over the 7 present in the BSDL syntax.

14929Dandan Ding, Marco Mattavelli,Christophe Lucarz, Lu Yu

Classification of Tokens for FUs of MPEG-4 SP and MPEG-4/AVC in RVC FrameworkThe contribution specifies the “channels” that are established between FUs of the RVC toolbox in terms of type of tokens carried and on their sequences. Such information cannot be easily extracted by the current version of the RVC textual description, but is fundamental to understand when new configurations of FUs can be implemented.

14931 Dandan Ding, Lu Yu, Marco Mattavelli

A RVC Framework and Tokens Definition Proposed for AVS JiZhun ProfileThe contribution presents the textual description and the“channels” specification of the AVS standard so as to share the maximum of common FU partitions, token types and token sequences of the current RVC toolbox.

14932

Sunyoung Lee, Hyungyu Kim, Sinwook Lee,Jaebum Jun, Si Kyung Kim, Chungku Yie,Euee S. Jang

Results of RVC CE 1.1The contribution presents the results ofCE 1.1. It proposes a modified and extended version of CDDL with the following features: 1) automatic generation of CAL code for syntax parser from a decoder description in CDDL, 2) modified description format for SRT and SET to support both monolithic and hierarchical syntax parsing description, 3) modified description format for DVT to support generic entropy decoding (e.g., CAVLD and exponential-Golomb), 4) new interface description to map CSCI in syntax parser to elements in network of FUs

14933Sinwook Lee, Jaebum Jun, Byoungjun Kim,Chungku Yie, Euee S. Jang

Results of RVC CE 1.2: CDDLThe contribution presents a binary compressed format for the description of a network of FUs.

14942 Dandan Ding, Lu Yu, Honggang Qi

Further RVC Exploration Experiments Report on New 8x8 Inverse Transform and Quantization ToolsThe contribution presents the result of an experiment where the MPEG-4 SP decoder described in the RVC framework by FUs is reconfigured using a FUs implementing a linear transform algorithm different from the one in the toolbox.

14961 Marco Mattavelli, Dave CAL Coding Practice Guide

97

Parlour, Jorn Janneck

This contribution presents a tutorial guide for the development of CAL FUs that results into efficient SW and synthesizable and efficient HW implementations when CAL is converted to SW and HDL by appropriate code generation tools.

14965

Maxime Pelcat, Mickaël Raulet, Olivier Déforges,Médéric Blestel, Jean-François Nezan

Implementing SVC from RVC AVC: description of the specific SVC FUs.The contribution specifies the FUs that are necessary to implement a SVC decoder in the RVC framework when all FUs of AVC are available.

14972 Dandan Ding, Honggang Qi, Lu Yu

Text Description of RVC FUs for Intra Prediction of AVS JiZhun Profile The contribution reports the textual description of FUs for implementing the AVS intra predition JiZhun profile.

14981

Matthieu Wipliez, Ghislain Roquier, Mickaël Raulet, Jean-François Nezan, Marco Mattavelli, Ian Miller

Status of CAL2C code generationThe contribution presents the development status of a tool for the conversion of a network of FU (i.e. a codec configuration) into C code.

Output Documents:

No. Title TBP Available23001-4 Codec Configuration Representation

9453 Text of ISO/IEC CD 23001-4 Codec Configuration Representation N 07/11/2323002-4 Video Tool Library

9458 Text of CD ISO/IEC 23002-4 Video Tool Library N 07/11/239459 Video Tool Library Extensions V1.0 N 07/11/099460 Description of Core Experiments in RVC N 07/10/269461 RVC Simulation Model (RSM) V6.0 N 07/11/099462 RVC Work Plan N 07/10/269463 RVC Conformance Testing Working Draft 3.0 N 07/11/099464 Description of Exploration Experiments in RVC N 07/10/269465 Methodologies for Video Toolbox Extension N 07/11/09

7 Explorations – Free Viewpoint Video/TelevisionThe exploratory work on free-viewpoint video has its roots in the “3DAV” exploration, which was originally started in December 2001, and later led in a first CfP on multiview video compression technology (current MVC development in JVT). Based on inputs received and discussions performed in Shenzhen, further clarification was reached on the relationship and potentials of these topics. Considering the MPEG portfolio in stereo and multiview, currently we have / investigate

• 23002-3: Defining a format to enable simple stereoscopic application (only one video plus depth possible). In the previous (Lausanne meeting) a request was made to extend 23002-3 by more technology to allow multiple depth layers to better cope with occlusions, but consensus was reached that such approaches should better be subsumed under the FTV perspectives as a possible simple case.

98

• MVC (14496-10/Amd.1): Targets encoding of discrete set of multiple views to highest pixel fidelity, where however current results show that not too much additional compression can be gained by using inter-view similarities; therefore, the necessary rate would still be (depending on number of views) significantly higher than for a single video, while it will be lower than for simulcasting the views. Nevertheless, for high view precision as required in N-view displays, such technology is justified.

During the discussion on FTV requirements, it was emphasized that for many consumer-type applications that would require multiview adaptation technology, a large rate overhead (as compared to single view) would be unacceptable. FTV can therefore be defined as a compressed representation and associated technologies which enable generating a large number of different views from a sparse view set. This most probably (from technologies currently known) requires implementation of depth/disparity map estimation (non-normative), definition of depth/disparity map representation/compression, and interpolation/rendering methods (not clear yet whether the latter should be non-normative or normative). All of these elements rely on each other, such that proper technology selection will most probably not be simple. Furthermore, higher distortion may be expected than for MVC (or at least quality may not be measurable in terms of pixel fidelity, and geometric distortions may appear that might only be noticeable under certain observation conditions). The amount of distortion most probably would also depend on compactness (density of views) and complexity of the methods. Depending on the specific application, the view number to be generated may range from two for simple stereoscopic video up to "many" for almost-free walk-through within a scene. Different applications are described in N9466, and it would be desirable to have a common (but scalable) set of technology to accommodate all of them.

General approach: • N cameras (input views) with only a sparse set of K views encoded• M output views with quality depending on

– Degree of viewing angle X per available input view– Compactness of representation / data rate R– Quality of view interpolation

• Scalability of technology and backwards compatibility (monoscopic view decodeable) appears important

Development of such technology will require careful preparation of a CfP, which could at earliest be issued in July 2008. As a first step, the following two documents were issued:• FTV Test Cases and Evaluation (N9467)

– Could cover different application needs when only relatively low number of cases are tested (K=1..3)

– Sequences from dense camera settings (from which the relevant views are subsampled) and good depth maps required

• Call for Contributions on FTV Test Material (N9468)– Dense test sequences (specifications given)– Depth map estimation software (and test cases)

Documents reviewed 14876 Andy Tescher for USNB USNB Contribution: Remarks on multi-view and

free-viewpoint video coding work (MVC/FTV)The video subgroup thanks the USNB for the valuable comments on multi-view and free-viewpoint TV coding work. The issue of “inward-looking” and “outward-looking” scenarios is

99

regarded as important, but further study of applications, requirements and prospective technology is needed to identify whether it is useful to establish a common framework for both cases. Regarding the necessity of depth map generation and encoding, a considerable amount of clarification was achieved, for which we refer to N9467 and N9468. The main scope of such technology would be to enable generation of a multitude of views from a much smaller number of encoded viewpoints by utilizing associated depth information. From the applications and requirements study performed in N9466, such a framework could cover a wide range of possible scenarios, which could be seen as unification and extension of technology currently available in ISO/IEC 23002-3 (simple stereoscopic applications) and under development for ISO/IEC 14496-10:200x/Amd.1 (multiview video coding).

14952 Akio Ishikawa, Sei Naito, Shigeyuki Sakazawa

Walk-Through Experience using Ray Space Representation toward Free Viewpoint TV (R)

14949Tanimoto [email protected]

Axi-Vision Camera: Real-time depth-mapping HDTV camera

14879

Taka senoh, Kenji Yamamoto, Ryutaro Oi,Tomoyuki Mishina, Makoto Okui

Consideration of FTV image generation from image+depthDepth information can often not be computed correctly. Different cases where actual object distance is needed. Also important for correct rendering of 3D information.

14888Masayuki Tanimoto, Toshiaki Fujii, Kazuyoshi Suzuki

Multi-view depth map of Rena and Akko&Kayo (R)

14889Masayuki Tanimoto, Toshiaki Fujii, Kazuyoshi Suzuki

Experiment of view synthesis using multi-view depth (R)

14920 Shinya Shimizu, Hideaki Kimata

View generation from neighboring two videos and two depth maps (R)

14994Yo-Sung Ho, Sang-Beom Lee, Kwan-Jung Oh,Cheon Lee

Depth Map Generation for FTV

14996 Yo-Sung Ho, Sang-Tae Na, Kwan-Jung Oh, Cheon Lee

Depth Coding and Virtual View Synthesis for FTV

Output documents:No. Title TBP Available

Exploration – Free Viewpoint TV Coding9466 Applications and Requirements of FTV N 07/10/269467 FTV Test Cases and Evaluation N 07/10/269468 Call for Contributions on FTV Test Material Y 07/11/02

100

8 Other issues

8.1 Color

14916(=JVT-Y034)

Shun-ichi Sekiguchi, Shuichi Yamagishi, Yoshihisa Yamada, Kohtaro Asai,Tokumichi Muratami

On adaptive chroma sampling for 4:4:4 video coding (R)Macroblock-adaptive 4:4:4 / 4:2:0 coding (examples shown where color disappears in very small colored areas). Shown results only with Y-PSNR, which does not tell very much (worse performance than 4:2:0 coding, but better than 4:4:4 coding). Currently, no evidence about real benefit. Further study needed, also in context of potential complexity increase by macroblock-wise switching as compared to the benefit that it gives.

14940


Application Scenarios and Derived Requirements for Color Reproduction MAFPurpose: Convey the color capturing characteristics to Terminal. Also include some MPEG-7 metadata such as authoring.

14939


Specification Investigation for Consistent Color ReproductionProblem relating to color reproduction most probably already resolved by the appropriate header information that can be conveyed in MPEG-2, MPEG-4.2 and MPEG-4 AVC streams. Proponents should study this and report if they find that there are any missing elements. Issue of other metadata would better fit into the scope of the AHG on “Augmenting Video by metadata“, where the types of metadata listed in 14940 would be a subset of the possible types.

8.2 Improved compression

14917 Steffen Kamp, Michael Evertz, Mathias Wien

Decoder Side Motion Vector DerivationInput reporting about rate reduction relative to current JM software by saving motion information and performing a search with small search range at the decoder side (in certain modes – direc, 8x8, 16x16). This appears to be effective particularly at low rates.

101

Annex G – JVT report

Source: Gary J. Sullivan, Jens-Rainer Ohm, Thomas Wiegand, Ajay Luthra

1 AbstractThe Joint Video Team (JVT) of ITU-T Q.6/16 and ISO/IEC JTC 1/SC 29/WG 11 held its 25th meeting during 21 – 26 October, 2007 at the Marco Polo Hotel in Shenzhen, China. The JVT meeting was held under the chairmanship of Dr. Gary Sullivan (Microsoft/USA) and Dr. Jens-Rainer Ohm (RWTH Aachen/Germany), and under the associate chairmanship of Dr. Thomas Wiegand (Fraunhofer HHI/Germany) and Dr. Ajay Luthra (Motorola/USA). The JVT meetings opened at approximately 9:15 a.m. on Sunday 21 October 2007 and closed at approximately 12:35 p.m. on Friday 26 October 2007. Approximately 176 people attended the JVT meetings and approximately 75 input documents were discussed. The meetings took place in a co-located fashion with a meeting of ISO/IEC JTC 1/SC 29/WG 11 – one of the two parent bodies of the JVT. The subject matter of the JVT meeting activities consisted of work on video coding.

103

2 Contents1. Abstract 1012. Contents 1023. Documents of the JVT meeting 105

3.1. Input documents 1053.1.1 Administrative input contributions..........................................................................1053.1.2 Input liaison statements and parent-body inputs.....................................................1063.1.3 Non-administrative input contributions...................................................................1063.1.4 Late-registered input contributions, BoG reports, etc.............................................108

3.2. Late document availability 1083.3. Withdrawn document registrations 1093.4. Major output documents 109

JVT-Y200 Meeting report of the 25th JVT meeting (this document) [2007-11-14]..................................109JVT-Y201 (WG 11 N9527) Outgoing JVT liaison statements [2007-10-26]............................................109JVT-Y204-M (WG 11 N9442 = ISO/IEC 14496-4:2004/FPDAM 30) Draft conformance testing for Prof Prof (Teruhiko Suzuki) [2007-11-30].................................................................................................................110JVT-Y206-M (WG 11 N9444 = ISO/IEC 14496-5:2001/FPDAM 18) Draft reference software for Prof Prof [2007-11-30]...............................................................................................................................................110JVT-Y207 (WG 11 N9446 Joint multi-view video model (JMVM) 6 text [2007-11-09]..........................110JVT-Y208-M (WG 11 N9447) JMVM 6 software [2007-11-30]...............................................................110JVT-Y209 (WG 11 N9445) Joint draft multi-view video coding (MVC) [2007-11-09]...........................110JVT-Y212-M (WG 11 N9483) Verification test plan for SVC [2007-11-16]............................................110

3.5. JVT internal output documents 110JVT-Y202-M Joint scalable video model (JSVM) text..............................................................................110JVT-Y203-M JSVM software.....................................................................................................................110JVT-Y205-M Draft conformance testing for SVC (V. Bottreau)...............................................................110JVT-Y210-M ITU-T Rec. H.264 | ISO/IEC 14496-10 Advanced video coding defect report (G. Sullivan)110JVT-Y211-M Draft reference software for SVC........................................................................................110

3.6. MVC core experiment output documents 110JVT-Y301 CE 1 on MVC motion skip.......................................................................................................110JVT-Y302 CE 2 on MVC adaptive reference filtering...............................................................................110

4. JVT administrative and liaison topics1114.1. IPR policy reminder and update 1114.2. Meeting opening and remarks by the chairmen 1124.3. JVT communication practices1134.4. Scheduling and logistics notes 1134.5. Administrative documents 114

JVT-Y000 (Admin) List of documents of Geneva meeting.......................................................................114JVT-Y001-M (Admin) [G. J. Sullivan, J.-R. Ohm, A. Luthra, T. Wiegand] AHG Report: Proj mgmt and errata...........................................................................................................................................................114JVT-Y002 (Admin) [T. Wiegand, K. Suehring, A. Tourapis, T. Suzuki, K.P. Lim] AHG Report: JM text, ref soft, bitstream, conf.....................................................................................................................................115JVT-Y003 (Admin) [H. Schwarz, J. Vieron, T. Wiegand, M. Wien, A. Eleftheriadis, V. Bottreau] AHG Report: JD & JSVM text, S/W, conf...........................................................................................................117JVT-Y004 (Admin) [Y. Gao, A. Segall, T. Wiegand] AHG Report: SVC bit depth and chroma format..118JVT-Y005 (Admin) [J. Ridge, M. Karczewicz] AHG Report: FGS applications and design simplification119JVT-Y006 (Admin) [A. Vetro, P. Pandit] AHG Report: MVC high-level syntax & buffer management.119JVT-Y007 (Admin) [H. Kimata, A. Smolic, P. Pandit, A. Vetro, Y. Chen] AHG Report: JMVM & JD text & software.......................................................................................................................................................120JVT-Y008 (Admin) [H. Kimata, A. Smolic] AHG Report: MVC exper. framework & test cond............121JVT-Y009-M (Admin) [P. Pandit] AHG Report: MVC solutions using existing AVC decoders.............122JVT-Y010 (Admin) [P. Pandit, H. Kimata] AHG Report: MVC RRU and mixed-resolution view coding122JVT-Y011 (Admin) [P. Pandit, H. S. Koo] AHG Report: MVC JMVM coding tools...............................122

4.6. Closing session notes 1234.7. JVT liaison communications 123

104

5. AVC base specification and related topics 123JVT-Y083 ( Prop 2.2) [S. Narasimhan (Motorola)] On end_of_stream NAL unit and splicing.............123JVT-Y084-L (Late Prop 2.2) [A. Rodriguez (Cisco)] Provisions for concatenation and splicing of streams <<withdrawn>>..........................................................................................................................................124

6. Scalable video coding (SVC) phase II 1246.1. Core experiment #1 & related docs: SVC bit depth scalability 124

JVT-Y039 ( Prop 2.2/3.1) [M. Winken, H. Schwarz, T. Wiegand (HHI)] CE1: Results for SVC bit-depth scalability....................................................................................................................................................124JVT-Y056-V ( Info) [M. Wien (Aachen U.)] Verif JVT-Y039 results for bit-depth scalability............124JVT-Y032 ( Prop 2.2/3.1) [M. Winken, H. Schwarz, T. Wiegand (HHI)] Bit-depth SVC: New results for Freeway sequence.......................................................................................................................................125JVT-Y057-V ( Info) [M. Wien (Aachen U.)] Verif JVT-Y032 new results for Freeway sequence.......125JVT-Y048 ( Prop 2.2/3.1) [Y. Ye, H. Chung, M. Karczewicz, I. S. Chong (Qualcomm)] Prop SVC bit depth scalability....................................................................................................................................................126JVT-Y050-V ( Info 2.0/3.1) [Y. Gao and Y. Wu (Thomson)] CE1: Verif JVT-Y048 Qualcomm CE1 SVC prop.............................................................................................................................................................127JVT-Y067 ( Prop 2.2/3.1) [S. Liu, A. Vetro (MERL)] CE1: SVC bit-depth scalability results.............127JVT-Y073-V ( Info) [A. Segall (Sharp)] Verif of JVT-Y067 MERL CE1 response..............................129JVT-Y071 ( Prop 2.2) [A. Segall, Y. Su (Sharp)] CE1: Inter-layer prediction for SVC bit-depth scalability.....................................................................................................................................................................129JVT-Y078-LV (Late Info 2.2/3.1) [S. Liu, A. Vetro (MERL)] Verif SVC JVT-Y071 CE1 results from Sharp.....................................................................................................................................................................130JVT-Y072-L (Late Info) [A. Segall (Sharp)] Donation of tone mapped image sequences........................130JVT-Y080 ( Prop 2.2/3.1) [Y. Gao, Y. Wu (Thomson)] CE1: SVC combined spatial and bit-depth scalability....................................................................................................................................................131JVT-Y081 ( Prop 2.2/3.1) [Y. Wu, Y. Gao (Thomson)] CE1: SVC study on inter-layer prediction: bit-depth scalability....................................................................................................................................................131JVT-Y049-V ( Info) [I. S. Chong, Y. Ye, M. Karczewicz (Qualcomm)] CE1: Verif JVT-Y080 and JVT-Y081 Thomson CE1 SVC props.................................................................................................................132JVT-Y088-B [A. Segall] BoG report on bit depth and chroma format scalability.....................................132

6.2. SVC fine-granularity scalability 134JVT-Y075 ( Prop 2.2/3.1) [M. Karczewicz, R. Ranchal. Y. Ye (Qualcomm)] SVC FGS Simplifications134JVT-Y074-V ( Info) [A. Segall (Sharp)] Verif of JVT-Y075 Qualcomm proposal on FGS simplification136

6.3. SVC Color space scalability 136JVT-Y076 ( Prop 2.2) [J. H. Park, Y. H. Kim, B. H. Choi (KETI)] Requirement of SVC color space scalability....................................................................................................................................................136

6.4. SVC historical information request 137JVT-Y085-L (Late Info) [M. Karczewicz, Y. Bao (Qualcomm)] Comments on JD text of CAVLC in SVC enhancement layer......................................................................................................................................137

6.5. SVC Error Resilience 138JVT-Y047 ( Prop NN 2.0/3.1) [Y. Guo, Y.-K. Wang, H. Li (Nokia)] SVC motion-copy error conceal for key pics.......................................................................................................................................................138

6.6. SVC high-level syntax and SEI 139JVT-Y046 ( SEI showcase) [C. He, H. Liu, Y.-K Wang, H. Li (Nokia)] SVC showcase of temporal level switching point SEI.....................................................................................................................................139JVT-Y066 ( Prop 2.2/3.1) [N. Sprljan, L. Cieplinski (MEI)] Perceptually optimal SVC layer removal ordering SEI................................................................................................................................................139

6.7. SVC Conformance and verification 139JVT-Y020 ( Ed. Draft) [V. Bottreau (Thomson), A. Eleftheriadis (LM)] SVC conformance testing draft139JVT-Y021 ( Info) [V. Bottreau (Thomson)] SVC verif test bitstreams Scalable High profile...............140

7. Multi-view coding (MVC) 1417.1. Core experiment #2 & related docs: Adaptive reference filtering 141

JVT-Y041 ( Prop 2.2/3.1) [P. Lai, A, Ortega, P. Pandit, P. Yin, T. Dong, C. Gomila (Thomson & USC)] MVC CE2: Adapt ref filtering....................................................................................................................141JVT-Y045-V ( Info) [H. Koo (LG)] MVC CE2: Verif of Thomson prop JVT-Y041............................142

7.2. Core experiment #3: MVC view synthesis prediction & related docs 142JVT-Y068 ( Prop 2.2/3.1) [S. Yea, A. Vetro (MERL)] CE3: MVC report on view synthesis pred.......142JVT-Y064 ( Prop 2.2/3.1) [S. Shimizu, H. Kimata (NTT)] CE3: MVC view synth resid pred on hierarchical inter-view reference....................................................................................................................................143

105

JVT-Y065 ( Prop NN 2.2/3.1) [Y. S. Ho, K. J. Oh, C. Lee, S. B. Lee, S. T. Na, B. H. Choi, J. H. Park (GIST)] CE3: Depth map gen and virtual view synth................................................................................143JVT-Y024 ( Prop 2.2/3.1) [G. Jiang, T. Qiu, M. Yu, Z. Peng, Q. Xu (Ningbo U.)] Disparity est and compression in MVC with disparity maps..................................................................................................144JVT-Y031 ( Req 2.2/3.1) [T. Senoh, et al. (NICT)] MVC requirements for depth info.........................144General discussion and conclusion for CE3 issues.....................................................................................145

7.3. Applications and scope discussion for MVC 1457.3.1 Depth map coding scenarios discussion..................................................................1457.3.2 Joint discussion with MPEG video on MVC / FTV applications and scope...........146

M14876 USNB input to WG 11 parent body.............................................................................................146Initial discussion of FTV application scenarios..........................................................................................147

7.3.3 Additional break-out report discussions on FTV applications and scope...............148JVT-Y087-B [A. Vetro, F. Bruls] BoG report: Summary of BoG Discussions on FTV............................148

7.4. MVC Compression Tools 1487.4.1 MVC coding tool benefit study...............................................................................148

JVT-Y044 ( Prop 2.2/3.1) [T. Dong, P. Pandit, P. Yin, C. Gomila (Thomson)] Study of MVC coding tools.....................................................................................................................................................................148

7.4.2 Illumination compensation & related subjects........................................................149JVT-Y033 (Prop 2.2/3.1) [G. H. Park, M. W. Park, Y. L. Lee, D. Y. Suh, K. Kim (KHU)] Simplif B- and P-SKIP modes on MVC illum comp..............................................................................................................149JVT-Y038 ( Prop 2.2) [J. Huo, H. Yang, Y. Chang (Xidian U.), S. Lin, S. Gao, L. Xiong (Huawei)] MVC illum & color compensation........................................................................................................................150

7.4.3 Motion skip operation..............................................................................................150JVT-Y036 ( Prop 2.2) [S. Lin, S. Gao, H. Yang, L. Xiong (Huawei)] RDV based MVC motion skip..150JVT-Y037 ( Prop 2.2) [H. Yang, J. Huo, Y. Chang (Xidian U.), S. Lin, S. Gao, L. Xiong (Huawei)] Inter-view motion skip MVC with fine motion...................................................................................................151JVT-Y069-V ( Info 2.0/3.1) [J. Luo (Thomson)] Verif of JVT-Y037 Huawei prop JVT-Y070............152JVT-Y058 ( Prop 2.2/3.1) [Y.-J. Jeon, H.-S. Koo, B.-M. Jeon (LG)] Motion skip issues in MVC........152JVT-Y059-V ( Info 2.0/3.1) [J. Luo (Thomson)] Verif JVT-Y058 motion skip....................................153

7.4.4 Single-loop decoding...............................................................................................153JVT-Y053 ( Prop 2.2.1/3.1) [Y. Chen, Y.-K. Wang, M. M. Hannuksela (Nokia)] Single loop decode and motion skip in JMVM.................................................................................................................................153JVT-Y042 ( Prop 2.2/3.1) [P. Pandit, P. Yin, T. Dong, C. Gomila, H. Koo, Y. Jeon, B. Jeon (Thomson & LG)] MVC single-loop decoding................................................................................................................154JVT-Y060-V ( Info) [Y.-L. Lee (Sejong U.)] Verif JVT-Y042 MVC single-loop decoding.................155General discussion on single-loop decoding...............................................................................................155

7.5. Low-complexity MVC / Stereoscopic 1557.5.1 Reference picture resampling (RPR) for MVC.......................................................155

JVT-Y030 ( Prop 2.2/3.1) [H. Kimata, S. Shimizu (NTT)] Exper results on MVC down-sampled inter-view pred.............................................................................................................................................................155JVT-Y054 ( Prop 2.2.1/3.1) [Y. Chen, S. Liu, Y.-K. Wang, M. M. Hannuksela, H. Li (Nokia)] Low complexity asymmetric MVC.....................................................................................................................156JVT-Y082 ( Info 2.0) [C. Fehn, P. Kauff, A. Smolic (HHI), S. Cho, N. Hur, J. Jim, S.-I. Lee (ETRI)] Asymmetric coding of stereoscopic video for mobile 3DTV.....................................................................156

7.5.2 Reduced-resolution update (RRU) for MVC...........................................................157JVT-Y052 ( Prop 2.2/3.1) [S. Cho, N. Hur, J. Kim, S.-I. Lee (ETRI), C. Fehn (HHI)] Resid-downsampled stereoscopic video for moble 3DTV...........................................................................................................157

7.6. MVC with depth 1587.7. JMVM analysis and optimization 158

JVT-Y022 ( Info 2.2) [R. He, G. Jiang, M. Yu (Ningbo U.)] Determining decoding path in MVC......158JVT-Y023 ( Info 2.2/3.1) [G. Jiang, Y. Yang, M. Yu (Ningbo U.)] Evaluation of random access of MVC schemes.......................................................................................................................................................158JVT-Y026 ( Info 2.0) [M. Yu, Z. Peng, G. Jiang (Ningbo U.)] Statistical analysis of macroblock mode selection in JMVM......................................................................................................................................159JVT-Y027 ( Info 2.2) [M. Yu, Q. Xu, G. Jiang, Z. Peng (Ningbo U.)] Bandwidth distortion model for MVC in interactive system...................................................................................................................................159JVT-Y028 ( Info 2.2/3.1) [Y. Yang, M. Yu, G. Jiang (Ningbo U.)] Dependency func for perf analysis of MVC...........................................................................................................................................................160

106

7.8. MVC high-level syntax 160JVT-Y025 ( SEI showcase 2.2) [G. Jiang, R. He, M. Yu (Ningbo U.)] Showcase for code optimization of active view info SEI in JMVM...................................................................................................................160JVT-Y029 ( Prop 2.2) [M. Yu, R. He, G. Jiang (Ningbo U.)] MVC syntax simplif in active view info SEI.....................................................................................................................................................................160JVT-Y040 ( Prop 2.2/3.1) [H. Nakamura, M. Ueda (JVC)] On MVC high-level syntax.......................161JVT-Y043 ( Prop 2.2/3.1) [J. Luo, P. Yin, C. Gomila (Thomson)] MVC HRD & VUI high-level syntax161JVT-Y055 ( Prop 2.2.1/3.1) [P. Yang, X. Xu, G. Zhu, Y. He (Tsinghua U.)] High level syntax for MVC view parallel proc........................................................................................................................................162JVT-Y062-LV (Late Info) [Q. Chen, Z. Chen (Thomson)] Verif JVT-Y055 high level syntax for MVC view parallel proc................................................................................................................................................162JVT-Y061 ( Prop 2.2/3.1) [J.-H. Yang, J.-G Kim, S.-J. Choi (LG)] On MVC high-level syntax..........163

7.9. Test Sequences 163JVT-Y077 ( Info) [C. K. Chung, H. Song, J. H. Park, B. H. Choi (KETI)] Multi-view test sequence for MVC...........................................................................................................................................................163JVT-Y079-V [Y. S. Ho, K. J. Oh, C. Lee (GIST)] Verif JVT-Y077 MVC test sequence? <<withdrawn>>164

8. New AVC Proposals 1648.1. Adaptive chroma sampling 164

JVT-Y034 ( Prop 2.2/3.1) [S. Sekiguchi, S. Yamagishi, Y. Yamada, K. Asai, T. Murakami (MEI)] On adaptive chroma sampling for 4:4:4...........................................................................................................164

8.2. New levels 164JVT-Y035 ( Prop levels 2.0/3.1) [Y. Bandoh, S. Takamura, Y. Yashima (NTT), Shinichi Sakaida, Yukihiro Nishida (NHK), T. Itoh, A. Nakagawa (Fujitsu), I. Ando, H. Takehara (JVC)] Prop new higher levels. .164JVT-Y086-L JNB input on additional levels of AVC and related subjects................................................165General discussion of AVC new levels issues............................................................................................166

9. JVT internal operating rules 16610. List of AHGs established 168

10.1. JVT project management and errata reporting 16810.2. JM Text, reference software, bitstream exchange and conformance 16810.3. SVC JSVM text, software and conformance 16810.4. SVC bit depth and chroma format scalability16810.5. SVC FGS applications and design simplification 16910.6. MVC high-level syntax and buffer management 16910.7. MVC JD and JMVM text and software 16910.8. MVC reduced resolution update and mixed resolution view coding 16910.9. MVC JMVM coding tools 169

11. Resolutions reported to WG 11 parent body 17012. Attendance 170

3 Documents of the JVT meeting

3.1 Input documents

3.1.1 Administrative input contributionsJVT-Y000 (Admin) List of documents of Shenzhen meetingJVT-Y001-M (Admin) [G. J. Sullivan, J.-R. Ohm, A. Luthra, T. Wiegand] AHG Report: Proj mgmt

and errataJVT-Y002 (Admin) [T. Wiegand, K. Suehring, A. Tourapis, T. Suzuki, K.P. Lim] AHG Report: JM

text, ref soft, bitstream, confJVT-Y003 (Admin) [H. Schwarz, J. Vieron, T. Wiegand, M. Wien, A. Eleftheriadis, V. Bottreau]

AHG Report: JD & JSVM text, S/W, confJVT-Y004 (Admin) [Y. Gao, A. Segall, T. Wiegand] AHG Report: SVC bit depth and chroma

format

107

JVT-Y005 (Admin) [J. Ridge, M. Karczewicz] AHG Report: FGS applications and design simplification

JVT-Y006 (Admin) [A. Vetro, P. Pandit] AHG Report: MVC high-level syntax & buffer management

JVT-Y007 (Admin) [H. Kimata, A. Smolic, P. Pandit, A. Vetro, Y. Chen] AHG Report: JMVM & JD text & software

JVT-Y008 (Admin) [H. Kimata, A. Smolic] AHG Report: MVC exper. framework & test condJVT-Y009-M (Admin) [P. Pandit] AHG Report: MVC solutions using existing AVC decodersJVT-Y010 (Admin) [P. Pandit, H. Kimata] AHG Report: MVC RRU and mixed-resolution view

codingJVT-Y011 (Admin) [P. Pandit, H. S. Koo] AHG Report: MVC JMVM coding tools

3.1.2 Input liaison statements and parent-body inputsNone noted.

3.1.3 Non-administrative input contributionsJVT-Y020 ( Ed. Draft) [V. Bottreau (Thomson), A. Eleftheriadis (LM/Vidyo)] SVC conformance

testing draftJVT-Y021 ( Info) [V. Bottreau (Thomson)] SVC verif test bitstreams Scalable High profileJVT-Y022 ( Prop 2.2) [R. He, G. Jiang, M. Yu (Ningbo U.)] Determining decoding path in MVCJVT-Y023 ( Info 2.2/3.1) [G. Jiang, Y. Yang, M. Yu (Ningbo U.)] Evaluation of random access

of MVC schemesJVT-Y024 ( Prop 2.2/3.1) [G. Jiang, T. Qiu, M. Yu, Z. Peng, Q. Xu (Ningbo U.)] Disparity est

and compression in MVC with disparity mapsJVT-Y025 ( SEI showcase 2.2) [G. Jiang, R. He, M. Yu (Ningbo U.)] Showcase for code

optimization of active view info SEI in JMVMJVT-Y026 ( Info 2.0) [M. Yu, Z. Peng, G. Jiang (Ningbo U.)] Statistical analysis of macroblock

mode selection in JMVMJVT-Y027 ( Info 2.2) [M. Yu, Q. Xu, G. Jiang, Z. Peng (Ningbo U.)] Bandwidth distortion model

for MVC in interactive systemJVT-Y028 ( Info 2.2/3.1) [Y. Yang, M. Yu, G. Jiang (Ningbo U.)] Dependency func for perf

analysis of MVCJVT-Y029 ( Prop 2.2) [M. Yu, R. He, G. Jiang (Ningbo U.)] MVC syntax simplif in active view

info SEIJVT-Y030 ( Prop 2.2/3.1) [H. Kimata, S. Shimizu (NTT)] Exper results on MVC down-sampled

inter-view predJVT-Y031 ( Req 2.2/3.1) [T. Senoh, et al. (NICT)] MVC requirements for depth infoJVT-Y032 ( Prop 2.2/3.1) [M. Winken, H. Schwarz, T. Wiegand (HHI)] Bit-depth SVC: New

results for Freeway sequenceJVT-Y033 (Prop 2.2/3.1) [G. H. Park, M. W. Park, Y. L. Lee, D. Y. Suh, K. Kim (KHU)] Simplif

B- and P-SKIP modes on MVC illum compJVT-Y034 ( Prop 2.2/3.1) [S. Sekiguchi, S. Yamagishi, Y. Yamada, K. Asai, T. Murakami

(MEI)] On adaptive chroma sampling for 4:4:4JVT-Y035 ( Prop levels 2.0/3.1) [Y. Bandoh, S. Takamura, Y. Yashima (NTT), Shinichi Sakaida,

Yukihiro Nishida (NHK) , T. Itoh, A. Nakagawa (Fujitsu), I. Ando, H. Takehara (JVC)] Prop new higher levels

JVT-Y036 ( Prop 2.2) [S. Lin, S. Gao, H. Yang, L. Xiong (Huawei)] RDV based MVC motion skip

JVT-Y037 ( Prop 2.2) [H. Yang, J. Huo, Y. Chang (Xidian U.), S. Lin, S. Gao, L. Xiong (Huawei)] Inter-view motion skip MVC with fine motion

108

JVT-Y038 ( Prop 2.2) [J. Huo, H. Yang, Y. Chang (Xidian U.), S. Lin, S. Gao, L. Xiong (Huawei)] MVC illum & color compensation

JVT-Y039 ( Prop 2.2/3.1) [M. Winken, H. Schwarz, T. Wiegand (HHI)] CE1: Results for SVC bit-depth scalability

JVT-Y040 ( Prop 2.2/3.1) [H. Nakamura, M. Ueda (JVC)] On MVC high-level syntaxJVT-Y041 ( Prop 2.2/3.1) [P. Lai, A, Ortega, P. Pandit, P. Yin, T. Dong, C. Gomila (Thomson &

USC)] MVC CE2: Adapt ref filteringJVT-Y042 ( Prop 2.2/3.1) [P. Pandit, P. Yin, T. Dong, C. Gomila, H. Koo, Y. Jeon, B. Jeon

(Thomson & LG)] MVC single-loop decodingJVT-Y043 ( Prop 2.2/3.1) [J. Luo, P. Yin, C. Gomila (Thomson)] MVC HRD & VUI high-level

syntaxJVT-Y044 ( Prop 2.2/3.1) [T. Dong, P. Pandit, P. Yin, C. Gomila (Thomson)] Study of MVC

coding toolsJVT-Y045-V ( Info) [H. Koo (LG)] MVC CE2: Verif of Thomson prop JVT-Y041JVT-Y046 ( SEI showcase) [C. He, H. Liu, Y.-K Wang, H. Li (Nokia)] SVC showcase of

temporal level switching point SEIJVT-Y047 ( Prop NN 2.0/3.1) [Y. Guo, Y.-K. Wang, H. Li (Nokia)] SVC motion-copy error

conceal for key picsJVT-Y048 ( Prop 2.2/3.1) [Y. Ye, H. Chung, M. Karczewicz, I. S. Chong (Qualcomm)] Prop

SVC bit depth scalabilityJVT-Y049-V ( Info) [I. S. Chong, Y. Ye, M. Karczewicz (Qualcomm)] CE1: Verif JVT-Y080

and JVT-Y081 Thomson CE1 SVC propsJVT-Y050-V ( Info 2.0/3.1) [Y. Gao and Y. Wu (Thomson)] CE1: Verif JVT-Y048 Qualcomm

CE1 SVC propJVT-Y051 ( Prop 2.2/3.1) [L. H. Zhu, J. H. Yang, H. Zhang, Z. B. Chen (Thomson)] Suppl SPS

for SVC or MVC <<withdrawn>>JVT-Y052 ( Prop 2.2/3.1) [S. Cho, N. Hur, J. Kim, S.-I. Lee (ETRI), C. Fehn (HHI)] Resid-

downsampled stereoscopic video for moble 3DTVJVT-Y053 ( Prop 2.2.1/3.1) [Y. Chen, Y.-K. Wang, M. M. Hannuksela (Nokia)] Single loop

decode and motion skip in JMVM JVT-Y054 ( Prop 2.2.1/3.1) [Y. Chen, S. Liu, Y.-K. Wang, M. M. Hannuksela, H. Li (Nokia)]

Low complexity asymmetric MVCJVT-Y055 ( Prop 2.2.1/3.1) [P. Yang, X. Xu, G. Zhu, Y. He (Tsinghua U.)] High level syntax for

MVC view parallel procJVT-Y056-V ( Info) [M. Wien (Aachen U.)] Verif JVT-Y039 results for bit-depth scalabilityJVT-Y057-V ( Info) [M. Wien (Aachen U.)] Verif JVT-Y032 new results for Freeway sequenceJVT-Y058 ( Prop 2.2/3.1) [Y.-J. Jeon, H.-S. Koo, B.-M. Jeon (LG)] Motion skip issues in MVCJVT-Y059-V ( Info 2.0/3.1) [J. Luo (Thomson)] Verif JVT-Y058 motion skipJVT-Y060-V ( Info) [Y.-L. Lee (Sejong U.)] Verif JVT-Y042 MVC single-loop decodingJVT-Y061 ( Prop 2.2/3.1) [J.-H. Yang, J.-G Kim, S.-J. Choi (LG)] On MVC high-level syntaxJVT-Y062-LV (Late Info) [Q. Chen, Z. Chen (Thomson)] Verif JVT-Y055 high level syntax for

MVC view parallel procJVT-Y063 [withdrawn] <<withdrawn>>JVT-Y064 ( Prop 2.2/3.1) [S. Shimizu, H. Kimata (NTT)] CE3: MVC view synth resid pred on

hierarchical inter-view referenceJVT-Y065 ( Prop NN 2.2/3.1) [Y. S. Ho, K. J. Oh, C. Lee, S. B. Lee, S. T. Na, B. H. Choi, J. H.

Park (GIST)] CE3: Depth map gen and virtual view synthJVT-Y066 ( Prop 2.2/3.1) [N. Sprljan, L. Cieplinski (MEI)] Perceptually optimal SVC layer

removal orderingJVT-Y067 ( Prop 2.2/3.1) [S. Liu, A. Vetro (MERL)] CE1: SVC bit-depth scalability resultsJVT-Y068 ( Prop 2.2/3.1) [S. Yea, A. Vetro (MERL)] CE3: MVC report on view synthesis pred

109

JVT-Y069-V ( Info 2.0/3.1) [J. Luo (Thomson)] Verif of JVT-Y037 Huawei propJVT-Y070 [vacant] <<vacant>>JVT-Y071 ( Prop 2.2) [A. Segall, Y. Su (Sharp)] CE1: Inter-layer prediction for SVC bit-depth

scalabilityJVT-Y072-L (Late Info) [A. Segall (Sharp)] Donation of tone mapped image sequencesJVT-Y073-V ( Info) [A. Segall (Sharp)] Verif of JVT-Y067 MERL CE1 responseJVT-Y074-V ( Info) [A. Segall (Sharp)] Verif of JVT-Y075 Qualcomm proposal on FGS

simplificationJVT-Y075 ( Prop 2.2/3.1) [M. Karczewicz, R. Ranchal. Y. Ye (Qualcomm)] SVC FGS

SimplificationsJVT-Y076 ( Prop 2.2) [J. H. Park, Y. H. Kim, B. H. Choi (KETI)] Requirement of SVC color

space scalabilityJVT-Y077 ( Info) [C. K. Chung, H. Song, J. H. Park, B. H. Choi (KETI)] Multi-view test

sequence for MVCJVT-Y078-LV (Late Info 2.2/3.1) [S. Liu, A. Vetro (MERL)] Verif SVC JVT-Y071 CE1 results

from SharpJVT-Y079-V [Y. S. Ho, K. J. Oh, C. Lee (GIST)] Verif JVT-Y077 MVC test sequence?

<<withdrawn>>JVT-Y080 ( Prop 2.2/3.1) [Y. Gao, Y. Wu (Thomson)] CE1: SVC combined spatial and bit-depth

scalabilityJVT-Y081 ( Prop 2.2/3.1) [Y. Wu, Y. Gao (Thomson)] CE1: SVC study on inter-layer prediction:

bit-depth scalabilityJVT-Y082 ( Info 2.0) [C. Fehn, P. Kauff, A. Smolic (HHI), S. Cho, N. Hur, J. Jim, S.-I. Lee

(ETRI)] Asymmetric coding of stereoscopic video for mobile 3DTVJVT-Y083 ( Prop 2.2) [S. Narasimhan (Motorola)] On end_of_stream NAL unit and splicing

3.1.4 Late-registered input contributions, BoG reports, etc.JVT-Y084-L (Late Prop 2.2) [A. Rodriguez (Cisco)] Provisions for concatenation and splicing of

streams <<withdrawn>>JVT-Y085-L (Late Info) [M. Karczewicz, Y. Bao (Qualcomm)] Comments on JD text of CAVLC

in SVC enhancement layerJVT-Y086-L JNB input to WG 11 on additional levels of AVC and related subjectsJVT-Y087-B [A. Vetro, F. Bruls] BoG report on FTV Summary of BoG Discussions on FTVJVT-Y088-B [A. Segall] BoG report on B-D scalability

3.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-AHG-report, non-liaison) contribution would be presented without having a minimum of 4 JVT participants (working for 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 a presented late contribution shall send an email apology to the JVT email reflector. This rule does

110

not apply to material requested by the JVT at the meeting (e.g., reports of JVT-authorized side activities).

Clarification: Does not apply to verification contributions.

Further clarification: The four people shall be from different organizations.

JVT decision: Agreed.

A check mark () indicates a contribution considered to be available on time.

The suffixes for contributions not marked as “” are explained below:– "-L" indicates a non-administrative contribution that was somewhat late but was available by

the second meeting day (or, in the case of JVT-Y086-L, initially arrived as parent-body input and later registered for JVT consideration).

– "-Q" were more late than that (no documents in this category at this meeting).– "-M" were still missing at the time of preparation of this report.– "-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.

One contribution was subject to lateness penalties as follows:JVT-Y085-L (Late Info) [M. Karczewicz, Y. Bao (Qualcomm)] Comments on JD text of CAVLC in SVC enhancement layerApology for lateness: Promised to arrive in a timely fashion (but does not seem to have arrived as of 1 month after the meeting).JVT members supporting presentation: T. Wiegand, Y.-K. Wang, J. Sampero, M. Wien, A. Segall

There were no objections to presentations of late documents at this meeting.

It was noted that, with only one contribution subject to lateness penalties, the situation surrounding the need for on-time availability of contributions has substantially improved since our lateness penalty rules were adopted.

3.3 Withdrawn document registrationsJVT-Y051 [L. H. Zhu, J. H. Yang, H. Zhang, Z. B. Chen (Thomson)] Suppl SPS for SVC or MVC <<withdrawn>>JVT-Y063 [withdrawn] <<withdrawn>>JVT-Y079-V [Y. S. Ho, K. J. Oh, C. Lee (GIST)] Verif JVT-Y077 MVC test sequence? <<withdrawn>>JVT-Y084-L (Late Prop 2.2) [A. Rodriguez (Cisco)] Provisions for concatenation and splicing of streams <<withdrawn>>

3.4 Major output documentsMajor output documents submitted to parent-body review included the following. (Dates listed are planned dates of availability.)

3.4.1.1.1 JVT-Y200 Meeting report of the 25th JVT meeting (this document) [2007-11-14]

3.4.1.1.2 JVT-Y201 (WG 11 N9527) Outgoing JVT liaison statements [2007-10-26]

111

3.4.1.1.3 JVT-Y204-M (WG 11 N9442 = ISO/IEC 14496-4:2004/FPDAM 30) Draft conformance testing for Prof Prof (Teruhiko Suzuki) [2007-11-30]

3.4.1.1.4 JVT-Y206-M (WG 11 N9444 = ISO/IEC 14496-5:2001/FPDAM 18) Draft reference software for Prof Prof [2007-11-30]

3.4.1.1.5 JVT-Y207 (WG 11 N9446 Joint multi-view video model (JMVM) 6 text [2007-11-09]

3.4.1.1.6 JVT-Y208-M (WG 11 N9447) JMVM 6 software [2007-11-30]

3.4.1.1.7 JVT-Y209 (WG 11 N9445) Joint draft multi-view video coding (MVC) [2007-11-09]

3.4.1.1.8 JVT-Y212-M (WG 11 N9483) Verification test plan for SVC [2007-11-16]

3.5 JVT internal output documentsJVT internal output documents included the following. (Dates listed are planned dates of availability.)

3.5.1.1.1 JVT-Y202-M Joint scalable video model (JSVM) text

3.5.1.1.2 JVT-Y203-M JSVM software

3.5.1.1.3 JVT-Y205-M Draft conformance testing for SVC (V. Bottreau)

3.5.1.1.4 JVT-Y210-M ITU-T Rec. H.264 | ISO/IEC 14496-10 Advanced video coding defect report (G. Sullivan)

3.5.1.1.5 JVT-Y211-M Draft reference software for SVC

3.6 MVC core experiment output documentsSubmission (to the JVT) of final description (and any data necessary for conducting experiment): next meeting start – 3 weeks.

Submission (to the CE partners) of final software and results: next meeting start – 2 weeks

3.6.1.1.1 JVT-Y301 CE 1 on MVC motion skipCoordinator(s): Ying Chen (Nokia)Participants: GIST, HHI, Huawei, Intel, KETI, LG, Mitsubishi, Nokia, NTT, Qualcomm, Sejong

Univ., Thomson, Tsinghua Univ., Xidian Univ.Technology to be tested: JVT-Y036, JVT-Y037, JVT-Y053

3.6.1.1.2 JVT-Y302 CE 2 on MVC adaptive reference filteringCoordinator(s): Purvin Pandit (Thomson)

112

Participants: GIST, HHI, Huawei, Intel, KETI, LG, Mitsubishi, Motorola, Nokia, NTT, Qualcomm, Sejong Univ., Thomson, Tsinghua Univ., Xidian Univ.

Technology to be tested: JVT-Y041

4 JVT administrative and liaison topics

4.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 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 new common patent policy for 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 (new 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 recently 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

113

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 SVC amendment project and nearing 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 SVC and MVC extensions (not to mention any notices not previously filed relating to the new professional profiles or other previous projects).

It is suggested that, to enable proper interpretation of such formal notices, the SVC or 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 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.

4.2 Meeting opening and remarks by the chairmenThe meeting was opened at approximately 9:15am on Sunday 21 October 2007.

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 two largest areas of activity consist of scalable video coding (SVC) and 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.

Documents were made available for download at http://ftp3.itu.int/av-arch/jvt-site/2007_10_Shenzhen.

The deadline was Monday October 15th 2007 for registrations and uploads.

Initially-missing non-administrative documents included JVT-Y062, JVT-Y072, and JVT-Y078. However, two of those three were verification documents and the other one was a test sequence donation, so their lateness did not seem to pose any significant issue. The only late-registered (non-parent input) technical contribution was JVT-Y084-L, which wasn't very severely late.

Meeting information could be found at http://market.huawei.com/hwgg/mpeg82/.

A document template had been made available at http://ftp3.itu.int/av-arch/jvt-site/JVT-Yxxx.dot. It contained important instructions and policy information. Participants had been encouraged to read it and use it as the basis of their contributions.

114

Opening remarks:– IPR policy reminder– Professional profiles – follow up work on reference software and conformance– Scalable video coding (SVC) phase I – final text was to be submitted after review of input from

editors, work was needed on reference software and conformance and collaboration with MPEG was needed on verification testing

– SVC phase II – work areas included investigation of bit depth and chroma format scalability and fine-granularity scalability

– Multiview video coding (MVC) was a major project underway, and constituted the topic of most contributions to the meeting

Further work and additional needs on the development, standardization, and maintenance of the base specification and the recently-completed professional profiles, and of associated reference software and conformance specifications was also noted. Needs for verification testing to be conducted by the WG 11 parent body were noted and discussed.

The incoming status of work on errata aspects of the AVC specification was as found in JVT-X210 from the previous meeting.

The chair remarked that there were fewer late document uploads this time than a few meetings ago, and that the submitted documents seem to be adhering better to the JVT guidelines in terms of formatting, filenames, etc., which is a good development, although further improvement (particularly in the formatting conventions) is still needed. The recently-established JVT operating rules on that subject may have helped.

4.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 "[email protected]", where "xyz" corresponds to– "experts" for general experts group discussions– "bitstream" for bitstream exchange activities– "svc" for SVC work– "mvc" for MVC work

4.4 Scheduling and logistics notesSome parallel sessions were held during the meeting, particularly including some parallel review of MVC and SVC contributions. Some “break-out group” (BoG) side activities and informal study efforts were also conducted. Documents produced by break-out group activities (if any) are listed in this report with the abbreviation “BoG” and are suffixed with "-B".

115

A contribution template JVT-Yxxx.dot for the JVT meeting was made available on the JVT ftp site: http://ftp3.itu.int/av-arch/jvt-site/2007_10_Shenzhen. It contained essential information for JVT participants. Participants had been instructed to read it carefully, particularly if they planned to be submitting contributions to the meeting.

The document registration and upload deadline was Monday 15 October 2007.

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 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.

Notes on scheduling of topics:Sunday – SVCMonday morning – Did not meet (parent plenary)Monday 1:30 pm onwards – MVCTuesday 9:00 am – Requirements-related topics (non-MVC)Tuesday 10:00 am – Various topicsTuesday 2:00 pm – FTV & depth maps (incl. USNB input comments)Tuesday 4:00 pm – SVC (FTV in parallel)Wednesday 9 am – 10:45 am – Did not meet (parent plenary)Wednesday time 11:00 – SVC testingWednesday 2:00 pm MVC (Sydney)Wednesday 2:00 pm Joint w/ Systems on transport/storage for SVC (Hawaii)Wednesday 6:00 pm – Social eventThursday 9:00 am – AVC corrigenda and splicingThursday 11:00 am Prof prof ref soft & conf (bothFPDAM w/ edit period)Thursday 11:02 am SVC ref soft & conf (no action now on these)Thursday 11:05 am SVC phase 1 editing reviewThursday 11:10 am FTV applications & needsThursday 2:00 pm Joint w/ Systems on transport/storage for SVC (Hawaii)Thursday 2:00 pm MVC (Sydney)Thursday 8:00 pm SVC phase 2 revisitsThursday JVT-Y084 splicing + other subjectsThursday SVC phase 1 editing review + other subjectsThursday 4:00 pm SVC test & plan revisitFriday – Meeting end by 2 pm

4.5 Administrative documents

4.5.1.1.1 JVT-Y000 (Admin) List of documents of Geneva meetingAs listed herein.

4.5.1.1.2 JVT-Y001 -M (Admin) [G. J. Sullivan, J.-R. Ohm, A. Luthra, T. Wiegand] AHG Report: Proj mgmt and errata

General project status was reported verbally as described above (see opening remarks).

116

A new version of the meeting report of the Geneva meeting was available on 21st.

On errata – the JVT-X210 output of the previous meeting was produced and made available during the current meeting.

One input on errata consisted of JVT-Y083 on bitstream concatenation issues.

4.5.1.1.3 JVT-Y002 (Admin) [T. Wiegand, K. Suehring, A. Tourapis, T. Suzuki, K.P. Lim] AHG Report: JM text, ref soft, bitstream, conf

This document described the activities of the JM text, reference software and bitstream conformance Adhoc-Group since the last JVT meeting.

On JM Reference Text: There was no activity to report on the JM reference text.

On JM reference software: Updates for 4:4:4 common mode and lossless coding have been integrated into the development branch. The latest code submissions are currently being tested and were released in JM 13.0 during the Shenzhen JVT meeting.

JM 12.4 had been released as a bug fix release of JM 12.3.JM 13.0 was released during the Shenzhen JVT meeting.

The following issues were reported to be the most important (volunteers needed):

As the official H.264/AVC reference software, the JM should be a correct source for checking implementations. This means the decoder should be able to decode all valid H.264/AVC bitstreams and the encoder should never create invalid bitstreams. This is currently not the case.

Depending on the configuration the JM encoder can create invalid bitstreams:– Level constraints are not properly checked– The 16-bit transform requirement is not checked– In Baseline/Main/Extended profile the restriction of CAVLC syntax elements needs proper

handling

The software coordinators would like to encourage all H.264/AVC experts to volunteer for fixing these issues.

Known Issues / Reporting bugs: A web based bug tracking system has been set up for keeping track of known issues and missing features. The system is publicly accessible but requires registration for entering bug reports.

The system is located at http://ipbt.hhi.de.

This internet site contains also some usage instructions.

Please note that the bug tracking system is using encrypted/secure http (https) for protecting the user’s login. The used certificate is self signed and has to be imported into the user’s web browser. The SHA-1 fingerprint of the certificate is 69:21:86:d9:3e:72:da:3f:e8:30:df:a8:dd:fa:a5:4c:ed:85:b5:09.

117

A list of known issues and their state can be found at: https://ipbt.hhi.de/mantis/view_all_bug_page.php.

A list of current bugs can also be found in the annex of the AHG report document.

It was requested that certain rules should be followed before reporting any new bugs:– The database should be searched on whether the same issue was previously reported. If the

problem was reported before, but there is additional information, then this information should be added to the original report.

– It should be specified if the problem is related to the encoder, decoder or both.– The version of the software used should be specified.– Description of the problem should be as precise as possible.– The necessary steps to reproduce the problem should be described in detail.– If available, the configuration files or/and command line syntax used to run the software should

be provided.– The language of the standard should be used when referencing the text description.– After filing the report, the user should check if he/she is requested to provide additional or

other information relating to this issue.

Bitstream Exchange Activities: Communications related to bitstream exchange activity have taken place on the bitstream exchange reflector (“[email protected]”). The reflector of this AHG was moved from IMTC to Univ. of Aachen. However this area was not so active since the last JVT meeting.

The FTP area for downloading bitstream files is on the main JVT Experts FTP site:ftp://ftp3.itu.int/jvt-site/bitstream_exchange/

The bitstreams can alternatively be accessed from the following http site.http://ftp3.itu.int/av-arch/jvt-site/bitstream_exchange/

To volunteer a bitstream for testing, please include it in a zip archive along with related files (trace files, configuration, reconstructed frames) in a zip archive and upload it to the dropbox:ftp://ftp3.itu.int/jvt-site/dropbox

In general, the following naming convention is being followed for the bitstreams in the exchange:FeatureCode_Source_VersionLetter

Please refer to the spreadsheet and files on the FTP site for examples.

Once a bitstream is uploaded to the dropbox, send an e-mail to [email protected], and/or the bitstream exchange reflector and it will be made available in the bitstream_exchange directory.

To sign up for the bitstream exchange reflector, use the web address given below. http://mailman.rwth-aachen.de/mailman/listinfo/jvt-bitstream.

No new bitstreams for non-professional profiles had been exchanged since the last meeting.

Conformance bitstreams for professional profiles: New conformance bitstreams for High 10 intra, High 422 intra, High 444 intra, CAVLC 444 intra, High 444 profile were generated and available at JVT ftp site. Remaining bitstreams are the bitstreams for lossless coding. Since the implementation of lossless coding in JM software has been finished, the bitstreams will be generated soon. The verification of conformance bitstreams is on going.

118

The AHG recommended– To continue to collect more conformance bitstreams– To promote professional profile conformance and reference software to FPDAM at this

meeting

On conformance activity (incl. prof prof) – software implementation has now implemented all features – last version released was 12.4 – new version to be released during this meeting. Bitstreams being collected – effort progressing well.

No new problem reports on conformance issues for other (non-SVC) profiles.

4.5.1.1.4 JVT-Y003 (Admin) [H. Schwarz, J. Vieron, T. Wiegand, M. Wien, A. Eleftheriadis, V. Bottreau] AHG Report: JD & JSVM text, S/W, conf

This document presented the report of the AhG on JD & JSVM text, JSVM software, and conformance.

The text for the SVC Amendment was provided in JVT-X201. The document JVT-X201 includes changes that are related to issues encountered and resolved by the editors in the final SVC amendment editing process, including the consideration of ITU-T "Last Call" comments.

A list of issues encountered and resolved by the editors in the final SVC amendment editing process was provided, including consideration of ITU-T “last call” comments that could conceivably be considered to be other than simple clarifications and corrections of completely obvious errors.

The editors were thanked and congratulated on doing an excellent job of the editing work.

There was some discussion regarding the specified extraction process in relation to filler data and SEI data; and the relationship between the HRD parameters in the AVC base layer SPS relative to those in an SVC VUI structure. This aspect was checked and finalized during the meeting.

At the San Jose Meeting the JSVM software was branched-off. One branch was created with the goal to align the software with the JD text. A second was created for implementing tools that are considered for SVC phase 2.

The goal of the current JSVM integration period was to obtain JD-aligned software. The work was going on since there were 3 remaining integration works to be performed. Note that multiple slices had been integrated in the software. A table was provided to show the current status of the JSVM 10 software integration process. Remaining items included

– IntraBL treated as inter for constrained intra pred (JVT-W090); Intra MBs in base layer not exceeding IntraBL by more than 1.5 ( JVT- W090); Inheritance of deblocking control (JVT-W046); MBs required for picture only for QID = 0 (JVT-W052). Various HL syntax issues (see notes on JVT-W125); Profile changes as recorded in profiles section; … – to be done by editors.

– deblocking JVT-W063r1 (to be done by Polycom),– change to scaling in position calc for large pictures (see notes on JVT-W136 of prior

meeting – to be done by Microsoft), and– rate control JVT-W043 to be done by Dolby.

119

On SVC phase 2 software, nothing was reportedly integrated during the current integration period, as two proponents had decided not to implement their tools.

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 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

Examples of how to access the CVS repository were provided in the AHG report document.

The CVS repository includes a JSVM software manual, which provides further information on the JSVM software.

Text of ISO/IEC 14496-4:2004/PDAM 31 "Conformance Testing for SVC Profiles" is available on the WG11 site as N9192. Its twin text has been provided as input document JVT-Y020 to the Shenzhen JVT meeting.

Text of ISO/IEC 14496-4:2004/PDAM 31 (JVT-Y020) includes the specification of 82 SVC Conformance bit streams for Scalable Baseline, Scalable High and Scalable High Intra profiles:

– Scalable Baseline profile: 61 bit streams among which the following use cases are illustrated :

– MGS: 6 – MGS + Temporal: 14– Spatial: 14– Spatial + Temporal: 20 – MGS + Spatial + Temporal: 3 – CGS + Spatial + Temporal: 3 – Spatial + Temporal + CGS: 1

– Scalable High profile : 17 bit streams among which the following use cases are illustrated:

– MGS: 4 – Spatial: 3 – Spatial + Temporal: 6 – MGS + Temporal + Spatial: 2 – CGS + Temporal + Spatial: 1 – Spatial + Temporal + CGS: 1

– Scalable High Intra profile : 4 bit streams among which the following use cases are illustrated:

– Spatial: 3– CGS + Spatial: 1

The AHG recommended to– Identify and correct problems in SVC Conformance specification – Add new bit stream descriptions for use cases not or insufficiently covered

120

– Establish a work plan and collect associated bitstreams for inclusion in SVC Conformance specification

4.5.1.1.5 JVT-Y004 (Admin) [Y. Gao, A. Segall, T. Wiegand] AHG Report: SVC bit depth and chroma format

This AhG was established at the Geneva meeting to study bit-depth and chroma format scalability. 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

The AhG sent a kick-off message to the JVT main reflector ([email protected]) on August 15, 2007. There were three other messages on the reflector. All messages contained [BDS] in the subject line.

It was suggested to send liaison letters to the Blu-ray Disc Association and the DVD Forum "to study the possibilities for adding these formats to what can go on those physical discs or their networked upgraded (persistent storage)." This was proposed by Tom McMahon (Broadcom) and supported by Andrew Segall (Sharp).

The following related documents were reported to have been registered: JVT-Y032, JVT-Y039, JVT-Y048, JVT-Y049, JVT-Y050, JVT-Y056, JVT-Y057, JVT-Y067, JVT-Y071, JVT-Y072, JVT-Y073, JVT-Y078, JVT-Y080, JVT-Y081.

The AhG recommended– To review related contributions during the meeting– To continue the study of bit-depth and chroma format scalability– To continue evaluating test material– To send liaison letters to the Blu-ray Disc Association and DVD Forum as proposed on the

reflector

Liaison activity suggested.

4.5.1.1.6 JVT-Y005 (Admin) [J. Ridge, M. Karczewicz] AHG Report: FGS applications and design simplification

In the Geneva meeting, the JVT created a FGS applications and design simplification AHG activity with the following mandates:– Identify applications for that may require FGS functionality and their characteristics– Determine to what extent new coding tools are needed to achieve the functionality– Define experiments and test conditions relating to FGS technology– Explore simplification of FGS tool design

121

One input contribution to this meeting was noted to be closely related to the AHG work items: JVT-Y075 [M. Karczewicz, R. Ranchal. Y. Ye (Qualcomm)] SVC FGS Simplifications.

The AhG recommended– To continue the study of FGS Applications and Design Simplification– To review the related contributions

4.5.1.1.7 JVT-Y006 (Admin) [A. Vetro, P. Pandit] AHG Report: MVC high-level syntax & buffer management

At the Geneva meeting, the JVT established the AhG on MVC high-level syntax & buffering with the following mandates: – Discuss high-level syntax for MVC including NAL unit type, NAL unit header extension, SPS

extensions, slice layer and integration with SVC syntax.– Discuss reference picture management to enable simultaneous picture output of different views

and to facilitate parallel processing.– Discuss issues related to HRD.– Propose refined syntax and decoding processes for JMVM.

No email was exchanged on this topic on the reflector. Editors have made several improvements to the JD text related to high level syntax.

The AhG on MVC high-level syntax & buffering recommended discussing the issues mentioned above and making any necessary revisions to the MVC text.

4.5.1.1.8 JVT-Y007 (Admin) [H. Kimata, A. Smolic, P. Pandit, A. Vetro, Y. Chen] AHG Report: JMVM & JD text & software

At the Geneva meeting, the JVT established the AHG on MVC JD and JMVM text and software with the following mandates:– Collect comments on draft, perform necessary editing and delivery.– Maintain JMVM and JD document and collect comments on the text.– Coordinate JMVM software integration– Coordinate bug-fixing process for the JMVM software– Maintain JMVM software manual

The JMVM5 and JD4 were submitted to JVT as JVT-X207 and JVT-X209, respectively. The JD text was also submitted to MPEG as PDAM text.

Key changes made to the JD text included:– Revised definition of V-IDR and idr_flag (JVT-X029)– Clarified concept of IDR access unit (JVT-X085)– Bug fix for parallel decoding information SEI (JVT-X058)– Clarified that there is a single base view (JVT-X025)– Revised syntax of prefix NAL unit (adds svc_mvc_flag)– Better alignment with the latest SVC specification (e.g., considering latest definition of NAL

unit types and subset sequence parameter set syntax)

122

– Clarified that view dependency of anchor shall apply to V-IDR pictures and IDR access unit in general; revised definition of V-IDR to clarify that V-IDR is an anchor picture

– Revision of terms such as reference picture list and additional definitions– The following points were also discussed among the editor’s, but no action was taken:– Considered adding informative notes on relation between IDR, V-IDR and anchor picture

based on some suggestions at the previous meeting (basically, V-IDR corresponds to a closed GOP, while anchor allows for open GOP). However, the editor’s felt that the definitions are sufficiently clear, therefore no such notes were added.

– Discussed definition of primary coded picture and detection of first VCL NAL unit. This term and process is clear from the base specification.

– Considered whether SP (H.3.17 reference picture list, and H.8.2 Decoding process for reference picture lists construction), EP, EB (H.3.4 EB slice, H.3.5 EP slice, and H.8.2 Decoding process for reference picture lists construction) slices should be included as part of MVC spec or not. This should be discussed further at the meting.

– Discussed empty sections of HRD. In particular, bitstream and decoder conformance for MVC still needs to be addressed.

The JMVM 5 software was delivered to the group on August 10th, 2007. This release contained the integration of scalable nesting SEI message, active view info SEI message, view scalability info SEI, bitstream extractor application based on view scalability SEI message, multiview scene info SEI, multiview acquisition info SEI and several bug fixing and software improvement.

Some software issues that still need to be addressed are:– Fix software for compile errors for gcc 3.4+ version– Remove all compilation warnings– Output order of views is not sequential or parallel. It is on an as ready basis.– All the macros need to be cleaned up & removed permanently along with commented code

related to SVC– Prepare validation scripts (work in progress)– Provide support GOPsize=1 (with motion skip & IC)– Trace file support for arbitrary view_id assignments

The AhG on JMVM and JD text editing recommended:– To consider editor’s input in preparing future versions of the JMVM and JD.– To discuss the issues in the current version of the software as mentioned above– To improve the manual created for the JMVM software– To follow the same software integration guidelines present in JSVM (repeated below)

Software integration guidelines and rules

In order to improve the whole software integration process, the software integration guidelines and rules are as following:– The integrated software shall compile without warnings when using the provided VC6 and,

VS .NET workspaces, as well as linux makefiles.– Do not use variable declarations inside the header of for-loops (the scope for for-loops is not

correctly supported with all compilers).– Follow the coding style of the JMVM software. Use 2 (two) spaces for indentation, no tabs.– Re-use code and integrate functionality as possible. Try to avoid redundant code.– Do not change the meaning of existing input parameters but define new ones if necessary (and

applicable).

123

– Make sure that new parameters have meaningful default values. Tools should not be switched on by default (if not decided different by the JVT).

– Do not re-structure the output of the compiled binaries (if not decided different by the JVT).– Please change the JMVM version number macro (i.e. “_JMVM_VERSION_”) located in the

file “CommonDefs.h” to be inline with your integration tag.

CVS tag information is as follows:[CVS] host address: garcon.ient.rwth-aachen.de

user name: jvtuser password: jvt.Amd.2authentication: pserver path: /cvs/jvt module name: jmvm or jmvm_red

jmvm_red does not check out certain old folders related to SVC.

4.5.1.1.9 JVT-Y008 (Admin) [H. Kimata, A. Smolic] AHG Report: MVC exper. framework & test cond

At the Geneva meeting, the JVT established the AHG on MVC experimental framework and testing conditions with the following mandates:– To evaluate application needs in MVC framework.– To discuss testing conditions to evaluate specific application needs.– To consider needs for new tools to be evaluated.

The AHG noted that there was one related MPEG contribution M14876 from the USNB of WG 11, which suggests start of a new direction to support Panorama video, suggests that a high-quality reference depth map estimation technique be made available, and discusses the relation between MVC to MPEG FTV activities.

The AHG recommended discussing the relation of MVC to MPEG FTV, and new direction to support Panorama video, and depth map estimation techniques.

4.5.1.1.10 JVT-Y009 -M (Admin) [P. Pandit] AHG Report: MVC solutions using existing AVC decoders

At the Geneva meeting, the JVT established the AHG on MVC solutions using existing AVC decoders, with the following mandates:– Collect comments on methods for enabling AVC decoding of multiview video

(spatial/temporal/others)– Study the complexity of such methods– Investigate the applications enabled– Study compatibility of MVC solutions with existing AVC profiles & levels

At this meeting, no AHG report document was filed and it was noted that there were no contributions on this topic. It was therefore suggested not to create a similar AHG for the subsequent period.

4.5.1.1.11 JVT-Y010 (Admin) [P. Pandit, H. Kimata] AHG Report: MVC RRU and mixed-resolution view coding

At the Geneva meeting, the JVT established the AHG on MVC RRU and mixed-resolution view coding with the following mandates:

124

– Investigate approaches for enhancing MVC coding efficiency using spatial downsampling– Evaluate the complexity of such methods– Investigate the relationship between downsampling approaches and view interpolation– Evaluate subjective quality associated with methods

The following contributions to this meeting were suggested to be relevant to this topic: JVT-Y030, JVT-Y052, JVT-Y054, JVT-Y082.

The AHG recommended to review the related contributions during the meeting.

4.5.1.1.12 JVT-Y011 (Admin) [P. Pandit, H. S. Koo] AHG Report: MVC JMVM coding tools

The JMVM coding tools AhG was created at the Geneva meeting in July, 2007 with the following mandates.– Investigate simplification and improvement of current JMVM coding tools (IC and motion

skip)– Clarify issues related to motion skip mode:– Improve motion skip mode by adaptive reference view selection for motion skip– Describe motion skip for multiple inter-view reference pictures (consider both anchor and/or

non-anchor pictures)– Conduct a fair comparison of motion skip by disabling motion skip for non-anchor pictures

based in inter-view dependencies indicated in SPS– Study IC for motion skip mode using sequences containing temporal illumination changes (e.g.,

KDDI data from original call for evidence) – Investigate techniques for single loop decoding to reduce complexity starting with motion skip

A few emails about testing conditions for multiple inter-view reference pictures were exchanged over the reflector.

The following contributions relevant to this topic were identified in the AHG report: JVT-Y033, JVT-Y036, JVT-Y037, JVT-Y038, JVT-Y042, JVT-Y044, JVT-Y053, JVT-Y054, JVT-Y058, JVT-Y059, JVT-Y060.

The AHG recommended to discuss and evaluate the contributions related to the AhG.

4.6 Closing session notesIn 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 WG 11 parent body and Huawei for hosting the 25th JVT meeting.

The meeting was closed at 12:35 pm on Friday 26 October 2007.

4.7 JVT liaison communications

The JVT did not receive liaison communications at this meeting.

125

The JVT sent liaison statements as found in JVT-Y201 to a number of organizations – specifically to BDA, DVD Forum, DVB, ATSC, SCTE, SMPTE, 3GPP, 3GPP2, OMA, ISMA, IETF. The purpose of these liaison statements was

– to inform relevant organizations of the recently-completed work on professional profiles and scalable video coding, and

– to solicit input from relevant organizations on requirements for future work on scalable video coding (SVC) relating to bit depth, chroma format, and color gamut issues.

5 AVC base specification and related topicsThe latest prior errata reporting status was provided in the JVT-X210 output document of the previous meeting. Two additional documents related to errata issues were submitted for consideration at this meeting: JVT-Y083, and JVT-Y084. One of these was considered by the JVT and the other was withdrawn by its contributor.

5.1.1.1.1 JVT-Y083 ( Prop 2.2) [S. Narasimhan (Motorola)] On end_of_stream NAL unit and splicing

Splicing is currently used in US Cable networks for digital advertisement insertion based on the MPEG-2 video standard, and there are plans to migrate these applications based on AVC in the near future. In these applications, the splicing equipment (or function) combines two independently encoded AVC streams and is expected to produce an AVC “conforming” output for receiving equipment. This contribution outlined some issues related to generating an AVC conformant output by such splicing equipment and suggests some changes to the AVC standard to assist these applications.

JVT decision: In the next corrigendum, we plan to add an informative note to subclause 7.4.2.6 (end of stream RBSP semantics), stating approximately as follows:

“NOTE – When an end of stream NAL unit is present, the bitstream is considered to end (for purposes of the scope of this Recommendation | International Standard). In some system environments, another bitstream may follow after the bitstream that has ended, either immediately or at some time thereafter, possibly within the same communication channel.”

For no_output_of_prior_pics_flag (item 64 of JVT-X210), a “(but should not)” or “permitted (but not recommended)” is planned to go into subclause 7.4.3.3.

Our plan in relation to the ISO/IEC approval process, is to issue a DCOR in January and COR in July.

JVT has agreed on how to address end of stream NAL units and no_output_of_prior_pics_flag, and will document the details of the conclusion in an upcoming COR.

5.1.1.1.2 JVT-Y084 -L (Late Prop 2.2) [A. Rodriguez (Cisco)] Provisions for concatenation and splicing of streams <<withdrawn>>

This contribution was withdrawn by its contributor.

126

6 Scalable video coding (SVC) phase II

6.1 Core experiment #1 & related docs: SVC bit depth scalability

6.1.1.1.1 JVT-Y039 ( Prop 2.2/3.1) [M. Winken, H. Schwarz, T. Wiegand (HHI)] CE1: Results for SVC bit-depth scalability

This document presents results for the Viper sequences using configuration 1 and 3 of CE 1 on bit-depth scalability using the approach as described in JVT-X057. Results from the current design using latest test conditions were provided. No change to syntax, semantics, and decoding process. Encoder bug fixes and some other software progress were reported.

Includes PPS-level tone map specification – vs. prior SPS-level.

This method remains our current reference design.

6.1.1.1.2 JVT-Y056 -V ( Info) [M. Wien (Aachen U.)] Verif JVT-Y039 results for bit-depth scalability

This was a verification contribution relative to CE1 SVC on bit depth scalability for document JVT-Y039. The results of JVT-Y039 were reported to have been confirmed.

Summary of the verification task: The proponents reportedly provided the source code of the modified JSVM_8_12 software with BDS as distributed among the CE-participants, configuration files, simulation scripts, and bitstreams according to the test conditions.

For verification the following steps were reported to have been performed:– The software provided by the proponents was successfully compiled under Linux and was used

for the simulations.– The test sequences provided on the ftp site at Sharp and provided by the proponent were used.– Simulations were run using the simulation scripts provided by the proponents.– The provided bitstreams were successfully decoded.– The results were reportedly found to exactly match the results reported in the RD data provided

with the streams. These results reportedly matched the results reported in contribution JVT-Y039 for both configurations (configurations 1 and 3). The results were reported in the accompanying Excel sheet.

Question: How carefully was this software studied? Answer: Not much study – just ran the software.

6.1.1.1.3 JVT-Y032 ( Prop 2.2/3.1) [M. Winken, H. Schwarz, T. Wiegand (HHI)] Bit-depth SVC: New results for Freeway sequence

This document presents new results for the Freeway sequence under the testing conditions as given in JVT-W302 (Core Experiment on Bit-depth Scalable Video Coding). It was reportedly shown how a significantly improved rate distortion performance could be achieved by using a three layered approach with an AVC-rewritable 8 bit intermediate layer. This approach reportedly requires no changes in syntax and semantics to the current JSVM. As a reference, the results for this sequence as summarized in JVT-X102 were given.

127

Shows improvement for this sequence (bad performance of proposal in results of last meeting). Claims that tone-mapping operator as used for this sequence produces low-contrast 8 bit sequence (higher bit levels hardly used). Now uses a three-layer approach (with linear 8-bit in between, using re-writing as one stream). Tweaked manually, but most probably an automatic algorithm could detect such weird tone mapping and automatically run such an approach.

Suggested interpretation of prior phenomenon of not-so-good performance on this sequence: interaction of two factors– non-linear tone-mapped picture rather dark (max luma 162), and– MCP was only using the 8-bit base layer.

Proposed solution: a 3-layer approach using an intermediate layer and final layer for the 10-bit enhancement with linear tone mapping. Two bottom layers structure to enable AVC rewriting.

Modified scheme reportedly has R-D performance comparable to prior Thomson approach.

6.1.1.1.4 JVT-Y057 -V ( Info) [M. Wien (Aachen U.)] Verif JVT-Y032 new results for Freeway sequence

This was a verification contribution relative to CE1 SVC on bit depth scalability for document JVT-Y032, reporting results for the Freeway sequence. The results of JVT-Y032 were reported to have been confirmed.

Summary of the verification task: The proponents provided the source code of the modified JSVM_8_12 software with BDS as distributed among the CE-participants, configuration files, simulation scripts, and bitstreams according to the specified test conditions.

For verification, the following steps were reported to have been performed:– The software provided by the proponents was successfully compiled under Linux and was used

for the simulations.– The test sequences provided on the ftp site at Sharp and provided by the proponent were used.– Simulations were run using the simulation scripts provided by the proponents.– The provided bitstreams were successfully decoded.– The results were found to exactly match the results reported in the RD data provided with the

streams. These results reportedly matched the results reported in contribution JVT-Y032. The results were reported in the accompanying Excel sheet.

– An example configuration was encoded and was found to exactly match the bistream provided by the proponent.

Question: How carefully was this software studied? Answer: Verified by bitstream decoding; no thorough study of software.

6.1.1.1.5 JVT-Y048 ( Prop 2.2/3.1) [Y. Ye, H. Chung, M. Karczewicz, I. S. Chong (Qualcomm)] Prop SVC bit depth scalability

In this contribution, an approach to bit depth scalability coding was proposed. This proposal relates to the difference between the HHI scheme and the Thomson scheme. Ways to “merge” the HHI scheme and the Thomson scheme are described. Simulations are only completed for the HHI framework. Simulations reportedly show that, for the Freeway sequence and the 12-bit sequences where the HHI scheme (prior to this meeting) underperformed the Thomson scheme, a modified

128

method was reported to have performance on par with Thomson. Preliminary results reportedly indicate that a merge may also be applied to the Thomson scheme and used to bring up its performance, especially for the 10-bit sequences where it has underperformed the HHI scheme.

For the HHI scheme, the reason why it (previously) underperformed the Thomson method on Freeway sequence appears to bre because it disallows any temporal prediction to be carried out in the enhancement layer (10-bit MC). The same underperformance was reported to have been observed for the two 12-bit sequences (e.g. “Sunrise”). Lack of this prediction path can degrade coding efficiency when the additional bits carried in enhancement layer video are useful to form a more accurate temporal prediction. The JVT-Y048 proposal suggests to enable the BLskip mode to provide an alternative prediction path. It was suggested for the encoder to make an R-D decision between the existing IntraBL+inverse tone mapping mode, and the BLSkip mode. The encoder would then send a 1-bit flag per macroblock to indicate the selected mode. In the proposal, residual prediction is always turned off if the BLSkip mode is used.

Uses tone mapping and motion compensation (by introducing BL_skip mode). Requires multi-loop decoding and storage of both 8 bit and 10 bit results. For the 12-bit case, performance is not significantly more complex than simulcast.

Adds a requirement for the decoder to perform a high-bit-depth motion compensation.

Question: How much better than simulcast are the presented results? In presented results, there seems to be a high ratio of enhancement layer bits to base layer bits. Are the test conditions appropriate for the target application?

Question: Does it require multi-loop? Yes – requires full decode of base layer.

Question: Does it require storage of both the 8 bit and >8 bit layer decoded pictures? Yes.

Proponent suggestion is not immediate adoption of this scheme as-is, but rather further study of the issues.

A request was made for the latest results to be shown together, with comparison to simulcast, and to include Viper sequences.

6.1.1.1.6 JVT-Y050 -V ( Info 2.0/3.1) [Y. Gao and Y. Wu (Thomson)] CE1: Verif JVT-Y048 Qualcomm CE1 SVC prop

This was a verification contribution relating to CE1 on bit-depth scalability for document JVT-Y048.

The proponents of JVT-Y048 provided source code based on the bit-depth scalability reference software for JVT-X057, configuration files conforming to the test conditions defined in the CE1 description JVT-X301, simulation scripts, and experimental results.

For verification the following steps were reportedly performed:– The software provided by the proponents was compiled to generate encoder and decoder

executables.– The test sequences provided on the bit-depth scalability AhG ftp site at Sharp were

downloaded.

129

– The reconstructed sequences (some other test sequences other than those for CE1) at the encoder and the decoder were matched.

– Simulations were conducted using the simulation scripts provided by the proponents.– Results were reported in the provided Excel files.– The results were reported to exactly match the results reported in document JVT-Y048

Question: Was the software closely studied algorithmically or just run as provided by the other proponent? Answer: Just run. Verification done by only running software (no study).

6.1.1.1.7 JVT-Y067 ( Prop 2.2/3.1) [S. Liu, A. Vetro (MERL)] CE1: SVC bit-depth scalability results

This document presented new results for the inter-layer prediction scheme for SVC bit-depth scalability proposed in JVT-X075. The new results were generated based on core experiment conditions defined in JVT-X301r1.doc. The merits of a block-based inter-layer prediction were also discussed.

The inter-layer prediction technique proposed in JVT-X075 applies a scale factor and offset value for each macroblock of each color channel. These values are predicted from spatially neighboring blocks and entropy coded. The proposed inverse tone mapping technique is independent of the forward tone mapping method and is reported to be able to cover a wide range of bit-depths. Also, the proposed method could reportedly be applied adaptively to different regions of interest, different frame pictures, and different color channels.

The key merits of the proposed approach in contrast to the global look-up table method reportedly include:– Adaptive to variety of tone mapping techniques, including locally adaptive tone mapping

schemes, which could improve coding efficiency for such sequences.– Low delay encoding since inter-layer prediction decisions are made locally on a block basis

without the need to determine the values of a LUT for an entire picture or group of pictures.– Reduced decoder complexity since implementing per pixel LUT is more costly than applying a

block-based scale and offset.

Proponent recommendations:– Discuss the merits of block-based inter-layer prediction and consider adopting this approach as

an alternative to the global LUT method currently defined in the JSVM.– Continue the CE to further evaluate inter-layer prediction techniques when different tone

mappings are applied, e.g., to different regions or color components.

Some problems were evident for chroma channels – proponent is working on that.

Local adaptation by linear scaling plus offset function: Scaling factor, offset and prediction direction are encoded per macroblock (differentially) instead of tone mapping with LUT. Independent chroma prediction (independent of color format). It was claimed that the scheme could be benefical for larger bit depth ranges (8->12 bit) and for locally adaptive tone mapping schemes. Experimentally, some problems were found for chroma, approx. 2 dB loss (above 45 dB) compared to LUT method (bug? – preliminary results that improve shown in revision). For sequences with global tone mapping (Viper) LUT performs better overall. For 12-bit sequences with local tone mapping, LUT performs better below 45 dB (note: strange behaviour of LUT method at the rate point around 25 Mbps; LUT method still SPS based, not PPS based as presented in Y039). In the

130

range of 50 dB and above, local adaptation by linear function provides gains of 0.5-0.7 dB for the two test sequences available.

Further study needed: More test material on 12 bit and diversity in common tone mapping algorithms needed. More evidence about relevance for application and potential profiles needed.

Extra overhead causes degradation of quality at low bit rates.

PSNR level is very high.

Remark: The results of the reference method shown in this contribution are for design status prior to the output of the last meeting – particularly not including PPS-level tone map adjustment capability.

Remark: How much better than simulcast? What are the bit rate ratios?

Remark: There is no 12-bit MC in this, so there is a complexity difference relative to 12-bit simulcast solution.

Proponent suggests merit of this approach in regard to local adaptation capability, such as region-of-interest application or other use of differing tone map use in different areas of picture.

Question: What is the encoder method to determine the parameters? Right now encoder is doing a search.

Remark: Decoder supporting both LUT and this approach would need two code paths and ability to switch between them, and syntax parsing capability.

Question: How common would we think a localized tone map use would be?

Remark: What are the application requirements? 12 bit 4:2:0?

Question: Is there a clear benefit for this spatial adaptivity capability?

Remark: In professional applications, increased fidelity has value for reasons other than visual viewing quality.

Proposed technique seems not beneficial for Viper sequences. Benefit seems small on the two other sequences.

Remark: Very strange behavior in some reference curves – e.g., decrease in objective fidelity with increase in bit rate.

We seem to need a better understanding of the needs and more test sequence data. Further study necessary.

Based on current results, no action to be taken.

6.1.1.1.8 JVT-Y073 -V ( Info) [A. Segall (Sharp)] Verif of JVT-Y067 MERL CE1 response

131

This document provides verification of Mitsubishi's response to CE1 on bit-depth scalability. Mitsubishi provided Sharp the software for JVT-Y067. Sharp reportedly carefully inspected the software, which included integrating Sharp's proposal into the software and performing a detailed comparison between JVT-Y067 and JVT-Y071. Sharp then compiled the software and generated results as specified in the CE. All results reportedly matched. JVT-Y067 was thereby reported to be verified.

6.1.1.1.9 JVT-Y071 ( Prop 2.2) [A. Segall, Y. Su (Sharp)] CE1: Inter-layer prediction for SVC bit-depth scalability

This document provided a response to CE1: Inter-layer Prediction for Bit-Depth Scalable Coding. This response included results from JVT-X067, which proposed a modified inter-layer for bit-depth scalability. The scheme consists of a series of shifts and adds and is spatially varying.

This is conceptually very similar to JVT-Y067, and results were presented that included curves for each of these techniques. The Sharp method seems better at lower rates while MERL method seems better at higher rates.

An encoder-decoder mismatch problem occurred on one sequence.

A recommendation was made to further study 12-bit and localized tone mapping case.

See notes above in discussion of JVT-Y067.

6.1.1.1.10 JVT-Y078 -LV (Late Info 2.2/3.1) [S. Liu, A. Vetro (MERL)] Verif SVC JVT-Y071 CE1 results from Sharp

This document provided a cross-verification of the CE1 document JVT-Y071, proposed by Sharp. Both MERL and Sharp reportedly integrated their proposals, i.e. JVT-X075 for MERL and JVT-Y071 (JVT-X067r1) for Sharp, into the CE1 common software. The verification was based on the integrated software, and the bitstreams were generated according to the CE1 core experiment conditions. An accompanying Excel file contained simulation results with RD curves in comparison with the CE1 (LUT) results. The results of JVT-Y071 from Sharp were reported to have been confirmed.

Detailed source code review conducted. Results confirmed.

6.1.1.1.11 JVT-Y072 -L (Late Info) [A. Segall (Sharp)] Donation of tone mapped image sequences

In the previous Geneva meeting, there was an interest from the JVT for additional higher bit-depth data for testing bit-depth scalable coding tools. Sharp reported that it is currently able to donate two such sequences, and the purpose of this document was to document how the sequences were created.

The two donated sequences are currently stored on the Sharp FTP site that hosts the bit-depth and chroma format scalability AhG. The FTP is ftp.sharplabs.com, and the username and password are (bitdepth_ahg, 2bitd3pTh). The files are located in the directory 1080p/TwelveBit; stored in ZIP containers and titled “sunrise” and “library”.

132

The files were generated from high dynamic range video content that was originally stored in floating point format and in a linear RGB space. The 12-bit representation of the sequence was created by the following process:

– RGB values normalized to the set [0, 1].– Normalized values were converted to YCC using the ITU-R BT.709 reference

primaries.– Chroma planes subsampled by a factor of two in each dimension using the separable

filter [-0.063 0.0 0.0299 0.0 -0.0831 0.0 0.3098 0.4994 0.3098 0.0 -0.0831 0.0 0.0299 0.0 -0.0063]

– Resulting 4:2:0 data was quantized “linearly” to 12 bits of precision with a rounding operation.

The output was then stored in a YUV file container as 16-bit data, with the 12 bit data stored in the least significant bits.

Creation of the corresponding 8-bit data was accomplished by operating on the original, floating point image. It was created using the following process:

– Image tone mapped to 8-bits using a spatially varying operator described in documents referenced in the contribution. Here, the output corresponds to the LCD image of an HDR display and is stored as 8-bit R'G'B'.

– Tone mapped output converted to YCC using the ITU-R BT.709 reference primaries.– Chroma planes subsampled by a factor of two in each dimension using the separable

filter [-0.063 0.0 0.0299 0.0 -0.0831 0.0 0.3098 0.4994 0.3098 0.0 -0.0831 0.0 0.0299 0.0 -0.0063]

– Resulting 4:2:0 data was quantized “linearly” to 8 bits of precision with a rounding operation.

Note: Data are 12-bit 4:2:0. Remark: Is this realistic?

Thanks were expressed to the contributors. A copyright statement was included in the zip container.

6.1.1.1.12 JVT-Y080 ( Prop 2.2/3.1) [Y. Gao, Y. Wu (Thomson)] CE1: SVC combined spatial and bit-depth scalability

This contribution presented simulation results of Thomson’s proposed technical solution to bit-depth scalability JVT-X051. The software integration and the test conditions in the performance test were subject to JVT-X301. In particular, simulations results of combined spatial and bit-depth scalability were provided. Complete simulation results including the PSNR-bitrate points for Y, Cb, and Cr channels were reported.

This contribution proposes a technical solution to bit-depth scalability that was reportedly conforming to the current SVC standard (exact meaning?). The inter-layer bit-depth prediction was realized by a left bit-shift of each channel (Y, Cb and Cr) of the base layer MB to predict the co-located enhancement layer MB (which can be supported by the current inverse tone map design). This process was suggested to be called “upsampling process for bit depth prediction” and is proposed to be invoked when bit depth scalability is enabled. With the proposed solution, there was reported to be no new syntax elements needed to support the proposed solution.

Uses bit shift/truncation for the mapping between 8 and 10 bit (no tone mapping); unlike the current JSVM LUT tone mapping, this uses motion compensation in the enhancement layer.

Motion compensation needed for spatial scalability.

133

Comparable to case 3 of JVT-Y039 – both parties were asked to report back with a comparison of their results – see BoG report JVT-Y088 and related notes. Note: 3-layer approach may be less complex because higher spatial resolution MC is performed with 8 bit.

The proposal uses MC at the enhancement layer, unlike the current reference adopted method, along with inter-layer prediction with bit depth expansion.

Question: Comparison to current reference method (the one with 8-bit MC at lower layer only)?

Without the spatial scalability aspect, we have the same situation as at last meeting, basically. Except for the “freeway” sequence, the reference method does better. With the new 3-layer rewrite approach JVT-Y032, the compression results seem about the same for the two approaches.

How about a 3-layer approach – use a spatial scalability enhancement layer that is then enhanced with bit depth scalability. JVT-Y039 reportedly includes such results as its “configuration 3”, which seems directly comparable to what is reported in this contribution.

How do the results compare? Seem roughly comparable at first glance, and simulcast relationship should be considered for such a comparison. Interested parties were asked to look at these issues off-line. See BoG report JVT-Y088 and related notes.

6.1.1.1.13 JVT-Y081 ( Prop 2.2/3.1) [Y. Wu, Y. Gao (Thomson)] CE1: SVC study on inter-layer prediction: bit-depth scalability

This contribution presented further study on inter-layer prediction within the framework of bit-depth scalable coding proposed in JVT-X051, which uses motion compensation at the enhancement layer bit depth.

It focused on enhancing the JVT-X051 method by employing inter-layer prediction techniques other than linear scaling.

As an example, the LUT based inverse tone mapping algorithm (proposed in JVT-X057) is applied to the enhancement layer macroblock of which the co-located base layer macroblock is intra-coded. Experimental results comparing the LUT based inverse tone mapping technique and the linear scaling in inter-layer prediction were provided. The contribution also provides some experimental results on the 12-bit test sequences by enabling both adaptive inter-layer prediction and the proposed LUT based inverse tone mapping in INTRA_BL mode.

Uses lookup table for 8 to 10 bit mapping, and also MC in the 10-bit layer. Shows improvement relative to the previous proposal (with bit shift = linear mapping).

Remark: Do we have results of comparing the proposed scheme relative to the reference scheme that does not use MC with high bit depth? Not provided in contribution.

Interested parties were asked to look at these issues off-line.

Comparison with results from JVT-Y032 and JVT-Y039 was asked to be made and reported. It was suggested to review then to find out how much is gained by MC in the 10 bit layer.

See BoG report JVT-Y088 and related notes

134

6.1.1.1.14 JVT-Y049 -V ( Info) [I. S. Chong, Y. Ye, M. Karczewicz (Qualcomm)] CE1: Verif JVT-Y080 and JVT-Y081 Thomson CE1 SVC props

This document provided a verification of JVT-Y080 and JVT-Y081, which were Thomson's CE1 proposals. Thomson reportedly provided Qualcomm with the source files for JVT-Y080 and JVT-Y081 which we reportedly inspected and compiled. And Thomson provided config files and Excel spreadsheets. Sequences were obtained from the CE1 ftp site. Qualcomm then generated data points according to the testing conditions in CE1 and compared with the Thomson spreadsheets. The results were reported to match.

Question: How close was the source code inspection?

Participants of CE were asked to provide comparisons of their newest results in common figures; for 12-bit case, it was requested to clarify what the useful rates and application scenarios are, what typical simulcast rates would be, and where we stand as compared to simulcast.

See BoG report JVT-Y088 and related notes

6.1.1.1.15 JVT-Y088 -B [A. Segall] BoG report on bit depth and chroma format scalability

Results of work on bit depth and chroma format scalability were presented as JVT-Y088, and are summarized as follows:

• What’s the application for BDS?– Support professional/higher end displays and “traditional” display in single bit-

stream– Provide “premium” high bit-depth content– Observation from Thomson

• Saw visual difference for computer generated content at 10-bit vs. 8-bit• Did not see visible difference between 10-8 for film

– We must be able to see differences (subjective tests)– More information (liaison statements to BDA to HD-DVD)– Blu-ray/HD-DVD/Broadcast

• 8-bit decoders• HDMI 1.3 (30, 36/48)• Must fit…

– Production/post-production• Needs: reduce storage costs of managing multiple versions of sequences• Support different resolutions (HD to 4k-by-2k)

– Quantify needs …• Consumer Applications: Blu-ray/HDDVD

– Two layer system with same spatial resolution– Resolution: HD (1080p24)– Total bit-rate not to exceed 29Mbps/40Mbps– No additional constraint on baselayer bitrate (with exception of video bit-rate

constraint)– No sacrifice of visual quality of base layer– Enhance layer

• Higher bit-depth• Higher chroma format? 4:2:2 or 4:4:4?• Wider color gamut: YCC to xvYCC support• Percentage of bits

135

• 4:2:0 both layer: target 25%• 4:2:0 to 4:2:2:/4:4:4: target ? (but probably something higher than

25%; perhaps 40%)• Recommendations from BoG:

– Continue CE and AhG– Liaison letters to BDA and HD-DVD forum– CE sequences to include:

• Source type: • Viper (Freeway, waves, plane, CR and staples) • No SVT• sunset ?• NASA, CG (further study)• Desire to test total of 8

• Stay with 1080p• Try to test both 10/12 bit data• TMO (linear: 1, global: 4, spatial: 2)

– Mandate of AhG to include 4:2:0 to 4:2:2/4:4:4 scenario• Also desire to test 4:2:0->4:4:4

– For all sequences: generate 4:4:4, convert to 4:2:2, convert to 4:2:0, convert to 8-bit– New mandate for AhG

• SVT data may be redundant … consider 1-2 sequences• Viper data: capital records, night, staples show very similar visual characteristics; suggest

using only 1-2 (choose the one with scene cut)

The results of prior experiments were consolidated into accompanying spreadsheets and reviewed – however, no proponent seems to have provided full results for all test sequences.

Remark: Combination of bit depth and spatial scalability does not appear useful.

Comment: Things might look different with some new results – perhaps 1 dB relative to simulcast.

Remark: There were differences between simulcast scenarios input to this meeting.

Suggestion to redefine simulcast comparison in terms of focusing on quality differences at equal total bit rate…

The test data available seems inadequate.

Various factors were discussed.

Visual evaluations seem necessary to be able to make conclusions about designs.

The effort so far has been basically an exploration area – further input would be needed to clarify the market needs.

Our situation: Further clarification of the need and usefulness of the technology seems necessary before proceeding with a standardization project on bit depth or chroma format scalability.

136

6.2 SVC fine-granularity scalability

6.2.1.1.1 JVT-Y075 ( Prop 2.2/3.1) [M. Karczewicz, R. Ranchal. Y. Ye (Qualcomm)] SVC FGS Simplifications

This contribution discussed elements of the VLC coding used in FGS. Based on this analysis changes were proposed reportedly resulting in simplification, with an average performance drop of 0.8%.

The provided plots included results for MGS run in low delay mode as described in JVT-X071.

The contributor proposed to start a CE to evaluate the proposed changes and compare to “vector CAVLC”.

Simplification was compared to AR-FGS, bit rate increase 0.8 % average (mostly at higher rates)

The proposal was claimed to be much better than MGS in cases where a constant bit rate per frame needs to be sent.

Results of delta-rate and delta-psnr compared to MGS (hier. P pictures) were requested to be provided (both for CBR and VBR)

Also it was requested to provide a better understanding of the intended application domain (mobile multipoint videoconferencing?)

Subjective results? Not provided – It was suggested that this may be worth considering in further study.

Remark: AR aspect adds complexity to encoding and decoding – e.g. relative to MGS. The proponent indicates that this may not be the case. Remark: At least the decode complexity is certainly higher. There are more motion compensations to perform (although one is bilinear).

Question: Does low delay imply real-time encoding? Yes.

Roughly the same number of bits for each picture in these tests? Approximately yes.

Bitstream and software availability? Yes. Software is available.

Trade-off between complexity and delay? Response: Proponent suggests that MGS complexity is about the same.

Remark: We have standardized something already – do we have clear evidence that it is not adequate?

Question: What is the asserted benefit of this relative to the hierarchical forward-P picture case? Proponent response: The ability to maintain a roughly equal number of bits per picture in a CBR channel scenario which helps reduce delay. Remark: Should also consider complexity – increased complexity has a delay impact.

Proponent: Benefit of proposed FGS is asserted to be about 2 dB relative to similarly-constrained bit allocation use of current MGS design.

137

Remark: Looking at JVT-X040, do not see that. What are average numbers over all sequences for new proposal and for previous AR-FGS, both for CBR and VBR? Are there any average numbers reported in JVT-X040? Proponent indicates that new proposal has 0.7% degradation relative to prior AR-FGS; comparing to MGS “low-delay”, about 2 dB better; comparing to VBR (no delay constraint), about 0.5 dB better. In both cases, a “GOP size” of 4 frames was used for MGS (i.e. 3-level hierarchical P with one I picture at beginning) while IPPPP for the proposal.

Question: Is constant rate really needed in such low-delay scenarios? For variable bit rate, improvement is not so much – and should avoid introducing an incompatible “dialect”.

Question: One packet per frame? Proponent: Not necessarily.

Question: What is the benefit of FGS (or even SVC) when there is constant bit rate? Proponent: May be constant bit rate on uplink but perhaps not further downstream. Some material presented previously. Suggestion to just send the bit rate that the receiver can receive? Proponent: For cases with multiple recipients of the video? Remark: Multipoint video conferencing on mobile networks?

Question: How much of a niche application are we considering here? Low delay with CBR for multipoint SVC?

Suggestion to have some CE in which FGS technology may apply – what would be the topic?

The issues were requested to be discussed offline to clarify application need/scenario.

Interaction with other application scenarios where other AVC/SVC scenarios would be relevant? Is this for a relatively closed application domain of mobile devices, or a set of devices that has wider interaction with other devices?

Some AR-FGS-related changes previously adopted were reported to not have been integrated into the software yet. CABAC may or may not (but should be) supported in the software.

Suggestion: To create AHG which will help to integrate CABAC and AR-FGS simplifications that were previously intended to be adopted, and investigate the JVT-Y075 VLC changes in the AHG.

Question: How can we conclude on whether a profile that includes FGS technology is needed or not?

Question: Is mobile multipoint videoconferencing the only target application?

Remark: JVT-W093, JVT-X040 and JVT-X071 may contain relevant information to clarify application needs. An application suggested is “Videoshare”, which is a one-way multicast. Question: Is there a serious delay constraint need for that application?

6.2.1.1.2 JVT-Y074 -V ( Info) [A. Segall (Sharp)] Verif of JVT-Y075 Qualcomm proposal on FGS simplification

This document reported verification of Qualcomm's proposal on FGS simplification (JVT-Y075). Sharp reportedly inspected the source code (source code was marked with #define statements, read through those sections and compiled it both ways and provided both results). Sharp also reportedly compiled and generated results for the conditions investigated by Qualcomm. All results reportedly matched with the exception of the Mother and Daughter sequence. (It is believed that Sharp and

138

Qualcomm used different original sequences for Mother and Daughter.) Results were included with the submission.

A new version of the contribution was uploaded. There was a difference on one sequence – likely to be the result of slightly different source sequences (Mother & Daughter case).

6.3 SVC Color space scalability

6.3.1.1.1 JVT-Y076 ( Prop 2.2) [J. H. Park, Y. H. Kim, B. H. Choi (KETI)] Requirement of SVC color space scalability

This document asserted a requirement for color space scalability and described possible scenarios that might benefit from color space scalable coding. This document also claimed that the conventional color conversion equation for color space scalability can cause a mismatch problem between encoder and decoder because of floating point operation so that an integer point conversion method is described for color space scalable video coding. The proposed method requires syntax modifications for color space scalability. Modified syntax tables were described.

Different applications: Requirements for scalability in terms of color sampling and color spaces (matrices). It was claimed that, in the case of layer prediction, color transfer matrices must be mathematically precise (not FP). Solutions proposed included integer transfer matrices and lookup tables.

Remark: Matrix definition may not be sufficient because different color spaces also include e.g. gamma transfer characteristics.

Typically, color is treated outside the coding/decoding process. E.g. YCbCr of BT.709 is different from BT.601. But is it the case that nobody typically cares?

Would it rather be appropriate to encode all scalable layers within only one color space? E.g. conversion of YCbCr to RGB outside the decoding process would rather produce a small error which is in the near lossless range. Further study would seem necessary.

Remark: Chroma format scalability should in principle work, but is not included in any profile yet.

The suggestion in the proposal was to consider inserting an integer-based color conversion into the decoding process – sending integer coefficients in the bitstream.

Remark: True color conversion could be (a lot) more than a matrix transformation – also consider transfer characteristics, colour primaries, reference white.

Remark: Consider the possiblity that the base layer is SD (using the BT.601 color space) and the enhancement layer is HD (using the BT.709 color space).

Question: How much real benefit would there be by pulling a color conversion process into the decoding process?

Remark: Including sampling grid upsampling (e.g. 4:2:0 to 4:2:2) in the decoding process may be more well-justified than including color space conversion in the decoding process.

139

The provided material was primarily verbal argumentation – real data demonstrating the benefit of such a scheme would be more desirable.

The proponent indicated a desire to show some preliminary results at next meeting.

Presentation deck available? Yes, newly-provided.

6.4 SVC historical information request

6.4.1.1.1 JVT-Y085 -L (Late Info) [M. Karczewicz, Y. Bao (Qualcomm)] Comments on JD text of CAVLC in SVC enhancement layer

This contribution requested clarification on the technology adopted for the CAVLC decoding processes for the SVC enhancement layer.

JVT-W090 was a CE experiment result report for a CE described in JVT-V301 (with CE leader J. Ridge; with J. Ridge of Nokia and M. Karczewicz of Qualcomm listed in the document as partners; and with HHI, Freescale, Huawei, ICT, TI, and RWTH Aachen listed in the meeting report as additional partners). The plan to perform the CE was approved at the January Marrakech meeting, and the final CE plan was agreed by the CE partners and available for review approx four weeks prior to the April San Jose meeting. It contained some changes to CAVLC which came from Nokia for partitioning coefficients into different NAL units in “method 3” along with some other changes to CAVLC and CABAC that had been proposed by others.

The JVT-W090 proposal focused on the changes proposed by HHI. An “r1” of JVT-W090 included software and results for both the changes proposed by HHI and the changes from Nokia to CAVLC. Nokia indicates that they considered their changes to CAVLC to be intended as the benchmark design for the CE and thought that the input experiment results from HHI would be sufficient for evaluating these changes, so they did not consider a submission of a contribution of their own to be necessary for consideration of these changes. In hindsight, Nokia expressed regret that they did not clarify the situation by submitting their own proposal contribution for the aspects of the CE technology that they originated. The meeting report recorded adoption of JVT-W090 in response to the experiment results submitted by HHI.

The Nokia changes were edited into the San Jose JD output along with the HHI changes. Subsequent review of the text between then and through the Geneva meeting and the Last Call review process in ITU-T did not indicate any problem with the outcome. And now there is still no indication of a technical problem with them (although Qualcomm indicates that they would have preferred the CAVLC entropy coding for MGS SVC enhancements to have been more closely aligned with non-SVC CAVLC coding for reasons of minimizing the implementation effort needed for SVC support).

Suggestion: CE descriptions should have IPR forms from each contributor of technology to the CE and are considered proposals from the set of technology contributors. Agreed.

6.5 SVC Error Resilience

6.5.1.1.1 JVT-Y047 ( Prop NN 2.0/3.1) [Y. Guo, Y.-K. Wang, H. Li (Nokia)] SVC motion-copy error conceal for key pics

140

The current JSVM software only supports the frame-copy error concealment method for key picture (i.e. the first picture of each “GOP”) losses if the same spatial or CGS layer data is considered for error concealment. This contribution presented motion-copy error concealment for key picture losses. Four QCIF@30Hz common sequences were tested with single-layer coding. Experimental results reportedly demonstrated that motion-copy can achieve better results than frame-copy at the tested GOP sizes (1, 2, 4, 8, 16) and packet loss rates (3%, 5%, 10%, 20%). For the Football and Foreman sequences, the gains for GOP sizes less than 4 were reportedly about 0.5~2 dB, whereas the gains for the other GOP sizes were reportedly no more than 0.5 dB. For the Bus and Mobile sequences, the gains for GOP sizes less than 8 were reportedly about 2~4 dB, whereas the gains of the other GOP sizes were reportedly about 0~2 dB. Source code and simulation scripts (including executable files and batch files) were provided in attached files of the contribution.

Non-normative motion-copy error resilience for key pictures in JSVM.

Non-normative proposal. Motion-compensated block copy from previous key picture.

Questions: How modular? How extensive? Maintenance issue? Response: Code for slice error concealment is more of a maintenance issue.

Question: Would there be interference with other work? Remark: Normative work should take priority.

Question: How much work do we have yet to go to get the text and software aligned? Not completely sure.

Is it working for interlace? Think so.

JVT decision: Adopted (but at a lower priority for software integration than the normative aspects).

6.6 SVC high-level syntax and SEI

6.6.1.1.1 JVT-Y046 ( SEI showcase) [C. He, H. Liu, Y.-K Wang, H. Li (Nokia)] SVC showcase of temporal level switching point SEI

At the Geneva meeting, a temporal level switching point SEI message (proposed in JVT-X032) was adopted in SVC. In this contribution, a showcase for the temporal level switching point SEI message was presented. The showcase tries to demonstrate that, without temporal level switching point SEI messages, a streaming server would have to run complex analysis to obtain the information contained in the SEI messages, or would have to perform temporal level switching without the information, which would then result in incorrect decoding results and degraded video quality. The source code of the implementation and the simulation scripts for the showcase were both provided as attachments.

JVT decision: Showcase is considered acceptable.

6.6.1.1.2 JVT-Y066 ( Prop 2.2/3.1) [N. Sprljan, L. Cieplinski (MEI)] Perceptually optimal SVC layer removal ordering SEI

This contribution proposed using CGS and allowing a varying number of dependency layers at different temporal levels, while preserving perceptually optimal video quality for the given bit-rate. The proposed strategy is based on the creation of new adaptation points for which decoding is

141

supported by loss compensation post-processing at the decoder. Application of such a scheme was asserted to lead to additional useful decoding points, as was asserted to be shown in the presented results. A syntax supporting a description of preferred layer combinations was proposed.

Question: After being “pruned” in this manner, is the bitstream still a conforming bitstream? Response: Perhaps not – it appears to an ordinary decoder like a bitstream from which some packets have been lost.

Remark: A specified decoder behavior in response to the missing data may needed.

Question: How much better is the perceptual quality of pruning using this proposal than the kind of pruning that can be performed without it?

Remark: The lack of conformance of such a bitstream that is (deliberately) delivered to a decoder poses a conceptual problem – we generally do not work on explicitly enabling deliberate construction of non-conforming bitstreams.

Remark: The work seems somewhat preliminary.

Further investigation would be needed to determine the value of this scheme relative to what we can now do without it.

Presentation is available.

6.7 SVC Conformance and verification

6.7.1.1.1 JVT-Y020 ( Ed. Draft) [V. Bottreau (Thomson), A. Eleftheriadis (LM)] SVC conformance testing draft

This contribution contains proposed modifications for the SVC conformance testing draft text (relative to JVT-X205).

Presentation uploaded (during meeting).

See also AHG report JVT-Y003.

January (before next meeting) target for delivery of bitstreams – however, there is a dependency on reference software.

82 bitstreams (from each of which can be derived more than one subset bitstream).

The editors are generally satisfied with the bitstream coverage.

Need to check correspondence of text description with editorially-final SVC text.

6.7.1.1.2 JVT-Y021 ( Info) [V. Bottreau (Thomson)] SVC verif test bitstreams Scalable High profile

This information contribution provided SVC verification test bit streams for the Scalable High profile. The proposed bitstreams correspond to different bit rate settings relative to the SH2 test as described in MPEG’s SVC Verification Test Plan 1 (MPEG output document N9189). In addition,

142

the contribution discussed alternative subjective evaluation methods that are used within the “Scalim@ges” project.

Scalim@ges is reportedly a project from the "Media and Networks Cluster” in France, launched in July 2006 for two years. The project is reportedly composed of four large companies (Thomson, France Telecom, Alcatel, TDF), some SMEs (whatever those are), and research institutes. The goal is to demonstrate the viability of SVC on business cases from the broadcast, broadband and mobile domains. The introduction of the 1080p format is also reportedly considered.

The "Media and Networks Cluster” brings together actors from higher education and academic research institutions, SMI/SMEs (SMI being another undefined TLA) and large companies mainly from Bretagne and Pays de la Loire regions, who are leaders in the media and networks fields.

As described in SVC Verification Test Plan 1 [N9189], the SH2 test corresponds to a low bit rate setting. This contribution proposed to use two different bit rate settings for the SH2 test, namely medium and high.

There are different subjective methodologies; for the current purpose the contributors proposed to use the SAMVIQ and preference methodologies.

SAMVIQ (described in an EBU technical report of 2003) is a multi stimuli continuous quality scale method using explicit and hidden references. It provides an absolute measure of the subjective video codec quality which can be compared directly with the reference, i.e. the original video signal. SAMVIQ reportedly permits a high degree of resolution in the grades given to the systems that fits accurate quality discrimination requirements. The SAMVIQ methodology produces, for each sequence, a MOS (Mean Observer Score), a confidence interval, and a standard deviation. The MOS is a value between 0 and 100 which represents the video quality and the confidence interval represents the range of values ([MOS-IC ; MOS+IC]), where there is a probability of 95% to include the MOS for a high number of subjects.

Preference tests produce, for each sequence, a percentage. This percentage represents the proportion of observers who prefers a first video clip to a second. Normalized to 100, it produces the proportion of observers who prefers the second sequences to the first. Preference tests reportedly do not provide a straightforward quality score, but were asserted to be useful in the following cases:

– discriminate conditions or confirm tendencies in case of similar quality that cannot be distinguished with usual quality assessment methodology respect of interval of confidence;

– comparison of video quality between different picture resolutions, since it is reportedly not possible to obtain a reliable quality score between different image sizes.

(This was an information document with respect to JVT consideration.)

7 Multi-view coding (MVC)Question: Will MVC profiles be designed to support interlaced video? (Needs to be answered in order to determine the set of features that need to be designed.)

Answer: No.

JVT decision: Agreed (at least this is the direction in which we are headed presently).

143

It was suggested to make a resolution to visibly note this, and this suggestion was agreed upon.

7.1 Core experiment #2 & related docs: Adaptive reference filtering

7.1.1.1.1 JVT-Y041 ( Prop 2.2/3.1) [P. Lai, A, Ortega, P. Pandit, P. Yin, T. Dong, C. Gomila (Thomson & USC)] MVC CE2: Adapt ref filtering

This contribution was submitted in response to CE2 (JVT-X302) as created at the last meeting to evaluate the coding gain of adaptive reference filtering (ARF) for MVC. JVT-W065 proposed an adaptive reference filtering approach (ARF) for inter-view prediction in multi-view video coding. It was asserted to be aimed at coding multi-view video that exhibits mismatches in frames from different views. Following this, document JVT-X060 discussed the complexity of ARF and proposed to use a simpler filter (3x3) with a smaller region of support compared to 5x5 filter in JVT-W065. This contribution presented more detailed results for ARF according to CE2 experiment requirements. ARF was implemented for anchor pictures only for both P and B frame. Complete results were presented for anchor pictures (only).

Filters were designed as Wiener filters, customized for predicting each (original) source video sequence when operating the complete encoding process. There were several filters for each picture, selected based on a depth estimate classifier.

The planned experiments were not yet completed. Results were provided for the anchor pictures only. For this subset of the pictures, the average bit rate savings on those pictures was asserted to be 6%, or equivalently 0.3 dB (for the anchor pictures only). The gains are asserted to range from 0.07 dB to 0.59 dB. The asserted gain is larger for sequences with stronger focus mismatches.

The proponent did not finish the full intended set of experiments; and proposed continuing the CE.

Question: Will this work for interlace? Will MVC support interlace? (preliminarily No, per above)

Question: Is the exact set of filter tap values really critical?

Remark: Can just build filter into the MCP process.

Question: Is the motion search using the filtered reference picture for the motion estimation? Yes.

The proponent’s presentation was made available.

Software was not provided in the contribution.

Suggestion: Include filter simplification in CE investigation.

Conclusion: Continue CE.

7.1.1.1.2 JVT-Y045 -V ( Info) [H. Koo (LG)] MVC CE2: Verif of Thomson prop JVT-Y041

This document provided verification results of JVT-Y041 from Thomson. LG received source code, executables, coded bitstreams, and information including PSNR and bit rate generated by Thomson’s encoder (for anchor pictures only). LG ran the provided source code (without close

144

inspection of its design), carried out the decoding process, and compared the decoded results with the information by encoder.

LG received source code, executables, coded bitstreams for six sequences, and information including PSNR and bit rate generated by Thomson’s encoder. A reference software problem unrelated to the contribution reportedly prevented verification for the Akko & Kayo sequences. For Akko&Kayo, since the view_id is discontinuous and does not start from 0, and the bitstream assembler does not work. For Flamenco2, in MVC coding structure, it does not have B views, so the result reportedly should be the same as Thomson’s old P views results, and was not checked. LG reported that all provided sequences were decoded successfully. The measured PSNR and bit rate during the decoding process were reported to be identical to the data provided by Thomson.

7.2 Core experiment #3: MVC view synthesis prediction & related docs

7.2.1.1.1 JVT-Y068 ( Prop 2.2/3.1) [S. Yea, A. Vetro (MERL)] CE3: MVC report on view synthesis pred

This contribution reports the progress of CE3 on view synthesis prediction for multiview coding. Preliminary results on the use of view synthesis prediction for coding efficiency improvement in free viewpoint scenarios were reported. The depth map for each view was reportedly encoded separately from the multiview video and used to generate view synthesis prediction for coding efficiency improvement. The effects of down-sampling as well as the use of different QPs for the depth map were also reported.

When comparing to the total bit rate for sending both the pictures and the associated depth map, improvements of 5% or about 0.2 dB were reported for various configurations.

Presentation? Available.

Software? Not provided.

7.2.1.1.2 JVT-Y064 ( Prop 2.2/3.1) [S. Shimizu, H. Kimata (NTT)] CE3: MVC view synth resid pred on hierarchical inter-view reference

This contribution proposed a view generation method for view synthesis residual prediction.

Center view is coded with depth map. Depth map is not encoded for other views.

Only tested on one sequence; only for anchor pictures, with base view all intra coded.

Preliminary experimental result for the sequence “Rena” is, when comparing to the total bit rate for sending both the pictures and the associated depth map, reportedly a 13% bit rate saving or a 0.6 dB PSNR gain on anchor pictures using Bjøntegaard measures.

The gain reportedly increases to 15% if there is no need to consider the bit rate of depth map.

Other views are all reportedly predicted from their adjacent views by following the common experiment conditions.

Presentation? Uploaded later.

145


7.2.1.1.3 JVT-Y065 ( Prop NN 2.2/3.1) [Y. S. Ho, K. J. Oh, C. Lee, S. B. Lee, S. T. Na, B. H. Choi, J. H. Park (GIST)] CE3: Depth map gen and virtual view synth

Multi-view depth can be used in virtual view synthesis for free viewpoint video (FVV)/free viewpoint television (FTV) and view synthesis prediction (VSP) for multi-view video coding. However, among the current test sequences, only “Breakdancers” has accompanying depth map information. This contribution describes a depth generation scheme and virtual view synthesis using depth data. An analysis of virtual view synthesis and its relationship to depth coding and preprocessing is also reported.

In this contribution, multi-view depth generation and rendering results under various conditions were reported. Image segmentation and 3D warping techniques were used for depth generation. However, there were reported to be remaining problems such as inaccurate object segment and low temporal correlation. This work was still reported to be ongoing. The experiments on depth map reportedly demonstrated that down-sampling is not good and median filtering can be beneficial to depth coding.



7.2.1.1.4 JVT-Y024 ( Prop 2.2/3.1) [G. Jiang, T. Qiu, M. Yu, Z. Peng, Q. Xu (Ningbo U.)] Disparity est and compression in MVC with disparity maps

A framework of multi-view video plus disparity maps was presented in this contribution. In the framework, the disparity maps are for the use of fast virtual view generation at the user side. On the point of view that the computation ability of the user side is limited due to the resources of the client, it was suggested to be better to generate disparity maps at the server and transmit them to the client. The asserted advantage of sample-wise disparity maps is asserted to be that such maps can be used directly for view generation. However, this is at the cost of relatively larger transmission bandwidth. 8×8 block disparity maps are recommended in this contribution, and a disparity estimation scheme is presented, in which the relationship between adjacent disparity maps is asserted to be easy to use. The 8×8 block disparity maps are losslessly coded by CABAC so as to not introduce coding artifacts which strongly influence the reconstruction quality of rendered arbitrary views. Based on the 8×8 block disparity map transmitted from the server, a sample-wise disparity refinement algorithm was described to generate the pixel-wise disparity map for view synthesis.

Suggests to encode N views and N-1 losslessly (CABAC) encoded disparity maps having 1/8 resolution horizontally and vertically. The decoder then performs post-processing to construct full-resolution disparity maps from the decoded lower-resolution disparity maps.

The contribution reports that a 0.5 dB gain can be achieved by using the refined disparity map

Remark: May need to encode more data in cases where the views are not rectified.

Remark: Encoding depth rather than disparity map information may reduce the number of maps needed to be coded.

146

Remark: May need to consider vector map coding.



7.2.1.1.5 JVT-Y031 ( Req 2.2/3.1) [T. Senoh, et al. (NICT)] MVC requirements for depth info

(Corresponds to WG 11 document m14879.)

This input document suggested requirements for depth information, especially when rendering virtual-camera images. The proponent suggested considering the following to be a requirement: “Depth information shall be able to provide the absolute-distance of objects in order to enable virtual- camera image rendering, as well as the 3D image rendering with correct dimension.”

The contribution discusses enabling the ability to synthesize new views from the provided views by use of depth map information.

The need for this seems generally agreed in principle.

See section below on applications and scope discussion for MVC / FTV.

Question: “should” or “shall”? Exact details should be worked out as appropriate.

FTV requirements will be an MPEG output.

7.2.1.1.6 General discussion and conclusion for CE3 issuesRemark: Each contributor for this CE seems to be doing quite different and preliminary work. Is this a core experiment or a general research area?

Remark: Applying a video codec as-is to depth map coding does not seem to be the right thing to do. Question: Why not?

7.3 Applications and scope discussion for MVC

7.3.1 Depth map coding scenarios discussionCoding scenario #1: Consider coding M ordinary 2D+t video sequences, plus P depth maps. This information can be used to synthesize N views (possibly with N being very large or conceptually infinite). This could enable “3D TV” at, e.g. twice the bit rate of ordinary “2D TV”.

Coding scenario #2: Consider coding M ordinary 2D+t video sequences (joint or “simulcast” coding). These sequences (without additional depth map information) can provide the N=M views to be presented on some display.

Coding scenario #3: Consider coding M=1 ordinary 2D+t video sequences, plus P=1 depth maps, plus one additional 2D+t “background” (BG) video sequence.

147

Each coding scenario may be capable of generation of N views for presentation on an autostereoscopic video display (such that moving your head will change your stereo view perspective).

Remark: Coding scenario #1 is likely to provide better performance in terms of the number of bits needed to provide the necessary quality for the N views.

For M=1 and P=1, we can do this with MPEG-C Part 3.

For M=2 and P=0, we can do this with stereo video SEI messages.

For M=1 and P=1 plus BG, we have something that has been recently discussed in an MPEG AHG as a potential extension of MPEG-C Part 3 in response to a proposal that arrived at the Lausanne meeting of MPEG.

Is that our target application?

“Free viewpoint TV” is considered a more elaborate application than the driving of an autostereoscopic display – more of a virtual reality ability to navigate more arbitrarily within some visual environment. Is that correct?

7.3.2 Joint discussion with MPEG video on MVC / FTV applications and scope

7.3.2.1.1 M14876 USNB input to WG 11 parent bodyThe USNB of WG 11 provided the following three remarks on multi-view and free-viewpoint video coding work (MVC/FTV):

1. The USNB suggests consideration of two distinct forms of multiview video coding. These two forms are: “inward-looking” / “parallel viewing” (where the multiple views are created from distinct viewing positions pointing at essentially the same scene area to be viewed), and “outward-looking” (also known as panoramic mode, where the multiple views are created by taking different viewing angles from the same viewing position). The USNB notes that the current multi-view test set is comprised only of inward-looking sequences. The USNB certainly appreciates the difficulty in obtaining multiview test data (as USNB members have contributed sequences to the current test set), but it is suggested that WG 11 make an effort to gather panoramic video data. Neighboring views in the panorama case may have different inter-view predictive coding issues than adjacent views in the inward-looking case. Inclusion of these cases may thus affect the design and analysis of the view coding layer.

2. The USNB also recognizes that depth map information relating to multi-view video is important to successful widespread adoption of both multiview and free-viewpoint video applications. The USNB suggests that WG 11 undertake activities to demonstrate the capabilities of current state-of-the-art for such depth map estimation. The USNB further suggests that a high-quality reference depth map estimation technique be made available for the design and testing of related video coding standards and to aid implementers of WG 11 specifications. The USNB expects that such techniques should be adopted in MPEG standards as reference software.

148

3. The USNB has reviewed the requirements for free-viewpoint television (FTV) and notes that coding of depth/disparity map information is an integral part of enabling free viewpoint video applications. Since the work on MVC has also led to exploring the coded representation of depth map information for the purpose of optimizing MVC coding efficiency, the USNB suggests that inclusion of depth/disparity map information for the purpose of enabling free viewpoint video be considered within the scope of the MVC project. The USNB believes that an integrated treatment of the subject would lead to a more coherent overall design of the video coding layer.

The USNB indicated that its members will contribute to the work in these areas.

Remark: What are some application scenarios for the “outward looking” case.

Question: Is the outward looking case part of “FTV”?

For the case of panoramic view: Is it possible to gain compression, when cameras have little overlap? Is joint coding substantially beneficial to the outward-looking case?

Seek input on applications and requirements for outward-looking.Study on this was already performed in 3DAV explorationFTV could also use semi-automatic or manually produced depth mapsDepth/disparity map encoding is relevant, should be performed as part of MVC

Disposition: We request further input on the application scenario of the outward-looking case, the role that coding technology can play in that environment, and the degree to which current coding technology does not fulfill the needs, and test material.

7.3.2.1.2 Initial discussion of FTV application scenariosApplication #1 – watch 3-d video on a screen, either “stereoscopic” (e.g. with glasses) or “autostereoscipic” within a limited range of perspective (e.g. 10 degrees).

Application #2 – free navigation with “3-D” or “2-D” viewing (interactively – with a broad range of perspective).

Remark: The coding efficiency benefit of inter-view prediction is rather limited – the bit rate is roughly proportional to the number of coded views.

Remark: Changes of perspective by use of view interpolation, produces artifacts – it may look OK when sitting still, but not look correct while the perspective is moving.

Remark: Display technology is evolving and different displays are capable of showing different (and increasing) numbers of views – we should not presuppose some particular number of views.

Remark: We should create a format that allows any number of views to be created from the encoded data without a proportional increase of bit rate. Perhaps a 2x bit rate increase relative to ordinary 2-D viewing is acceptable, but we should forget much higher bit rate relationships.

Remark: Backward compatibility is an important requirement.

Activities:

149

– Application scenario requirements– Depth map technology development

Some relevant recent WG 11 output documents:– N7777 Steroscopic video requirements– N9163 MVC requirements (Lausanne)– N9168 FTV requirements

Some relevant WG 11 input contributions:– 14779 AHG report on new video – 14952 FTV– 14949 Depth-viewing HDTV camera

Additional WG 11 technical-oriented input contributions: 14879, 14888, 14889, 14920, 14994, 14996.

Suggestion:– Identify typical application cases– Test material for such cases– What can be done with existing standards? Which parts would need to be normative?

Remark: Consider two application scenarios: Navigation in video, generation of views for multiview; their combination may be further out in the future.

Problem: Increase in data rate as compared to single should not be high. This will need to be traded off against the quality of the generated views.

Remark: Range of views will typically be higher in FTV than in current MVC scope (which is, in principle, accommodating N-view displays).

Remark: Technology should be scalable in a way that by stripping off data the ranges of view variation support (and quality) are varied.

WG 11 AHG to be formed to improve understanding of the applications & requirements, and to study the issue of depth maps.

7.3.3 Additional break-out report discussions on FTV applications and scope

7.3.3.1.1 JVT-Y087 -B [A. Vetro, F. Bruls] BoG report: Summary of BoG Discussions on FTV

This document describes the FTV concept, target applications and first thoughts on experimental evaluation resulting from break-out group discussion during the meeting. This is expected to form the basis for experiments that would be defined in an upcoming Call for Proposals on the topic. Open issues to be discussed further were also highlighted.

Presentation on identifying applications and parameters – table shown. Outlines number of views, number of depth maps, properties of applications.

Applications were identified in an accompanying spreadsheet.

150

A “Call for Test Material & Software for FTV Experiments” was provided as an annex.

Needs for displays, test material, etc. were discussed.

FTV can be defined as a compressed representation and associated technologies which enable generating a large number of different views from a sparse view set. This most probably (from technologies currently known) requires implementation of depth/disparity map estimation (non-normative), definition of depth/disparity map representation/compression and interpolation/rendering method (not clear yet whether the latter should be non-normative or normative). All of these elements rely on each other, such that proper technology selection will most probably not be simple. Depending on the application, the view number to be generated may range from two for simple stereoscopic up to "many" for almost-free walk-through within a scene.

WG 11 will issue the following output documents on FTV at this meeting:– N9466 on applications and requirements– N9467 describing FTV test cases and evaluations, and – N9468 which will be a call for contributions on FTV test material.

7.4 MVC Compression Tools

7.4.1 MVC coding tool benefit study

7.4.1.1.1 JVT-Y044 ( Prop 2.2/3.1) [T. Dong, P. Pandit, P. Yin, C. Gomila (Thomson)] Study of MVC coding tools

The current MVC JD does not contain any new coding tools. The JMVM so far has included two new coding tools: illumination compensation and motion skip. This contribution presented updated experiment results, comparing simulcast with JMVM without new coding tools, and JMVM with new coding tools using JMVM 5.0.

It was asserted that, compared with simulcast, JMVM without new coding tools achieves about 17% bit rate savings on average, while JMVM with new coding tools achieves about 24% bit rate savings on average (an addition 9% savings relative to JMVM not using new tools), when using JMVM common test conditions.

The contribution recommends that the JVT adopt the new tools that are in the JMVM into the JD and create two profiles: a “simple” profile to support only high level syntax and an “efficiency” profile that supports new coding tools.

Remark: May be too early to determine profiles.

Question: How long would the complete specification of these tools require in the text specification? Perhaps 40 pages (currently 13 pages).


7.4.2 Illumination compensation & related subjects

7.4.2.1.1 JVT-Y033 (Prop 2.2/3.1) [G. H. Park, M. W. Park, Y. L. Lee, D. Y. Suh, K. Kim (KHU)] Simplif B- and P-SKIP modes on MVC illum comp

151

In this contribution, a modified method of B- and P-SKIP modes on illumination compensation was proposed. Compared to JMVM 5.0, this method reportedly shows almost the same performances as the existing JMVM method while reducing the complexity of decoding processes and memory bandwidth.

The motivation of this contribution is simplification.

Some participants expressed support for the proposal, suggesting that it simplifies decoder operation. Another participant indicated that there might not be a real simplification here, partly because some parts of the computation can be shared between different parts of the decoder processing.

It was observed that this is not a change to the basic effectiveness of the IC coding tool, which is a more important topic for our current focus of effort.

The contribution reports on a strange case: ic_flag=1 & DVIC=0. Does this indicate a bad encoder mode decision or should this be restricted? Proposes changes to derivation process for DVIC.

The proposal reports having the same coding efficiency, but reduced complexity. Complexity analysis: numerical results were based on number of times that IC was invoked, as well as arithmetic operations. A substantial savings was reported, but there appears to be a tradeoff. Some clarification is needed.

It as noted that the IC tool is not currently part of the MVC JD specification.

Remark: There might be alternative solutions.

The case of ic_flag = 1 and DVIC = 0 case is agreed to have a problem.

JVT decision: Adopted into JMVM as a bug fix, since there is a need to fix the problem.


7.4.2.1.2 JVT-Y038 ( Prop 2.2) [J. Huo, H. Yang, Y. Chang (Xidian U.), S. Lin, S. Gao, L. Xiong (Huawei)] MVC illum & color compensation

In this proposal, a linear compensation model was used to compensate illumination and color mismatch for MVC. Model parameters were estimated using statistical linear regression analysis. For the illumination compensation, it operates on the MB-level due to there being local luminance variation in pictures. The color compensation is based on slice level, reportedly because the color inconsistency between pictures is mainly introduced by the diversity of cameras. It was asserted that the simulation results show that this method can improve coding efficiency – especially for the non-rectified video sequences.

The contributor had not yet finished the full test – instead, they used only a small number of frames of each sequence: the average improvement relative to illumination compensation in the work thus far was reported to be 1-2%.

Question: More complex than illumination compensation? Yes, but similar complexity to ordinary weighted prediction.

152

The previous meeting contribution JVT-X055 lacked comparison to illumination compensation. This contribution integrates the proposed color compensation method with existing illumination compensation.

Compared to IC, gains on the order of 1~2% for 5 test sequences were reported.

Similar complexity as weighted prediction. More complex than IC.

Further study may be performed to investigate the behavior on the full set of test data.

7.4.3 Motion skip operation

7.4.3.1.1 JVT-Y036 ( Prop 2.2) [S. Lin, S. Gao, H. Yang, L. Xiong (Huawei)] RDV based MVC motion skip

In this proposal, a motion skip mode for MVC based on a regional disparity vector (RDV) was proposed. The proposed method uses an RDV instead of a global disparity vector (GDV) to indicate the corresponding macroblock position in the picture of a neighbouring view, and the RDV is not represented in the bitstream. Comparing with JMVM 5.0 with MotionSkipMode enabled, the average improvement is reported to be a 2.3% bit rate reduction (best result 4.3%). Complexity is reported to be somewhat increased.

Remark: The GDV bit cost is negligible.

Remark: Two-pass encoding operation is needed to determine the GDV in an encoder, whereas that appears not to be needed for this proposed method? So the encoder complexity may be reduced by this method? This sounds like an advantage of this proposal relative to the current GDV technique.

Remark: Proposal introduces dependency between RDV’s that might impact single loop decoding.

Proponent suggested to continue investigation of the technique. Such further study is encouraged.

7.4.3.1.2 JVT-Y037 ( Prop 2.2) [H. Yang, J. Huo, Y. Chang (Xidian U.), S. Lin, S. Gao, L. Xiong (Huawei)] Inter-view motion skip MVC with fine motion

In this document, an inter-view motion skipped multi-view video coding scheme with fine motion matching was proposed. Compared with the existing motion skipped coding scheme in JMVM 5.0, several improvements were reportedly introduced. First, the precision of motion information used for motion skipped coding was asserted to be improved. Second, it was asserted that the optimal motion information is selected from a set of high-precision motion information candidates to maximize coding gains. For each inter-view reference picture, the set of high-precision motion information candidates were obtained within a predefined search window, the center of the search window was inferred by global disparity. Next, the candidates from all the inter-view reference pictures were compared with each other in term of rate-distortion performance, and the optimal one was reportedly selected. If the motion skip mode outperforms other coding modes, the side information about the motion information selection would be transmitted to the decoder. Compared with JMVM 5.0 with MotionSkipMode enabled, the average improvement for all the 8 test sequences was reported to be 0.14 dB gain or 3.5% bitrate reduction (the best results were 0.31 dB gain or 6.3% bit rate reduction).

153

The contribution proposes to use global disparity vectors at 8x8 resolution rather than 16x16, which allows derivation of motion information from corresponding blocks in neighboring views with a finer scale.

No change to syntax, only changes to semantics to specify disparity vectors at the 8x8 level.

Question: Were the simulations done using common conditions? Not quite, but similar.

Simulations were done with slight modifications to the prediction structure defined in common conditions to allow inter-view prediction for anchor and non-anchor frames in P and B-views.

Compared to existing motion skip mode, up to 0.31 dB / 6.32% bitrate reduction for Akko&Kayo, average 0.14 dB / 3.53% bitrate reduction for all 8 sequences. Compared to JMVM reference, up to 0.689 dB / 14.25% bit rate reduction for Rena; average 0.38 dB / 8.44% bitrate reduction for all sequences except for Breakdancers and Uli (simulation still running).

Complexity: No increase at decoder; small increase in encoder.

Remark: It would be nice to know how much is contributed by each aspect of the proposal.

The proponent suggested a CE to explore the gains obtained by different aspects of the proposal.

Source code availability? Will be provided to CE partners.

Disposition: Create a CE based on this.

7.4.3.1.3 JVT-Y069 -V ( Info 2.0/3.1) [J. Luo (Thomson)] Verif of JVT-Y037 Huawei prop JVT-Y070

This document reports verification results for the proposal by Huawei as described in document JVT-Y037 “Inter-view Motion Skipped Multi-view Video Coding with Fine Motion Matching”. The decoding executables, coded bitstreams for views, encoder configuration files and simulation results were provided by Huawei. For Akko&Kayo, Ballroom, Breakdancers, Exit, Race1, Rena and Uli, the decoding and its results were reportedly verified.

The contributor received encoder configuration file and view coded bitstreams of Akko&Kayo, Ballroom, Breakdancers, Exit, Flamenco2, Race1, Rena and Uli. They were reported to have been decoded successfully, with details as follows:

– For Akko&Kayo, Ballroom, Breakdancers, Exit, Race1 and Rena, The verification results were reported to be perfectly matched with the ones provided.

– For Flamenco2, the contributor only received coded bitstreams for QP 22, 27 and 37. These verification results were reported to be perfectly matched with the ones provided.

– For Uli, the bit rates were matched, but the PSNR was not matched. It was reported that this was due to using differing original YUV files from those of the Uli sequence as used by Huawei. According to Huawei, this could be a bug in their own tool that was used to convert the original image files to the source YUV sequence.

The source code was not checked.

154

7.4.3.1.4 JVT-Y058 ( Prop 2.2/3.1) [Y.-J. Jeon, H.-S. Koo, B.-M. Jeon (LG)] Motion skip issues in MVC

In this contribution, some motion skip issues raised at the last meeting were presented. At the Geneva meeting, some issues about motion skip that were reportedly not clear were raised and an ad-hoc group ‘JMVM coding tools’ was established. This contribution is asserted to clean up these issues as responses of the mandates of the ad-hoc. The issues this contribution deals with are as follows: 1) Simplification of GDV (Global Disparity Vector) calculation, 2) Signaling in anchor and/or non-anchor pictures with respect to inter-view dependency of non-anchor pictures, 3) Motion skip for multiple inter-view reference pictures, and 4) Simulation of motion skip by disabling motion skip in some non-anchor pictures of which inter-view prediction is forced not to be used according to view dependency information in SPS. This contribution also presented experimental result of motion skip for multiple inter-view reference pictures. Simulation results reportedly showed that bit-saving is obtained for non-anchor pictures having multiple inter-view reference pictures.

JVT-X024 was proposed at the last meeting, with a favorable disposition provided follow-up work was done. This was reported to have taken place.

JVT decision: Adopt JVT-X024 simplification of GDV (Global Disparity Vector) calculation.JVT decision: Adopt fix to condition of sending global_disparity_mb.JVT decision: Adopt text fix to mismatch between JMVM text & software reported for motion_skip_flag.

Proposes to allow sending multiple GDVs for motion skip in cases of multiple inter-view reference pictures. Average savings on the B views is reported as 3.7%. Gain as percentage of total bit rate would be substantially smaller.

Remark: This is not common conditions, and is in response to a comment pointing out that there was no way to handle this case in the design. The coding gain is not the main point here. This is asserted to be essentially a bug fix – no design change.

JVT decision: Adopt sending multiple GDVs for motion skip in cases of multiple inter-view reference pictures.

Additional information including simulation of motion skip by disabling motion skip in some non-anchor pictures reportedly shows that the motion skip design provides a net 2.16% average gain on common conditions.

The following notes should be redundant with the above notes: The contribution deals with several fixes to motion skip tool.1) Simplification of GDV (global disparity vector) calculation. Adopted as presented in JVT-X024.2) Signaling in anchor and/or non-anchor pictures with respect to inter-view dependency of non-anchor pictures. Adopted as bug fix.3) Motion skip for multiple inter-view reference pictures. Resolves an ambiguity in the spec and software when multiple inter-view references. Adopted.

Another set of essentially-redundant notes: First issue: Simplification of motion skip that was already presented last meeting and up for further study. Adopted. Second issue: Change signaling of motion skip (condition when to send motion skip, text alignment with software) adopted. Third

155

issue: Derive motion skip from multiple reference pictures. This is response to a question from last meeting where the behaviour of the tool under non-common testing conditions needed to be investigated. In principle, this is a bug fix of the software. Gain of 3.69% on average is reported (only for B views). Adopted.

7.4.3.1.5 JVT-Y059 -V ( Info 2.0/3.1) [J. Luo (Thomson)] Verif JVT-Y058 motion skip This document reported verification results for the proposal by LG as described in document JVT-Y058. The decoding executables, assembled coded bitstreams and source code were provided by LG. For Akko&Kayo, Ballroom, Breakdancers, Exit, Race1, Rena and Uli, the decoding and its results were reportedly verified.

The contributor received decoding executables, source code and assembled coded bitstreams of Akko&Kayo, Ballroom, Breakdancers, Exit, Race1, Rena and Uli. They were reported to have been decoded successfully. It was reportedly observed that the verification results were matched with the ones provided in the file JVT-Y058_a.xls.

The source code was not checked.

7.4.4 Single-loop decoding

7.4.4.1.1 JVT-Y053 ( Prop 2.2.1/3.1) [Y. Chen, Y.-K. Wang, M. M. Hannuksela (Nokia)] Single loop decode and motion skip in JMVM

In this contribution, high level syntax changes for supporting of single-loop decoding were proposed.

Coding efficiency gains of the motion skip tool for both the single-loop decoding scheme and the multiple-loop decoding scheme (i.e. current JMVM with motion skip enabled and illumination compensation disabled) were also reported. The simulation results reportedly show that motion skip benefits the single-loop decoding scheme with an average bit-saving of around 7.5% for the test sequences defined in the common test conditions. However, for the multiple-loop decoding scheme, only around a 2.3% bit-rate savings is reported. After reporting the results, some potential improvements to motion skip are discussed.

Full decoding is performed only for target views. From non-target views, only intra and motion vectors (for skip cases) are used. Anchor pictures are fully decoded. As a result, no loop needs to be run for the non-target views. Proposal includes a request for a flag that indicates whether a view will be used for motion skip reference, and another flag that indicates whether single loop decoding of a particular view is possible. The reported average bit rate saving comparison, performed against other methods that allow single-loop decoding, was as follows: relative to Simulcast 29.7%, relative to anchor-only prediction 7.5%. The advantage of motion skip in multiple-loop decoding was reported to be 2.25%; and the loss compared to multi-loop decoding was reported to be only around 1-2% average (with motion skip on).

The authors proposed 1) to adopt the high-level syntax changes to the JMVM, 2) to keep the motion skip tool in the JMVM, and 3) to set up a core experiment to study possible improvements of the motion skip tool, aiming at better performance in both single-loop decoding and multiple-loop decoding scenarios.

Some reported issues are resolved by actions reported above in relation to JVT-Y058.

156

Question: What is the loss of single-loop decoding relative to multi-loop decoding with– Motion skip off? Answer: Didn’t think about that.– Motion skip on? Answer: Roughly 1% loss on average (details in accompanying spreadsheet).

7.4.4.1.2 JVT-Y042 ( Prop 2.2/3.1) [P. Pandit, P. Yin, T. Dong, C. Gomila, H. Koo, Y. Jeon, B. Jeon (Thomson & LG)] MVC single-loop decoding

This contribution proposed a single loop decoding mode for MVC. It asserted that for some applications where only certain views need to be decoded, complet reconstruction of the reference view (i.e. reconstructed sample data) is not essential. Only certain syntax elements and data from those views can instead be inferred and used for the target view. This can reportedly have the advantage of saving memory and complexity. In particular, it was proposed that a reference view should not be completely reconstructed, such that only parsing its syntax is sufficient. The target view may then use this parsed information. The motion skip mode (already supported in JMVM) is used as the main coding tool to support single loop decoding in this contribution. Finally, RD results are presented without using reconstructed reference view pictures for inter-view prediction of non-anchor pictures.

The proposal is similar to JVT-Y053. Allows inter-view prediction only for anchor pictures. It also makes use of the reported loss, relative to Single Layer, of 1.64 % (0.04 dB). An SPS Flag is proposed to switch single-loop decoding on or off (a different solution than JVT-Y053).

Question: What is justification to make it switchable? Response: Depends on the application (e.g. for M-view display all views need to be decoded).

Syntax proposed is less flexible, but simpler than what is proposed by Nokia in JVT-Y053.

7.4.4.1.3 JVT-Y060 -V ( Info) [Y.-L. Lee (Sejong U.)] Verif JVT-Y042 MVC single-loop decoding

This contribution reports verification of JVT-Y042 "Single Loop Decoding for MVC". The results of JVT-Y042 were reportedly confirmed.

The proponents provided the decoder source code, bitstreams of the modified JMVM 5.0 software (corresponding to JVT-Y042), configuration files and simulation results.

The software provided by the proponents was reportedly cursorily reviewed (not closely checked), compiled, and run.

The results of the provided SW were reported to be the same as those reported in JVT-Y042.

7.4.4.1.4 General discussion on single-loop decodingSuggestion: Why bother having a switch – mainly for experimental purposes for now.

JVT decision: Adopt single-loop decoding into JMVM using syntax switch proposed in JVT-Y042.JVT decision: Adopt flag in slice header to omit motion skip flag at lower layer.

Plan CE on potential improvements of motion skip.

157

7.5 Low-complexity MVC / Stereoscopic

7.5.1 Reference picture resampling (RPR) for MVC

7.5.1.1.1 JVT-Y030 ( Prop 2.2/3.1) [H. Kimata, S. Shimizu (NTT)] Exper results on MVC down-sampled inter-view pred

This contribution reports experimental results for down-sampled inter-view prediction for MVC, as was requested at the last JVT meeting. The down-sampled inter-view prediction scheme was asserted to have been proposed for mixed spatial resolution views to reduce bit rate and complexity for multi-view video coding. This document also reports performance analysis of coding efficiency in terms of the generation method of the down-sampled images.

A low-resolution view is predicted from a high-resolution view for inter-view prediction.

Downsampling is performed by just dropping samples without using any anti-alias filtering (this enables use of the same memory area for storing the down-sampled picture as well as the higher-resolution picture) – this scheme was reported not to harm the coding efficiency of inter-view prediction for the low-resolution video.

Comparison was provided to mixed-resolution coding without inter-view prediction across resolutions.


A 47% bit rate savings was reported for the low-resolution views, relative to not using inter-view prediction across resolutions.

Remark: That seems like an unexpectedly high degree of benefit.

The bit rate savings for the low-resolution part (each second view) as compared to separate MVC encoding of low and high resolution views was reported to be 47% on average. Assuming that the low resolution part, in the case of separate MVC encoding, would still be 1/3 of overall bit rate, this would still be more than a 15% BR savings. The loss due to not performing filtering when generating the down-sampled reference was reported to be very low (<1 dB on average).

Note: This saving appears unreasonably high, provided that typically inter-view prediction is applied less often than temporal prediction.

Note: The application where every-other camera has a different resolution may be very specific.

Question: What is the relationship to JVT-Y052 and JVT-Y054?

Remark: It might be more interesting to know the amount of improvement from the technique, multiplied by the fraction of the total bit rate that is consumed by the lower-resolution views – e.g., reduce the 47% by a factor of 3.

158

7.5.1.1.2 JVT-Y054 ( Prop 2.2.1/3.1) [Y. Chen, S. Liu, Y.-K. Wang, M. M. Hannuksela, H. Li (Nokia)] Low complexity asymmetric MVC

“Asymmetric MVC” refers to coding of two views of a stereoscopic video source with different qualities. In this proposal, a new asymmetric coding technique was proposed for MVC by enabling inter-picture prediction from a higher resolution picture to a lower resolution picture, when the current picture is one fourth of the size of the inter-view reference picture. It was asserted that the proposed scheme has low complexity and requires a smaller decoded picture buffer size compared to downsampled inter-view prediction. (The preceding sentence may be unclear.) Simulation results reportedly showed that it provides comparable coding efficiency compared to downsampled inter-view prediction, and both reportedly outperform the “simulcast MVC” coding scheme, wherein two sets of views with different resolutions are independently coded into two MVC bitstreams.

This is the same basic idea as JVT-Y030, but with a 2-tap anti-alias filtering applied in some cases when downsampling.

Remark: Is it acceptable to have different views with different resolution? For stereo, perhaps. Stereo seems to be the main argument for support of this.

The primary motivator is complexity reduction (relative to what – exactly? – relative to only coding high-resolution views). As far as implementation effort is concerned, this increases effort.

Remark: So far we have desired to focus on achieving similar quality in all views.

7.5.1.1.3 JVT-Y082 ( Info 2.0) [C. Fehn, P. Kauff, A. Smolic (HHI), S. Cho, N. Hur, J. Jim, S.-I. Lee (ETRI)] Asymmetric coding of stereoscopic video for mobile 3DTV

This contribution described the use of reference picture resampling (RPR) “asymmetric coding” with inter-view prediction for the compression of stereoscopic video sequences. It reported that downsampling one of the views before coding with inter-view prediction can lead to additional coding gains compared to the simulcast case. It was asserted that according to earlier psychological studies of stereoscopic vision, such processing should not reduce the overall visual quality of the resulting three-dimensional (3D) percept.

The suggestion is to consider RPR as a low-overhead way to enable stereoscopic applications. The contribution reports a requirement of 10-30% bit rate overhead by quarter-resolution downsampling (e.g. 320x240 QVGA and 160x120 QQVGA).

The contribution referred to JVT-W094 for binocular suppression theory.

The contribution suggested further study.

Remark: The motivation seems to be stereo rather than a general N-view cases.

Disposition: Plan to continue AHG to further investigate.

159

7.5.2 Reduced-resolution update (RRU) for MVC

7.5.2.1.1 JVT-Y052 ( Prop 2.2/3.1) [S. Cho, N. Hur, J. Kim, S.-I. Lee (ETRI), C. Fehn (HHI)] Resid-downsampled stereoscopic video for moble 3DTV

This contribution proposes a stereoscopic video coding using a residual-downsampling algorithm that is applied on macroblock basis. The proposed video coding algorithm was reported to be more efficient at lower bitrates for mobile 3DTV service such as T-DMB (Terrestrial Digital Multimedia Broadcasting). For supporting the proposed coding algorithm in the JMVM, the contribution also proposes residual-downsampling related syntax in the sequence_parameter_mvc_extension( ) syntax structure.

The contribution uses an “IPPP” coding structure.

The design is conceptually the same as reduced resolution update (RRU) (e.g., as in H.263 Annex Q or MPEG-4 Part 2 RRU) applied to the entire sequence.

For four two-view 320x240 sequences (not common conditions sequences), around a 0.5 or 0.6 dB average gain was reported.

The residual was encoded by half spatial resolution.

Remark: The PSNR values with up to 45 dB (as compared to original full resolution) appear unreasonably high.

Remark: How is it possible to achieve 40+ dB (and even a benefit in that range) without any ability to encode high-frequency residual differences?


Cross-verification? Apparently not.

The design was based on the Baseline profile, so no 8x8 transform block size capability was assumed.

The design couples the RRU invocation to the segmentation used for prediction of each region. If a large block size is applied for prediction, RRU is invoked (regardless of whether high frequency residuals are present or not). If a small block size is applied for prediction, RRU is not invoked.

Remark: Tying the RRU decision to the transform size flag (or adding modes or something like that rather than coupling directly to prediction block size) would seem to make more sense.

Remark: Or perhaps just enabling use of an 8x8 transform (perhaps with discarding of high-frequency components – possibly as an encoder-only decision without special syntax) rather than using RRU at all would be a better design.

Response from proponent: This also switches from quarter-sample motion to half-sample motion whenever the block size is relatively large.

Remark: Such switching could be applied separately from RRU concepts – would it provide gain? – we speculate not.

160

Further study would be needed to determine whether there is value in this, and how much.

Disposition: Include in the same AHG with RPR.

7.6 MVC with depth

7.7 JMVM analysis and optimization

7.7.1.1.1 JVT-Y022 ( Info 2.2) [R. He, G. Jiang, M. Yu (Ningbo U.)] Determining decoding path in MVC

As mentioned in WG 11 document M13121, while compression efficiency is important in multi-view video system, many applications of multi-view video (e.g., free viewpoint video) reportedly also require the ability to randomly access different views from the compressed bitstream. To perform view switching in real-time, efficient random access is reportedly essential. For this purpose, when users access one frame of a multi-view video sequence randomly, it is reportedly necessary for the multi-view video system to be able to determine how to find and decode the corresponding frame quickly and efficiently. An algorithm was proposed in M13121to reduce the number of frames that a decoder must process to perform random access. To further improve the random access performance of the multi-view video system; a concept of a frame level matrix of prediction structure was presented, based on which a calculation method of the decoding path was presented. An example based on a hierarchical B picture prediction structure was used to compare the proposed algorithm with the algorithm in M13121. It was asserted that the proposed algorithm can obtain a better decoding path, so it was asserted to effectively reduce the decoding complexity and improve random access performance in the multi-view video system.

A non-normative decoder implementation speed optimization technique provided as information.

7.7.1.1.2 JVT-Y023 ( Info 2.2/3.1) [G. Jiang, Y. Yang, M. Yu (Ningbo U.)] Evaluation of random access of MVC schemes

Random access on both temporal and spatial dimensions was proposed as a basic requirement for future multiview video applications. However, evaluation on random accessibility is asserted to be a critical problem in research and development of multiview video systems, while discussions and research had reportedly not been sufficient in the previous JVT meetings. This contribution provided a “universal definition” for random accessibility for multiview video systems through graph theory and stochastic methods. Although some evaluation methods were proposed by other works to measure random accessibility in some ways, the outcome scores in these methods are asserted to be equipment-dependent. In this contribution, the proposed definition and evaluation function for random accessibility is reportedly a general method measured by graph theory and stochastic procedures. Experiments were implemented, and it was asserted that the parameters of random accessibility will change according to the corresponding complexity of the MVC scheme. Furthermore, the proposed methods and functions can reportedly be used as evaluation tools to assess the performance of existing MVC schemes and the needs of future multiview video applications.

7.7.1.1.3 JVT-Y026 ( Info 2.0) [M. Yu, Z. Peng, G. Jiang (Ningbo U.)] Statistical analysis of macroblock mode selection in JMVM

161

In the Joint Multiview Video Model (JMVM), the macroblock mode of each macroblock is reportedly decided by full searching of all modes. Excellent rate-distortion performance is reportedly achieved in this manner, but at the expense of a large computational complexity. This contribution reports statistical analysis results based on the JMVM reference software with regard to macroblock mode selection. The statistical results reportedly show that the proportions of selected macroblock modes are not equal. Most of the macroblocks are reportedly encoded with the SKIP macroblock mode, while the Inter1616 mode is reported to be the second most common. These two modes reportedly account for more than 58% of all macroblock mode selections. The motion-skip mode, which reportedly greatly improves rate-distortion performance, reportedly plays an important role in MVC and is reportedly applied in significant percentages for all test sequences. The proportions of other inter macroblock modes, such as Inter168, Inter816, Inter88 and Inter88Frext, are reported to be less than those of the SKIP and Inter1616 macroblock modes. Although the Intra modes are least frequently selected of all modes, they are reported to be indispensable to video encoding. It is asserted that these statistical analysis results may be helpful for designing fast macroblock mode selection algorithms.

7.7.1.1.4 JVT-Y027 ( Info 2.2) [M. Yu, Q. Xu, G. Jiang, Z. Peng (Ningbo U.)] Bandwidth distortion model for MVC in interactive system

Traditionally, rate distortion performance with respect to all views is used to evaluate the encoding efficiency of multiview video coding (MVC) schemes, and some comparative study of MVC prediction structures has been given. Under this criterion, the Hierarchical B Pictures (HBP) structure, which benefits from the carefully designed prediction structure in the temporal domain as well as the spatial domain, is regarded as one of the most efficient MVC schemes. Even though the coding efficiency is substantially improved by using temporal and interview correlations, it is reportedly desired for the server that only partial compressed data will be interactively selected and transmitted to the client due to the limit of network bandwidth and limited resources of clients, and the fact that the user only watches several specific viewpoint views during a relatively long period instead of needing all viewpoint views, and the number of views which should be transmitted is relative to the user’s selection, the type of display and the view dependence of the coding scheme. From this point of view, rate distortion analysis only reflects the memory needed for storing the total bitstream of the encoded multiview video signal. It is intuitive that view dependency enables a coding scheme to achieve high coding efficiency because more interview correlations can be exploited, however, it is asserted that this will also result in more viewpoints that have to be transmitted even though some of them are not directly selected by the user (being involved only in the predication of the needed views). Therefore, the traditional rate distortion, referred to as the encoding rate distortion model, just evaluates the “static performance” of an MVC scheme in coding efficiency but not the “dynamic performance” associated with the user’s interactive selection when used for an interactive multiview video system. A transmission bandwidth distortion model was suggested for evaluating multiview video coding (MVC) schemes in an interactive multiview video system in this contribution, instead of the traditional encoding rate distortion model at the encoder, and comparative results of some typical MVC prediction structures under this suggested evaluation model were also given.

7.7.1.1.5 JVT-Y028 ( Info 2.2/3.1) [Y. Yang, M. Yu, G. Jiang (Ningbo U.)] Dependency func for perf analysis of MVC

Compression related requirements in future multiview video applications reportedly have close relationships with prediction dependency structures of multiview video coding (MVC) schemes. Evaluation of the complexity of prediction dependency structures of MVC schemes will reportedly be very important for assessing both the needs of future multiview video applications and other performance issues in multiview video systems. This contribution reported on an investigating of

162

these issues and defines a complexity measure for prediction dependency structures of MVC schemes. The contribution defined a view dependency function based on graph theory to describe the complexity and coupling degree of an MVC scheme. Particular MVC schemes were investigated by the proposed methods. The dependency function was further applied to evaluate random accessibility and decoding effort.

7.8 MVC high-level syntax

7.8.1.1.1 JVT-Y025 ( SEI showcase 2.2) [G. Jiang, R. He, M. Yu (Ningbo U.)] Showcase for code optimization of active view info SEI in JMVM

At the JVT meeting at San Jose, an active view information SEI message (JVT-W036) was adopted into Joint Draft 3.0 on MVC. It specifies the views that are required for output. And in the following JVT meeting in Geneva, a showcase for the active view information SEI message for MVC as contributed in JVT-X027 provided a test platform for the active view information SEI message. However, the test platform contributed in JVT-X027 reportedly has a little defect: If someone wants to change the output view information, it is reportedly necessary to modify the code. This is reportedly very inconvenient to users. So this proposal suggests to revise the procedures to allow that only the modification of the configuration file is enough when the output view information needs to be changed. In this contribution, a showcase for this code improvement is presented.

JVT decision: Showcase considered satisfactory.

JVT decision: Software change agreed.

7.8.1.1.2 JVT-Y029 ( Prop 2.2) [M. Yu, R. He, G. Jiang (Ningbo U.)] MVC syntax simplif in active view info SEI

At the JVT meeting in San Jose, an active view information SEI message (JVT-W036) was adopted into Joint Draft 3.0 on MVC. It specifies the views that are required for output. And at the JVT meeting in Geneva, a showcase for the active view information SEI message for MVC (JVT-X027) provided a test platform for the active view information SEI message. But the information of the syntax table provided by JVT-W036 reportedly has some redundancy, and this contribution suggests to change it.

Remarks: The proposal uses an undefined “sizeof” function. The proposed change only saves a few bits at the sequence level, so is not important.

Considering the problem in form, although it may perhaps only be editorial, there seems to be insufficient need to consider changing this at this stage.

7.8.1.1.3 JVT-Y040 ( Prop 2.2/3.1) [H. Nakamura, M. Ueda (JVC)] On MVC high-level syntax

This contribution presents a comment on redundancy when coding without using inter-prediction, and it proposes that view dependency information is coded only when necessary and the information is not coded when not necessary.

The contribution suggests saving bits by not sending view dependency information in coded video sequences that do not use any inter-view prediction.

163

Remark: The number of bits suggested to be saved is very very small (as a percentage of total bit rate), and the anticipated use case seems to not be the primary target for the design.

Deferred for further study.

7.8.1.1.4 JVT-Y043 ( Prop 2.2/3.1) [J. Luo, P. Yin, C. Gomila (Thomson)] MVC HRD & VUI high-level syntax

This contribution proposed high level syntax for an MVC Hypothetical Reference Decoder and bitstream restriction parameters. The first part presented a signaling of HRD constraints for each temporal level of each view. It was asserted that the signaling enables HRD verification for the coded presentation for a particular temporal level of a particular view. The second part was the signaling of bitstream restriction parameters for each temporal level of each view. It was asserted that the signaling enables the decoder to efficiently allocate resources for decoding a subset of the bitstream. Proposed syntax changes were provided.

The group discussed the concepts of conformance and terminology – e.g., do we specify the existence and output of more than one picture per access unit?

Consider, for example, the prior difficulty with the 4:4:4 work, where there was a need to struggle editorially with the concepts of the definition of what a picture is and whether there could be more than one primary coded picture per access unit. Similar difficulties arose during SVC drafting.

Suggestion: Specify only the decoding and output process for one view. If a decoder wants to output additional views, it can conceptually just do this specified process once for each view that it wants to output. There may not be a need to have a specified decoding process that is required to output multiple views. The essential concepts would remain the same, while the ability to properly describe and enforce conformance requirements would be much improved and much more consistent with non-MVC usage of basic concepts and terminology. (Essentially this seems to be only a matter of proper editorial expression of our intent.)

Conclusion: We certainly need to work out such details as HRD operation for MVC, but at this point the discipline of expression in the text may not be adequate for considering these issues. Further study is needed.

7.8.1.1.5 JVT-Y055 ( Prop 2.2.1/3.1) [P. Yang, X. Xu, G. Zhu, Y. He (Tsinghua U.)] High level syntax for MVC view parallel proc

This was a follow up contribution in relation to JVT-X079. A view parallel coding architecture and its corresponding syntax change are presented in this proposal. As shown in results, by enabling the diagonal inter-view prediction, average gain was reported as 0.1 dB for overall pictures and 0.15 dB for non-key frames. For high motion sequences, the reported gain was 0.2 dB for overall pictures and 0.25 dB for non-key frames. This proposal further provided the syntax changes of the proposed method.

Part of the motivation was low delay.

Remark: The method of identifying the other picture to reference seems narrow-minded and less general than might be advisable. Why not sent a frameNumWrap difference to identify the picture instead of depending on POC?

164

Remark: There seems to be a loss robustness problem, since there is no way to unambiguously identify what picture is intended to be referenced in the case of lost view pictures. We generally don’t use POC for such purposes. What if the picture was in a different sub-sequence dependency structure? Why not send a frameNumWrap difference or long-term index within the referenced view to identify the picture instead?

Clarification: The proposal is to put the switch of what time instance of another view gets referenced up at the picture level, not at the macroblock/sub-macroblock level.

Note that the comparison here is relative to doing no referencing to other views in the non-anchor pictures.

Remark: This seems like a profile thing, since it seems like it cannot be the encoder that decides whether to reference same-time-instances in other views. The encoder would not naturally want to be forced to be unable to use same-time-instance pictures in other views.

Question: How much is the loss of coding efficiency relative to being allowed to reference the other view at the same time instant? Not reported.

Remark: The gain reported seems small, and the scenario seems highly specialized, and some design details seem questionable.

7.8.1.1.6 JVT-Y062 -LV (Late Info) [Q. Chen, Z. Chen (Thomson)] Verif JVT-Y055 high level syntax for MVC view parallel proc

This document reported cross-check results for JVT-Y055 “High level syntax for MVC view parallel proc”. Source code and configuration files were provided by the proponent of JVT-Y055. The verification was reportedly performed by checking, compiling the source code, generating the bitstreams and test data, and decoding the bitstreams. The simulation results of JVT-Y055 were reported to have been confirmed.

Executable files were reportedly regenerated and used for generating the cross-check results. Then bistreams were reportedly decoded and results compared with the results in JVT-Y055. For all the performed verification tests, the bitstreams were reported to have been decoded correctly with results that matched the results reported in JVT-Y055.

Question: How closely was the source code & algorithms checked? Unknown.

7.8.1.1.7 JVT-Y061 ( Prop 2.2/3.1) [J.-H. Yang, J.-G Kim, S.-J. Choi (LG)] On MVC high-level syntax

In the current JD, sequence parameter set MVC extension syntax describes the dependency relations among different views. This document asserts that there are some redundancies in the current description, and proposes to remove those redundancies.

Aspect #1: Proposes to not send some syntax elements that are always required to be 0 anyway.

JVT decision: Adopted this aspect.

Aspect #2: Proposes a change of SPS syntax.

165

The proposal seems to not be fully understood. Some concern was expressed that there are other places in the document that depend on the parts that are proposed to be changed, and that the changes might have problematic implications on those parts.

The potential bit rate savings is extremely minor.

7.9 Test SequencesSee also notes relating to JVT-Y072.

7.9.1.1.1 JVT-Y077 ( Info) [C. K. Chung, H. Song, J. H. Park, B. H. Choi (KETI)] Multi-view test sequence for MVC

KETI has prepared one multi-view test sequence that is being made publicly available for standardization and research efforts in this area. Further details on these sequences were provided in this document.

At the Geneva meeting, KETI showed the multi-view test sequence but reportedly did not provide enough backup data such as camera parameters and comparison between JM and JMVM.

At this meeting, KETI has prepared other multi-view video sequences which have 8 views, and the size of these sequences is 640x480x300 frames.

The capture system is described in JVT-X082 and there is no change to it. Please refer to JVT-X082 for further detail on that topic.

No restrictions on the use of these sequences were requested.

The sequences can be accessed directly with the following ftp informationFTP address: ftp://203.253.130.48Username: mvcPassword: KETI (Case-sensitive)Directory: /MVC/Sequence

KETI reportedly compared Rate-distortion curve between JM 12.4 and JMVM 5.0. As shown Fig.2 of the contribution, JMVM 5.0 reportedly always shows better coding performance than that of the JM for all points. JMVM tools (IC 2-3% and MS <1%) reportedly show better coding performance, but the degree of performance improvement seems to be not so significant.

It was suggested to add these sequences into our common conditions. That topic is deferred for further study.

7.9.1.1.2 JVT-Y079 -V [Y. S. Ho, K. J. Oh, C. Lee (GIST)] Verif JVT-Y077 MVC test sequence? <<withdrawn>>

166

8 New AVC Proposals

8.1 Adaptive chroma sampling

8.1.1.1.1 JVT-Y034 ( Prop 2.2/3.1) [S. Sekiguchi, S. Yamagishi, Y. Yamada, K. Asai, T. Murakami (MEI)] On adaptive chroma sampling for 4:4:4

(Presented jointly with MPEG video.)

In this contribution, the result of an investigation of the value of adaptive chroma sampling mechanism for further performance improvement of 4:4:4 video coding was reported. In the last (Geneva) meeting, JVT-X044 asserted that coding performance of High 4:4:4 predictive profile provides a reasonable rate-distortion trade-off with improved color reproduction compared with conventional 4:2:0 coding. It also asserted that YUV based coding performance is generally superior to that of direct RGB coding in very low bit rate conditions, however, the reconstruction quality of luma signal can reportedly be degraded due to using more bits for the additional chroma samples. Based on this observation, a preliminary estimation of the value of adaptive use of 4:2:0 chroma sampling within 4:4:4 coding has reportedly been made by collecting macroblocks having better rate-distortion trade-off from 4:2:0 coded results vs. 4:4:4 coded results. Even though it does not take into account the difference of prediction reference fidelity, it was suggested that this adaptivity could improve luma reproduction fidelity while maintaining that of chroma components.

Macroblock-adaptive 4:4:4 / 4:2:0 coding was proposed (examples were shown where color disappears in very small colored areas). Results were shown only with Y-PSNR, which does not tell very much (worse performance than 4:2:0 coding, but better than 4:4:4 coding). Currently, no evidence appears to have been provided about the real benefits. Further study is needed, also in context of potential complexity increase by macroblock-wise switching as compared to the benefit that it may give.

8.2 New levels

8.2.1.1.1 JVT-Y035 ( Prop levels 2.0/3.1) [Y. Bandoh, S. Takamura, Y. Yashima (NTT), Shinichi Sakaida, Yukihiro Nishida (NHK), T. Itoh, A. Nakagawa (Fujitsu), I. Ando, H. Takehara (JVC)] Prop new higher levels

(Corresponding WG 11 contribution M14890.)

This document proposes new levels for MPEG-4 AVC/ITU-T H.264 beyond the current level 5.1 in order to support higher resolution video formats such as 3840x2160/60p and 7680x4320/60p.

Higher resolution video format systems beyond HDTV called UHDTV have reportedly been developed and are reportedly emerging in the industry. These formats have reportedly already been standardized in ITU-R Recommendation BT.1769. For the transport of these video signals, ITU-T Recommendation J.601 identifies MPEG-4 AVC/ITU-T H.264 as one of coding schemes, noting the necessity of new higher levels. Codec systems based on MPEG-2 and MPEG-4 AVC/ITU-T H.264 for 7680x4320/60p have reportedly been developed using multiple HDTV codec units by dividing the complete images spatially and temporally. Some transmission experiments via gigabit IP networks were reportedly demonstrated at NAB2006 and IBC2006, and an experimental live relay broadcast from Tokyo to Osaka for public viewing was also conducted using a commercial IP network.

167

MPEG-4 AVC/ITU-T H.264 currently specifies a maximum level known as level 5.1, which supports a maximum frame size of 36 864 macroblocks and a maximum macroblock rate of 983 040 macroblocks/sec at up to 240 Mbit/s. This corresponds to a maximum frame rate of 30.34 frames per second for 3840x2160 and 7.5 per second for 7680x4320.

It was proposed to specify new higher levels 5.2, 6, and 6.1 in MPEG-4 AVC/ITU-T H.264 corresponding to the following scenarios:

Level 5.2: 3840x2160/60fps (up to 4K x 2K / 60fps) 400 Mbit/s – 5 ref framesLevel 6: 7680x4320/30fps (up to 8K x 4K / 30fps) 960 Mbit/s – 5 ref framesLevel 6.1: 7680x4320/60fps (up to 8K x 4K / 60fps) 1600 Mbit/s – 5 ref frames

Current consideration is reportedly being conducted toward introduction of higher resolution formats in 2011 and beyond.

Remarks: AVC already has 3 levels that nobody has implemented yet. This could also be done by running different decoders in parallel.

Question: Are these bit rates realistic? Think about it.

Remark: 5 reference frame requirement may also be a little high.

Remark: Consider slice structure constraints, etc.

Remark: Consider >= 72 fps.

JVT & MPEG are interested to hear more about these developments, but currently it seems to be too early to go for a concrete definition of new levels. MPEG will draft a response to the Japanese NB on this topic.

8.2.1.1.2 JVT-Y086-L JNB input on additional levels of AVC and related subjects(Corresponding WG 11 contributions: M14863, M14868, M14869, and M14890.)

Presented jointly with MPEG video.

Summary: 1920x1080 up to 120/240p, 4kx2k/60p, 8kx4k/60p is being prepared/discussed in industry and standardization bodies such as SMPTE. It should be avoided that proprietary definitions appear in the market, and it was therefore asserted that MPEG should start consideration of defining additional profiles rather soon. 1920x1080 at 60p will reportedly happen very soon, and next will reportedly be 4kx2k. Higher resolution formats are still farther away.

Comment: We do not usually direct the definition of video formats, but try to accommodate as many formats as possible that are common in the market (or are soon expected) with a given level. In cases where formats are just emerging, it might be premature to make definitions. Definitions of maximum macroblock numbers, maximum buffer sizes, maximum bit rates are also important to consider when a level is defined and typically require some more careful study. Some of these values may also be different for consumer or professional applications.

Another option for implementation of larger formats would be, e.g., to combine four 4Kx2K tiles into on 8Kx4K frame (it is also an issue of decoder complexity whether a high-resolution profile is doable, could be done at systems level).

168

8.2.1.1.3 General discussion of AVC new levels issuesRemark: AVC already has 3 levels that haven’t been implemented yet.

Remark: Could also be done by running different decoders in parallel.

Applications? Broadcast starting in 2011.

Plan to study for future definition –there is time to study.

MPEG & JVT are interested to hear more about these developments, but currently it is too early to go for a concrete definition of new levels. These statements are to be considered in the drafting of a response to the Japanese NB by WG 11.

JVT response: We plan to provide new levels in the future as necessary to serve industry deployments of important services; however we plan to avoid doing this prematurely and to ensure thorough and adequate study in creating such definitions. No immediate action – further study encouraged.

9 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 this and other recent 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 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 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-Yxxx.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

169

with an e-mail notification containing title, authors and abstract (identical to the one in the doc) which is no longer than 200 words and no shorter than 25 words and is written in 3rd person 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 you take the files out of the zip container, you'll still know what contribution they came from. Every file in the .zip container for document JVT-Yxxx should start with JVT-Yxxx. Example: JVT-Yxxx.doc (main document), JVT-Yxxx_presentation.pdf, JVT-Yxxx_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 we get 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 company different than the proponent based on

the textual description (after adoption, both decoder source code versions must be made publicly available and 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.

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.

10 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.

10.1 JVT project management and errata reportingDiscussion: [email protected]: Gary Sullivan, Jens Rainer Ohm, Ajay Luthra, and Thomas Wiegand

170

Mandates:– Collect errata reports on standards under management of JVT– Coordinate overall interim JVT progress– Prepare status information for JVT status reporting

10.2 JM Text, reference software, bitstream exchange and conformanceDiscussion: [email protected]: 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) Conformance specifications– Identify and correct problems in Conformance specifications and associated bitstreams

10.3 SVC JSVM text, software and conformanceDiscussion: [email protected]: 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

10.4 SVC bit depth and chroma format scalabilityDiscussion: [email protected]: Yongying Gao, 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– Study combined spatial and bit depth scalability– Define experiments and test conditions– Investigate software and text modification needs– Identify complexity issues

10.5 SVC FGS applications and design simplificationDiscussion: [email protected]: Justin Ridge, Marta KarczewiczMandates:– Identify applications that may require FGS functionality and their characteristics

171

– Determine to what extent new coding tools are needed to achieve the functionality– Define experiments and test conditions relating to FGS technology– Coordinate with JSVM software effort to align JSVM software with current design– Explore simplification of FGS tool design

10.6 MVC high-level syntax and buffer managementDiscussion: [email protected]: Anthony Vetro, Purvin PanditMandates:– Discuss high-level syntax for MVC including NAL unit type, NAL unit header extension, SPS

extensions, slice layer and integration with SVC syntax.– Discuss reference picture management to enable simultaneous picture output of different views

and to facilitate parallel processing.– Discuss issues related to HRD.– Propose refined syntax and decoding processes for JMVM.

10.7 MVC JD and JMVM text and softwareDiscussion: [email protected]: Hideaki Kimata, Aljoscha Smolic, Purvin Pandit, Anthony Vetro, Chen YingMandates:– Collect comments on draft, perform necessary editing and delivery.– Maintain JMVM and JD document and collect comments on the text.– Coordinate JMVM software integration– Coordinate bug-fixing process for the JMVM software– Maintain JMVM software manual

10.8 MVC reduced resolution update and mixed resolution view codingDiscussion: [email protected]: Purvin Pandit, Hideaki Kimata, Sukhee Cho, Karsten Müller– Investigate approaches for enhancing MVC coding efficiency using spatial downsampling– Evaluate the complexity of such methods– Investigate the relationship between downsampling approaches and view interpolation– Investigate low-complexity methods for mobile stereoscopic 3DTV applications– Evaluate subjective quality associated with methods

10.9 MVC JMVM coding toolsDiscussion: [email protected]: Purvin Pandit, Han Suh Koo– 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

172

11 Resolutions reported to WG 11 parent bodyIn addition to requesting approval of the texts described above in section 3.4 and of the AHGs described above in section 10, the following JVT resolutions were reported to the WG 11 parent body:

1. The video subgroup and the JVT thank the National Bodies of Japan and the US for their ballot comments on ISO/IEC 14496-4:2004/PDAM 30.

2. The video subgroup and the JVT thank the National Bodies of Japan and the US for their ballot comments on ISO/IEC 14496-5:2001/PDAM 18.

3. The video subgroup and the JVT thank the National Bodies of Germany and US for their ballot comments on ISO/IEC 14496-10:200X/PDAM 1. We request National Bodies to consider the study document N9445 [JVT-Y209] and provide additional comments before the FPDAM is issued at the Antalya meeting.

4. The video and test subgroups and the JVT would like to thank all the participants of the SVC verification testing activities for their contributions to this effort.

5. The JVT solicits input on applications and requirements for bit-depth and chroma-format scalability.

6. The JVT solicits input on the need for interlaced video scan support in applications of MVC.

7. The JVT recommends to designate the following persons as editors of ISO/IEC 14496-10:200X: Heiko Schwarz, Gary Sullivan, Thomas Wiegand, and Mathias Wien.

8. The JVT chairmen propose to hold the 26th JVT meeting during January 12-18, 2008 under WG 11 auspices in Antalya, TR. Further JVT meetings are proposed to be held during April 18-25, 2008 under the auspices of the meeting of ITU-T SG 16 in Geneva, CH, and during July 19-25, 2008 under WG 11 auspices in Hannover, DE.

12 AttendancePersons registered to attend the meeting, as recorded by a sign-in sheet circulated during the meeting, were the following (176 listed participants):

1. Ahn, Chang-Beom (Kwangwoon Univ.)2. Asai, Kohtaro (Mitsubishi)3. Bandoh, Yukihiro (NTT)4. Bjøntegaard, Gisle (Tandberg)5. Bottreau, Vincent (Thomson R&D France)6. Bourge, Arnaud (Philips / NXP)7. Bruls, Fons (Philips)8. Carballeira, Pablo (Univ. Polit. de Madrid)9. Chang, Eun-Young (ETRI)10. Chang, Yilin (Xidian Univ.)11. Chao, Hongyang (Sun Yat-Sen Univ.)12. Chen, Lulin (Omneon Video Networks USA)13. Chen, Sijia (Zhejiang Univ.)14. Chen, Weizhong (Huawei Tech.)15. Chen, Yi-Wen (ITRI/NCTU)16. Chen, Ying (Tampere Univ. Tech.)17. Chiu, Yi-Jen (Intel)18. Cho, Sukhee (ETRI)19. Choi, Byeongho (KETI)20. Chujoh, Takeshi (Toshiba)21. Cock, Jan De (Ghent Univ.)

173

22. Cui, Hui-Zi (Sejong Univ.)23. Eleftheriadis, Alex (Layered Media)24. Fröjdh, Per (Ericsson)25. Fu, Jian (Huawei)26. Fuldseth, Arild (Tandberg)27. Gao, Shan28. Gao, Yongying (Thomson)29. Guleryuz, Onur (Docomo USA Labs)30. Guo, Haitao "Harry" (Apple)31. Guo, Xun (MediaTek)32. Han, Dong-hoon (Sejong Univ.)33. He, Jones (Freescale)34. He, Relong (Ningbo Univ.)35. He, Yun (Tsinghua Univ.)36. Ho, Yo-Sung (GIST)37. Horowitz, Michael (CoVi Tech. --> Vidyo)38. Hsiang, Shih-Ta (Motorola)39. Huang, Yu-Wen (MediaTek)40. Huo, Junyan (Xidian Univ.)41. Im, Jinseok (LG Electronics)42. Ishtiaq, Faisal (Motorola)43. Itoh, Takashi (Fujitsu Labs)44. Jeon, Byeong-Moon (LG Electronics)45. Jeon, Byeungwoo (SKKU)46. Jeon, Yongjoon (LG Electronics)47. Jeong, Seyoon (ETRI)48. Jia, Jie (Sejong Univ.)49. Jiang, Gangyi (Ningbo Univ.)50. Jin, Xin (Chinese Univ. of Hong Kong)51. Jung, Joël (France Telecom R&D)52. Kang, Jung Won (ETRI)53. Karczewicz, Marta (Qualcomm)54. Kim, Dae-Yeon (Sejong Univ.)55. Kim, Jae-Gon (ETRI --> Korea Aerospace Univ.)56. Kim, Jinwoong (ETRI)57. Kim, Jong Lak (DSP Group)58. Kim, Kyuheon (Kyunghee Univ.)59. Kim, Sang-mi (Sejong Univ.)60. Kimata, Hideaki (NTT)61. Kotodynski, Robert (Telekomunikacja Polska)62. Ku, Cheonhak (LG Electronics)63. Lee, Bumshik (ICU)64. Lee, Kun-Bin (MediaTek)65. Lee, Men Huang (Panasonic)66. Lee, Yoon-Jim (Kyunghee Univ.)67. Lee, Yung Ki (Sejong Univ.)68. Lee, Yung-Lyul (Sejong Univ.)69. Lei, Shawmin (Sharp Labs USA --> MediaTek)70. Lei Sai Kit, Richard (ASTRI)71. Lim, Jeongyeon (ICU --> SK Telecom)72. Lin, Sixin (Huawei)

174

73. Liu, Shan (Mitsubishi Electric)74. Liu, Suxing (Shengheio Univ.)75. Liu, Yingjia (Huawei)76. Lizeano, Leonardo (Telefonica R&D)77. Luo, Jiancong (Thomson)78. Luthra, Ajay (Motorola)79. Masashi, Takahashi (Hitachi)80. Müller, Karsten (Fraunhofer HHI)81. Muczko, Marian (Telekomunikacja Polska)82. Naito, Sei (KDDI)83. Nakamura, Hiroya (JVC)84. Narasimhan, Sam (Motorola)85. Nilsson, Mike (BT)86. Notebaert, Stijn (Ghent Univ.)87. Oelbaum, Tobias (Tech. Univ. Munich)88. Oh, Kwan-Jung (GIST)89. Oh, Seoung-Jun (Kwangwoon Univ.)90. Ohm, Jens-Rainer (RWTH Aachen Univ.)91. Park, Gwang-Hoon (Kyung Hee Univ.)92. Park, Hyoung-Mee (Sejong Univ.)93. Park, Ji Ho (KETI)94. Park, Joon-young (LG Electronics)95. Park, Min-Cheol (Sejong Univ.)96. Park, Min-woo (Kyung Hee Univ.)97. Park, Seanae (Kwangwoon Univ.)98. Park, Seung-Wook (LG Electronics)99. Park, Youngo (Samsung Electronics)100. Pateux, Stephane (Orange - France Telecom)101. Peng, Zhan (Huawei)102. Qian, Zhebin (GE)103. Ridge, Justin (Nokia)104. Rault, Patrick (Quartics)105. Rodriguez, Arturo (Scientific Atlanta / Cisco)106. Sampaio Lobo, Lincoln (Philips)107. Sampedro, Jesus (Polycom)108. Schwarz, Heiko (Fraunhofer HHI)109. Segall, Andrew (Sharp Labs USA)110. Sekiguchi, Shun-ichi (Mitsubishi)111. Senoh, Takanori (Univ. Tokyo)112. Seo, Chang-Won (Sejong Univ.)113. Sheng, Shine (Ten Cent)114. Shim, Seung-yong (Sejong Univ.)115. Shimizu, Shinya (NTT)116. Shin, Hwa Seon (KETI)117. Shin, Jae-Seob (Pixtree)118. Shiodera, Taichiro (Toshiba)119. Sim, Donggyu (Kwangwoon Univ.)120. Sjöberg, Rickard (Ericsson)121. Su, Yeping (Thomson USA --> Sharp USA)122. Suh, Doug Young (KHU)123. Sullivan, Gary (Microsoft Corp.)

175

124. Sun, Huifang (Mitsubishi)125. Suzuki, Teruhiko (Sony)126. Tan, Thiow Keng (NTT DoCoMo)127. Tanimoto, Masayuki (Nagoya Univ.)128. Tanizawa, Akiyuki (Toshiba)129. Tescher, Andy (Microsoft)130. Tian, Dong (Thomson)131. Tomonobu, Yoshino (KDDI)132. Topiwala, Pankaj (FastVDO)133. Tsukuba, Takeshi (Sharp)134. Tung, Yi-Shin (Setabox Tech. Corp. --> Hon Hai Precision/Foxconn)135. Ugur, Kemal (Nokia)136. Van de Walle, Rik (Ghent Univ.)137. Vermeirsch, Kenneth (affiliation ?)138. Vetro, Anthony (Mitsubishi Electric)139. Vieron, Jerome (Thomson R&D France)140. Wang, Xianglin (Nokia)141. Wang, Ye-Kui (Nokia)142. Wedi, Thomas (Panasonic)143. Wiegand, Thomas (Fraunhofer HHI)144. Wien, Mathias (RWTH Aachen Univ.)145. Wittmann, Steffen (Panasonic)146. Wang, Jing (Huawei)147. Wong, Hoi Ming (ASTRI)148. Wu, Wei (Sejong Univ.)149. Wu, Yuwen (Thomson)150. Wu, Dajun (I2R)151. Xiong, Lianhuan (Huawei)152. Xu, Lidong (Intel)153. Xu, Xiaozhong (Tsinghua Univ.)154. Xue, Jianni (Xian Jiaotong Univ.)155. Yamakage, Tomoo (Toshiba)156. Yamamoto, Tomoyuki (Sharp)157. Yamasaki, Takahiro (Oki Electric Industry)158. Yang, Haitao (Xidian Univ.)159. Yang, Jeong-Hyu (LG Electronics)160. Yang, Ping (Tsinghua Univ.)161. Yang, Zhijie (Broadcom)162. Yao, Wei (I2R)163. Yashima, Yoshiyuki (NTT)164. Ye, Bin (Ningbo Univ.)165. Yea, Sehoon (MERL)166. Yin, Peng (Thomson)167. Yang, You (Ningbo Univ.)168. Yoo, Jeong-Ju (ETRI)169. Yoo, Young Joe (Sejong Univ.)170. Yu, Haoping (Thomson)171. Yu, Yong (Broadcom)172. Zhang, Huipin (Cisco)173. Zhang, Xiaosen (Huawei)174. Zheng, Xiaozhen (Huawei)

176

175. Zhu, Gang (Tsinghua Univ.)176. Zhu, Lihua (Thomson)

177

Annex H– Audio report

Source: Schuyler Quackenbush, Chair

1 Opening of the meeting.........................................................................................................1772 Administrative matters...........................................................................................................177

2.1 Approval of previous meeting report 1772.2 Approval of agenda and allocation of contributions 1772.3 Task Groups 1772.4 Communications from the Chair 1772.5 Joint meetings 1772.6 Received National Body Comments and Liaison matters 177

3 Record of AhG meetings.......................................................................................................1773.1 AhG Meeting AAC-ELD Sunday 0900-13001773.2 AhG Meeting Speech and Audio Coding Sunday 0400-1800 183

4 Audio plenary, joint meeting and task group activities.........................................................1854.1 Review of AHG reports 1854.2 Received national body comments and liaison matters 1854.3 Joint meetings and documents from other groups 1854.4 Task Group discussions 186

4.4.1 MPEG-4 audio, conformance, reference software......................................................1864.4.2 MPEG-D MPS.............................................................................................................1864.4.3 MPEG-D SAOC..........................................................................................................1874.4.4 MPEG-4 AAC-ELD....................................................................................................1884.4.5 Speech and Audio Coding...........................................................................................191

5 Meeting deliverables..............................................................................................................1915.1 Recommendations for final plenary 1915.2 Establishment of Ad-hoc Groups 1915.3 Approval of output documents 1925.4 Responses to Liaison and NB comments 1925.5 Press statement 192

6 Future activities.....................................................................................................................1926.1 Schedule of future meetings 1926.2 Agenda for next meeting 1926.3 All other business 1926.4 Closing of the meeting 192

Annex A Participants...............................................................................................................193

178

Annex B Audio Contributions and Schedule...........................................................................194Annex C Task Groups.............................................................................................................199Annex D Output Documents....................................................................................................200Annex E Agenda for the 83rd MPEG Audio Meeting..............................................................203

179

1 Opening of the meetingThe MPEG Audio Subgroup meeting was held during the 82nd meeting of WG11, October 22-26, 2007 in Shenzhen, CN. The list of participants is given in Annex A.

2 Administrative matters2.1 Approval of previous meeting reportThe 81st Audio Subgroup meeting report was registered as a contribution, and was approved.

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 and MDS 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 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 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.5 Joint meetingsThere were no joint meetings with Audio over the course of the week.

2.6 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 Response by14877 USNB Contribution: Soundfield reproduction

technology S. Quackenbush

14878 USNB Contribution: Profiles for ALS that meet industry needs S. Quackenbush

14789 Liaison Statement from ITU-T SG 16 [SC 29 N 8677] None14791 IEC NP: 100/1269/NP [SC 29 N 8693] A. Taleb, S.

Quackenbush14910 Liaison Statement from ITU-T SG 16 [SC 29 N 8817] S. Quackenbush14911 Liaison Statement from 3GPP2 [SC 29 N 8819] None14790 IEC CD 62516 [SC 29 N 8678] K. Kjörling, E. Oh

14862 Swedish NB comments on IEC CD 62516 [m14790 (SC 29 N 8678)] K. Kjörling

14865 German NB comments on IEC CD 62516 [m14790 (SC 29 N 8678)] K. Kjörling

3 Record of AhG meetings

180

3.1 AhG Meeting AAC-ELD Sunday 0900-1300Pierrick Phillip, France Telecom, presented



This gave information on listening tests specified in the workplan and additional test results.FhG-BS vs FhG (12 listeners)

Overall – no statistical difference Per item – 1 better with BS

FT-BS vs FT (12 listeners) Overall – FT-BS better than FT Per item – 4 better with BS, none worse

FT vs FhG (10 listeners) Overall – no difference Per item – 1 better for FT, 2 worse

FT-BS vs FhG-BS (8 listeners) Overall – FT-BS better Per item – 3 better with BS, none worse

FT-BS vs FhG-BS (9 listeners, at Philips) Overall – FT-BS better than FhG-BS Per item – 3 better with FT-BS, 1 worse

FT-BS vs FhG (11 listeners) Overall – FT-BS better than FhG Per item – 3 better with BS, none worse

Kristopher K, Coding Technologies, presented



This gave information on listening tests specified in the workplan and additional test results.FT-BS vs FT (9 listeners)

Overall – FT-BS better than FhG Per item – 5 better with BS, none worse

FhG-BS vs FhG (9 listeners) Overall – no difference Per item – 5 better with BS, none worse

FhG vs FT (9 listeners) Overall – FhG is better Per item – 5 better with FhG, none worse

FT-BS vs FhG (9 listeners) Overall – FT-BS is better Per item – 2 better with FT-BS, none worse

FhG-BS vs FT-BS (6 listeners) Overall – FhG-BS is better Per item – 3 better with FhG-BS, none worse

Markus Schnell, FhG, presented

14998



181













This gave information on listening tests specified in the workplan and additional test results.FT-BS vs FT (14 listeners)

Overall – FT-BS better Per item – 8 better with BS, none worse

FhG-BS vs FhG (14 listeners) Overall – no difference Per item –none different

FhG vs FT (15listeners) Per item – 4 better with FhG, none worse

FT-BS vs FhG (10 listeners) Per item – 2 better with FT-BS, none worse

FhG-BS vs FT-BS (10 listeners) Per item – 3 better with FT-BS, 2 worse

Henney Oh, LG, presented

15010



This gave information on listening tests specified in the workplan and additional test results. This reports on tests conducted at LG and Yonsei University.FT-BS vs FT (11 listeners)

Overall – FT-BS better Per item – 3 better with BS, none worse

FhG-BS vs FhG (11 listeners) Overall – BS is better Per item –none different

FhG vs FT (11 listeners) Overall – FhG is better Per item – 2 better with FhG, none worse

FT-BS vs FhG (10 listeners) Overall – BS is better Per item – 2 better with BS, none worse

FhG-BS vs FT-BS (10 listeners) Overall – no difference Per item – 1 better with FT-BS, none worse

DiscussionPierrick Phillip, France Telecom, pooled all test results from all test sites to obtain the following graphs.

182




FT-BS vs. FT

-3

-2

-1

0

1

2

3

es04 es05 nadib07 nadib08 nadib13 nadib17 nadib20 nadib28 nadib39 GrandTotal

FhG-BS vs. FhG

-3

-2

-1

0

1

2

3


183

FT vs. FhG

-3

-2

-1

0

1

2

3


184

FT-BS vs. FhG-BS

-3

-2

-1

0

1

2

3


FT-BS vs. FhG

-3

-2

-1

0

1

2

3


Based on the test results, Werner Oomen, Philips, constructed the following picture. It shows the systems under test, and the arrows between systems are labelled with the number of test items for which the listening test results showed a statistically significant improvement in performance. The green color is taken from the pooled test results, other colors are results from the individual test sites.

185

All experts in the AhG agree with the following: When pooling all data, FT-BS was better than FT for 8 items and FhG-BS was better than

FhG for no items at the 95% level of significance. In terms of the Workplan from the last meeting, N9238 Workplan for AAC-ELD, this level of performance does not trigger any agreed upon action.

The Chair asked for a show of hands on the following positions:Those who had a strong position in support of the BS technology 10Those who had a strong position that was not in support of the BS technology 5Those who felt that the BS technology provided quality improvement 14Those who felt that the BS technology did not show quality improvement 5

RecommendationsThe AhG recommends that the Audio Subgroup

Continue to discuss the points of view captured by the statements above. That more than audio quality must be considered for adoption of the Core Experiment

technology.

3.2 AhG Meeting Speech and Audio CodingSunday 0400-1800Miyoung Kim, Samsung, presented

14959



It was noted that at the previous MPEG meeting evidence was provided on performance of Samsung technology when operating at 16, 20, 24 kb/s for stereo signals. This contribution shows the performance of Samsung technology when operating at 16, 20, 24 kb/s for mono signals, which is summarized as follows:16 kb/s mono

For speech, NT is not different from VC For music, NT is better that VC at the 95% level of significance. For mixed content, NT is better that VC at the 95% level of significance. When pooling all content types, NT is better that VC at the 95% level of significance.

186




24 kb/s mono For speech, NT is not different from VC For music, NT is not different from VC For mixed content, NT is not different from VC When pooling all content types, NT is better that VC at the 95% level of significance.

The contribution also presented the bitrate used to code each test item. This data was cross-checked by Audio Research Labs, as reported on the AhG reflector.Anise Taleb, Ericsson, commented that he is not able to confirm the performance of VC because the Samsung results are not reported on a per-item basis. The Chair suggested that all the Samsung NT performance information to date be captured in a WG11 output document. Eunmi Oh, Samsung, presented


Thoughts on Joint speech and audio coding

This reviewed the status of all items in the candidate test set and addressed the following issues: Clarify exact source, if CD. Clarify copyright and clarifying whether MPEG has permission to use the item for the

purposes of developing an MPEG standard. Noted that audio books may be an important application area for joint speech and audio

coding, and nominated several additional items in the mixed category that are excerpts from audio books.

Recommended that the following be addressed via a workplan: Adjust the level of each item so that all items are in a listener’s “comfort zone.” For each item, determine whether the best means to derive mono from stereo is via

downmix, left channel or right channel.

David Virette, France Telecom, presented

14980 Pierrick Philippe David Virette Comments on Speech and Audio Coding Activity

This contribution proposes that all items be concatenated, coded and then split prior to presentation for subjective evaluation. This concatenation can be used to eliminate issues of coder startup, shutdown and bit buffer management. In addition, it can be used to emulate the speech/music transition in the encoding and decoding process.It further recommended that there should be five test items in each of the categories of speech, music and mixed content.Finally, it recommended a two step selection procedure:

Retain only codecs better or equal to VC in the first step If necessary, as second step, that there be a collaborative effort to merge qualified codecs

into a single RM.

The Chair noted such collaboration is problematic if a proponent fully describes their technology prior to collaboration and if during the collaboration phase their technology is eliminate and hence is not part of the selected RM.Anisse Taleb, Ericsson, presented

14971 Anisse TalebManuel Briand

Comments on draft CfP on Speech and Audio Coding

This contribution raises a number of issues concerning the CfP. First, the requirements are for speech and audio coding without reference to latency, but the

introductory paragraphs refer to “voice communications applications.”

187











Second, that the CfP notes that WG11 is not obliged to proceed with standardization subsequent to the call, but elsewhere language suggests that standardization will proceed after evaluation of the CfP.

Third, Ericsson experts are concerned that if test items are selected far in advance of submission it could permit tuning of codecs. It is proposed that the process for final test items selection be discussed and carefully formulated.

Fourth, proponent complexity is described in CPU load on an x86 platform. Ericsson experts propose that instead that complexity be reported as a count of arithmetic operations, e.g. on a theoretical floating-point DSP architecture.

Fifth, the proposal notes that if may be that no submitted technology may meet the CfP requirements. In this case, a process should be identified to e.g. merge submissions into a single technology that meets the CfP requirements.

Schuyler Quackenbush, ARL, presented15006 Schuyler Quackenbush Draft CfP for Speech and Audio CodingThis contribution contained a revised CfP based on the output document from the last meeting. The Chair noted that the final CfP will be issued at this meeting, so that working on the CfP text will be one of the most important tasks for this week. With that in mind, Quackenbush presented three additional document that he felt would guide the Speech and Audio Call: Further edits on the CfP, Guidelines for Evaluation and Workplan for Evaluation Tests. These were distributed to the group and will be discussed later in the week.RecommendationsThe AhG recommended that the Audio Subgroup:

Draft an output document that collects all Samsung NT performance information to date. Draft an output document workplan to clarify test items issues raised in the Samsung

contribution m15011. Issue the final CfP on Speech and Audio Coding at this meeting. Issues raised by

contributions 14980 and 14971 should be discussed.

4 Audio plenary, joint meeting and task group activities4.1 Review of AHG reportsThere were no requests to review any of the AHG reports.

4.2 Received national body comments and liaison mattersNB Comment and Liaison documents were reviewed and the drafting of the responses was delegated.

4.3 Joint meetings and documents from other groupsRequirementsHiroya Nakamura, JVC, presented

14975Sadahiro YasuraHiroya NakamuraMotoharu Ueda

Requirements for FTV Audio

This contribution presented a number of new audio-related requirements for FTV. These include Channel-oritented representation (i.e. loudspeakers)

o Recording-oriented parameterso Listener-oriented paremeters

Object-oriented representations (i.e. sound sources)o Position-oriented recording

188






The Chair noted that it is very difficult for audio experts to endorse, revise or expand the text of the contribution since there is very little information on the overall goals and application scenarios of the FVT work. Hence no action was taken at this meeting.

4.4 Task Group discussions4.4.1 MPEG-4 audio, conformance, reference software

Andreas Schneider, Coding Technologies, presented14986 Klaus Peichl Proposed correction to SBR conformance testingThe contribution reviewed the SBR conformance procedure and then explained a pathological issue with one of the monophonic conformance signals. The solution is to create the bitstream at a higher bitrate so as to make the AAC-encoded base band better conditioned for the subsequent SBR operation. The Chair noted that the old bitstream could be labelled as “deprecated” as of an indicated date, and manufactures are directed to use the new bitstream for testing of new product.It was the consensus of the ASG to create a DCOR to MPEG-4 Conformance AMD 8 based on this contribution.Heiko Purnhagen, Coding Technologies, presented

14988

Heiko Purnhagen [email protected] Alexander Groeschel [email protected] Holger Hoerich


This notes that it is possible to signal an arbitrary sampling rate, but in a ProgramConfigElement there is no possibility to signal arbitrary sampling rates. The contribution proposes adding a paragraph to clarify this issue. It was the consensus of the Audio Subgroup to incorporate this into the existing DCOR on DST and MP3on4 and LTP.Tilman Liebchen, LG, presented


It was the consensus of the Audio Subgroup to make this contribution the text of Cor. 3. It is anticipate that 14496-3/Cor 5, 14496-3/AMD2/Cor 3 and 14496-3/AMD3/Cor 1 will be incorporated into 14496-3 Fourth Edition.

4.4.2 MPEG-D MPS

Heiko Purnhagen, Coding Technologies, presented

14856



The contribution raises additional corrections that it proposed to incorporate into 23003/DCOR1. Most are editorial in that they clarify text or correct editing errors. One correction proposed a mechanism to extend the CRC that signals the integrity of the SBR payload from 8 bits to 16 bits.It was the consensus of the Audio Subgroup to incorporate this into 23003/COR1.Andreas Schneider, Coding Technologies, presented14860 Andreas Schneider Update on MPEG Surround conformanceThis contribution presented the current status of MPEG Surround Conformance, which has the status of FPDAM. There are now 19 defined for two base coders, and 36 of the 38 bitstreams are available. The contribution reports that there are still bugs in the MPEG Surround ANSI-C encoder and MPEG Surround conformance tool, but it is expected that these issues will be resolved by the next MPEG meeting.

189

















4.4.3 MPEG-D SAOC

Oliver Hellmuth, FhG, and Erik Schuijers, Philips, presented

14989

J. EngdegårdH. PurnhagenB. ReschL. VillemoesC. FalchO. HellmuthJ. HerreJ. HilpertA. HölzerL. TerentievJ. BreebaartJ. Koppens


This contribution is the proposed text of the Spatial Audio Object Coding (SAOC) Working Draft. The text is comprised of the following sections:

Encoder (informative) Multipoint Control Unit (MCU) stream combiner SAOC to MPEG Surround transcoder

The presentation gave a brief overview of the technology in SAOC, including SAOC to MPEG Surround transcoding Stereo to stereo processing, typically with object re-positioning Binaural rendering of the virtual multichannel presentation Effects interface (Insert and Send)

It was the consensus of the Audio Subgroup to convert this contribution into an output document.

Oliver Hellmuth, FhG, presented


SAOC Reference software

The contribution contains the reference code in an attached *.zip file. The transcoder compiled from the ANSI-C code decodes the bitstreams submitted as part of the CfP and produces MPEG Surround streams that are bit-identical to those associated with the CfP submissions, but subject to occatoinal rounding errors due to the transition from MATLAB based code to ANSI-C code. These rounding errors are at most one quantization level and occur for no more than 0.3% of the parameters. Jeongil Seo, ETRI, presented

14908

Jeongil SeoSeungkwon BeackKyeongok KangKwangki KimMinsoo Hahn


This contribution proposed two Core Experiments. After looking into the SAOC WD, it was discovered that CE1 is exactly as the SAOC WD currently operates, and so this CE is not meaningful. ETRI expects to propose the second CE at the next meeting.Oliver Hellmuth, FhG, presented14985 Oliver Hellmuth

Jürgen HerreLeonid Terentiev


190










Andreas HölzerCornelia FalchJohannes Hilpert

This proposes an additional tool that enhances performance for the Karaoke application. The additional tool is the Two-to-Three (TTT) element to combine and split a foreground object and a background object, where background is L, R (stereo downmix) and the foreground object is C (mono object). FhG expects to propose this CE at the next meeting.The contribution presented listening test results for the cases of Mute/Karaoke and Solo, each with varying levels of residual coding. Results showed that, with 24 kb/s of residual, performance was improved from “fair” for RM0 to “excellent” for the CE proposal. An audio demonstration is available at this meeting. FhG expects to present a cross-check listening test at the next meeting to make a complete CE proposal. Osamu Shimada, NEC, presented

15009



The contribution gives information on a new tool that could be incorporated into SAOC that permits monophonic signals to be separated into individual objects, e.g. speech and undesired background noise. The new tool permits separate control of object level and object localization. This separation would be done in the SAOC decoder. NEC expects to present this as a CE proposal at the next MPEG meeting.

4.4.4 MPEG-4 AAC-ELD

Pierrick Philippe, France Telecom, presented

14979 Pierrick Philippe David Virette Proposed changes to ELD AAC

The contribution covers three broad topics: Block Switching CE – changes in FPDAM text to support incorporation of Block Switching

CE Delayless mixing – corrections and clarifications to the proposed informative annex. Syntax changes

It is the FT recommendation that the AAC-ELD syntax be as close to the MPEG-4 syntax as possible. This includes the following issues:

Backward compatibility is not possible, so backward compatible signalling is not required. Retain method of embedding SBR data in extension payload Suggested small syntax changes may not result in significant bitrate savings.

Markus Schnell, FhG, noted that the FPDAM text already has removed embedding of SBR data in extension payload. Concerning syntax changes the result in bit savings, the Chair noted that savings of up to 1 kb/s corresponds to approximately 3% when operating at 32 kb/s, which is significant.Markus Schnell, FhG, presented

14999 Markus SchnellRalf Geiger Proposed changes on ELD

This contribution proposes the following Transmission of multiple SBR headers in ELDSpecifcConfig to support multichannel

signals. This permits the system to be correctly initialized after reading the ELDSpecifcConfig.

191










Simplification of sytax. This proposes to transmit SBR payload after the AAC data, and do this in a way that supports multichannel.

Error sensitivity categories. This proposes to assign SBR data to two categories of error resilience.

Clarification of text describing filter bank.

Markus Schnell, FhG, presented15000 Markus Schnell Proposed Signaling Extension for AAC ELDThis contribution proposes changes to the ELDSpecificConfig such that all information needed to instantiate a AAC-ELD decoder is known after parsing the ELDSpecificConfig (e.g. output sampling rate, number of channels, single or dual rate). It also proposes an extensible mechanism in the Config that permits new tools (e.g. SAOC) to have their configuration information carried in the ELDSpecificConfig. Discussion of m14979, m14999 and m15000It was the consensus of the Audio Subgroup to:

Since backward compatibility is not possible, avoid backward compatible signalling methods for AAC-ELD. The task group will draft text for subpart 1, which will be reviewed when the FPDAM text is reviewed.

Incorporate the following into the AAC-ELD FPDAM text: new syntax for extensible ELDSpecificConfig (m15000) new error sensitivity categories (m14999) clarification of informative text describing encoder filterbank (m14999) transmission of multiple SBR headers in ELDSpecifcConfig to support multichannel signals

(m14999)

Continue to discuss Block Switching CE Transport of SBR payload Small syntax changes aimed at bitrate savings

Jeff Huang, Qualcomm, presented

15008Yuriy ReznikRavi ChivukulaJeff Huang

Proposed informative addition to AAC ELD

This contribution presents information on the relationship between the MDCT filterbank in AAC and the filterbank in AAC-ELD. In particular, it is shown that the ELD filterbank can be computed using an MDCT core within some simple indexing and sign inversions as pre- and post-processing steps.The consensus of the Audio Subgroup is to continue to discuss ideas of fast forms of filterbanks and other computationally complex element of MPEG specifications, with the possibility of creating informative text in the future that would address such issues in a comprehensive way (e.g. for both ELD and SBR filterbanks, etc). Additionally, the Audio Subgroup encourages the authors to publish the ideas presented in this contribution in the literature so as to make them available to implementers of MPEG specifications.Further Discussion: Thursday AfternoonJeff Huang, Qualcomm, presented a candidate output document that might become an MPEG-4 Technical Report. This document is intended to present fast implementations of filterbanks found in MPEG-4 specifications, such as the filterbank in AAC, the filterbank in AAC-ELD and the SBR filterbank. Ralph Sperschneider, FhG, and Werner Oomen, Philips, felt that this was not an appropriate topic to pursue in the Audio Subgroup. Mohammed Mansour, TI, raised the issue of how would the Audio Subgroup select the “best” implementation for inclusion into this document. Ralph Geiger, FhG, noted that the current content of the document, based on contribution m15008,

192





may not even be the best implementation for the ELD filterbank. The Chair noted that one could have “core experiments” on such a document, but that might not be the best use of Audio Subgroup resources.It was the consensus of the Audio Subgroup that the proposal not be an output document and that such a technical report will not be entertained at this time. However, the Chair will investigate whether the Implementation Studies Group might be an appropriate form for such work. Reference code for such fast implementations may be collected as part of the MPEG-4 VM.David Virette, France Telecom, presented

14973 Pierrick PhilippeDavid Virette

Proposal for MPEG-4 AAC ELD Verification Tests

The contribution proposes the following as a framework for the AAC-ELD verification test: Mono signals G722.1 Annex C at 32 kb/s MPEG-4 AAC-ELD at 32 kb/s MPEG-4 AAC-LD at 32 kb/s and 38 kb/s MPEG-4 HE-AAC at 32 kb/s MUSHRA methodology Use Speech and Audio database as test items

The contribution proposed to have a pre-selection phase that will select final test items from the set of candidate coded items, and FT Ralf Geiger, FhG, presented

15001 Markus SchnellRalf Geiger

Proposal for MPEG-4 ER AAC ELD Verification Test

The contribution proposes the following as the framework for a verification test: Mono signals G722.1 Annex C at 32 kb/s G722.2 (AMR-WB) at 23 kb/s MPEG-4 AAC-LD at 32 kb/s MPEG-4 AAC-ELD at 32 kb/s MPEG-4 HE-AAC at 32 kb/s MUSHRA methodology Use MPEG-4 test set as test items

DiscussionKristofer Kjörling, Coding Technologies, noted that there should be application-driven and technology-driven tests. He proposed that an application-driven test might be

AAC-ELD at 32 kb/s and 48 kb/s and even 64 kb/s G722.1 Annex C at 32 kb/s

It was decided to continue to discuss this in a break-out group with the goal of drafting a test workplan that will be an output document.Discussion Thursday 9AMThe Chair presented a summary of the core experiment results from the past several meetings. Bernhard Grill, FhG, presented his summary of the core experiment results from the past several meetings. The proponents of AAC-ELD and the block switching CE discussed the pros and cons of the block switching CE, including level of performance improvement and impact on complexity and implementation.The Chair summarized the discussion by noting that the non-symmetric windows in the AAC-ELD filterbank together with the TNS tool provide the means for effectively coding transients. Added to this base architecture, the block switching tool provides an increment in performance. However, the

193









level of increment is small and the tool has an impact on some implementation platforms, such as low-cost DSP chips and some use cases, such as those that might exploit frequency-domain mixing.

It was a consensus of the Audio Subgroup that block switching provides an improvement, but the Audio Subgroup feels that the amount of improvement is small relative to potential complexity increase and applicability of the proposed technology to identified scenarios.

It was the consensus of the Audio Subgroup that the Block Switching technology not be adopted into the AAC-ELD FDAM text.Discussion Thursday 2:30PMThe remain open issues on AAC-ELD are:

Transport of SBR payload Small syntax changes aimed at bitrate savings

Transport of SBR payload. The FPDAM text has syntax in which the SBR payload is part of the AAC-ELD payload rather in the extension payload. There were no opinions expressed to change the FPDAM text, so it was the consensus of the Audio Subgroup to keep the FPDAM text as is.

Syntax Changes. Markus Schnell, FhG, reviewed the set of syntax changes that are presented in contribution m14999, and which are that same as those presented in Chapter 7 of N9237, Technology under Consideration for AAC-ELD. Pierrick Philippe, France Telecom, raised an objection to the proposed changes, and reminded audio experts that these objections are presented in his contribution m14979. The Chair confirmed that the proposed changes result in 11 bits/frame of savings, or a savings of 0.55 kb/s when operating AAC-ELD in 48 kHz/24 kHz dual mode. The Chair further noted that there is no backward compatibility in AAC-ELD, and hence no compelling reason to retain a given structure in the bitsteram. Kristofer Kjörling, Coding Technologies, felt that it would be inappropriate for the Audio Subgroup to neglect this potential bitrate savings when the primary objective of its work is compression efficiency. It was the consensus of the Audio Subgroup to incorporate the proposed syntax changes into the AAC-ELD FDAM text.

Thursday 5PMMarkus Schnell, FhG, presented the AAC-ELD FDAM text. There was consensus on the FDAM text. The Chair advised that approval Friday morning will be a formality only with minimum discussion, but noted that there will be a 1-month editing period to check and re-check the correctness of the text. The Chair also noted that he has the expectation that all National Bodies will approve the AAC-ELD FPDAM text in MPEG closing plenary.

Ralf Geiger, FhG, presented the DoC on AAC-ELD FPDAM. The response to the FNB, GNB and USNB was discussed and it was agreed that revisions were required and this will be done in a task group this evening.

4.4.5 Speech and Audio Coding

The Chair presented the CfP text several times for review and revision by the group. Likewise, the Chair presented the Evaluation Guidelines text for review and several revisions were made. After review, there was consensus on the text of the CfP and final text will be reviewed and approved Friday morning. The open issues in the Evaluation Guidelines will be identified Friday morning prior to review and approval.

5 Meeting deliverables

194

5.1 Recommendations for final plenaryThe Audio recommendations were presented and approved.

5.2 Establishment of Ad-hoc GroupsThe following ad-hoc groups were established by the Audio subgroup:

No. Title Mtg9525 AHG on Audio Standards Maintenance No9526 AHG on Speech and Audio Exploration and SAOC Yes

5.3 Approval of output documentsAll output documents, shown in Annex D, were presented in Audio plenary and were approved.

There was considerable discussion of following document

9502 Proposed Workplan on AAC-ELD Verification TestMuch of the discussion resulted from a lack of consensus on the systems to be included in the test. There were strong opinions for and against inclusion of AMR-WB in the test. It was decided to remove AMR-WB from the Verification Test document (see removed excerpt, below), and after this was done, there was consensus on approving the document. The systems under test will be discussed at the next MPEG meeting prior to finalization of test plan.Text removed:“AMR-WB 23.8 kbit/s 16 kHz 25 ms

For the AMR-WB reference the input signal shall be low pass filtered at 7kHz using the P.341 filter of the ITU-T Software Tool Library.“

5.4 Responses to Liaison and NB commentsThe responses to Liaison and NB comments were prepared and approved.

5.5 Press statementThe Audio contribution to the press statement was prepared and approved via email.

6 Future activities6.1 Schedule of future meetingsAd Hoc group meetings are indicated in Section 5.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.

6.2 Agenda for next meetingThe agenda for the next MPEG meeting is shown in Annex E.

6.3 All other businessThere was none.

6.4 Closing of the meeting The 82nd Audio Subgroup meeting was adjourned Friday at 13:40.

195

Annex A Participants

First Name Last Name Country AffiliationMinsoo Hahn KR Information and Communications Univ.Jeff Huang USA Qualcomm Inc.Yue Lang CN huaweiMingu Lee KR Seoul National UniversityJun Matsumoto JP SonyMasayuki Nishiguchi JP SonyHochong Park KR Kwangwoon UniversityShidong Shang China FreescaleSang Bae Chon KR Seoul National Univ.Zhengzhong Du CN Huawei TechnologiesRalf Geiger DE Fraunhofer IISBernhard Grill DE Fraunhofer IISNoboru Harada JP NTTOliver Hellmuth DE Fraunhofer IISHaibin Huang SG I2RDong Soo Kim KR LG ElectronicsKwangki Kim KR Information and Communications Univ.Mi Young Kim KR SamsungKristofer Kjörling S Coding TechnologiesTaejin Lee KR ETRITe Li SG I2RTilman Liebchen DE LG ElectronicsHongfei Ma CN Xidian UniversityMohamed Mansour USA Teas InstrumentsTakehiro Moriya JP NTTMarkus Multrus DE Fraunhofer IISToshiyuki Nomura JP NECTakeshi Norimatsu JP PanasonicEunmi Oh KR SamsungHenney Oh KR LG ElectronicsWerner Oomen NL Philips Applied TechnologiesHee-Suk Pang KR LG ElectronicsPierrick Philippe FR France Telecom R&DHeiko Purnhagen SE Coding TechnologiesSchuyler Quackenbush USA ARLAndreas Schneider DE Coding TechnologiesMarkus Schnell DE Fraunhofer IISErik Schuijers NL PhilipsJeongil Seo KR ETRIOsamu Shimada JP NECRalph Sperschneider DE Fraunhofer IISAnisse Taleb SE Ericsson ABYasuhiro Toguri JP SonyMauri Vaananen FIN Nokia Res. CenterDavid Virette FR France Telecom R&DOliver Wuebbolt DE ThomsonWei Xiao CN Huawei TechnologiesSungyong Yoon KR LG Electronics

196

Annex B Audio Contributions and Schedule

Day / Time Task Group Document XSunday0900-1300 AhG on AAC-ELD



X



X

14998



X

15010



X

Discussion and presentation of any other information.Recommendations and review of AhG Report

1300-1400 Lunch

1400-1600 AhG on Speech and Audio Coding

14959



X


Thoughts on Joint speech and audio codingX


Comments on Speech and Audio Coding Activity

X

14971 Anisse TalebManuel Briand

Comments on draft CfP on Speech and Audio Coding

X

15006 Schuyler Quackenbush Draft CfP for Speech and Audio Coding XDiscussionRecommendations and review of AhG Report.

Monday0900-1130 MPEG Plenary1200-1300 Audio Plenary14882 Schuyler Quackenbush 81st MPEG Audio Report X

197




































14777 R. Sperschneider AHG on Audio Standards Maintenance X

14778 S. Quackenbush Eunmi Oh

AHG on AAC-ELD, Speech and Audio Exploration and SAOC

X

NB Comments

14877 Andy Tescher for USNB USNB Contribution: Soundfield reproduction technology

X

14878 Andy Tescher for USNB USNB Contribution: Profiles for ALS that meet industry needs

X

Liaison

14789 ITU-T SG 16 via SC 29 Secretariat

Liaison Statement from ITU-T SG 16 [SC 29 N 8677]

X

14791 IEC TC 100 via SC 29 Secretariat

IEC NP: 100/1269/NP [SC 29 N 8693] X

14910 ITU-T SG 16 via SC 29 Secretariat

Liaison Statement from ITU-T SG 16 [SC 29 N 8817]

X

14911 3GPP2 via SC 29 Secretariat Liaison Statement from 3GPP2 [SC 29 N 8819]

X

14790 IEC TC 100 via SC 29 Secretariat IEC CD 62516 [SC 29 N 8678] X

14862 Swedish NB via SC 29 Secretariat

Swedish NB comments on IEC CD 62516 [m14790 (SC 29 N 8678)]

X

14865 German NB via SC 29 Secretariat

German NB comments on IEC CD 62516 [m14790 (SC 29 N 8678)]

MPEG Ballots



X


X


X


X


X


X


X

14796 SC 29 SecretariatSummary of Voting on ISO/IEC 14496-5:2001/Amd.10:2007/DCOR 1 [SC 29 N 8702]

X


X

198

















































































mailto:??


mailto:??


X

1300-1400 Lunch1400-1500 Requirements

14975Sadahiro YasuraHiroya NakamuraMotoharu Ueda

Requirements for FTV AudioX

MPEG-4

14986 Klaus Peichl Proposed correction to SBR conformance testing

X

14988

Heiko Purnhagen [email protected] Alexander Groeschel [email protected] Holger Hoerich


X

1500-1600 MPEG Surround

14856



X

14860 Andreas Schneider Update on MPEG Surround conformance X1600-1800 SAOC

14989

J. EngdegårdH. PurnhagenB. ReschL. VillemoesC. FalchO. HellmuthJ. HerreJ. HilpertA. HölzerL. TerentievJ. BreebaartJ. Koppens


X


SAOC Reference software X

14908

Jeongil SeoSeungkwon BeackKyeongok KangKwangki KimMinsoo Hahn


X

14985

Oliver HellmuthJürgen HerreLeonid TerentievAndreas HölzerCornelia FalchJohannes Hilpert


X

199































15009



X

Tuesday0900-0930 MPEG-4


X

0930-1300 AAC-ELD

14979 Pierrick Philippe David Virette Proposed changes to ELD AAC X

14999 Markus SchnellRalf Geiger Proposed changes on ELD X

15000 Markus Schnell Proposed Signaling Extension for AAC ELD

X

15008Yuriy ReznikRavi ChivukulaJeff Huang

Proposed informative addition to AAC ELDX

14973 Pierrick PhilippeDavid Virette

Proposal for MPEG-4 AAC ELD Verification Tests

X

15001 Markus SchnellRalf Geiger

Proposal for MPEG-4 ER AAC ELD Verification Test

X

1300-1400 Lunch1400-1800 Task Group Activities

Speech and Audio CfP X1800-1900 Liaison1900- ChairsWednesday0900-1100 MPEG Plenary1200-1300 Lunch1300-1700

Speech and Audio CfP, Evaluation XTask group activity

1800-203 0 Social Bus to Splendid China at Marco Polo south doors

2050-2230 Social Dinner Dinner at Crowne Plaza Hotel Ball RoomThursday0900-1300

AAC-ELD Bock switching CE XSpeech and Audio CfP, Evaluation X

1230-1330 Lunch1330-1800

200


























Proposed TR on Filterbank Implemetation XAAC-ELD open issues XSA CfP XSA Evaluation X

1700-1800Review of and consensus onAAC-ELD FDAM and DoCSA CfP

X

1800- Chairs MeetingFriday Audio plenary0900-1300 Recommendations for final plenary X

Establishment of new Ad-hoc groups XAhG Mandates XGet document numbers X

1000 Approve Responses to NB comments X1030 Approval of output documents X

Review of Audio presentation to MPEG plenary

X

Agenda for next meeting -A.O.B. XClosing of the Audio meeting X

1300-1400 Lunch1400- MPEG Plenary

201

Annex C Task Groups

1. MPEG-4 AAC-ELD2. Speech and Audio3. MPEG-D SAOC4. MPEG-D MPS5. MPEG-4 audio, conformance, reference software

202

Annex D Output DocumentsNo. Title TBP Available

14496-3 Audio9490 DoC on ISO/IEC 14496-3:2005/DCOR 5 No 07/10/269491 ISO/IEC 14496-3:2005/Cor. 5, DST and MP3on4 and LTP No 07/10/269492 DoC on ISO/IEC 14496-3:2006/Amd. 2:2006/DCOR 3 No 07/10/269493 ISO/IEC 14496-3:2006/Amd. 2:2006/Cor. 3, ALS No 07/10/269495 ISO/IEC 14496-3:2005/Amd. 3:2006/Cor. 1 No 07/10/269496 DoC on ISO/IEC 14496-3:2005/FPDAM 8 No 07/10/26

9497 ISO/IEC 14496-3:2005/FDAM 8, MP4FF Box for Original Audio File Information

No 07/10/26

9498 DoC on ISO/IEC 14496-3:2005/FPDAM 9 No 07/10/269499 ISO/IEC 14496-3:2005/FDAM 9, AAC-ELD No 07/11/309500 ISO/IEC 14496-3:200x, Fourth Edition No 07/11/30

9501 Proposed Overview of Transport of AAC, HE-AAC and MPEG Surround in MPEG-2 Systems

No 07/11/30

9502 Proposed Workplan on AAC-ELD Verification Test No 07/10/26No. Title TBP Available

14496-4 Conformance testing9503 DoC on ISO/IEC 14496-4:2004/DCOR 5 No 07/10/269504 ISO/IEC 14496-4:2004/Cor. 5, Audio Corrections No 07/10/269505 ISO/IEC 14496-4:2004/Amd 8/DCOR 1, SBR conformance testing No 07/10/269506 DoC on ISO/IEC 14496-4:2004/Amd 13/DCOR 1 No 07/10/26

9507 ISO/IEC 14496-4:2004/Amd 13/Cor 1, New bitstreams for LD-AAC profile coders

No 07/10/26

9508 Status of BSAC Conformance No 07/10/26No. Title TBP Available

14496-5 Reference Software 9509 DoC on ISO/IEC 14496-5:2001/Amd. 10:2007/DCOR 1 No 07/10/26

9510 ISO/IEC 14496-5:2001/Amd. 10:2007/Cor. 1, BSAC in SLS and ALS Corrections

No 07/10/26

9511 DoC on ISO/IEC 14496-5:2001/PDAM 20, MPEG-1 and -2 on MPEG-4

No 07/10/26

203

9512 ISO/IEC 14496-5:2001/FPDAM 20, MPEG-1 and -2 on MPEG-4 No 07/10/26No. Title TBP Available

23003-1 MPEG Surround9513 DoC on ISO/IEC 23003-1:2007/DCOR 1 No 07/10/269514 ISO/IEC 23003-1:2007/Cor. 1 No 07/11/309515 Study on ISO/IEC 23003-1:2007/FPDAM 1, Conformance No 07/11/309516 Study on ISO/IEC 23003-1:2007/FPDAM 2, Reference Software No 07/11/30No. Title TBP Available

23003-2 Spatial Audio Object Coding9517 WD on ISO/IEC 23003-2:200x, SAOC text and reference software No 07/11/309518 Status and Workplan on SAOC Core Experiments No 07/10/26No. Title TBP Available

Exploration – Audio and speech coding9519 Call for Proposals on Unified Speech and Audio Coding YES 07/10/269520 Draft Evaluation Guidelines for Speech and Audio Call No 07/10/269521 Report on Evidence for Unified Speech and Audio Coding No 07/10/269522 Workplan for Candidate Test Items No 07/10/26No. Title TBP Available

Liaison Statements9523 Liaison Statement to ITU-T SG 16 No 07/10/269524 Liaison Statement to IEC on CD 62516 No 07/10/26

204

Annex E Agenda for the 83rd MPEG Audio Meeting

Agenda Item1. Opening of the meeting2. Administrative matters

2.1. Approval of agenda and allocation of contributions2.2. Communications from the Chair2.3. Joint meetings2.4. Review of task groups and mandates2.5. Approval of previous meeting report2.6. Review of AhG reports 2.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 Conformance and Reference Software4.4. MPEG Maintenance, including MPEG-1, MPEG-2, MPEG-4, SMR and MPEG Surround issues

5. Discussion of unallocated contributions6. Meeting deliverables

6.1. Recommendations for final plenary6.2. Establishment of new Ad-hoc groups6.3. Approval of output documents6.4. Responses to NB comments6.5. Responses to Liaison statements6.6. Press statement

7. Future activities8. Agenda for next meeting9. A.O.B10. Closing of the meeting

205

Annex I – 3DG report

Source: Marius Preda, Chair

1 Opening of the Meeting

1.1 Approval of the agenda

1.2 Goals for the weekThe goals of this week are:

Review FAMC text and update the FPDAM Review on-going AFX experiments and issue the WD for SP Review 3DGCM related contributions and issue the CD Review and promote the 3DGC profiles Issue FDAM of Geometry and Shadow reference software Issue FDAM of Geometry and Shadow conformance Issue PDAM.0 of FAMC reference software Issue PDAM of FAMC conformance Investigate future developments of MPEG 3D Graphics

1.3 Standards from 3DG

Std Pt Edit. Project Description CfP WD CDPDAM

FCDFPDAM

FDISFDAM

Obs

4 4 2004 Amd.32 FAMC conformance 07/04 07/10 08/01 08/074 4 2004 Amd.33 Multiresolution profile

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

4 4 2004 Amd.34 3DGC Model conformance 07/10 08/01 08/04 08/104 5 2001 Amd.21 FAMC reference software 07/04 07/10 08/01 08/07

206

4 5 2001 Amd.22 3DGC Model RefSoft 07/10 08/01 08/04 08/104 16 200x 3rd Ed. AFX 07/10 08/01 08/04 08/104 16 2006 Amd.2 FAMC 07/07 08/01 08/074 16 2006 Amd.3 3D Multiresolution profile 07/07 07/10 08/044 16 2006 Amd.4 Scene partitioning 07/10 08/01 08/04 08/104 16 2006 AMD.1/Cor.1 3DMC ext. corr. 07/10 08/044 25 200x 3D Graphics Compression

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

1.4 Room allocation3DG : Rome

1.5 Allocation of contributions and summary of the discussions

N° Title Schedule ActivityD1 Monday D1

MPEG Plenary D1 09:00~11:30 MPEG GeneralLunch Break D1 13:00~14:003DG Plenary D1 14:00~18:00 3DG GeneralRoll call, Agenda, Goals, FAQ, etc., clarify the status on www.mpeg-3dgc.org maintenance- migration of the 3DGC web server from Samsung to Orange Labs

Marius Preda

14866

Report of AHG on 3DGC documents, experiments and software maintenance- the need of having the conformance of the 3DGC in one single place or to create a summary file indicating in which amendment each tool has the conformance described.Resolution: Prepare a document containing the AFX tools and indicating the place for all the conformance and RefSoft (tool by tool)Action to be performed by Jeong-Hwan

Jeong-Hwan Ahn, Ning Lu

207

N° Title Schedule ActivityAFX 3rd Edition - collecting AFX related parts in one single document in order to improve the communication and easy the access to the standard.Resolution: Issue the 3rd edition including AMD1 to 4. Synchronise the timing of this edition with the one of P25. Allocated editors: Marius, Patrick, Jeong-Hwan

Marius Preda, all

Coffee Break 15:30~16:00Dissemination- need to publish latest AFX developpements in a unique placeResolution: investigate if it possible to organize a special session in ICME2008 or in ICIP2008.The communication session needs 3 sections: presentation of AFX latest developments, call for state of the art and new compression technologies from academia, call for short communication from industry focused on requirements, implementation difficulties, …

Karsten Muller, Marius Preda

FAMC (AMD2)

14891

Proposed corrections and changes to ISO/IEC 14496-16:2006/PDAM2 (FAMC)Recommendations- to correct wrong parameter types- to byte align headersResolution: recommendations accepted, a NB comment is necessary for supporting the modifications, a study text for FAMC will be issued

Nikolce Stefanoski, Jörn Ostermann

14934 FAMC decoder software descriptionPresentation of the current implementation of the decoder, source code of the decoder is provided.Resolution: contribution accepted : the proposed decoder is considered as FAMC reference implementation. Activity should continue with the goal of integrating the decoder in

Khaled Mamou, Heiner Kirchhoffer, Nikolce Stefanoski, Detlev Marpe, Karsten

208








N° Title Schedule Activity

IM1Müller, Jörn Ostermann, Titus Zaharia, Françoise Prêteux

14936

FAMC decoder conformanceContribution providing an almost complete set of FAMC bistreams. The covered functionalities are:- compression of geometry and normals- DCT, lifting schema, LD and combinations- CABAC - streamingBitstreams are in FAMC format. Resolution: Activity should continue with the goal of providing the dataset in MP4 file format.

Khaled Mamou, Heiner Kirchhoffer, Nikolce Stefanoski, Detlev Marpe, Karsten Müller, Jörn Ostermann, Titus Zaharia, Françoise Prêteux

14958

Progress report on the FAMC integration into the MPEG-4 RefSoftThe contribution is a commitment to finish the software implementation of FAMC for the next meeting

Khaled Mamou, Titus Zaharia, Françoise Prêteux

Core Experiments (Scene Partitioning) D1 16:00~18:00 CE2

14953

Comments on Space Partitioning CE- consider the 2D case, changes in the node design, local versus global coordinatesRecommendations accepted

Jean Le Feuvre

14880

Report on CE2: Space Partitioning- binary format for efficiently handle the scene partitioning data (wrt a potential BIFS representation the format is 20%-80%)Res: issue a new AMD, Patrick is the editor, a Req. for AMD has to be prepared

Patrick Gioia, Linda Pagès

D2 Tuesday D23DGCM D2 09:00~10:30

14903 Compression Results for BBA on COLLADA Animation- presenting the manner of extracting the animation tracks

Blagica Jovanova, Marius Preda,

209

N° Title Schedule Activityfrom COLLADA and the compression results (7%-20% from RAR)Res: adopt BBA for compressing tracks in COLLADANeed of investigating IC and FAMC

Francoise Preteux

14905 Storage of XML documents and associated media resources in the ISO file format

Blagica Jovanova, Cyril Concolato, Jean Le Feuvre, Marius Preda

Will also be discussed in Systems

Xxx

Common Framework for Software Implementation (status on IC integration)- donate the software allowing to produce compressed MP4 files for COLLADA and X3D (by INT), make a contribution for next meeting with the software ASAP, initiate discussions on the reflector on how to use the software

all

RefSoft and Conformance for 3DGCMRefSoft should be able to decode MP4 files and obtain the initial XML representation (when XML is not binarised)Editor for Conformance: Jeong-HwanEditor for RefSoft: BlagicaCoffee Break 10:30~11:00Profiles D2 11:30~12:00Multi-Resolution Profile AMD 3 and ConformanceNo changes in AMD3The conformance list has to be completed, a plan for crosschecking the new bitstreams should be provided.

Patrick Gioia

Lunch Break D2 12:00~14:003DMC and future of Mesh Compression D2 14:00~15:00

14904

Support for multiple texture coordinates and additional attributes per vertex in 3DMC- Apply the proposed recommendations to 3DMCExt by issuing a COR- in addition to add a versioning system in 3DMCExt allowing to include the original 3DMC as well as making provisions for future developmentsCOR1: Editor: Marius

Ivica Arsov, Marius Preda , Francoise Preteux

14935 Simple and Fast Compression of 3D Meshes Giseok Son, Daiyong

210

N° Title Schedule Activity- A compression method based on delta prediction and specific binarization. Files are up to 30% bigger that 3DMC with VO preservation but encoding and decoding time decreases by 70%.Res: compare with BIFS encoding/decoding wrt data size and complexity Present the absolute numbers for decoding / polygon.

Kim, Hyungyu Kim, Euee S. Jang

Coffee Break 15:30~16:00Metaverse D2 16:00~17:00

14906 MPEG-4 3D Graphics in MetaverseMarius Preda, Francisco Moran, Francoise Preteux

Joint with Systems D2 17:00~17:30

14905

Storage of XML documents and associated media resources in the ISO file formatResolution: inside meta-boxdata references

3 (self)4 #ffp(track_ID=2)5 #ffp(track_ID=3)

item location

12 dref index 1, offset=0, length=013 dref index 2, offset=0, length=0

item name12 name=myaudio.mp4, mime=video/mp413 name=myvideo.mp4, mime=video/mp4

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

Blagica Jovanova, Cyril Concolato, Jean Le Feuvre, Marius Preda

Room: Zurich Joint meeting with Systems

D3 Wednesday D3MPEG Plenary D3 09:00~12:00 MPEG General

Lunch Break D3 12:00~14:003DGC Plenary (Editing of documents) D3 14:00~18:00Set up the CEs all

211

N° Title Schedule Activity- CE Scene partitioning is closed (the technical work is finished) - CE on MeshComp.Part 16 AMD2 (FAMC) EditingIssue the study all

FAMC RefSoft and ConformanceIssue PDAM for each all

Part 16 AMD3 (MRZ Profile) EditingIssue FPDAM all

MRZ ConformanceReview again Thursday all

D4 Thursday D43DGC Plenary (Editing of documents) D3 09:00~12:003DMC AMD1/Corr.1 Goal of the document: Update 3DMCext to include 3DMC (as version 1) and correct the support of multiple attributes per vertex.

all

WD of Scene Partitioning allLunch Break D3 12:00~14:003DGC Plenary (Editing of documents) D3 14:00~18:003DGCM EditingPromote it in CD all

3DGCM RefSoftwareWD1.0 all

3DGCM RefSoftware Req all3DGCM ConformanceWD1.0 all

3DGCM Conformance Req allAFX 3rd Edition allConf and RefSoft tool by tool Jeong-HwanCore Experiment all

D5 Friday D53DG output documents Review D4 09:00~12:00 3DG General

212

N° Title Schedule ActivityCore Experiment cont.1 CE all

Part 16 AM2 (FAMC) Review allFAMC RefSoft and Conformance Review allPart 16 AM3 (MRZ Profile) Review allMRZ Conformance Review all3DGCM Review all3DMC AMD/Corr 1 allAhGs and resolutions allLunch Break D5 12:00~14:00MPEG Plenary D5 14:00~ MPEG General

1.6 Attendance list

Name Country CompanyJeong-Hwan Ahn Korea Samsung AITMarius Preda France INTFrançoise Prêteux France INTPatrick Gioia France France Telecom

R&DEuee S. Jang Korea Hanyang Univ.Daiyong Kim Korea Hanyang Univ.JaeBum Jun Korea Hanyang Univ.SinWook Lee Korea Hanyang Univ.Karsten Muller Germany FHG-HHINikolce Stefanoski Germany Leibniz

Universtat Hannover

He Zan Ming Korea Hanyang Univ.

213

2 Resolutions of 3DG

2.1 Output documents

2.2 Part 4 Conformance testing 2.2.1 The 3DGC subgroup recommends approval of the following documents

No. Title TBP Available14496-4 Conformance testing

9546 Text of ISO/IEC 14496-4:2004/ FDAM21 (Geometry and Shadow Conformance)

No 07/10/26

9528 PDAM of ISO/IEC 14496-4:2004 AMD32 (FAMC Conformance) No 07/10/269529 PDAM of ISO/IEC 14496-4:2004 AMD33 (MultiResolution Profile

Conformance)No 07/10/26

9530 Request for Amendment of ISO/IEC 14496-4:2004 (3DGCM Conformance)

No 07/10/26

9531 WD 1.0 of ISO/IEC 14496-4:2004 AMD34 (3DGCM Conformance) No 07/10/26

2.2.2 The 3DGC subgroup recommends nominating Jeong-Hwan Ahn (Samsung) as project editor of ISO/IEC 14496-4/Amd 34 (3DGCM conformance).

2.3 Part 5 Reference Software 2.3.1 The 3DGC subgroup recommends approval of the following documents

No. Title TBP Available14496-5 Reference Software

9547 Text of ISO/IEC 14496-5:2001/ FDAM13 (Geometry and Shadow RefSoft)

No 07/10/26

9532 PDAM of ISO/IEC 14496-5:2001 AMD21 (FAMC RefSoft) No 07/10/269533 Request for amendment of ISO/IEC 14496-5:2001 (3DGCM

RefSoft)No 07/10/26

9534 WD1.0 of ISO/IEC 14496-5:2001 AMD22 (3DGCM RefSoft) No 07/10/26

2.3.2 The 3DGC subgroup recommends nominating Marius Preda (INT) as project editor of ISO/IEC 14496-5/Amd 22 (3DGCM RefSoft).

2.4 Part 16 Animation Framework eXtension (AFX) 2.4.1 The 3DGC subgroup recommends approval of the following documents

No. Title TBP Available14496-16 Animation Framework eXtension (AFX)

9535 Study Text of ISO/IEC 14496-16:2006/PDAM2 (Frame-based Animated Mesh Compression)

No 07/10/26

9536 Text of ISO/IEC 14496-16:2006/FPDAM3 (3D MultiResolution Profile)

No 07/10/26

214

9537 Request for amendment of ISO/IEC 14496-16:2006 (Scene Partitioning)

No 07/10/26

9538 WD1.0 of ISO/IEC 14496-16:2006 AMD 4 (Scene Partitioning) No 07/10/269539 Text of ISO/IEC 14496-16:2006/AMD1.Corr1 (3DMC Extension

Correction)No 07/10/26

9540 WD 1.0 of AFX 3rd Edition No 07/11/269541 3D Graphics Core Experiments Description No 07/10/26

2.4.2 The 3DGC subgroup requests National Bodies to kindly consider the study document N 9535 in their upcoming ballot votes on ISO/IEC 14496-16:2006/PDAM 2.

2.4.3 The 3DGC subgroup recommends nominating Patrick Gioia (France Telecom) as project editor of ISO/IEC 14496-16:2006/Amd 4 (Scene Partitioning).

2.4.4 The 3DGC subgroup recommends nominating Marius Preda (INT) as project editor of ISO/IEC 14496-16:2006/Amd 1/Cor. 1(3DMC Extension Correction).

2.4.5 The 3DGC subgroup recommends nominating Marius Preda (INT), Patrick Gioia (France Telecom) and Jeong-Hwan Ahn (Samsung) as project editors of 3rd Edition of ISO/IEC 14496-16:2006 (AFX).

2.5 Part 25 3D Graphics Compression Model2.5.1 The 3DGC subgroup recommends approval of the following documents

No. Title TBP Available14496-25 3D Graphics Compression Model

9542 Text of CD of ISO/IEC 14496-25 Yes 07/10/26

2.6 Establishment of 3DG Ad-Hoc Groups

N9494 AHG on 3DG documents, experiments and software maintenance

Mandate: 1. Maintain and edit 3DG documents2. Coordinate 3DG CE activity3. Coordinate 3DG related conformance and reference software

Chairmen: Jeong-Hwan Ahn (Samsung AIT),Nikolce Stefanoski (TNT)

Duration: Until 82nd Meeting Meetings Sunday before 82nd meetingReflector: mpeg-3dgc AT gti. ssr. upm. EsSubscribe: http://www.gti.ssr.upm.es/mailman/listinfo/mpeg-3dgc

215

http://www.gti.ssr.upm.es/mailman/listinfo/mpeg-3dgc

3 Closing of the MeetingSee you in Antalya.

216