[ValidiyExpiration] Update the manifest when the InbandEventStream value attribute is three #51
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sebastianpiq
changed the title
cotid-qualabs
merged commit 1c2470e
into
feature/mpd-update-on-validity-expiration
1 check failed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The schemeIdUri
urn:mpeg:dash:event:2012is used to identify anInbandEventStreamwith an attribute value of 1 (MPD validity expiration), 2 (MPD Patch), or 3 (MPD Update).MPD validity expiration events provide the ability to signal to the client that the MPD with a specific publish time can only be used up to a certain media presentation time. In the case of MPD Update events, a complete MPD shall be included in the in the DASHEvent structure, immediately following the publish_time field. The content of the mpd field shall be the MPD.