Fix #260: FFmpeg.codecs() returns empty list#261
Merged
bramp merged 1 commit intobramp:masterfrom Oct 9, 2022
Merged
Conversation
Owner
|
Thanks! I think we can just abandon the old format. I'm sure it's years out of date. |
Collaborator
Author
|
Figured it out in the meantime: The change was made at around FFmpeg 1.0. |
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
2 participants
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.
Fix #260: Update the codecs parser to the current output of FFmpeg.
@bramp: Please check using one of your installations. I couldn't find the format used within FFmpeg versions since 2.8.15.
I'm a bit confused as to why this was never noticed in such a long time (but the feature might not be used that much).