Jump to content
  • 0

DashMuxing delay is giving more or 404 for segments


Sampath Vatti
 Share

Question

Hi,

I was able to enable CMAF DashMuxing with below params
settings.dashMuxingEnabled=true
settings.dashSegDuration=2
settings.dashFragmentDuration=0.5
settings.dashTargetLatency=3.5
settings.dashWindowSize=5
settings.dashExtraWindowSize=5

With these settings, delay was around 3-5 secs soon after starting a session in /LiveApp/play.html?name=stream1&playOrder=dash player and around 8-12secs latency in JWPlayer and also in ExoPlayer in Android.
But if start playing the same session after 10-15 mins, its throwing 404 error for requested segments and stream is never getting started.

And after experiments with parameters, I have made below changes to parameters : 
settings.dashMuxingEnabled=true
settings.dashSegDuration=2
settings.dashFragmentDuration=0.5
settings.dashTargetLatency=3.5
settings.dashWindowSize=10
settings.dashExtraWindowSize=20
With these params, I was never getting 404 errors for segements whenever I start to play a session. But the lag of the live session has increased a lot to 25-30secs which was not at all acceptable in our product usecase.

 

Please guide us with some optimal configurations to get hasslefree Live with dash format with lesser lag. 

We were expecting 3-5 secs lag to played fine in JWPlayer and Android Exoplayer without any 404 errors n should be able to play a session whenever we start a session.

Thanks alot in advance for the time and efforts you people spare for product.

Awaiting quick help.

Thanks
Sam
Link to comment
Share on other sites

  • Answers 1
  • Created
  • Last Reply

Top Posters For This Question

Popular Days

Top Posters For This Question

1 answer to this question

Recommended Posts

 Share

×
×
  • Create New...