Add configurable maximum transcode sizes #178
Merged
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
|
Tested for transcode and livestream sizes , everything seems ok. |
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.
Adds options to the configuration page to allow setting a maximum size for generated transcoded files, and for streaming transcoded files.
Default value is "Original" which uses the existing resolution of the source video. Other values are "240p", "480p", "720p", "1080p", "4K". The transcoding code uses this as the maximum size to down-scale to. If a scene has a lower resolution than the max, then that resolution is used. This scaling is applied to the height for normal landscape videos, and applied to the width for portrait videos.
Should help address the performance issues identified in #31. Related to #10.