initial draft for direct API access for ffmpeg #32
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
initial draft for direct API access for ffmpeg Signed-off-by: Aly, Walid <[email protected]>
walidbarakat
force-pushed
the
ffmpeg_multiviewer_direct_API
branch
from
63c9a9a to
708ca25
Compare
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.
initial draft for direct API access for ffmpeg.
i tried to describe the filter complex command and pointing the function that tries to realize it through direct access API. this just a draft to be reviewed by the team to ensure i'm on the right path when it comes to using the right APIs and ffmpeg programming model. feedback about this is the most wanted, plus some cooperation to suggest direct API call to MTL plugin.