-
Notifications
You must be signed in to change notification settings - Fork 506
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
Re-read old manifest after crash #89
Comments
It is complicated to maintain states across packager restarts. Even if it is supported, there will still be some gaps, which might not be desirable. |
Yes, there will be some gaps, but this will be a player's decision how to deals with them. |
Hi KQ, BRS/ |
I have some thoughts on maintaining states across packager restarts. It is a complicated issue and difficult to handle it properly. I am also interested in the packager asserts and DTS defects you mentioned. If there is some problem in the content, even if we restart the packager with states carried over, we may run into the same problems again. You have probably mentioned it before, can you list all the stream defects you have seen? We can go through these defects to see if there is another way out of it. |
Hi,
|
Ok, the decoding timestamp was moved back by about 8.88 seconds... Any idea how often does it occur? |
KQ,
In case with DVB-S, the second case is frequent because environment reasons. |
I see. Am I correctly to say that for both case 1 and case 2, the timestamp difference should be small, a couple of seconds or even less? If that is the case, we might just ignore these frames until the timestamp catches up. For example,
We can drop frames 5 and 6. Do you think it will work? |
KQ,
|
The timestamp difference in the last one is significant... I'll prepare a testing code for you later. |
I've reopened #50. Let's track this problem there. |
Hi, |
As mentioned in #50, the solution we are going to implement is to start a new segment when seeing timestamp rolling back. Unfortunately, we don't have resource to work on this yet. We may look into it late this year. |
Hi KQ,
Because this crashes exoplayer and not so much shaka-player:) |
Yes. May consider putting them in two different periods instead of the same period - which will be more complicated. |
Hello,
on edash-packager restart, it starts to write new manifest file. Then the old video/audio segments are
not reachable. Is there a way after restart to re-read the old manifest and then continue to work without
lose old data? Or is too complicated?
The text was updated successfully, but these errors were encountered: