mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-24 07:30:57 +01:00
[PR #14314] [MERGED] Use square root scaling for high framerate videos' bitrate requirements #13752
Labels
No labels
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
EFjellyfin.db
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: starred/jellyfin#13752
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/jellyfin/jellyfin/pull/14314
Author: @gnattu
Created: 6/15/2025
Status: ✅ Merged
Merged: 6/15/2025
Merged by: @crobibero
Base:
master← Head:resolution-square-root-scaling📝 Commits (2)
55bdc12Use square root scaling for high framerate videos' bitrate requirementsa0cde06Add comment📊 Changes
1 file changed (+6 additions, -1 deletions)
View changed files
📝
MediaBrowser.Model/Dlna/ResolutionNormalizer.cs(+6 -1)📄 Description
The previous linear scaling model is inefficient for modern codecs for high frame rate(>30fps) videos. It may force an extremely low resolution like 540p, under poor network conditions(<5Mbps). High frame rates benefit from H264’s temporal inter-frame compression, and human perception of quality diminishes with increasing frame rates. Square root scaling for high framerate videos fits the use case better.
Changes
Issues
Fixes #14238
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.