DASH - Understanding MPD at availabilityStartTime

[Arjen Veenhuizen]

Some more thoughts on this topic:

I checked with a valid Microsoft live stream :



It will read something like:


you can see that the publishtime gets updated meaning the MPD is refreshed
but the availabilityStartTime not. It stays at the time the live steaming
started. Here they do use the mpeg dash profile
“urn:mpeg:dash:profile:isoff-live:2011”. 

Bitmovin seems to use the dash-if one, and according to dash-if:


> In order to make the MPD joining friendly and to remove data that is
> available in the past, any segments that have fallen out of the time shift
> buffer may no longer be announced in the MPD. In this case, the Period
> start may be moved by changing one or both, MPD at availabilityStartTime and
> Period at start. 

And since bitmovin does this
“profiles="urn:mpeg:dash:profile:isoff-live:2011,urn:com:dashif:dash264",
maybe they take a bit of both…?




--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/DASH-Understanding-MPD-availabilityStartTime-tp4675767p4675815.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.