Skip to content

Use the video height too when picking the resolution - #342

Open
zotabee wants to merge 1 commit into
jellyfin:masterfrom
zotabee:resolution-from-height
Open

zotabee wants to merge 1 commit into
jellyfin:masterfrom
zotabee:resolution-from-height

Conversation

@zotabee

@zotabee zotabee commented Oct 18, 2026 •

Copy link
Copy Markdown
Contributor

The resolution only looks at the video's width. Narrow 1080p videos (4:3 or cropped, like 1288x1080 or 1346x1032) are sent as hd_720p, and so are widescreen SD encodes like 1024x576.

A video now counts as 2160p, 1080p or 720p when its width or its height reaches the threshold (new height minimums 2100, 1000 and 700). The 720p width minimum goes from 950 to 1200, so 1024x576 stays 576p, while a 4:3 720p video (960x720) is still caught by its height.

Tested with master and the changed DLL on the real video sizes of all 18,755 movies and episodes in my library. Only 29 change:

Video size Items master This PR
1288x1080, 1346x1032, 1350x1080 3 movies hd_720p hd_1080p
1024x576, 960x534, 960x546 26 movies and episodes hd_720p sd_576p

On my Jellyfin 12.1 server, the next export re-sent exactly these 29 items, and comparing my Trakt data exports from before and after, exactly these 29 changed on trakt.tv.

Builds with no warnings on its own and merges cleanly with #320, #321, #322, #323 and #329, which change the same file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019NK5BSFsEuuqMcNPPpysee
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant