Always create FFmpeg Vulkan hw context #1349
Merged
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
m00nwtchr
force-pushed
the
master
branch
2 times, most recently
from
c4b17c0
to
e79f017
Compare
nowrep
force-pushed
the
ffmpeg-vulkanctx
branch
2 times, most recently
from
fc65c88
to
7427e0b
Compare
nowrep
force-pushed
the
ffmpeg-vulkanctx
branch
from
7427e0b
to
95621fb
Compare
Vixea
approved these changes
Jan 11, 2023
zarik5
pushed a commit
that referenced
this pull request
Feb 9, 2023
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.
Vulkan ffmpeg context is not currently needed for AMD GPUs, but it will eventually be required for Vulkan encoder.
This simplifies shared ffmpeg code and moves DRM hw context creation to VAAPI encoder.