The idea is to loose dependency on the last received segment for calculating the next one i would like to suggest adding an option for live streams that will always use the time server to get the current segment. This will prevent the user from depending on the last segment and will improve the live stream
@yogevNisim, we are re-thinking the way time->segment index conversion is done. Will take your feedback into account. Thanks.
+1
My suggestion is to add some sort of livemode a la youtube live - when you in this mode it will request the segments based on current wall time and remote time server. However as soon as the user seeks to a none live time it will return back to how dash js currnently works (seekTarget and then incremaneting the segments index one by one)
player.setLiveEdgeModeEnabled(boolean) => will activate the mode
player.getLiveEdgeModeEnabled(boolean)
@yogevNisim, we have implemented some improvements in #2652 that affects this issue. There was a "lack of truncation issue" that was causing issues in time/remote time server sync and added extra delay. Could you please check if the problem you are experiencing is mitigated there?
Most helpful comment
+1
My suggestion is to add some sort of livemode a la youtube live - when you in this mode it will request the segments based on current wall time and remote time server. However as soon as the user seeks to a none live time it will return back to how dash js currnently works (seekTarget and then incremaneting the segments index one by one)
player.setLiveEdgeModeEnabled(boolean) => will activate the modeplayer.getLiveEdgeModeEnabled(boolean)