Skip to content

Compensate for Chromium MPEG inaccuracy.#627

Merged
subdavis merged 5 commits into
mainfrom
client/fix-610
Mar 10, 2021
Merged

Compensate for Chromium MPEG inaccuracy.#627
subdavis merged 5 commits into
mainfrom
client/fix-610

Conversation

@subdavis
Copy link
Copy Markdown
Contributor

@subdavis subdavis commented Mar 9, 2021

This problem was exactly what I expected: falling on the wrong side of the frame boundary due to small variations in real frame size and maybe floating point errors.

Also force video playback pause events to snap to nearest frame boundary so that detections created on video that was paused cannot happen in the middle of a frame's width.

fixes #610

@subdavis subdavis requested a review from BryonLewis March 9, 2021 18:20
BryonLewis
BryonLewis previously approved these changes Mar 9, 2021
Copy link
Copy Markdown
Collaborator

@BryonLewis BryonLewis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry it took me so long to conceptualize what was going on.

@subdavis
Copy link
Copy Markdown
Contributor Author

Updated to reflect the true cause of this bug: Chrome!

See detailed inline comment about how and why this fix is correct.

@subdavis subdavis changed the title Compensate for floating point errors on frame sync Compensate for Chromium MPEG inaccuracy. Mar 10, 2021
@BryonLewis BryonLewis self-requested a review March 10, 2021 12:19
@subdavis subdavis merged commit 1abd58c into main Mar 10, 2021
@subdavis subdavis deleted the client/fix-610 branch March 10, 2021 13:02
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

Successfully merging this pull request may close these issues.

[BUG] Off-By-One video sync issue

2 participants