Review of AHG reports
There were no requests to review any of the AHG reports.
-
m36505
| -
AHG on 3D Audio and Audio Maintenance
| -
ISO secretariat
| -
| -
m36507
| -
AHG on Responding to Industry Needs on Adoption of MPEG Audio
| -
ISO secretariat
| -
| Ballots to process
The following table indicates the ballots to be processed at this meeting.
Received National Body Comments and Liaison matters
The Liaison statements were presented, discussed, and resources to draft responses were allocated.
Number
|
Title
|
Topic
|
36220
|
Recommendation ITU-R BS.1116-3
|
Liaison Statement from ITU-R SG 6
|
36221
|
Recommendation ITU-R BS.1196-4
|
Liaison Statement from ITU-R SG 6
|
36226
|
Development of a baseline renderer (for audio)
|
Liaison Statement from ITU-R SG 6/WP 6C
|
36227
|
Metadata descriptors for sound content
|
Liaison Statement from ITU-R SG 6/WP 6B
|
36357
|
ATSC Liaison Response to MPEG Audio
|
ATSC
|
36579
|
Liaison Statement from CableLabs on MPEG-H 3D Audio
|
CableLabs
|
36641
|
Liaison Statement from CableLabs on MPEG-H 3D Audio
|
(Duplicate of 36579)
|
36642
|
Liaison Statement from SCTE on 3D Audio
|
SCTE
|
Joint meetings
Groups
|
What
|
Where
|
Day
|
Time
|
Audio, Systems
|
3D Audio in MPEG-2 TS
m36466 Carriage of Multiple Streams in a Single PID
|
Systems
|
Tuesday
|
1230-1300
|
Audio, Systems
|
MPEG-H Audio AMD 2
Carriage of MPEG-H Systems data in MPEG-H Audio
|
Audio
|
Tuesday
|
1400-1500
|
Audio, Systems
|
MPEG-H Audio AMD 2
Support 3D Audio in MPEG-4 FF
|
Audio
|
Tuesday
|
1500-1530
|
All
|
Assets
|
3
|
Wed
|
1400-1430
|
All
|
Communications
|
Wisla
|
Thursday
|
1600-1800
|
Plenary Discussions
There were no Audio plenary discussions.
Task group activities
In this report consensus positions of the Audio subgroup are highlighted in yellow. Other text captures the main points of presentations and subsequent discussion.
Joint Meetings With Systems on MPEG-H 3D Audio in MPEG-2 Systems (Tue 1230-1300)
Two input contributions have been discussed:
m36516 Proposed updates to ISO/IEC 13818-1 DAM 5
This document was presented by Harald Fuchs. It points to some editorial errors and further proposes to add the "Command Descriptor" from the TuC output document N15171 from the 111th meeting with some additional modifications. The document also discusses the question of a third stream type that was raised in N15171 and comes to the conclusion that this is not necessary.
It was agreed to incorporate the proposed changes from m36516 into a "Study of ISO/IEC 13818-1:2015 DAM 5 Carriage of MPEG-H 3D Audio over MPEG-2 Systems" as output document from this meeting with an editing peridod of two weeks.
m36466 Carriage of Multiple Streams in a Single PID
This document was presented by Robert Brondijk. It is also pointing to N15171 and the issue of multiple streams inside of one elementary stream and the issue of a third stream type. The proposed solution in this contribution is to add another level of descriptor loop in the PMT after the "command descriptor" if that is present. The proposal was rejected, because it would change a very critical part of MPEG-2 Systems (i.e. the PMT).
With Systems on Carriage of Systems meta-data in 3D Audio (Tue 1400-1500)
Schuyler Quackenbush, ARL, presented
-
m36502
| -
Thoughts on MPEG-H DAM2-Cariage-of-System-Data
| -
Schuyler Quackenbush
|
On slide summarized the presenters view of the technical shortcomings of the Carriage of Systems meta-data specification in DAM2. These were:
-
Identify exemplary use cases such that syntax supports the required bit rates.
-
Write sufficient specification for what is carried.
-
Specify a system decoder model in which SysMetaFrame() can be used. (MMT, DASH and MP2TS)
-
Define a conformance point for SysMetaFrame() data.
-
Support for extensibility.
The Chair presented
-
36357
| -
ATSC Liaison Response to MPEG Audio
| -
ATSC
|
He summarized the issues relevant to this meeting:
-
ATSC acknowledges the importance of having a mechanism for carriage of systems data when a transport mechanism for systems is not available.
-
ATSC notes that ATSC expert group TG3/S33 has specified such deliver mechanisms using video and audio watermarking.
Arianne Hinds, CableLabs, presented
-
36579
| -
Liaison Statement from CableLabs on MPEG-H 3D Audio
| -
CableLabs
|
The concerns raised were:
-
The proposed technologies may be as a security threat to their subscribers.
-
MPEG identify the specific requirements that resulted in the carriage of system metadata in the audio stream.
-
MPEG provide a system decoder model for the decoder architecture.
-
The impact of the metadata box on the overall size of the 3D Audio bitstream is not clear.
-
Carriage of systems metadata in the audio layer violates widely adopted principles of network layering
Yasser Syed, Comcast, presented
-
36642
| -
Liaison Statement from SCTE on 3D Audio
| -
SCTE
|
The concerns raised by SCTE were similar to those raised by CableLabs. The presenter additionally stated that the means for carriage should be such that:
-
It is easy to remove the systems data from the audio bitstream
-
It does not compromise the cable service in any way
Sang Bae Chon, Samsung, presented
-
m36446
| -
Proposed Clarification on System Data Carriage
| -
Sang Bae Chon
|
The contribution is an extensive revision of the DAM 2 text. The presenter reviewed the original problem to be solved, and then indicated how the proposed text provides a minimum-bitrate/byte count solution to the problem that addresses concerns raised by experts.
Sam Narishimham stated that the proposed text from Sang Bae Chon, Samsung, was much better than the original text and addressed all or many of the concerns raised.
Due to limited time in the joint meeting, the Audio Chair announced that there will be continued discussion of this topic in the Audio room Wednesday 1130 – 1300.
Continued Discussion (Wed 1100-1300)
Sang Bae Chon, Samsung, continued his presentation of m36446 with its specific response to the Liaison statements on this topic.
Several experts were concerns that the presentation does not specifically respond to issues raised by ATSC.
Sam Narisimham, Arrisi, raised a concern that the process resulting in the proposed technology did not begin with a review of requirements in the Requirements group.
Sam Narisimham, Arrisi thanks Samsung for the significant change made to the DAM 2 text. However, he still has questions:
-
How does 3D Audio bitstream get to Systems application in TV? Does bitstream travel over HDMI?
-
How does 3D Audio decoder deliver information to Systems application?
Bill Zou, DTS, asked if Samsung experts expect that bitstream is carried over HDMI?
Yeshwant Muthusamy, Samsung, confirmed that TV will have an audio decoder and that bitstream will be carried over HDMI.
Sam Narisimham, Arrisi asked if HDMI can carry compressed audio, video also systems information?
Yeshwant Muthusamy, Samsung, responded that in the use case that uncompressed video and compressed audio (i.e. 3D Audio bitstream), the proposed technology is a solution.
The Chair clarified that carriage of systems metadata is not mandated in the bitstream, but if it is in the bitstream, the decoder shall have a normative behaviour in passing the information to Systems.
Arianne Hinds, CableLabs, stated that she has been advised that it is not so easy to strip such information from a bistream.
Mary-Luc Champel, Samsung, stated that there is an “HDMI pass-through” mode that can pass an audio bitstream.
SangBae Chon, Samsung, noted that user configuration of the TV can permit such an “HDMI pass-through” mode.
Stanley Kyungmo, Samsung, stated that a TV know UTC, recover the system information (as XML), where UTC specifies when some action might be applied.
Open Issues
Arianne Hinds, CableLabs, stated that the proposal need more thorough review, and that this be done in a manner that is not constrained by other, possibly external, schedule issues. Specifically, put this in a document that is not linked to 3D Audio AMD 2.
Jaeyong Song, Samsung, stated that this is very much related to time-sensitive industry needs, for example ATSC.
Continued Discussion in Audio (Thu 1100-1200)
The Audio Chair summarized the technical issues associated with the current text specifying the Carriage of Systems Metadata. Concerning the possibility of achieving mature text at this meeting, he expressed concern that Systems experts have not invested sufficient time in drafting and reviewing the text – the text as it has progressed this week is largely the product of Audio experts crafting Systems-related text. The Audio Chair then summarized possible ways forward.
After further discussion, the Audio Chair concluded that there was consensus in the room to proceed as follows:
-
Re-issue DAM 2 text with additional text that specifies technology adopted at this meeting, but without the section specifying Carriage of Systems Metadata
-
Issue a PDAM 4 that specifies Carriage of Systems Metadata
Dostları ilə paylaş: |