Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Live streaming: check if manifest has been updated #116

Open
pavloivanchyshyn opened this issue Jan 24, 2018 · 6 comments
Open

Live streaming: check if manifest has been updated #116

pavloivanchyshyn opened this issue Jan 24, 2018 · 6 comments

Comments

@pavloivanchyshyn
Copy link

AFAIK, for the Live streaming, it's required to reload manifest at least after 'target_duration' for the first time and if the manifest has not changed then it must wait for a period of one-half the target duration before retrying.

So, it would be great to have an ability to check if the manifest has been already updated (e.g. using previous content).
As another possible version, it might have any sense to add a function which returns the latest line(s) from the manifest to make it possible to compare the latest line from previous manifest and current.

@leandromoreira
Copy link
Contributor

leandromoreira commented Jan 25, 2018

I think this logic might be something to the application using the m3u8 library, for instance, we built a monitoring tool for our live streams and there resides this logic.

@pavloivanchyshyn
Copy link
Author

Exactly. But this logic is common. Everyone should monitor their live streams and reload them if manifest was not changed.
I guess it makes sense to add this logic to the m3u8 library to make it reusable for each user of m3u8 instead of implementing the same thing by everyone.

@leandromoreira
Copy link
Contributor

Cool, so let's this open then.

@flavioribeiro
Copy link
Contributor

flavioribeiro commented Jan 25, 2018

not a commiter on this one but will give my two cents. m3u8 was made to be a simple stateless module for HLS manifests so I wonder if maintaining update cycles or states within the module would go in the opposite direction of the module's idea.

I'd rather create another component that uses m3u8 and keep states and update cycles for live as another open source module so everyone can use it the same way they use this one.

@mradecki
Copy link

mradecki commented Mar 6, 2021

@flavioribeiro Any update on that?

@flavioribeiro
Copy link
Contributor

Hey, @mradecki! my update is that I still have the same thinking about it. I haven't really signed up for any work on this, but I can see some use cases in the wild doing down to what was proposed above!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants