Fix grab-compute-capping-fps latency regression in zedsrc#97
Open
Fix grab-compute-capping-fps latency regression in zedsrc#97
Conversation
When grab-compute-capping-fps was set lower than camera-fps, the element still advertised the camera framerate in caps and latency queries. This caused downstream elements (queues, muxers, sinks) to schedule based on the wrong rate, adding ~140 ms of unnecessary latency — making capped mode no better than simply lowering camera-fps. Now the effective output framerate accounts for the capping parameter in caps negotiation, latency queries, and buffer duration.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When grab-compute-capping-fps was set lower than camera-fps, the element still advertised the camera framerate in caps and latency queries. This caused downstream elements (queues, muxers, sinks) to schedule based on the wrong rate, adding ~140 ms of unnecessary latency — making capped mode no better than simply lowering camera-fps.
Now the effective output framerate accounts for the capping parameter in caps negotiation, latency queries, and buffer duration.