question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Latency in the live media as compare to Shaka Player

See original GitHub issue

Hi,

I am checking a live content and can clearly see that in Shaka Player demo app, player is around 5 seconds before the live edge but in ExoPlayer it is around 30 seconds. There is no suggestedPresentationDelay in the media.

And if i configure the LowLatency with target offset then it goes closer to the live edge. Question is why the player does not try to go as much as possible to the live edge like Shaka Player.

ExoPlayer version: 2.17.1

I have sent the media over the email. Can you please help me to understand it ?

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
toniheicommented, Jul 6, 2022

Thanks for the manifest. As you already pointed out yourself, it doesn’t have the suggestedPresentationDelay value defined and thus ExoPlayer falls back to a default value of 30 seconds. ExoPlayer has to choose some value and because many live streams can’t support low latency values, 30 seconds is a sensible default that should work for most streams.

That leaves you with multiple ways to fix it:

  1. Update the manifest to include a suggestedPresentationDelay or a ServiceDescription with a Latency target value.
  2. Define which fallback ExoPlayer should use if both values are missing by setting DashMediaSource.Factory.setFallbackTargetLiveOffsetMs
  3. Override the target live offset (even if defined by the manifest) by setting MediaItem.LiveConfiguration.Buiider.setTargetOffsetMs for specific MediaItem instances, or use DefaultMediaSourceFactory.setLiveTargetOffsetMs to set an override for all MediaItems.
0reactions
GouravSnacommented, Jul 6, 2022

Thanks a lot @tonihei

Read more comments on GitHub >

github_iconTop Results From Across the Web

Performance of Low-Latency HTTP-based Streaming Players
This paper is dedicated to the analysis of the performance of low-latency players and streaming protocols. The evaluation is based on a series ......
Read more >
Tutorial: Network and Buffering Configuration - JSDoc
Shaka Player has separate network retry settings for each of the different types of requests: manifest, license, and segment requests.
Read more >
Performance of Low-Latency HTTP-based Streaming Players
HTTP Adaptive Streaming, HLS, DASH, Low-Latency live To better evaluate HAS systems, ... Our framework guarantees a fair comparison of different players by ......
Read more >
Part 3: How to compete with broadcast latency using current ...
Initial positioning of the player in the live timeline, compared to the ... This open source HLS player for MSE (Media Source Extensions) ......
Read more >
ACHIEVING BROADCAST-GRADE LOW LATENCY IN LIVE ...
The difference between those two numbers is your total latency. See Figure 2 for a flowchart showing such a test using AWS Elemental...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found