Repository navigation
Fix NVOF session recreation on frame-size changes - #39
Merged
Merged
Conversation
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
2 participants
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 CUDA frames change resolution, the camera-motion node tried to call
nvOFInitagain on an initialized handle and failed withNV_OF_STATUS=4. Recreate the NVOF session and its buffers, then seed a fresh reference frame. The existing session is reused for steady dimensions; only the node's stream is drained on replacement.Validation: rebuilt the CUDA/TensorRT Python module and ran
tests/cuda/smoke_camera_motion_resize.pyon a Tesla T4. All three transitions (720p → 1080p → 720p → 1080p) passed, withhas_prevreset and valid affine estimates on subsequent frames. The same test fails on the previous binary. The test uses eight finite frames and drains EOF before shutdown.