chore(server): explicitly use svt-av1 encoder #13389
Open
+5
−1
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
|
The FFmpeg build we use actually doesn't have libaom, so |
mertalev
approved these changes
Oct 12, 2024
mertalev
changed the title
danieldietzler
approved these changes
Oct 12, 2024
|
Running |
|
@mertalev do we need to add the svt-av1 package to the base image, or is it included by default with the jellyfin-ffmpeg package ? |
It comes with jellyfin-ffmpeg, so no change is needed. |
Nice |
martabal
approved these changes
Oct 12, 2024
STV-AV1 is much, much faster than the reference libaom encoder. In most real-world cases libaom is too slow to be practical, often struggling to achieve 0.1fps for 1080p content. I suspect this is what was intended in f1ca179 when AV1 support was originally added as it sets the `-svtav1-params` flag which is ignored unless using the STV-AV1 encoder. Furthermore there is lots of discussion about STV-AV1 in the PR thread.
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.
SVT-AV1 is much, much faster than the reference libaom encoder. In most real-world cases libaom is too slow to be practical, often struggling to achieve 0.1fps for 1080p content.
I suspect this is what was intended in f1ca179 when AV1 support was originally added as it sets the
-svtav1-paramsflag which is ignored unless using the SVT-AV1 encoder. Furthermore there is lots of discussion about SVT-AV1 in the PR thread.