Open nosoop opened 2 weeks ago
One way to architecture this might be to monitor the player heartbeat response, then spawn fragment downloader tasks based on .playabilityStatus.liveStreamability.liveStreamabilityRenderer.broadcastId
.
We still need a way to sync the manifest on expiry.
Occasionally manifests for the same broadcast will vary in the fragments offered, both possibly in format and individual sequences (e.g. one may offer VP9, but two fewer fragments than another one solely offering h264).
Fixing this so they're in sync likely requires a rework of the application in that instead of each fragment downloader task fetching their instances of the manifest and discovering new manifests independently, they need to operate on the same one and communicate unavailable results by polling back to the caller.