expose apiPreference in VideoWriter #718
Open
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
|
I am going to make some updates to this PR. I will look at gstreamer pipeline elements that are provided in the default install of gstreamer and remove the need for the h264 encoder. The test I added does require gstreamer. Is this an issue in the AppVeyor configuration? |
|
I think that opencv is not built with gstreamer inside appveyor. It uses |
|
one question , can this pr still be merged? Is there other way to achive this visbility to create VideoWriters to gstreamer? |
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.
This pull request adds VideoWriter_OpenCap that accepts apiPrefrence.
To create a VideoWriter with apiPreference, the function VideoWriterCap has been exposed to accept the apiPreference. A test has been added to videoio_test to test gstreamer caps.