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
I have been doing experiments with an old dash.js implementation 4.X.
I apologize for bringing up a question about an old version with last commits in February 2024 and that a 4->5 migration document in February 2025. However, I thought it was still a question worth asking in case anyone remembers or has more information on the topic.
I notice that in all 4.X tags, there is a factor deadTimeRatio which is applied to the already safe throughput if useDeadTimeLatency=true. I wonder if this calculation was intended to be there since there is already a latency adjustment if useDeadTimeLatency is set.
The deadTimeRatio calculation I am talking about is somewhat related to this issue. The code is still present in the 4.X implementations in the form:
It appears that the 4.X implementations have both the deadTimeRatio factor and the adjusted throughputMeasureTime.
Since the 5.X implementations no longer have the deadTimeRatio factor being applied and I have the adjusted throughputMeasureTime if useDeadTimeLatency=true.
Was there a reason why the 5.X players seem to have dropped the deadTimeRatio calculation and was it perhaps not needed in the 4.X implementations as well, or am I missing something here?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I have been doing experiments with an old dash.js implementation 4.X.
I apologize for bringing up a question about an old version with last commits in February 2024 and that a 4->5 migration document in February 2025. However, I thought it was still a question worth asking in case anyone remembers or has more information on the topic.
I notice that in all 4.X tags, there is a factor
deadTimeRatiowhich is applied to the already safe throughput ifuseDeadTimeLatency=true. I wonder if this calculation was intended to be there since there is already a latency adjustment ifuseDeadTimeLatencyis set.The deadTimeRatio calculation I am talking about is somewhat related to this issue. The code is still present in the 4.X implementations in the form:
@AxelDelmas seems to point out a potential issue with the deadTimeRatio factor. @wilaw seems to suggest
Which I suspect is related to the ThroughputHistory rule (4.X) / ThroughputModel (5.X). Code below taken from 4.X
throughputMeasureTime = useDeadTimeLatency ? downloadTimeInMilliseconds : latencyTimeInMilliseconds + downloadTimeInMillisecondsIt appears that the 4.X implementations have both the deadTimeRatio factor and the adjusted throughputMeasureTime.
Since the 5.X implementations no longer have the deadTimeRatio factor being applied and I have the adjusted throughputMeasureTime if
useDeadTimeLatency=true.Was there a reason why the 5.X players seem to have dropped the deadTimeRatio calculation and was it perhaps not needed in the 4.X implementations as well, or am I missing something here?
Thanks
All reactions