Add option to disallow some codecs for exoplayer #1403
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
This comment was marked as off-topic.
This comment was marked as off-topic.
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.
Some devices can't play some codecs using exoplayer for a variety of reasons, such as poor performance, bad hardware, or even buggy software. This change allows users to specify some codecs that their device has issues with. Jellyfin will try to transcode media to something else.
First time trying to contribute so please let me know if there are things I can improve.
Changes
Added an option to the Client Settings page for the exoplayer to list codecs to try not to play.
Issues
Allows users to work around some issues by specifying the problematic codec such as
#1359 #1342 #1389 #1264 #1220 #1174