Draft
Conversation
CheesecakeCG
force-pushed
the
nvfbc-support
branch
from
886e193 to
6c58fc2
Compare
CheesecakeCG
force-pushed
the
nvfbc-support
branch
4 times, most recently
from
d0c1778 to
2c7bfd3
Compare
CheesecakeCG
force-pushed
the
nvfbc-support
branch
from
2c7bfd3 to
3365e0f
Compare
CheesecakeCG
force-pushed
the
nvfbc-support
branch
from
3365e0f to
d4c26ef
Compare
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.
Depends on galister/wlx-capture#4
The NvFBC wrapper package doesn't seem to support capturing from other monitors besides the first one, but I think I must be doing something wrong. This PR doesn't properly check which monitor the image is for, and I haven't tested it with multiple monitors plugged in to know what happens when if you try.