issues
search
Dash-Industry-Forum
/
Guidelines-TimingModel
DASH-IF implementation guidelines: the DASH timing model
9
stars
1
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Availability during EarilestRemovalPoint
#23
irajs
closed
4 years ago
4
suggestedPresentationDelay
#24
irajs
closed
4 years ago
8
Terminology alignment with MPEG-DASH?
#25
irajs
closed
4 years ago
8
Enable seamless period cutting with simple addressing (SegmentTemplate@duration)
#26
sandersaares
closed
4 years ago
8
Require consistent AdaptationSet/Representation ordering across MPD updates?
#22
ojw28
closed
4 years ago
6
When, if ever, are edit lists okay to use and how to they affect timing calculations?
#27
sandersaares
closed
4 years ago
2
Require clock synchronization
#30
sandersaares
closed
4 years ago
3
Is "32 bit timescales are preferable for installed-base of browsers" still valid?
#29
sandersaares
closed
4 years ago
4
What does " If the MPD@availabilityStartTime is maintained for a portion of the live program that is offered in the static MPD" mean?
#28
sandersaares
closed
4 years ago
2
Clarify expected manifest transformation when a live event ends
#31
ojw28
closed
4 years ago
10
Clarify relationship of leap seconds to durations
#32
sandersaares
closed
4 years ago
14
Previous