You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please provide clear steps to reproduce your problem
Load live stream manifest that contains ContentSteering signalisation with different Location for manifest requests and BaseURL for segment requests, but which signalisation is not provided in the manifest updates (that are fetched from the Location contained in the 1st manifest).
If the bug is intermittent, give a rough frequency if possible
Observed behavior
Describe what the player is doing that is unexpected or undesired behaviour.
On the 1st manifest update, since there is no more Location, BaseURL and ContentSteering signalisation, the player reset all Location and BaseURL and stops the content steering controller.
Console output
Paste the contents of the browser console here.
You may need to enable debug logging in dash.js by calling player.updateSettings({ 'debug': { 'logLevel': dashjs.Debug.LOG_LEVEL_DEBUG }}) if you are using your own page.
Expected behavior
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."
Therefore the expected behavior would be to maintain and not invalidate Location, BaseURL and ContentSteering signalisation received from 1st manifest.
Environment
Steps to reproduce
Please provide clear steps to reproduce your problem
Load live stream manifest that contains
ContentSteering
signalisation with differentLocation
for manifest requests andBaseURL
for segment requests, but which signalisation is not provided in the manifest updates (that are fetched from theLocation
contained in the 1st manifest).If the bug is intermittent, give a rough frequency if possible
Observed behavior
Describe what the player is doing that is unexpected or undesired behaviour.
On the 1st manifest update, since there is no more
Location
,BaseURL
andContentSteering
signalisation, the player reset allLocation
andBaseURL
and stops the content steering controller.Console output
Expected behavior
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."
Therefore the expected behavior would be to maintain and not invalidate
Location
,BaseURL
andContentSteering
signalisation received from 1st manifest.An issue has be opened to get feedback and decide about the expected behavior: Dash-Industry-Forum/Content-Steering#30
The text was updated successfully, but these errors were encountered: