Upgrade the libavif version, supports the AVIF encoding feature #1
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
|
This PR also make the CocoaPods version, support both tvOS and watchOS. The previous version using Static Library, which has no build target for these platforms. |
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.
Seems the libavif upstream version, supports a better AVIF encoding solution. Which fix some serious bugs (the encoded image brand is not
ftpyavif.So maybe it's time to upgrade. The encoding speed, is slow (even compared to bpg format), but however, it's because of the upstream naive implementation, which can be fixed in the future, or with another dav1d codec.
PS: Tthis time I also upgrade the libaom with C implementation code, without the assembly code as well. Make it portable for all Apple platforms, like the Carthage one.