Feat: Add Option for Bitrate Mapping Where Nearest Value is Always Matched #283
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
|
Looks good but I don't see how you enable the option? |
birme
dismissed
their stale review
Looks good but I don't see how you enable the option?
|
Yes, that part is comming |
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.
PR, with a bump in hls-vodtolive to version 3.1.1 - now enables a new engineOption:
alwaysMapBandwidthByNearest: Will enable HLSVod to always map video profiles from prev and current vod by whichever is nearest. Without this option, HLSVod will map by index of there are the same amount of video profiles in prev and current vod.PR also fixes a fatal infinite loop bug.