Fix/byte track 0 fps with webrtc #743
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
grzegorz-roboflow
force-pushed
the
fix/byte-track-0-fps
branch
from
7ee469a
to
5331f2b
Compare
PawelPeczek-Roboflow
previously approved these changes
Oct 11, 2024
grzegorz-roboflow
requested review from
yeldarby,
probicheaux and
hansent
as code owners
PawelPeczek-Roboflow
approved these changes
Oct 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Currently, when running webrtc pipeline, source fps is unknown. This change is solving this problem twofold:
Type of change
How has this change been tested, please provide a testcase or example of how you tested the change?
Tested e2e manually
Any specific deployment considerations
N/A
Docs
N/A