-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Content Steering signaling and live manifest update #30
Labels
Milestone
Comments
4 tasks
TF Call:
It would be good to collect on what should be the desired function and based on this we update spec. |
IOP 2024/10/29
We favour option 2, but want to receive comments if anyone has concerns |
haudiobe
added
accepted-needs-implementation
Accepted and needs implementation
probable-agreement-please-comment
and removed
encourage-discussion
Encourages discussion
accepted-needs-implementation
Accepted and needs implementation
labels
Oct 29, 2024
IOP 2024/12/10
|
haudiobe
added
accepted-needs-implementation
Accepted and needs implementation
and removed
probable-agreement-please-comment
labels
Dec 10, 2024
Updated to version 1.1.2 on google docs. Please check and comment. https://docs.google.com/document/d/1TAjcazrbtRtYtrCjnhjEhiQeACX9RUOM/edit?usp=sharing&ouid=110747704626105171645&rtpof=true&sd=true |
haudiobe
added
implemented-comments-welcome
and removed
accepted-needs-implementation
Accepted and needs implementation
labels
Dec 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For live streams with manifest updates, in case the content steering signaling (
BaseURL
,Location
,ContentSteering
) is provided only in the first manifest but not in the manifest updates, what shall be the client behavior?BaseURL
andLocation
before manifest update for next fragment and manifest requests, and stop the steering manifest updates ?From IOP, section 5.3.3.3:
"In addition, updates in the MPD only extend the timeline. This means that information provided in a previous version of the MPD shall not be invalidated in an updated MPD."
In my understanding players should be conformed to option 2, but to date dash.js seems to be conformed to option 1.
Option 2 would enable setting up a content steering proxy service that manipulates and adds content steering signaling in the MPD and redirect subsequent manifest requests to a different
Location
, avoiding players to refresh the manifest from this proxy service.Regards
Bertrand
The text was updated successfully, but these errors were encountered: