Conversation
zlice
force-pushed
the
ffmpeg9
branch
2 times, most recently
from
September 15, 2026 15:48
e817a9a to
971e344
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
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.
Testing the changes
[skip ci] [ci skip] [no ci]
see previous ffmpeg8 PR #58253
If someone else test, could you verify if mlt7 picks up libavdevice8 ? It didn't install for me but I assume it may have been due to upgrading from ffmpeg8 branch instead of current repos and manually installing some packages.
New package
Local build testing
ffmpeg4
closes #51522
everything else, including vlc, can build with 8 or 9.
ffmpeg8
could probably get rid of 8 altogether with blender 5.2 and opencv5 #62568