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
The use case would be to start the dash stream at a specific position.
For example, a dash stream has a duration of 60 minutes, and we want to start the stream at 10 minutes instead of 0 minute.
This avoids having to load the first chunk just to do a player.seekTo() and loading chunks again at the desired position.
Proposed solution
After reading from dash.js repository, they use a #t=600 at the end of the url to notify it should start at 10 minutes.
Alternatives considered
Using player.seekTo()
The text was updated successfully, but these errors were encountered:
This avoids having to load the first chunk just to do a player.seekTo() and loading chunks again at the desired position.
If you seek before calling prepare, the media is immediately loaded from the requested position. Have you tried to call methods in this order?
If you want to support t= URL parameters, you can also easily convert parameter to a seek operation when setting the media item.
I can mark this issue as an enhancement to support this automatically (as it has also been asked for HLS before: google/ExoPlayer#9946). The right implementation may depend on google/ExoPlayer#6373 to be able to specify a start position that does not override the default position.
Use case description
The use case would be to start the dash stream at a specific position.
For example, a dash stream has a duration of 60 minutes, and we want to start the stream at 10 minutes instead of 0 minute.
This avoids having to load the first chunk just to do a
player.seekTo()
and loading chunks again at the desired position.Proposed solution
After reading from dash.js repository, they use a
#t=600
at the end of the url to notify it should start at 10 minutes.Alternatives considered
Using
player.seekTo()
The text was updated successfully, but these errors were encountered: