-
Notifications
You must be signed in to change notification settings - Fork 94
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
Prevent h26x from letting through invalid frames after frame loss #121
Comments
It would also be nice if this feature was hidden behind a flag. |
I'm actually unsure at this point whether this works currently already. Further testing should be on what happens when the network drops packets. There is supposed to be this feature that drops all undecodable frames. I would suggest fixing #105 before testing (working on it currently). |
There is a simple version of this in the master, but it is not yet a complete solution (removed the old system which did not work). It can be disabled with a flag. |
I disabled the current system by default because it won't work with non-monotonic timestamps, and it is not yet completed. |
I think at least one designed feature was to drop inter frames until the next intra in case of lost frames, but at the moment, this does not seem to prevent invalid frames from getting through (inter frames refer to previous intra frame and cannot be displayed if a previous frame or an intra frame is missing).
The text was updated successfully, but these errors were encountered: