-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Track switching and segments dowload scheduling #1926
Comments
Do you mind if I add this to the agenda for next week’s face to face?
From: Bertrand Berthelot <[email protected]>
Reply-To: "Dash-Industry-Forum/dash.js" <[email protected]>
Date: Thursday, May 11, 2017 at 2:41 AM
To: "Dash-Industry-Forum/dash.js" <[email protected]>
Cc: Subscribed <[email protected]>
Subject: [Dash-Industry-Forum/dash.js] Track switching and segments dowload scheduling (#1926)
Hi,
I have a concern regarding segments download scheduling when switching (audio) track.
When switching tracks, the segments of the new track are not downloaded in the expected order.
To ease understanding, please fin below a figure illustrating the problem:
[ash js-audio-track-switch]<https://urldefense.proofpoint.com/v2/url?u=https-3A__cloud.githubusercontent.com_assets_5312520_25942933_732f8e8a-2D363e-2D11e7-2D81f1-2D4957bb7d454d.jpg&d=DwMCaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=HMIPFyLErj4M8VUwg3x36W02236DJoh_A_hxovpfrCc&m=AkoKXI4lZ3fxGj_2LZIBNisr8Ue7LERMmtCZrCxTi3A&s=mtko1L9kGhJ-PtqBvF8mQjWe8pW0OfWS_XOuDOdFI8U&e=>
As you notice segment S6 will be downloaded before segments S3 of new track.
One consequence could to be to start to play S3 of previous track before downloading S3 of new track (in case of low bandwidth).
One solution to avoid this behavior would consist in removing buffer part after S1, once S1 of new track is appended. But maybe there is a valid reason for keeping buffer parts that should be overwritten?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Dash-2DIndustry-2DForum_dash.js_issues_1926&d=DwMCaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=HMIPFyLErj4M8VUwg3x36W02236DJoh_A_hxovpfrCc&m=AkoKXI4lZ3fxGj_2LZIBNisr8Ue7LERMmtCZrCxTi3A&s=1eHf4K5xHW9zOlCP21gHfcKMAL4FgzPOlHsFhwC39xE&e=>, or mute the thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AHgAjq3Ar5RcJV-5FBjj6stWgw0V8ivszXks5r4tfigaJpZM4NXwOc&d=DwMCaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=HMIPFyLErj4M8VUwg3x36W02236DJoh_A_hxovpfrCc&m=AkoKXI4lZ3fxGj_2LZIBNisr8Ue7LERMmtCZrCxTi3A&s=3Nk6IiKRHUEaI6Tvo14RQE6SE2pgPJunhO5PqkS5IbI&e=>.
|
Hi, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I have a concern regarding segments download scheduling when switching (audio) track.
When switching tracks, the segments of the new track are not downloaded in the expected order.
To ease understanding, please fin below a figure illustrating the problem:
As you notice segment S6 will be downloaded before segments S3 of new track.
One consequence could to be to start to play S3 of previous track before downloading S3 of new track (in case of low bandwidth).
One solution to avoid this behavior would consist in removing buffer part after S1, once S1 of new track is appended. But maybe there is a valid reason for keeping buffer parts that should be overwritten?
The text was updated successfully, but these errors were encountered: