6.4Action Points
7LASeR (14496-20) 7.1Topics
7.2Contributions
.
Number
|
Session
|
Title
|
Source
|
Dispositions
|
m24926
|
Scene
|
Content management and protection in LASeR
|
Angelo Difino, Giuseppe VavalÃ
|
Noted
|
7.3Summary of discussions
m24926:
LASeR is used in an Italian project. They want to use IPMP descriptors. There is a proposal for new LASeR requirements which have to be discussed in a joint meeting with Requirements. The document is noted.
7.4Action Points
8MPEG-21 DII (21000-3) 8.1Topics 8.1.1ISO/IEC 21000-3:2003/AMD 2 Digital item semantic relationships
8.2Contributions
Session
|
Number
|
Title
|
Source
|
Dispositions
|
m24236
|
Plenary
|
Summary of Voting on ISO/IEC 21000-3:2003/PDAM 2
|
SC 29 Secretariat
|
Accepted
N12651
|
8.3Summary of discussions
8.4Action Points
9Contract Expression Language (21000-20) 9.1Topics 9.1.1ISO/IEC 21000-20 Contract Expression Language
9.2Contributions
Number
|
Session
|
Title
|
Source
|
Dispositions
|
m24768
|
MPEG-M
|
A Contribution to MPEG-21 CEL
|
Xin Wang,
|
accepted
N12652
|
m24886
|
MPEG-M
|
Proposal for a MPEG-21 CEL Reference Software Plan
|
Jaime Delgado, Eva Rodriguez, Laurent Boch, Francesco Gallo
|
accepted
N12652
|
m24887
|
MPEG-M
|
List of open issues in MPEG-21 CEL DIS
|
Jaime Delgado, Eva Rodriguez, Laurent Boch, Francesco Gallo
|
accepted
N12652
|
|
|
|
|
|
9.3Summary of discussions
9.4Action Points
10Surveillance AF (23000-10) 10.1Topics 10.1.1ISO/IEC 23000-10 2nd edition
10.2Contributions
Session
|
Number
|
Title
|
Source
|
Disposition
|
AF
|
m25194
|
Correction of time references for 23000-10 2nd edition
|
Gero Baese
|
accepted
N12654
|
10.3Summary of discussions
m25194
The current version in the ballot has mistakes in using time reference, which are fixed.
10.4Action Points
11Interactive Music AF (23000-12) 11.1Topics
11.2Contributions
Number
|
Session
|
Title
|
Source
|
Disposition
|
m24773
|
AF
|
Proposed text for WD of Reference Software and Conformance for ISO/IEC 23000-12 IMAF AMD2
|
Yongwei Zhu, Ti Eu Chan
|
accepted
N12657
|
11.3Summary of discussions
m24773
The text to be produced in this meeting has a wrong title. It must me IMAF AMD 3 rather than IMAF AMD 2.
11.4Action Points
124D Media AF (23000-XX) 12.1Topics 12.1.1
12.2Contributions
Number
|
Session
|
Title
|
Source
|
Dispositions
|
m25061
|
AF
|
Proposal of 4D Media Application Format
|
Jiyeon Kim, Jae-Kwan Yun, Hyun-Jin Yoon, Kwang-Roh Park, Kyoungro Yoon
|
Noted
|
|
|
|
|
|
12.3Summary of discussions
m25061
The problem targeted in this proposal is not clear. The group did not accept starting a new activity in AF.
12.4Action Points
13Media presentation description and segment formats (23009-1) 13.1Topics 13.1.1ISO/IEC 23009-1 Media presentation description and segment formats
13.2Contributions
Number
|
Session
|
Title
|
Source
|
Dispositions
|
m24257
|
DASH
|
Proposed Updates for ISO/IEC 23009-1
|
Markus Waltl, Stefan Lederer, Christian Timmerer
|
accepted
N12723
|
m24717
|
DASH
|
Asynchronous Event Handling in DASH
|
Kilroy Hughes, Alex Giladi, Mukta Kar
|
accepted
N12682
|
m24788
|
DASH
|
DASH: URL anchors for MPD
|
Yasuaki Tokumo, Shuichi Watanabe, Takuya Iwanami
|
accepted
N12682
|
m24795
|
DASH
|
DASH: segment availability for low-latency live streaming
|
Yasuaki Tokumo, Shuichi Watanabe, Takuya Iwanami
|
noted
|
m24800
|
DASH
|
DASH: multicast/broadcast extension to DASH
|
Takuya Iwanami, Yasuaki Tokumo, Shuichi Watanabe
|
noted
|
m25126
|
DASH
|
Last segment indication in MPEG-2 TS segments
|
Alex Giladi
|
accepted
N12682
|
m25240
|
|
Event and Message signaling in DASH
|
Kilroy Hughes
|
accepted
N12682
|
m25232
|
|
Server Event Signalling in DASH
|
Thomas Stockhammer
|
accepted
N12682
|
13.3Summary of discussions 13.3.1m24257
This contribution lists several defect items including misuse of URN for MPD, typos and errors in example G. Agreed to be corrected.
13.3.2m24717 Asynchronous Event Handling in DASH
Thank you for bringing this issue back; we discussed it some time ago in DASH but let the conversation lapse. There are a number of concerns here, some minor, some major.
-
the tfdt isn’t a container box, alas;
-
and tying it to fragments means that the granularity of when this can be signaled is toed to the frequency of fragment boundaries;
-
placing this message in a box means it’s tied to encapsulation, not media (i.e. a track) or transport (i.e. HTTP); this brings questions of what happens with caches, fast forward, playing in the time-shift buffer, and so on, as well as what happens on re-fragmentation or de-fragmentation;
-
in un-multiplexed scenarios, is this added to every representation?
-
questions of detail: what is relative time, and what does an un-timed event mean?
We would like to consider the file format issues here, and then pend making a decision until the DASH discussion has happened later in the week. The DASH chair will refresh our memory on older contributions, minutes, etc., so as to enable a fully informed discussion.
13.3.3M25232
Partially accepted with modification. Will go to TUC after modification.
See the notes for 24717.
13.3.4m24788
Partially accepted. Update and to be included in subset.
URI anchors.
As initial point of play.
Thomas check that if subset. No spatial. Use adaptation set for track.
13.3.5m24795
Not accepted. Need further studies.
To improve DASH for low-latency live streaming.
Upload the stream by subsegments and make it partially available. CDN update might be issue.
13.3.6m24800
Not accepted. Can be discussed as part of co-located ad-hoc meeting with 3GPP.
Proposal for switching from multicast/broadcast to unicast.
3GPP also have a related work item.
Suggest a co-located meeting with SA4 to review and harmonize TUC and 3GPP enhanced multimedia.”.
Liaison letter to 3GPP.
Time and location: weekend prior to MPEG 101 meeting, Stockholm.
13.3.7m25126
Accepted for implementation guidelines on how to interpret SCT-35.
1-Last segment indication for M2TS for TUC
2. SCT-35 use and recommended behavior for client in Implementation guidelines
SCTE-35 signaling.
3-Liasion to SCT ask for a code definition for carry msg signal in SCT-35.
13.3.8m25240
This contribution proposes two types of events signaling such as server events and in-band events.
13.4Action Points
14Conformance and Ref. SW. for DASH (23009-2) 14.1Topics 14.1.1ISO/IEC 23009-2 1st edition
14.2Contributions
Number
|
Session
|
Title
|
Source
|
Dispositions
|
m24256
|
DASH
|
Updated ISO/IEC 23009-2 WD
|
Markus Waltl, Christian Timmerer
|
accepted
N12684
|
m24971
|
DASH
|
Media segment conformance for ISO BMFF
|
Thomas Stockhammer, Waqar Zia
|
accepted
N12684
|
m24972
|
DASH
|
Harmonization of MPEG-DASH Test Vectors
|
Thomas Stockhammer, Waqar Zia
|
Noted
|
m24974
|
DASH
|
Proposed updates to WD of 23009-2
|
Thomas Stockhammer, Waqar Zia
|
Accepted
N12684
|
m24979
|
DASH
|
Cross check of test vectors for dependent representations
|
Ed Asbun, Yuriy Reznik
|
Accepted
N12684
|
m25234
|
|
DASH Test Files for ISO Media Live Profile “Big Buck Bunny”
|
Kilroy Hughes, Harry Pyle
|
Accepted
N12684
|
|
|
|
|
|
|
|
|
|
|
Dostları ilə paylaş: |