patch libnvcuvid.so instead of libnvidia-encode.so #1
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
1 task
jailuthra
pushed a commit
that referenced
this pull request
Sep 14, 2023
537.34 (released on 2023.9.12)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Deeper analysis of libnvidia-encode internals revealed invokation of libnvcuvid functions for purpose of checking number of running encoders.
Current patch circumvents result check of this function inside nvEncOpenEncodeSessionEx function body. Probably, most proper way is to patch function which does immediate check of running encoders, and this patch supposed to do this. This patch works as well as one which patched
libnvidia-encode.so, but "fixes" decision in right place.