2.3Creation of Task Groups
Task groups were convened for the duration of the MPEG meeting, as shown in . Results of task group activities are reported below.
2.4Approval of previous meeting report
The Chair asked for approval of the 99th Audio Subgroup meeting report, which was registered as a contribution. The report was approved.
m24711
|
99th MPEG Audio Report
|
S. R. Quackenbush
| 2.5Review of AHG reports
There were no requests to review any of the AHG reports.
2.6Joint meetings
Groups
|
What
|
Where
|
Day
|
Time
|
Audio, Requirements
|
3D CfP, Evaluation, Test Items
|
Audio
|
Tue
|
1400-1500
|
All
|
Database of MPEG “milestone” documents
|
3DG
|
Wed
|
1130-1230
|
Audio, Requirements
|
3D CfP, Evaluation, Test Items
|
Audio
|
Thu
|
1600-1700
| 2.7Received National Body Comments and Liaison matters
No.
|
Body
|
Title
|
Response
|
m24231
|
IEC TC100
|
Text-to-Speech for Television
|
Chair
| 2.8Plenary Discussions
MPEG Codec-Independent Audio Code Points
m24981
|
Coding-independent Code-Points
|
David Singer, Thomas Stockhammer
|
Energy-Efficient Audio Processing
m24982
|
Energy-efficient Video Processing on Mobile Devices with Embedded Content Information
|
Zhan Ma, Mian Dong, Xin Li, Felix Fernandes, Sungoh Hwang, Jaeyeon Song
|
3Record of AhG meetings
There were no AhG meetings.
4Task group activities 4.1Joint Meetings 4.1.13D Audio Status, with Requirements (Tue 1400-1430)
The Audio Chair summarized the current status of and challenges in the 3D Audio work. It was agreed to have as a goal selection of 3D Audio RM0 technology at the 104th MPEG meeting in April, 2013.
4.1.2Database of MPEG “Milestone” Documents (Wed 1130-1230 – Max Neuendorf)
The objectives of this database project is to "store information related to the WG11 standard projects so that we can obtain the ‘views’ that are most useful to the membership."
The “data” used in the database is information about the Status, Edition, Amendments, Corrigenda, Interconnections, “Moved Standards” associated with the MPEG work.
More specifically, “data” may include:
-
ISO number, Part Number, edition number, type (TR/IS), Amd.x, Cor.x
-
short description (for each component, S, AMD, COR)
-
editor names (for each component, S, AMD, COR)
-
CfP, WDx, CDx, DISx, FDIS (date as mpeg meeting number + link to wg11 file)
-
CfP, WDx, PDAM, DAM, FDAM
-
WDx, DCOR, COR
-
WDx, DTR, TR
-
And perhaps a link to SC29 document number
The database permits “views” which may be presented as:
-
Table indicating the FDIS (or other stage) per standard
-
Table indication the stages per standard per part
-
Table N12703 (time line, target dates)
The Editor of a standard would have the following role:
-
Chairs for short description (duty)
-
Chairs should be able to update any entry
-
Chairs should be able to add an entry (e.g. new Amd.)
-
possible workflow (proposed by Youngkwon)
-
Chairs enter new data
-
Yukiko confirms
-
System provides output number (not from Pierrick)
-
System adds line in resolution document
-
other resolutions added manually
Is was agreed that the next Action items would be:
-
create database from Yukiko's database to serve as a base for future use
Dostları ilə paylaş: |