-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(server, web): Added TranscodePolicy "Bitrate higher than max bitrate or not in accepted format" #6479
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There might be a bug in the bitrate check, but otherwise looks good (only looking at the bitrate changes since the other changes are in #6460)
… was set by admin
…igher than set max bitrate
0ff5a30
to
7710074
Compare
@Hely0n I rebased the PR and it looks good. We can merge it once you add unit tests for the policy. |
Thank you very much. I plan to write them in the next days |
@mertalev I hope this unit test meets your expectations. I just oriented on the resolution policy. |
And here comes my last promise from #6319 :
The Bitratete policy.
This is just an additional transcode policy, which works like the "Transcode if higher than target resolution or not in desired format", but it will only transcode videos where the total bitrate is higher or equal than the bitrate set under "max bitrate".
This will allow admins to set the upload speed of the provider, where the server is running, as max bitrate so only videos that wouldn't be streamable due to their high bitrate will be transcoded regardless of their resolution.
This PR is build on top of my "Accepted Codecs"-PR ( #6460 ) .
With both features, the admin will have much more control about which videos have to be transcoded and thus allow for much better storage efficiency.