Lazy-load HLS media playlists on adaptation

Have you read the FAQ and checked for duplicate open issues? Yes

What version of Shaka Player are you using? Master

Can you reproduce the issue with our latest release version? Yes

Can you reproduce the issue with the latest code from master? Yes

Are you using the demo app or your own custom app? Demo app

If custom app, can you reproduce the issue using our demo app? Yes

What browser and OS are you using? chrome 74.0.3729.131 on windows 10

For embedded devices (smart TVs, etc.), what model and firmware version are you using? N/A

What are the manifest and license server URIs? I can’t share my media playlist but the two example live HLS of the shaka demo page have the same issue.

What did you do? Play a hls live stream with multiple profile audio and video.

What did you expect to happen? That only the two media playlist audio and video of the profile actually display is download

What actually happened? The media playlist of each video and audio profile is download, 8 media playlist in my case.

[joeyparrish]

Just a quick update: Now that HLS AES-128 is out in v4.2, this is our next priority for HLS.

Our goal is to have the HLS improvement projects cleared by the end of this year, though the work could be completed much sooner. Thanks, everyone, for your patience!

If you’d like to pitch in and help get things done faster, feel free to respond to any issue and ask to have it assigned to you. Contributions are always welcome!

[joeyparrish]

Nobody is working on that right now. The person who began that work is currently on leave. If somebody else wants to resume the work, they may, but there’s currently nobody assigned to it at Google. We only have two engineers (myself included) working on Shaka Player at Google at this moment, and we have other priorities to address, including improving the infrastructure for community contributions. We don’t want to be the bottleneck, and we know that for now, we still are. We apologize!

The good news is that the work we just merged for #2337 will simplify the changes needed to resolve this issue. The bad news is that there are very likely to be merge-conflicts when someone rebases that work in-progress you referenced.

If you have an event on Feb 22, I think it is highly unlikely that we will have the implementation complete and tested and released by then. We haven’t even closed #2337 yet, as we are still testing and verifying that we haven’t broken things like A/V sync edge cases for live HLS.

In the meantime, you could always choose to stream DASH, which has sufficient metadata in the manifest to play efficiently without fetching timestamps or init segments from each stream in advance. We apologize for the inconvenience.